Question 620
An operator wants to identify managed nodes by rack and role in the blueprint graph. Which design or operational principle best explains this behavior?
Explanation
Correct Answer
blueprint graph and object queries can select devices using modeled relationships rather than fragile substring matches. Here, an operator wants to identify managed nodes by rack and role in the blueprint graph. A useful discriminating check is to inspect object types, graph relationship properties and returned identities for the intended rack.
Incorrect Answers
“Blueprint object tags and query filters support targeted discovery and operational reporting” is relevant to a different condition: A team wants to locate every virtual network owned by a particular application during a migration. The stated question instead concerns: An operator wants to identify managed nodes by rack and role in the blueprint graph. Blueprint graph and object queries can select devices using modeled relationships rather than fragile substring matches. The controlling principle is “Blueprint graph and object queries can select devices using modeled relationships rather than fragile substring matches”.
That choice—“Reverting uncommitted edits is distinct from using Time Voyager to select a previously committed blueprint revision”—addresses this other problem: A team wants to undo only the last local edit in Staged without reverting the whole network to an older committed state. Here the scenario is: An operator wants to identify managed nodes by rack and role in the blueprint graph. Blueprint graph and object queries can select devices using modeled relationships rather than fragile substring matches. The controlling principle is “Blueprint graph and object queries can select devices using modeled relationships rather than fragile substring matches”.
“Apstra supports controlled blueprint day-two rack additions using supported rack types, resources and spine capacity” is associated with a distinct issue: An organization expands a Clos topology and wants newly created racks to inherit validated patterns and allocations. By contrast, the actual problem is: An operator wants to identify managed nodes by rack and role in the blueprint graph. Blueprint graph and object queries can select devices using modeled relationships rather than fragile substring matches. The controlling principle is “Blueprint graph and object queries can select devices using modeled relationships rather than fragile substring matches”.