In Juniper Apstra, all modifications to a blueprint's design and topology are performed in the 'Staged' environment. The 'Active' environment is a read-only representation of the currently deployed network configuration. To change the physical cabling (the cable map), the operator must navigate to the 'Staged' tab, then select the 'Physical' view, and finally the 'Links' sub-tab. Here, links between device ports can be added, modified, or deleted to match the physical reality before committing the changes to the live network.

A. The 'Active' view is read-only and used for monitoring the current state of the network, not for making configuration changes.

C. 'Connectivity Templates' define logical server attachments, not the physical fabric links. Also, the 'Active' view is read-only.

D. 'Connectivity Templates' are used for defining how servers and external systems connect to the fabric, not for modifying the core spine-leaf cabling map.

1. Juniper Apstra User Guide 4.2.1, "Blueprints > Staged > Physical > Links". This section of the documentation explicitly details the procedure for viewing and editing device-to-device physical links within the staged version of a blueprint.

2. Juniper Networks TechLibrary, "Day One+: Deploying a Data Center with Juniper Apstra", Chapter 4: "Build Your Network Blueprint". This guide illustrates the workflow, showing that all design changes, including physical topology, occur in the 'Staged' section.

During the Deploy phase Apstra allocates required items (ASN ranges, VLAN/VNI IDs, IP pools, etc.) from the global resource pools without user action. The blueprint consumes the next available values, guaranteeing uniqueness across all blueprints unless the operator overrides them before deployment.

A. Device profiles and assignments are unrelated to automatic pool allocation.

B. Pools exist globally by default; user-created pools are optional, not mandatory.

C. Resources are defined globally, not created within each blueprint.

1. Juniper Networks, “Apstra Resource Pools and Allocation Guide 4.2”, §4 “Automatic Allocation at Deploy Time” (pp. 42-45).

2. Juniper Networks, “Apstra Concepts Guide 4.2”, §3.4 “Global vs Blueprint Resource Pools”.

The exhibit displays the properties of a selected device within the Apstra UI. The key properties shown are "System Type: generic" and "Internal: True". A "generic system" in Apstra is a device connected to the fabric that is not a spine, leaf, or other standard fabric role. The "Internal: True" property signifies that this device is managed by Apstra, meaning an Apstra agent is installed on it, and Apstra is responsible for rendering its configuration. Therefore, the device is correctly identified as an internal generic system.

A. A peer switch would have a specific fabric role, such as 'leaf' or 'spine', not 'generic'.

B. An external generic system would have the property "Internal: False", indicating it is not managed by an Apstra agent.

D. An access switch would typically be assigned the 'access' or 'leaf' role within the Apstra data model, not the 'generic' system type.

1. Juniper Apstra User Guide, "Generic Systems". The documentation distinguishes between internal and external generic systems. It states, "Internal generic systems are managed by Apstra (agent installed)... External generic systems are not managed by Apstra." The exhibit's "Internal: True" property directly corresponds to the definition of an internal generic system.

The "Analytics" tab in the Juniper Apstra UI is the central location for all operational telemetry and time-series data. It contains pre-defined dashboards and probes for monitoring various aspects of the network's health and performance. For capacity planning, an operator would navigate to this tab to find historical and real-time data on metrics such as link utilization, which are collected and visualized by Apstra's analytics engine.

A: The "Active" tab shows the current deployed topology and its real-time state, not historical time-series information for trend analysis.

B: The "Staged" tab is used for designing and modifying the blueprint's intent before deployment; it contains no operational data.

D: The main "Dashboard" provides a high-level, multi-blueprint overview, while detailed time-series data for a specific blueprint is found within its "Analytics" tab.

1. Juniper Apstra User Guide 4.2.1, "Analytics". This section explicitly states, "From the blueprint, navigate to Analytics to see IBA dashboards that are collecting and analyzing relevant data."

2. Juniper Networks, "Automate the Data Center with Juniper Apstra," Courseware. Module 4, "Apstra Operating," demonstrates using the Analytics tab to inspect time-series data for interfaces.

Juniper Apstra's Security Policies define rules for traffic flow between different application groups or network zones. When these abstract policies are rendered and pushed to network devices, they are translated into platform-specific configurations. For Juniper Junos devices, these policies are implemented as firewall filters. For other vendors like Arista EOS or Cisco NX-OS, they are implemented as Access Control Lists (ACLs). Both firewall filters and ACLs are functionally equivalent in this context, serving as stateless packet filters to permit or deny traffic based on defined criteria.

A. Filter-based forwarding (FBF)

FBF is a routing feature that directs traffic to a specific next-hop based on filter criteria, which is different from the permit/deny function of a security policy.

C. Policy-based routing (PBR)

PBR is used to override default routing behavior based on policy, not for implementing the stateless firewall rules defined in Apstra Security Policies.

1. Juniper Apstra User Guide, "Policy". The documentation states, "Apstra policies are rendered as access control lists (ACLs) on the interface of the leaf devices."

2. Juniper TechLibrary, "Day One+: Deploying in the Data Center with Apstra", Chapter 5: Security Policies. This guide explains that Apstra policies are translated into device-specific ACLs or firewall filters to enforce the desired security posture.

