Question 540
A replacement leaf has a new serial number, but the blueprint still associates the old unavailable hardware with its logical role. Which initial check would most directly distinguish the likely cause?
Explanation
Correct Answer
This checks the relevant evidence first: review device replacement workflow, old/new system identifiers and required port/profile compatibility. The underlying concept is that device replacement requires reconciling the blueprint's intended logical device with the actual managed system identity. After confirming the finding, a controlled remediation is to assign the replacement supported system to the correct logical role using the documented controlled process.
Incorrect Answers
The option “Compare hardware identifiers, managed system IDs and blueprint allocation entries for the affected devices” is useful in a different setting: Two appliances appear as one managed system after inventory import because their identifiers were copied from a template. The case being tested is: A replacement leaf has a new serial number, but the blueprint still associates the old unavailable hardware with its logical role. The relevant inspection is: Review device replacement workflow, old/new system identifiers and required port/profile compatibility. The most discriminating first check is “Review device replacement workflow, old/new system identifiers and required port/profile compatibility”.
“Inspect the device-agent state, management authentication and discovered system ID before allocation” 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 replacement leaf has a new serial number, but the blueprint still associates the old unavailable hardware with its logical role. The relevant inspection is: Review device replacement workflow, old/new system identifiers and required port/profile compatibility. The most discriminating first check is “Review device replacement workflow, old/new system identifiers and required port/profile compatibility”.
“Compare LLDP-discovered endpoints and physical interface identifiers against the generated cable map” is associated with a distinct issue: A live rack cable is connected to the wrong spine port compared with the blueprint's intended cable map. By contrast, the actual problem is: A replacement leaf has a new serial number, but the blueprint still associates the old unavailable hardware with its logical role. The relevant inspection is: Review device replacement workflow, old/new system identifiers and required port/profile compatibility. The most discriminating first check is “Review device replacement workflow, old/new system identifiers and required port/profile compatibility”.