Question 280
Two replacement switches appear in the automation inventory and an operator assumes their descriptive hostnames alone uniquely match the blueprint nodes. Once the issue is resolved, which ongoing practice BEST prevents this type of failure?
Explanation
Correct Answer
A lasting control should detect the original error before release. Require hardware identity and inventory reconciliation before accepting newly discovered or replaced devices. That is important in this case because a managed fabric device must be associated with the correct physical identity and model so the controller generates and deploys the intended configuration. The scenario was: Two replacement switches appear in the automation inventory and an operator assumes their descriptive hostnames alone uniquely match the blueprint nodes.
Incorrect Answers
Apstra management events and revision metadata provide operational evidence of blueprint actions that the current switch state alone cannot reconstruct. Here, a managed fabric device must be associated with the correct physical identity and model so the controller generates and deploys the intended configuration.
Review Apstra role assignments whenever on-call responsibilities or staff membership change. That concerns apstra role-based access control for operators, while the issue here is managed device discovery and system identity. Validate the discovered device details, unique system identifier and blueprint node assignment before staging configuration to the replacement.
Previously collected telemetry may remain displayed after management collection stops and must not be mistaken for a live measurement. However, the present prevention decision is grounded in: Two replacement switches appear in the automation inventory and an operator assumes their descriptive hostnames alone uniquely match the blueprint nodes. For this issue, validate the discovered device details, unique system identifier and blueprint node assignment before staging configuration to the replacement.