Question 230
A data center needs to add another rack to a production fabric without replacing the existing blueprint. Which evidence most directly verifies the intended network outcome?
Explanation
Correct Answer
This directly tests the desired result: confirm the rack is represented in active intent and all expected uplinks and tenant services work. The decisive investigation is to check current spine port availability, resource pools and the proposed rack type against the active blueprint. The governing principle is that Apstra supports controlled blueprint day-two rack additions using supported rack types, resources and spine capacity.
Incorrect Answers
That choice—“Verify both expected server interfaces and VLAN or routing attachments appear in active intent and measured connectivity”—addresses this other problem: A new dual-homed application server is physically connected but its logical attachment is absent from the active blueprint. Here the scenario is: A data center needs to add another rack to a production fabric without replacing the existing blueprint. Apstra supports controlled blueprint day-two rack additions using supported rack types, resources and spine capacity. The direct acceptance evidence is “Confirm the rack is represented in active intent and all expected uplinks and tenant services work”.
The option “Confirm the installed device configuration reconciles with the intended active config and authorized baseline” is useful in a different setting: An audit asks why some device commands come from the baseline while others appear from intended virtual-network configuration. The case being tested is: A data center needs to add another rack to a production fabric without replacing the existing blueprint. Apstra supports controlled blueprint day-two rack additions using supported rack types, resources and spine capacity. The direct acceptance evidence is “Confirm the rack is represented in active intent and all expected uplinks and tenant services work”.
“Confirm active blueprint state matches the intended retained revision and critical services recover” is relevant to a different condition: An administrator discovers a bad blueprint deployment and needs to restore a prior retained intent state. The stated question instead concerns: A data center needs to add another rack to a production fabric without replacing the existing blueprint. Apstra supports controlled blueprint day-two rack additions using supported rack types, resources and spine capacity. The direct acceptance evidence is “Confirm the rack is represented in active intent and all expected uplinks and tenant services work”.