Question 770
At Transit Operations Center, an AOS-CX template pushes the same management gateway to two differently addressed branches. Which diagnostic comparison would distinguish this fault from nearby mechanisms?
Explanation
Correct Answer
For Transit Operations Center, the decisive mechanism is Switch template variables. Template-based provisioning must resolve per-device parameters before switch configuration. Compare effective rendered variables and template configuration with branch inventory data is the most direct way to isolate this particular failure before making a change.
Incorrect Answers
This is relevant to AP uplink physical mapping, where aP service onboarding depends on both physical power and the upstream management network In the Transit Operations Center case, Those observations could be normal while the stated fault persists. The specific mechanism is template-based provisioning must resolve per-device parameters before switch configuration
This is relevant to LACP uplink provisioning, where lACP forms one logical bundle only when peers agree on aggregation parameters In the Transit Operations Center case, Those observations could be normal while the stated fault persists. The specific mechanism is template-based provisioning must resolve per-device parameters before switch configuration
This is relevant to Bridge versus tunneled WLAN traffic, where bridge SSIDs forward locally; tunneled SSIDs use the gateway data path for policy In the Transit Operations Center case, Those observations could be normal while the stated fault persists. The specific mechanism is template-based provisioning must resolve per-device parameters before switch configuration