What are two types of policies that Juniper Apstra uses to push to switches using Security Policies? (Choose two.)
Correct Answer: B,D
Apstra 5.1 Security Policies are intended to enforce permit/deny controls for traffic between defined endpoints such as routing zones, virtual networks, and IP endpoints. Apstra expresses this security intent in an implementation-independent way, then renders and deploys the equivalent enforcement configuration onto the appropriate devices and interfaces. In Apstra terminology, the outcome is an ACL applied at enforcement points, such as virtual network interfaces (SVIs/IRBs) for east-west controls and border leaf interfaces for external-to-internal controls. Therefore, the two correct policy types in this context are access control lists (ACLs) and firewall filters. "ACL" is the abstract policy object Apstra compiles and applies, while on Junos v24.4 the concrete enforcement mechanism for stateless packet filtering on interfaces is typically implemented as a firewall filter. Apstra automatically places these rendered ACLs/filters where needed: when you add VXLAN endpoints (such as expanding a rack/leaf in a VN), the ACL is placed on the corresponding VN interface; when you add external connectivity points, relevant ACLs are placed on the border leaf enforcement points. This automation ensures that security intent remains consistent as the fabric scales or changes, reducing the risk of manual rule drift. In contrast, filter-based forwarding / policy-based routing changes forwarding decisions rather than expressing permit/deny security intent, and is not the primary mechanism used by Apstra Security Policies for reachability control.
Question 77
What are two formats that the cabling map can be exported as? (Choose two.)
Correct Answer: A,B
Question 78
You have recently committed a change after creating a new blueprint in Juniper Apstra. In the main dashboard, you see a number of anomalies related to BGR What is a likely cause of these anomalies?
Correct Answer: B
In Juniper Apstra, a blueprint is a logical representation of the network design and configuration. When you create a new blueprint, you need to commit the changes to apply them to the network devices. However, committing the changes does not mean that the network is immediately updated and operational. It may take some time for the network to converge and reflect the new state of the blueprint. During this time, you may see some anomalies related to BGP in the main dashboard, which indicate that the BGP sessions are not established or stable between the devices. These anomalies are usually temporary and will disappear once the network converges and the BGP sessions are up and running.
Question 79
You have a configuration deviation in the Juniper Apstra dashboard. What does this anomaly indicate in this scenario?
Correct Answer: C
A configuration deviation (also called a configuration anomaly) in Apstra indicates that the device's running configuration differs from Apstra's intended (golden) configuration for that node. In day-to-day operations, this most commonly occurs when an operator makes a change outside of Apstra's control, such as entering commands directly on the device CLI (for example, on a Junos v24.4 switch), using another automation system, or applying an out-of-band configuration method. Apstra continuously compares the device's operational configuration against what it expects based on blueprint intent. When it detects drift, it raises a deviation anomaly so operators can decide how to restore compliance. Typical remediations are either (1) remove/revert the out-of-band change so the device matches intent again, or (2) explicitly acknowledge the change in Apstra (for example, via an accept/suppress workflow, depending on the exact UI action and version), so the deviation is no longer treated as unexpected. While it is also possible for a deviation to be triggered by a device not accepting a rendered command (capability mismatch), the question asks what the anomaly indicates in this scenario; the primary meaning of "configuration deviation" is configuration changed outside of Apstra and therefore the network is no longer aligned with the intended state. That corresponds to option C.
Question 80
The servers attached to your Juniper Apstra managed data center fabric are running VMware. You want to get the details about which VMs are attached to which leaf interface. Referring to the exhibit, which statement is correct?
Correct Answer: A
In Juniper Apstra, to see details about which VMs are attached to which leaf interface, Apstra requires integration with the Virtual Infrastructure Manager (VIM), such as VMware vCenter for ESXi environments. Without defining and integrating a VIM, the VMs tab (as shown in the exhibit) will not display any data, even if servers are connected and running.
