It's more a theoretical question, trying to come to grips with VLAN. In essence, the dumb switch merely inherits whatever the assigned VLAN is, if any.
For argument sake, at the dumb switch, it's ok that 4 of the ports are assigned to VLAN200 but the 5th port is a Wireless Access Point. That AP is on the VLAN200, when it is preferred to be separated away, not be included in VLAN200.
I assume this is an autonomous AP.
1. If the managed switchport towards the dumb switch is set to access vlan 200, then all ports on the dumb switch will be vlan 200. Which means your AP will be on VLAN200 and all your wifi clients would be on vlan 200 (you knew this).
2. If the managed switchport towards the dumb switch is set to trunk, then all ports on the dumb switch will be trunks. Which means your AP will be on a trunk. This would allow you to break up your wifi clients to different vlans. For example, one SSID could be mapped to vlan 200, another to vlan 300, another to vlan 400. This is good for a guess wifi or kids wifi.
If you want to do option 2, then on your managed switch, you should set your trunk with a native vlan 200. This allows you to still trunk to the AP, but anything in vlan 200 will be untagged. This means your endpoints (e.g. cameras) won't need to to support tagging. They would think they are on vlan 200.
If you have a controller based AP, then you could tunnel everything back to the controller and drop off vlans at the controller.
Personally, I have three SSIDs at home (guest, IoT, internal) on the same AP.