Question 250
A data center implementation team investigates the following fault: Two Nexus switches form a vPC pair, but a VLAN needed by a downstream dual-homed host is missing from the peer-link allowed list. Which test outcome proves the intended service was restored?
Explanation
Correct Answer
This observation validates vpc peer link consistency: The vPC peer-link VLAN membership is inconsistent with downstream vPC service VLAN requirements. The corresponding corrective action is: Add the authorized VLAN to the peer-link trunk and resolve the corresponding vPC consistency alarms. Evidence about a different component does not establish the requested service outcome.
Incorrect Answers
The SPAN session source and dedicated monitor destination roles were assigned incorrectly. “Configure the authorized SPAN source and monitor-only destination and confirm the capture appliance connection” would address that alternative cause, not the condition in this question: the vPC peer-link VLAN membership is inconsistent with downstream vPC service VLAN requirements.
“Configure a matching supported LACP mode and port-channel membership across the two endpoints” responds to this separate finding: the port-channel peers use incompatible LACP negotiation settings and cannot aggregate all intended members. This question instead needs “Add the authorized VLAN to the peer-link trunk and resolve the corresponding vPC consistency alarms”, so the alternative does not meet the stated condition.
Bridge priority design does not select the intended distribution switches as the RSTP root and secondary root. “Set approved spanning-tree bridge priorities and validate the intended root and blocked-port topology” applies to that separate problem. The observed case is two Nexus switches form a vPC pair, but a VLAN needed by a downstream dual-homed host is missing from the peer-link allowed list; choosing this alternative would address the wrong failure mode.