Yes, a SPAN destination port can be configured as trunks or access ports. Keep in mind that by using one or the other, there will be no difference in what is outputted.
Having said that, however, if your source port is a trunk, frames on that trunk will be tagged with the appropriate VLAN ID. Frames that will be outputted from the SPAN destination port will NOT have these tags UNLESS it is configured as a trunk port AND the encapsulation dot1q is enabled.
For example, if you create a SPAN
monitor session 1, and you view this session with the commands below, you can see the encapsulation on the destination port is set to
Switch#show monitor session 1 Session 1 --------- Type : Local Session Source Ports : Both : Fa0/24 Destination Ports : Fa0/1 Encapsulation : Native Ingress : Disabled Switch#
If the destination port Fa0/1 is configured to be a trunk AND is configured with dot1q encapsulation, then the tags will be included.
I hope this has been helpful!