What is the primary reason for creating an Apstra worker node?
Correct Answer: D
In Apstra 5.1, the worker node's primary purpose is to add scalable runtime capacity to an Apstra cluster by hosting off-box services that would otherwise consume resources on the controller. Specifically, worker nodes run containerized services such as off-box device agents (used to communicate with and manage devices) and Intent-Based Analytics (IBA) components (such as probes and analytics-related services). This design keeps the controller node focused on cluster management and control-plane functions (API handling, cluster-wide state, blueprint control workflows), while shifting resource-intensive operational services to worker nodes. As your fabric grows-more switches, more telemetry, more devices requiring agent connectivity-CPU and memory demand increases notably, especially when IBA is enabled. Adding worker nodes allows you to scale those container workloads horizontally without redesigning the fabric or reducing analytics coverage. In a Juniper data center built on EVPN-VXLAN with Junos v24.4 leaf-spine roles, this separation helps ensure that Apstra can continuously validate intent, process streaming telemetry, and maintain device communications reliably at scale. Worker nodes therefore exist primarily to offload and scale operational agents and IBA services, improving performance and resilience for larger deployments.
Question 32
You have created a blueprint and are in the process of assigning systems. You require the leaf3-sonic device in the blueprint but do not want it to actively participate in the routing of the IP fabric. In the Juniper Apstra UI, which two modes satisfy this requirement? (Choose two.)
Correct Answer: B,D
Apstra deploy modes control how far a device progresses in the configuration lifecycle and whether it becomes active in the fabric. If you must keep leaf3-sonic present in the blueprint (modeled, cabled, and available for future use) but you do not want it to participate in IP-fabric routing, you use modes that keep the device not active. Ready mode assigns the device to the blueprint and applies only "Ready (Discovery 2)" level configuration-hostnames, interface descriptions, and port speed/breakout settings-while explicitly keeping the device out of fabric routing. In this mode, Apstra does not configure routing/BGP or L3 interface addressing for the IP fabric, so the switch is staged and visible for validation (for example, LLDP wiring checks) but does not forward as part of the Clos underlay. Undeploy mode removes the complete Apstra service configuration from the device. Operationally, this also ensures the device is not active in the fabric. It is commonly used when a device must be retained in the blueprint inventory/topology but should not be participating (for example, temporarily withdrawn, decommission preparation, or held as a spare). By contrast, Deploy makes the device active (full rendered fabric configuration, including BGP), and Drain is a maintenance state used to gracefully remove traffic from an already-active device rather than a state for keeping it non-participatory from the outset. Verified Juniper sources (URLs): https://www.juniper.net/documentation/us/en/software/apstra6.0/apstra-user-guide/topics/topic-map/device-config-lifecycle.html https://www.juniper.net/documentation/us/en/software/apstra4.2/apstra-user-guide/topics/topic-map/device-config-lifecycle.html
Question 33
What is the role of a Freeform blueprint in Juniper Apstra, as opposed to a Datacenter blueprint?
Correct Answer: B
A Freeform blueprint in Juniper Apstra provides a more flexible and less prescriptive modeling approach, suitable for topologies or use cases that don't conform to the standard Clos-based data center reference design used by the Datacenter blueprint type. Freeform blueprints still benefit from Apstra's configuration rendering, telemetry collection, and anomaly detection capabilities, but with more design freedom.
Question 34
Off-box agents are consuming too much CPU and memory on your Juniper Apstra controller. In this scenario, how would you solve this problem?
Correct Answer: B
In Apstra 5.1, off-box agents and analytics services are delivered as containerized workloads that consume CPU and memory within the Apstra cluster. When these workloads are concentrated on the controller node, the controller can become resource-constrained, impacting overall responsiveness and scaling limits. The supported architectural solution is to add a worker node (worker VM) and allow Apstra to place offbox (and, if applicable, iba) containers on that worker. This increases cluster capacity and shifts runtime load away from the controller, which should remain focused on core control-plane and management functions. Juniper's sizing guidance also treats worker nodes as the scalable unit for off-box agent growth: each VM node (controller or worker) supports a bounded number of off-box agents, and when one VM is insufficient, the prescribed approach is to increase capacity by adding worker nodes to the Apstra VM cluster. This method scales horizontally and avoids overloading the controller with operational containers. While increasing CPU/memory on the controller might help temporarily, the documented design pattern for sustained growth is to distribute the off-box workloads across worker nodes. Switching to on-box agents is a different operational model and not the direct remediation for controller resource pressure in an off-box deployment. Verified Juniper sources (URLs): https://www.juniper.net/documentation/us/en/software/apstra5.1/apstra-install-upgrade/topics/ref/apstra-server-resources.html https://www.juniper.net/documentation/us/en/software/apstra5.0/apstra-user-guide/topics/topic-map/apstra-cluster-nodes.html https://www.juniper.net/documentation/us/en/software/apstra4.2/apstra-user-guide/topics/topic-map/apstra-cluster-nodes.html
Question 35
Juniper Apstra has indicated an anomaly with respect to cabling. What are two ways to remediate the issue? (Choose two.)
Correct Answer: A,D
A cabling anomaly is an issue that occurs when the physical connections between the devices in the data center fabric do not match the expected connections based on the Apstra Reference Design. A cabling anomaly can cause problems such as incorrect routing, suboptimal traffic flow, or device isolation. To remediate the issue, you can use one or both of the following methods: Manually edit the cabling map. This allows you to override the Apstra-generated cabling and specify the correct connections between the devices. You can use the Apstra UI or the Apstra CLI to edit the cabling map and apply the changes to the fabric. Have Apstra autoremediate the cabling map using LLDP. This allows Apstra to collect LLDP data from the devices and use it to update the cabling map automatically. LLDP is a protocol that allows devices to exchange information about their identity, capabilities, and neighbors. Apstra can use the LLDP data to detect and correct any cabling errors in the fabric.
