Intent-based analytics (IBA) is a feature of Juniper Apstra that allows you to combine intent from the network design with current and historic data from devices to reason about the network at-large1. IBA has the following characteristics:

It is a real-time information processing pipeline. This means that IBA can ingest, process, and analyze large amounts of data from devices in real time, using agents and probes. Agents are software components that collect data from devices and send them to the Apstra server.Probes are user-defined queries that aggregate data across devices and generate advanced data that can be more easily reasoned about1.

It is used to establish network performance baselines. This means that IBA can use the advanced data to measure and monitor the network performance against the expected outcomes and service levels.IBA can also use the historic data to create baselines that represent the normal behavior and state of the network2.

It alerts the network operator when network performance moves away from the baseline. This means that IBA can detect and report any anomalies or deviations from the baseline or the intent in the network.IBA can also provide insights and recommendations for troubleshooting and resolving the issues2.

The following two statements are incorrect in this scenario:

It indicates when device operating versions require updating. This is not true, because IBA does not provide any information or guidance about the device operating versions or updates.IBA is focused on the network performance and compliance, not on the device maintenance or upgrade1.

It collects information from vendor websites. This is not true, because IBA does not collect any information from vendor websites or external sources.IBA only collects information from the devices in the network, using agents and probes1.

Intent-Based Analytics --- Apstra 3.3.0 documentation

What is Intent Based Networking? | Juniper Networks US

In the Juniper Apstra UI, you can create VNI pools for virtual networks that use VXLAN encapsulation in the overlay network. A VNI pool is a resource pool that contains a range of VNIs that can be assigned to the virtual networks.The valid VNI range for a VNI pool is 4096 through 16777214, according to the VXLAN standard1. Therefore, the statement B is correct in this scenario.

The following three statements are incorrect in this scenario:

Any range is acceptable for the VNI pool.This is not true, because the VNI range has a lower and upper limit defined by the VXLAN standard1. The lower limit is 4096, and the upper limit is 16777214. Any VNI outside this range is invalid and cannot be used for VXLAN encapsulation.

The valid VNI range is 2 through 4096. This is not true, because the VNI range does not start from 2, but from 4096.The VNIs from 2 to 4095 are reserved and cannot be used for VXLAN encapsulation1.

The valid VNI range is 1 through 10000.This is not true, because the VNI range does not include 1, which is also reserved and cannot be used for VXLAN encapsulation1.The VNI range also does not end at 10000, but at 16777214, which is the maximum possible value for a 24-bit VNI field1.

VNI Pools (Resources)

Juniper Apstra supports three deploy modes for devices:Deploy,Drain, andReady.These modes determine the configuration and state of the devices in the data center fabric12.

Deploy: This mode applies the full Apstra-rendered configuration to the device, according to the Apstra Reference Design.The device state becomesIS-ACTIVEand the device is ready to carry traffic in the fabric12.

Drain: This mode adds a ''drain'' configuration to the device, which prevents any new traffic from entering the device.The device state becomesIS-READYand the device is prepared for maintenance or decommissioning12.

Ready: This mode removes the Apstra-rendered configuration from the device, leaving only the basic configuration such as device hostname, interface descriptions, and port speed/breakout.The device state becomesIS-READYand the device is not part of the fabric12.Reference:

Device Configuration Lifecycle

Set Deploy Mode (Datacenter)

A pristine configuration in Juniper Apstra is the configuration file that is used to onboard a device into the Apstra software application.A pristine configuration contains the minimum settings that are required for the device to communicate with the Apstra server, such as the hostname, management IP address, username, password, and SSH key1. A pristine configuration has the following characteristics:

It is the configuration file placed on the device when decommissioning the device. This is because when a device is decommissioned from the Apstra software application, it is reverted back to its pristine configuration, which removes all the network configuration and services that were applied by the Apstra software application.This allows the device to be reused or repurposed for another network2.

It is the configuration file on a device before acknowledgment in Apstra. This is because when a device is onboarded into the Apstra software application, it is initially in the discovery state, which means that the device is discovered by the Apstra server, but not yet acknowledged by the user. In the discovery state, the device has the pristine configuration, which can be viewed and edited by the user.Once the user acknowledges the device, the device moves to the deployed state, which means that the device is ready to receive the network configuration and services from the Apstra software application3.

The following two statements are incorrect in this scenario:

It is the device's currently active configuration. This is not true, because the pristine configuration is not the device's currently active configuration, unless the device is in the discovery state or the decommissioned state.In the deployed state, the device's currently active configuration is the network configuration and services that are applied by the Apstra software application, which are based on the blueprint and the intent3.

It is the device's previously active configuration. This is not true, because the pristine configuration is not the device's previously active configuration, unless the device is in the decommissioned state. In the discovery state, the pristine configuration is the device's initial configuration, which may or may not be the same as the device's previous configuration before being onboarded into the Apstra software application.In the deployed state, the device's previously active configuration is the network configuration and services that were applied by the Apstra software application before the last commit3.

Pristine Config

Decommission Device

Device States

The Juniper Apstra Rendered configuration is the configuration that is generated from the staged blueprint and applied to the devices in the network. The Rendered configuration is dynamically rendered at commit time, which means that it is created on the fly based on the latest changes and validations in the blueprint. The Rendered configuration is not stored in any database, but it can be viewed in the Apstra UI or downloaded as a file. The Rendered configuration reflects the desired state of the network as defined by the intent of the blueprint. The other options are incorrect because:

A) It is built at commit time and stored in a MySQL database is wrong because the Rendered configuration is not stored in any database, let alone a MySQL database. Apstra uses a graph database to store the network topology and configuration data, not a relational database like MySQL.

B) It is stored in a NoSQL database and incrementally updated is wrong because the Rendered configuration is not stored in any database, let alone a NoSQL database. Apstra uses a graph database to store the network topology and configuration data, not a non-relational database like NoSQL. The Rendered configuration is not incrementally updated, but dynamically rendered at commit time.

D) It is rendered from the graph database and stored locally is wrong because the Rendered configuration is not rendered from the graph database, but from the staged blueprint. The graph database stores the network topology and configuration data, but the Rendered configuration is generated from the blueprint, which is a logical representation of the network design and intent. The Rendered configuration is not stored locally, but it can be downloaded as a file if needed.Reference:

Config Rendering in Juniper Apstra

AOS Device Configuration Lifecycle

Configlets (Datacenter Design)