Juniper JN0-480 Practice Test - Questions Answers, Page 3

According to the Juniper documentation1, the Revert button is located on the Uncommitted tab of the blueprint page. The Uncommitted tab shows the changes that have been staged but not yet committed to the network. The Revert button allows you to discard any uncommitted changes and revert to the last committed state of the blueprint. This is useful if you want to cancel the changes that you have made or if you want to start over with a fresh slate. Therefore, the correct answer is B. The Revert button deletes any uncommitted changes within Apstra.Reference:Commit / Revert Changes to Blueprint | Apstra 4.2 | Juniper Networks

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

The ztp.Json file on the Apstra ZTP server contains the configuration parameters for each device that is onboarded using ZTP. One of the parameters is the State, which can be one of the following values:init,ready,in_progress,done,error, ordisabled. The State indicates the current status of the device in the ZTP process. For example, if the State isready, it means that the device is ready to be onboarded by the Apstra ZTP server. If the State isdone, it means that the device has completed the ZTP process and is managed by the Apstra server. The State can be manually set or changed in the ztp.Json file to control the behavior of the device during ZTP. For more information, seeApstra ZTP Configuration File.Reference:

Apstra ZTP Configuration File

Apstra ZTP Introduction

Configure Apstra ZTP

The Links table in the Staged tab shows the physical connections between the devices in the fabric. It provides information such as the source and destination device names, hostnames, serial numbers, roles, interfaces, and link status. The Links table can be used to assist the team that is installing and cabling the devices by verifying that the devices are connected correctly and that the links are operational. The Links table can also be used to troubleshoot any connectivity issues that may arise during the installation process. For more information, seeLinks (Staged).Reference:

Links (Staged)

Topology (Staged)

Staged

A configlet is a small piece of configuration that can be applied to a device or a group of devices to make persistent changes that are not overwritten by Apstra. Configlets can be used to install manual changes that are not part of the Apstra rendered configuration, such as custom commands, scripts, or features.Configlets can be created, edited, and deleted from the Apstra GUI or CLI12.Reference:

Configlets Overview

Configlets User Guide

VMware anomaly detection is a feature of Apstra that provides visibility and validation of the virtual network settings and the physical network settings in a VMware vSphere environment. To enable this feature, Apstra requires a connection to a vCenter server that manages the ESX/ESXi hosts and the VMs connected to the Apstra-managed leaf switches. The vCenter server must be configured under External Systems in the Apstra web interface, and the vCenter integration must be staged and committed in the blueprint. This allows Apstra to collect information about VMs, ESX/ESXi hosts, port groups, and VDS, and to flag any inconsistencies or mismatches that might affect VM connectivity. The other options are incorrect because:

VMware anomaly detection is not on by default. It must be enabled by configuring a vCenter server under External Systems and adding a virtual infra to the blueprint.

VMware anomaly detection does not require a VMware hypervisor with exports enabled. It only requires LLDP transmit to be enabled on the VMware distributed virtual switch to associate host interfaces with leaf interfaces.

VMware anomaly detection does not require an Apstra server running on VMware. It can run on any supported platform, such as Linux, Windows, or Docker.Reference:

VMware vCenter/vSphere Virtual Infra

Anomalies (Service)

A Better Experience: VMware + Juniper Apstra

The cable map is a graphical representation of the physical connections between the devices in the data center fabric. It shows the status of the cables, interfaces, and BGP sessions for each device. You can use the cable map to identify and troubleshoot any cable, interface, or BGP anomalies that may occur in the fabric.You can also filter the cable map by device name, device type, device role, device state, cable state, interface state, or BGP state12.Reference:

Cable Map Overview

Cable Map User Guide

To create a new routing zone, you must specify the VRF Name, VLAN ID, and VNI for the routing zone. These are the mandatory fields in the user interface shown in the exhibit. The VRF Name is the name of the L3 domain that isolates the IP traffic of the routing zone from other routing zones. The VLAN ID is the identifier for the VLAN tagged Layer 3 links on external connections. The VNI is the VxLAN Network Identifier associated with the routing zone. The Routing Policies are optional fields that allow you to configure import and export route targets for the routing zone. These are only applicable for EVPN routing zones, which use MP-EBGP as the overlay control protocol. The other options are incorrect because:

A) VRF Name only is wrong because you also need to specify the VLAN ID and VNI for the routing zone.

B) VRF Name and Routing policies is wrong because you also need to specify the VLAN ID and VNI for the routing zone. Routing policies are optional and only relevant for EVPN routing zones.

D) VRF Name, VLAN ID, VNI, Routing Policies is wrong because Routing Policies are optional and not required to create a new routing zone.Reference:

Routing Zones (Virtual)

Data Center Automation Using Juniper Apstra

Time Voyager is a feature of Juniper Apstra that allows you to restore previous revisions of a blueprint, which is a logical representation of your network design and configuration. Time Voyager automatically saves the five most recent blueprint commits, which are the changes that you apply to the network. You can also manually save up to twenty-five revisions by keeping them, which prevents them from being overwritten by new commits. Therefore, the correct answer is B and D. Time Voyager retains the five most recent blueprint commits and Time Voyager retains up to twenty-five saved revisions.Reference:Time Voyager | Apstra 4.1 | Juniper Networks,Time Voyager Introduction | Apstra 4.2 | Juniper Networks,Juniper Apstra at a Glance | Flyer