Question 120
An operations team adds a hypervisor pair whose access ports are not modeled in Apstra generic-system inventory. Which initial check would most directly distinguish the likely cause?
Explanation
Correct Answer
This checks the relevant evidence first: inspect the intended leaf attachment ports, generic-system definition and relevant cable map. The underlying concept is that generic systems represent attached external workloads and can be modeled with their interfaces and supported connectivity patterns. After confirming the finding, a controlled remediation is to create or update the authorized generic system and its connectivity template within the staged blueprint.
Incorrect Answers
The option “Compare pristine baseline, incremental changes and final rendered config against the active blueprint” 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: An operations team adds a hypervisor pair whose access ports are not modeled in Apstra generic-system inventory. The relevant inspection is: Inspect the intended leaf attachment ports, generic-system definition and relevant cable map. The most discriminating first check is “Inspect the intended leaf attachment ports, generic-system definition and relevant cable map”.
That choice—“Check current spine port availability, resource pools and the proposed rack type against the active blueprint”—addresses this other problem: A data center needs to add another rack to a production fabric without replacing the existing blueprint. Here the scenario is: An operations team adds a hypervisor pair whose access ports are not modeled in Apstra generic-system inventory. The relevant inspection is: Inspect the intended leaf attachment ports, generic-system definition and relevant cable map. The most discriminating first check is “Inspect the intended leaf attachment ports, generic-system definition and relevant cable map”.
“Inspect configlet attachment criteria and generated configuration diffs for all matching targets” is associated with a distinct issue: A new configlet unexpectedly adds a command to spine switches when it was intended for a single border leaf. By contrast, the actual problem is: An operations team adds a hypervisor pair whose access ports are not modeled in Apstra generic-system inventory. The relevant inspection is: Inspect the intended leaf attachment ports, generic-system definition and relevant cable map. The most discriminating first check is “Inspect the intended leaf attachment ports, generic-system definition and relevant cable map”.