What are two available Juniper Apstra template types? (Choose two.)
Correct Answer: A,B
In Juniper Apstra 5.1, a template is a design abstraction used to create a blueprint. It captures the intended topology shape and design rules without tying the design to a specific vendor's CLI. Apstra supports multiple template types to match common data center fabric architectures. A rack-based template is used for the standard three-stage Clos (leaf-spine) approach. In this model, you define the spine logical devices and one or more rack types (containing leaf devices and optional endpoint constructs). This is the dominant pattern for EVPN-VXLAN IP fabrics: leaf switches provide server attachment, VXLAN encapsulation (VTEP function), and optional IRB gateways, while spines provide high-capacity L3 transit with ECMP. A collapsed template is used for a spine-less (spineless) topology. Instead of a separate spine tier, a collapsed design models a fabric where leaf nodes interconnect in a mesh-like arrangement (as supported by the template type) to provide underlay reachability and redundancy. This can be useful for smaller environments or edge data centers where a full spine tier is unnecessary. "Compressed" and "device-based" are not Apstra template types. Junos v24.4 is relevant when the blueprint is instantiated and deployed, but the template type selection is an Apstra design-time decision that determines the fabric topology class.
Question 52
You are adding a new switch to Juniper Apstra software. The Managed Devices page shows the "0 OS- Quarantined" status. What is the proper next step to make the device ready for use in a blueprint?
Correct Answer: A
When a new switch is added to Juniper Apstra software, it initially shows the "0 OS-Quarantined" status, which means that the device is not yet managed by Apstra and has not been assigned to any blueprint. The proper next step to make the device ready for use in a blueprint is to acknowledge the device, which is a manual action that confirms the device identity and ownership. Acknowledging the device changes its status to "OOS-Ready", which means that the device is ready to be assigned to a blueprint and deployed.
Question 53
When creating a probe, an operator wants to make it easy to view that probe's output. In this scenario, which element must be created to accomplish this task?
Correct Answer: A
In Apstra IBA, a probe is a directed graph made of stages (data you can inspect) and processors (operations that transform/aggregate data). While stages can be inspected during probe construction, the simplest operational way to make probe results readily consumable by day-2 operators is to publish them through widgets that can be placed on Analytics dashboards. A dashboard widget is the visualization and presentation object that renders either (1) counts of anomalies or (2) the outputs produced by stages and processors in a probe. Creating a widget tied to the probe output means the operator can open a dashboard and immediately see the metric trends, tables, or anomaly indicators without navigating into probe internals. A predefined probe is optional content (a starting template) and is not required for visibility. Processors and stages are internal probe building blocks, but they do not, by themselves, create an operator-friendly view in the UI. In a Junos v24.4 EVPN-VXLAN fabric, this is especially useful for link utilization, drops, latency signals, or any custom telemetry pipeline: you build the probe logic once, then expose the key results in a widget that persists across operational workflows and can be shared on standardized dashboards for capacity planning and troubleshooting. Verified Juniper sources (URLs): https://www.juniper.net/documentation/us/en/software/apstra4.2/apstra-user-guide/topics/concept/widgets.html https://www.juniper.net/documentation/us/en/software/apstra4.2/apstra-user-guide/topics/topic-map/widget-stage-create.html https://www.juniper.net/documentation/us/en/software/apstra4.2/apstra-user-guide/topics/concept/probes.html
Question 54
You have accessed your deployed blueprint and see the banner shown in the exhibit. Which two statements are correct in this scenario? (Choose two.)
Correct Answer: B,D
In Apstra 5.1, the top-level blueprint banner uses tab indicators (colored badges) to summarize blueprint status across areas such as Staged, Uncommitted, Active, and Analytics. The presence of an Uncommitted indicator signifies that there are staged modifications that have not yet been committed and therefore are not part of the active, deployed intent. That directly corresponds to the statement that changes exist which are not active on the fabric. At the same time, the banner shows an Active indicator in an alarm state, which reflects that the running fabric has issues requiring attention-commonly surfaced as anomalies (for example, configuration deviation, interface/link faults, protocol/session issues, or service-impacting conditions). In Apstra's operational model, these issues appear as anomalies that operators should investigate and remediate to restore compliance and health. Therefore, the statement that there are anomalies that must be addressed is also correct. The remaining options are not implied by this banner alone. Device profile assignment and resource assignment are build-time tasks, but their absence is not what the Uncommitted/Active alert indicators are specifically communicating here. The banner is highlighting uncommitted intent changes and active anomalies that affect the deployed blueprint state and assurance posture. Verified Juniper sources (URLs): https://www.juniper.net/documentation/us/en/software/apstra5.1/apstra-user-guide/topics/concept/uncommitted.html https://www.juniper.net/documentation/us/en/software/apstra5.0/apstra-user-guide/topics/topic-map/anomalies-service-active.html https://cloudlabs.apstra.com/labguide/Cloudlabs/6.0.0/test-drive-guide/lab1-junos-5_blueprints_.html
Question 55
You are building a blueprint using Juniper Apstra and must change the cable map to match the physical environment. Where in the blueprint UI is this task accomplished?
Correct Answer: B
To modify the cable map in Juniper Apstra so it matches the actual physical environment, you must do it in the Staged → Physical → Links section of the blueprint UI. Changes made in the staged view allow adjustments before committing them to the active fabric.