Property sets in Juniper Apstra are collections of key-value pairs, typically in JSON format, that function as variables. Their primary purpose is for variable substitution within Jinja2 templates, most commonly used in configlets. When a configlet that references a property set is imported into a blueprint, the property set must also be imported to make the variables available. For modularity, a single configlet can be designed to reference and utilize variables from multiple different property sets simultaneously, allowing for flexible and reusable configuration templates.

C. Property sets are also used in Intent-Based Analytics (IBA) probes, not just configlets, for defining dynamic or reusable probe parameters.

D. The syntax for creating a property set is standard JSON (key-value pairs), which is a vendor-agnostic format defined within Apstra itself.

1. Juniper Apstra User's Guide, "Design > Configlets". This section explains that configlets use Jinja2 templating and can reference property sets for variable substitution. It also shows the workflow of importing both configlets and their associated property sets into a blueprint.

2. Juniper Apstra User's Guide, "Property Sets". This section details the creation and management of property sets, stating, "Property sets are collections of key/value pairs that are used for variable substitution in configlets and IBA probes." This confirms their use beyond just configlets.

A three-stage Clos network, commonly known as a spine-and-leaf architecture, is a foundational design for modern data center fabrics. A key principle is that endpoint devices, such as servers and storage, connect to the leaf switches (the "edge" of the fabric). The spine layer serves as a high-speed backbone, interconnecting all leaf switches. For traffic entering or leaving the data center (North-South traffic), specialized "border leaf" devices are used. These border devices connect to external networks (like the Internet or WAN) and handle the ingress and egress of traffic for the entire fabric.

A. Spines are the core of the fabric and should not have external connections, as this would create a bottleneck and add complexity.

D. Servers connect to leaf devices to provide access to the fabric; connecting them directly to spines would violate the Clos architecture principles.

1. Juniper Networks, "Data Center Fabric Architecture Design Guide", Chapter 2: "Data Center Fabric Architecture". This guide explicitly states, "In a spine-and-leaf architecture, servers and storage devices connect to leaf devices."

2. Juniper Networks, "EVPN-VXLAN Data Center Fabric and DCI", Chapter 2: "Campus and Data Center Designs". This document describes the role of border leaf devices: "Border leaf devices provide Layer 3 connectivity between the data center and external networks."

When a device managed by Juniper Apstra has its configuration changed out-of-band (OOB) via the CLI, Apstra detects this as a "Config Deviation" anomaly. Clicking the "Accept Changes" button instructs Apstra to learn these OOB changes and incorporate them into its rendered or "golden" configuration for that specific device. This action effectively updates Apstra's intent to match the new reality on the device, resolving the anomaly.

A: Apstra does not guess intent or add similar configurations; it incorporates the exact changes that were made out-of-band.

C: Clicking "Accept Changes" resolves the deviation immediately; it does not hold changes pending a "Full Config" push.

D: This describes ignoring the anomaly. Accepting the changes prevents them from being overwritten by the next configuration push from Apstra.

1. Juniper Apstra User Guide 4.2.1, "Anomalies > Config Deviation". The guide explains that accepting changes "updates the pristine configuration with the out-of-band configuration."

2. Juniper Apstra Datasheet. Describes Apstra's role as the "single source of truth," which is maintained by either pushing intent-based config or accepting OOB changes to update the intent.

The Juniper Apstra device agent is a software component installed on managed network devices. Its primary responsibilities are to act as the intermediary between the Apstra controller and the device's operating system. The telemetry agent component collects real-time state, statistics, and logs from the device and streams this data back to the controller for analysis and validation. The deployment agent component is responsible for rendering the intended network configuration based on the blueprint and applying it to the device, ensuring the device's configuration matches the golden configuration.

A. Routing agent: The device's native network operating system (e.g., Junos OS) handles all routing functions. The Apstra agent configures routing protocols but does not perform routing itself.

B. Authentication agent: Device authentication (e.g., SSH, TACACS+) is managed by the device's OS. The Apstra agent authenticates to the device, but it is not an authentication service.

1. Juniper Apstra Documentation, "Device Agents". This document describes the agent's function: "The agent is responsible for all interaction between the device and Apstra, including configuration deployment and telemetry collection."

2. Juniper Apstra User Guide, "Agents". This section explains that agents "execute the generated configuration" (deployment) and "collect telemetry" from the devices they manage.

Juniper Apstra's Intent-Based Analytics (IBA) probes query the Apstra graph database to validate the intended state against the actual operational state of the network. The core component of a probe that specifies which devices, interfaces, or other network objects (represented as nodes in the database) to analyze is the Graph Query. This query selects a set of relevant nodes from the graph database, and the probe's processing logic is then applied to this set.

A. Reference design schema

The reference design schema defines the overall structure and relationships allowed in a blueprint, not the specific objects for a single probe.

C. Database nodes

Database nodes are the objects themselves (e.g., a switch). The graph query is the mechanism used to select these nodes for the probe.

D. Node-edge relationship

This describes the connection between two nodes in the graph database. A graph query traverses these relationships to find the target nodes.

1. Juniper Apstra User Guide, "Intent-Based Analytics > Probes". This section describes the components of a probe, stating, "The first stage of any probe is a graph query that returns a set of nodes."

2. Juniper TechLibrary, "Understanding Apstra Intent-Based Analytics". The documentation explains, "An IBA probe consists of a graph query that selects a set of nodes from the graph..."