Question 400
An organization expands a Clos topology and wants newly created racks to inherit validated patterns and allocations. 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
“Verify both expected server interfaces and VLAN or routing attachments appear in active intent and measured connectivity” is relevant to a different condition: An operations team adds a hypervisor pair whose access ports are not modeled in Apstra generic-system inventory. The stated question instead concerns: An organization expands a Clos topology and wants newly created racks to inherit validated patterns and allocations. 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”.
That choice—“Confirm the installed device configuration reconciles with the intended active config and authorized baseline”—addresses this other problem: A network engineer sees differences among the pristine, incremental and rendered configurations for a managed leaf. Here the scenario is: An organization expands a Clos topology and wants newly created racks to inherit validated patterns and allocations. 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”.
“Prove the revised blueprint builds with valid allocations and switches converge on intended active state” is associated with a distinct issue: An engineer wants to return to a blueprint commit created before several resource pool and hardware changes. By contrast, the actual problem is: An organization expands a Clos topology and wants newly created racks to inherit validated patterns and allocations. 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”.