Cisco
CompTIA
ISC
EC-Council
EXIN
Fortinet
ITIL
Juniper
Microsoft
VMware
Avaya
SAP
Google
NVIDIA
Salesforce
Amazon
Palo Alto Networks
ISC2
Splunk
ServiceNow
All Vendors
  2. Home
  3. Exams
  4. Juniper
  5. JN0-480

Juniper JN0-480 Exam
Data Center, Specialist (Page 7 )

Updated On: 1-Feb-2026
Page 2 of 14
PDF with 65 Questions

Which statement is true when onboarding a Juniper Networks device using a Juniper Apstra ZTP server?

  1. The Device Key lo be used can be set In the dhcpd.conf file on the ZTP server.
  2. The State can be set In the ztp.Json file on the ZTP server.
  3. The Management IP address cannot be predetermined.
  4. The Hostname will be the serial-number of the device.

Answer(s): B

Explanation:

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, or disabled. The State indicates the current status of the device in the ZTP process. For example, if the State is ready, it means that the device is ready to be onboarded by the Apstra ZTP server. If the State is done, 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, see Apstra ZTP Configuration File.


Reference:

Apstra ZTP Configuration File
Apstra ZTP Introduction
Configure Apstra ZTP



You are adding a new switch to Juniper Apstra software. The Managed Devices page shows the "0 OS- Quarantined" status.
What is the proper next step to make the device ready for use in a blueprint?

  1. Acknowledge the device.
  2. Take the device out of maintenance mode.
  3. Install the agent for the device.
  4. Take the device out of drain state.

Answer(s): A

Explanation:

When a new switch is added to Juniper Apstra software, it initially shows the "0 OS-Quarantined" status, which means that the device is not yet managed by Apstra and has not been assigned to any blueprint. The proper next step to make the device ready for use in a blueprint is to acknowledge the device, which is a manual action that confirms the device identity and ownership. Acknowledging the device changes its status to "OOS-Ready", which means that the device is ready to be assigned to a blueprint and deployed12.


Reference:

Managing Devices
AOS Device Configuration Lifecycle



Exhibit.



Which two statements about ESI values are correct for the server connections to the fabric shown in the exhibit? (Choose two.)

  1. A valid ESI value for Server A is 0x00.00.00.00.00.00.00.00.00.00.
  2. A valid ESI value for Server B is 0x00.20.20.20.20.20.20.20.20.20.
  3. A valid ESI value for Server A is 0x00.10.10.10.10.10.10.10.10.10.
  4. A valid ESI value for Server B is 0x00.00.00.00.00.00.00.00.00.00.

Answer(s): C,D

Explanation:

To answer this question, we need to understand the concept of ESI values in EVPN LAGs. An ESI is a 10-byte value that identifies an Ethernet segment, which is a set of links that connect a multihomed device (such as a server) to one or more PE devices (such as leaf switches) in an EVPN network. The same ESI value must be configured on all the PE devices that connect to the same Ethernet segment.

This allows the PE devices to form an EVPN LAG, which supports active-active or active-standby multihoming for the device. The ESI value can be manually configured (type 0) or automatically derived from LACP (type 1) or other methods. In the exhibit, Server A is connected to two leaf switches (QFX 5210) using a LAG with LACP enabled. Server B is connected to three leaf switches (QFX 5120) using a LAG with LACP enabled. Based on this information, the following statements are correct about ESI values for the server connections to the fabric:
C) A valid ESI value for Server A is 0x00.10.10.10.10.10.10.10.10.10. This is true because this ESI value can be automatically derived from the LACP configuration on the QFX 5210 devices. The LACP system ID is usually based on the MAC address of the device, and the LACP administrative key is a 2- byte value that identifies the LAG. For example, if the MAC address of the QFX 5210 device is
00:10:10:10:10:10 and the LAG ID is 10, then the LACP system ID is 00:10:10:10:10:10 and the LACP

administrative key is 00:0A. The ESI value is then derived by concatenating the LACP system ID and the LACP administrative key, resulting in 00:10:10:10:10:10:00:0A. This ESI value can be represented in hexadecimal notation as 0x00.10.10.10.10.10.00.0A, or padded with zeros as 0x00.10.10.10.10.10.00.0A.00.00. This ESI value must be configured on both QFX 5210 devices that connect to Server A.
D) A valid ESI value for Server B is 0x00.00.00.00.00.00.00.00.00.00. This is true because this ESI value is a reserved value that indicates a single-homed device. Server B is connected to three leaf switches (QFX 5120) using a LAG, but it is not multihomed to any of them. This means that Server B does not need an ESI value to form an EVPN LAG with any of the leaf switches. Instead, Server B can use the reserved ESI value of 0x00.00.00.00.00.00.00.00.00.00, which indicates that it is a single- homed device and does not participate in any EVPN LAG. This ESI value must be configured on all three QFX 5120 devices that connect to Server B. The following statements are incorrect about ESI values for the server connections to the fabric:
A) A valid ESI value for Server A is 0x00.00.00.00.00.00.00.00.00.00. This is false because this ESI value is a reserved value that indicates a single-homed device. Server A is connected to two leaf switches (QFX 5210) using a LAG with LACP enabled, which means that it is multihomed to both of them. This means that Server A needs an ESI value to form an EVPN LAG with the leaf switches. The ESI value must be unique and non-zero for each Ethernet segment, so the reserved ESI value of 0x00.00.00.00.00.00.00.00.00.00 is not valid for Server A. B) A valid ESI value for Server B is 0x00.20.20.20.20.20.20.20.20.20. This is false because this ESI value is not derived from the LACP configuration on the QFX 5120 devices. Server B is connected to three leaf switches (QFX 5120) using a LAG with LACP enabled, but it is not multihomed to any of them. This means that Server B does not need an ESI value to form an EVPN LAG with any of the leaf switches. Instead, Server B can use the reserved ESI value of 0x00.00.00.00.00.00.00.00.00.00, which indicates that it is a single-homed device and does not participate in any EVPN LAG. The ESI value of 0x00.20.20.20.20.20.20.20.20.20 is not valid for Server B, and it may cause conflicts with other Ethernet segments that use the same ESI value.


Reference:

Ethernet Segment Identifiers, ESI Types, and LACP in EVPN LAGs Understanding Automatically Generated ESIs in EVPN Networks Ethernet Segment in EVPN: All You Need to Know



What is the function of the Revert button in the Juniper Apstra Ul?

  1. The Revert button will rollback to the previous configuration of a specified device.
  2. The Revert button deletes any uncommitted changes within Apstra.
  3. The Revert button performs a rollback 0 on Juniper devices in the fabric.
  4. The Revert button will undo the last change made to the configuration.

Answer(s): B

Explanation:

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



Which three statements describe intent-based analytics? (Choose three.)

  1. It indicates when device operating versions require updating.
  2. It is a real-time information processing pipeline.
  3. It is used to establish network performance baselines.
  4. It alerts the network operator when network performance moves away from the baseline.
  5. It collects information from vendor websites.

Answer(s): B,C,D

Explanation:

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.


Reference:

Intent-Based Analytics -- Apstra 3.3.0 documentation
What is Intent Based Networking? | Juniper Networks US



Viewing page 7 of 14
Viewing questions 31 - 35 out of 65 questions



Post your Comments and Discuss Juniper JN0-480 exam prep with other Community members:

Join the JN0-480 Discussion