You want to gracefully take a device out of service to perform an OS upgrade. How would you accomplish this task using Juniper Apstra?
Answer(s): B
In Apstra 5.1, the correct operational method to gracefully remove a switch from service for maintenance is to set its Deploy Mode to Drain. Drain is a day-2 operational control that tells Apstra to adjust intent so the fabric can continue operating while the targeted device is logically taken out of service as much as the design allows. This is especially relevant in EVPN-VXLAN leaf-spine fabrics where taking down a spine or a leaf can disrupt underlay BGP adjacencies and overlay reachability if traffic is not shifted first.This action is performed from the blueprint's Active view because Drain affects the currently deployed, running fabric state (not a staged design change). Selecting the device under Active and changing Deploy Mode to Drain initiates the workflow that prepares the device for maintenance by reducing its role in forwarding and/or withdrawing dependent services according to the blueprint's modeled redundancy (for example, shifting server-facing traffic to an MLAG/ESI peer where applicable, or reducing reliance on the device for transit). After the device is drained, an OS upgrade can be performed with less impact, and the device can later be returned to service by switching Deploy Mode back to Deploy and committing the change.The "Upgrade" action is not the deploy-mode mechanism described for graceful removal; the key is Deploy Mode Drain from Active, which is explicitly intended for maintenance and decommissioning scenarios.Verified Juniper sources (URLs):https://www.juniper.net/documentation/us/en/software/apstra5.1/apstra-user- guide/topics/task/device-drain.html https://www.juniper.net/documentation/us/en/software/apstra4.2/apstra-drain-mode/apstra-drain- mode-guide/topics/concept/apstra-drain-mode-activate-or-disable-drain.html
Referring to the exhibit,what happens when an operator clicks the Accept Changes button on the right side of the screen in Juniper Apstra?
In Apstra 5.1, this screen represents a configuration deviation workflow: Apstra is comparing the intended (golden) configuration it generated from blueprint intent against the actual configuration currently on the device. When an operator makes a change directly on the switch CLI (for example, on a Junos v24.4 leaf), Apstra detects the difference and flags it as drift because it did not originate from the blueprint's intent model.Clicking Accept Changes tells Apstra to adopt the device's current CLI state as the new accepted baseline for that device, effectively incorporating the observed CLI delta into Apstra's intended configuration for purposes of future comparison and compliance. In other words, Apstra stops treating that specific deviation as an error because it has been acknowledged and absorbed into the "golden config" (the intent-aligned configuration Apstra considers correct for that node). This is commonly used when an emergency change was made on-box and you want Apstra's source of truth to reflect it, rather than reverting it.This differs from Apply Full Config, which is used to push Apstra's intended configuration down to the device to restore compliance. If you do not accept the change, a later commit/apply action can overwrite the CLI-entered configuration to re-align with blueprint intent.
The analytics probe shown in the exhibit is enabled.The ge-0/0/5 interface on the my-esl-001-leaf1 node receives an average of greater than 1 Mbps of traffic. Which two statements are correct in this scenario? (Choose two.)
Answer(s): A,B
In Apstra 5.1, an IBA probe is a defined analytics pipeline that applies to a scoped set of graph objects (here, interfaces) and evaluates telemetry against logic defined in its processors. The exhibit shows a probe that consumes Interface Counters Average and then applies a Range processor. In the processor configuration, the Anomalous Range is set to "greater than 1,000,000" (bytes per secondequivalent for ~1 Mbps depending on the probe's metric definition), and Raise Anomaly is set to True. Therefore, when ge-0/0/5 receives an average traffic level above the configured threshold, the probe's condition evaluates as anomalous and Apstra raises a probe anomaly for that interface. That makes statement A correct.When probe anomalies are raised, Apstra surfaces them in the blueprint's Analytics area because they are analytics-derived findings (as opposed to configuration drift or deployment workflow issues). As a result, the blueprint's Analytics tab indicator changes state (commonly to red with a badge count) to signal active analytics anomalies requiring attention. That makes statement B correct.This event is not classified as a service anomaly (which is associated with higher-level service intent/assurance objects) unless separately mapped by policy/logic, and it does not primarily drive the Active tab indicator, which is focused on operational state views rather than being the primary alert surface for IBA probe anomalies.
An operator is working on a capacity-planning exercise. The operator needs to examine the pre-built time-series information regarding link utilization. In the Juniper Apstra UI, which top-level tab would the operator have to access to find this information?
Answer(s): C
In Apstra 5.1, capacity planning based on pre-built time-series telemetry (such as link utilization trends) is part of Intent-Based Analytics (IBA). IBA is where Apstra ingests streaming telemetry from fabric devices, stores it as time-series data, and presents it through built-in analytics views (dashboards/widgets) and probes. Because the question specifically calls out "pre-built time series information regarding link utilization," the correct UI location is the Analytics top-level tab within the blueprint.The Active tab is primarily oriented to operational state and day-2 workflows (for example, viewing live state, queries, and device-level operational views). The Staged tab is where you modify intent (physical/virtual design, policies, catalog items) prior to committing and deploying. The Dashboard provides a high-level blueprint overview and navigation, but the drill-down and time-series analytics views that support trending and capacity analysis are accessed via Analytics.In an EVPN-VXLAN fabric using Junos v24.4, link utilization time-series is particularly valuable because underlay congestion can degrade overlay performance (BGP convergence behavior, ECMP distribution effectiveness, and endpoint experience). Apstra's Analytics tab centralizes these metrics so operators can evaluate utilization baselines, identify sustained hot links, and support proactive actions (rebalancing, adding capacity, or adjusting design intent) without relying on ad-hoc per- device CLI polling.Verified Juniper sources (URLs):https://www.juniper.net/documentation/us/en/software/apstra5.1/apstra-custom-telemetry- collection-guide/topics/concept/apstra-telemetry-and-intent-based-analytics.html
Which two statements are correct about Juniper Apstra reference designs? (Choose two.)
Answer(s): A,D
Apstra 5.1 provides multiple reference designs that define how intent is modeled and how configuration is produced. In the Freeform reference design, the network designer is responsible for creating and validating the device configurations using constructs such as device contexts, property sets, and config templates. Because configuration is authored rather than generated from a fixed data-center abstraction set, Freeform inherently requires practical knowledge of the device's configuration model and operational behavior--on Juniper platforms, that means being comfortable with Junos-style configuration and show/verification workflows. This makes statement A correct.Freeform in Apstra 5.1 is also limited to Juniper devices (Junos and Junos Evolved families). In other words, Freeform blueprints do not provide multi-vendor device onboarding and deployment in that reference design at this software level. That makes statement D correct as written in the question's choices.By contrast, the data center reference design in Apstra 5.1 is not limited to Junos-only device families; Apstra qualifies multiple NOS families for data center operation via device profiles and packages, and it renders intent accordingly. Therefore statement B is not correct. Finally, while CLI knowledge is always useful for troubleshooting, the data center reference design does not fundamentally require an operator to hand-author device CLI to deploy a standards-based EVPN- VXLAN fabric; that's one of the core benefits of the intent-based data center reference design.Verified Juniper sources (URLs):https://www.juniper.net/documentation/us/en/software/apstra5.1/apstra-user- guide/topics/concept/freeform.html https://www.juniper.net/documentation/us/en/software/apstra4.2/apstra-freeform-4.2.1/apstra- freeform-guide/topics/concept/freeform-overview-and-design.html https://www.juniper.net/documentation/us/en/software/apstra5.1/apstra-user- guide/topics/task/device-profile-import-freeform.html https://www.juniper.net/documentation/us/en/software/apstra5.1/apstra-user-guide/topics/topic- map/devices-qualified.html
Post your Comments and Discuss Juniper JN0-481 exam prep with other Community members:
Our website is free, but we have to fight against AI bots and content theft. We're sorry for the inconvenience caused by these security measures. You can access the rest of the JN0-481 content, but please register or login to continue.