Question 320
A data center administrator identifies the following risk: A newly cabled Cisco ACI leaf appears physically connected to a spine but never becomes an accepted fabric node under APIC management. Which design or configuration error caused the described issue?
Explanation
Correct Answer
The technical cause is The leaf has not completed the supported ACI fabric discovery and node-registration workflow. The appropriate response is: Verify fabric ports, discovery connectivity and the intended node identity, then register the new leaf in APIC. Confirm successful repair: APIC shows the assigned leaf as an active fabric member with the expected spine adjacency.
Incorrect Answers
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” would address that alternative cause, not the condition in this question: the leaf has not completed the supported ACI fabric discovery and node-registration workflow.
“Correct the supported ACI interface policy selector and physical domain association for the host-facing port” responds to this separate finding: the interface selector and policy-group to physical-domain binding do not deliver the intended EPG attachment. This question instead needs “Verify fabric ports, discovery connectivity and the intended node identity, then register the new leaf in APIC”, so the alternative does not meet the stated condition.
The ACI VMM domain connection does not synchronize the intended endpoint group to its virtual switch port groups. “Repair the approved ACI VMM integration and EPG domain association, then validate policy deployment” applies to that separate problem. The observed case is a newly cabled Cisco ACI leaf appears physically connected to a spine but never becomes an accepted fabric node under APIC management; choosing this alternative would address the wrong failure mode.