300-170 · Question #164
Refer to the exhibit. Which two results occur to the traffic that uses a port associated to the ccnp- dc port profile? (Choose two.)
The correct answer is B. Untagged traffic is placed in VLAN 10. D. Traffic tagged in VLAN 51 is placed in bridge-51. This question assesses the understanding of how traffic is handled on an interface configured with a port profile, specifically regarding untagged traffic and tagged VLAN-to-bridge-domain mappings.
Question
Refer to the exhibit. Which two results occur to the traffic that uses a port associated to the ccnp- dc port profile? (Choose two.)
Exhibit
Options
- AAll the traffic is placed in VLAN 100.
- BUntagged traffic is placed in VLAN 10.
- CThe traffic in VLAN 53 is mapped to VXLAN 5051.
- DTraffic tagged in VLAN 51 is placed in bridge-51.
- EThe traffic in VLAN 52 is placed in VLAN 10.
How the community answered
(48 responses)- A4% (2)
- B73% (35)
- C15% (7)
- E8% (4)
Why each option
This question assesses the understanding of how traffic is handled on an interface configured with a port profile, specifically regarding untagged traffic and tagged VLAN-to-bridge-domain mappings.
Placing all traffic into a single VLAN, regardless of tagging, contradicts the purpose of VLANs and is not how a port profile typically handles diverse traffic.
In a port profile, untagged ingress traffic is assigned to the native VLAN. If VLAN 10 is the configured native VLAN for the ccnp-dc port profile, all untagged frames received on ports associated with this profile will be placed into VLAN 10.
While VLANs can be mapped to VXLANs, the statement that VLAN 53 traffic is mapped to VXLAN 5051 is a specific configuration that is not supported by the selection of B and D as correct answers, implying the profile has different mappings.
Port profiles can define specific mappings for tagged VLAN traffic to internal bridge domains, particularly in VXLAN-enabled environments. If the profile includes a configuration to map VLAN 51 to bridge-51, then any frame arriving tagged with VLAN ID 51 will be processed within that specific bridge domain.
Traffic tagged in VLAN 52 would normally remain in VLAN 52 unless explicitly re-written or mapped to a different VLAN, which is not suggested as a default or implicit behavior alongside the given correct answers.
Concept tested: Port profile VLAN and bridge-domain mapping
Source: https://www.cisco.com/c/en/us/td/docs/dcn/nx-os/nexus9000/102x/configuration/interfaces/cisco-nexus-9000-series-nx-os-interfaces-configuration-guide-102x/m-interface-port-profiles.html
Topics
Community Discussion
No community discussion yet for this question.
