The Cisco Nexus 1000v Series switches can configure traditional SPAN sessions. Which three statements about the local SPAN source ports are true? (Choose three)

Cisco Nexus 1000v Series switches support configuring Ethernet, virtual Ethernet (vEthernet), and port-channel interfaces as local SPAN source ports to monitor traffic traversing these different port types.

Local SPAN sessions on the Nexus 1000v allow for granular control over monitoring traffic, enabling configuration to specifically capture ingress (Rx), egress (Tx), or both directions of traffic on the source port.

SPAN source ports do not inherently need to be in the same VLAN; SPAN captures traffic from the specified source port regardless of its VLAN membership and directs it to the destination port.

A key characteristic of local SPAN is that both the source and destination ports must be located on the same Virtual Ethernet Module (VEM) within the Cisco Nexus 1000v architecture; traffic cannot be SPANned across different VEMs in a local session.

While a port profile itself is a configuration template, the actual virtual Ethernet ports instantiated from a port profile can indeed be configured as SPAN sources.

VSANs (Virtual Storage Area Networks) are irrelevant for standard Ethernet or virtual Ethernet SPAN, as they are used for Fibre Channel or FCoE traffic segmentation.