Question 160
A failed managed switch is swapped physically yet Apstra refuses deployment to the replacement inventory device. Which design or operational principle best explains this behavior?
Explanation
Correct Answer
device replacement requires reconciling the blueprint's intended logical device with the actual managed system identity. Here, a failed managed switch is swapped physically yet Apstra refuses deployment to the replacement inventory device. A useful discriminating check is to review device replacement workflow, old/new system identifiers and required port/profile compatibility.
Incorrect Answers
“Apstra fabric onboarding needs a compatible managed agent and correctly established system identity, not only IP connectivity” is relevant to a different condition: A switch is reachable over SSH but Apstra cannot assign it to a blueprint because the device agent is not installed correctly. The stated question instead concerns: A failed managed switch is swapped physically yet Apstra refuses deployment to the replacement inventory device. Device replacement requires reconciling the blueprint's intended logical device with the actual managed system identity. The controlling principle is “Device replacement requires reconciling the blueprint's intended logical device with the actual managed system identity”.
That choice—“Unique accurate managed device identities are required for safe inventory and blueprint allocation”—addresses this other problem: A deployment team duplicates a device-system ID when registering two new leaf switches. Here the scenario is: A failed managed switch is swapped physically yet Apstra refuses deployment to the replacement inventory device. Device replacement requires reconciling the blueprint's intended logical device with the actual managed system identity. The controlling principle is “Device replacement requires reconciling the blueprint's intended logical device with the actual managed system identity”.
“Controlled build and deploy phases separate design validation, reviewed staged changes and active device updates” is associated with a distinct issue: An Apstra operator wants to distinguish blueprint validation from the actual deployment to managed switches. By contrast, the actual problem is: A failed managed switch is swapped physically yet Apstra refuses deployment to the replacement inventory device. Device replacement requires reconciling the blueprint's intended logical device with the actual managed system identity. The controlling principle is “Device replacement requires reconciling the blueprint's intended logical device with the actual managed system identity”.