Juniper JN0-480 Online Practice Questions and Exam Preparation

Juniper JN0-480 Online Questions & Answers

• Question 1:

  Which two statements about VXLAN VNIs are correct? (Choose two.)

  A. VNIs can have over 16 million unique values.
  B. VNIs identify a collision domain.
  C. VNIs identify a broadcast domain
  D. VNIs are alphanumeric values.
  A. VNIs can have over 16 million unique values.
  C. VNIs identify a broadcast domain

  ---

  Explanation/Reference:

  VXLAN VNIs are virtual network identifiers that are used to identify and isolate Layer 2 segments in the overlay network. VXLAN VNIs have the following characteristics:

  VNIs can have over 16 million unique values. This is because VXLAN VNIs are 24- bit fields that can range from 4096 to 16777214, according to the VXLAN standard. This allows VXLAN to support a large number of Layer 2 segments and

  tenants in the network.

  VNIs identify a broadcast domain. This is because VXLAN VNIs are used to group the end hosts that belong to the same Layer 2 segment and can communicate with each other using VXLAN tunnels. The VXLAN tunnels are established

  using the VTEP information that is distributed by EVPN. The VTEPs are VXLAN tunnel endpoints that perform the VXLAN encapsulation and decapsulation. The VXLAN tunnels preserve the Layer 2 semantics and support the broadcast,

  unknown unicast, and multicast traffic within the same VNI2. The following two statements are incorrect in this scenario:

  VNIs identify a collision domain. This is not true, because VXLAN VNIs do not identify a collision domain, which is a network segment where data packets can collide with each other. VXLAN VNIs identify a broadcast domain, which is a

  network segment where broadcast traffic can reach all the devices. Collision domains are not relevant in VXLAN networks, because VXLAN uses MAC-in-UDP encapsulation and IP routing to transport the Layer 2 frames over the Layer 3

  network.

  VNIs are alphanumeric values. This is not true, because VXLAN VNIs are numeric values, not alphanumeric values. VXLAN VNIs are 24-bit fields that can range from 4096 to 16777214, according to the VXLAN standard. Alphanumeric

  values are values that contain both letters and numbers, such as ABC123 or 1A2B3C.

  References:

  Virtual Extensible LAN (VXLAN) Overview

  EVPN LAGs in EVPN-VXLAN Reference Architectures

• Question 2:

  Which two statements are correct about repairing a Juniper Apstra cabling map before deploying your blueprint? (Choose two.)

  A. You must manually change the cabling map to update spine-to-leaf fabric links.
  B. Apstra can use LLDP data from the spine-to-lea! fabric devices to update the connections in the cabling map.
  C. Apstra can use LLDP data from the leaf devices to update the leaf-to-generic connections in the cabling map.
  D. You must manually change the cabling map to update leaf-to-generic links.
  B. Apstra can use LLDP data from the spine-to-lea! fabric devices to update the connections in the cabling map.
  C. Apstra can use LLDP data from the leaf devices to update the leaf-to-generic connections in the cabling map.

  ---

  Explanation/Reference:

  The cabling 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 cabling map to verify and repair the cabling before deploying your blueprint. Based on the web search results, we can infer the following statements: Apstra can use LLDP data from the spine-to-leaf fabric devices to update the connections in the cabling map. This is true because Apstra can collect LLDP data from the devices using the Generic Graph Collector processor and use it to update the cabling map automatically. LLDP is a protocol that allows devices to exchange information about their identity, capabilities, and neighbors. Apstra can use LLDP data from the leaf devices to update the leaf-to-generic connections in the cabling map. This is true because Apstra can also collect LLDP data from the leaf devices and use it to update the connections to the generic devices, such as routers, firewalls, or servers. Generic devices are devices that are not managed by Apstra but are part of the data center fabric. You must manually change the cabling map to update spine-to-leaf fabric links. This is false because Apstra can use LLDP data to update the spine-to-leaf fabric links automatically, as explained above. However, you can also manually change the cabling map to override the Apstra-generated cabling, if needed24. You must manually change the cabling map to update leaf-to-generic links. This is false because Apstra can use LLDP data to update the leaf-to-generic links automatically, as explained above. However, you can also manually change the cabling map to override the Apstra-generated cabling, if needed. References: LLDP Overview Edit Cabling Map (Datacenter) Generic Devices Import / Export Cabling Map (Datacenter)

• Question 3:

  When working with logical devices, you specify where each port group is connected.

  In thisscenario, which two Juniper Apstra Ul options are available to the operator? {Choose two.)

  A. router
  B. unused
  C. generic
  D. firewall
  B. unused
  C. generic

  ---

  Explanation/Reference:

  When working with logical devices, you specify where each port group is connected by selecting the port group layout and the port speed and role (s) for each port group. The Juniper Apstra UI offers two options to the operator for the port

  group role: unused and generic.

  Unused: This option means that the port group is not configured or used by Apstra. This can be useful for ports that are faulty, reserved, or not part of the data center fabric.

  Generic: This option means that the port group is configured with a generic role that is not specific to any device type or function. This can be useful for ports that are used for testing, troubleshooting, or custom purposes.

  References:

  Logical Devices

• Question 4:

  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?

  A. You have misconfigured ASNs.
  B. The fabric has not converged yet.
  C. Spine-leaf links are incorrectly set.
  D. A generic system has not been configured.
  B. The fabric has not converged yet.

  ---

  Explanation/Reference:

  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. Therefore, the statement B is the most likely cause of these anomalies in this scenario. The following three statements are less likely causes of these anomalies in this scenario: You have misconfigured ASNs. This is possible, but not very likely, because Juniper Apstra provides ASN pools that can be automatically assigned to the devices based on their roles. You can also manually specify the ASNs for the devices, but you need to ensure that they are unique and consistent with the network design. If you have misconfigured ASNs, you may see some anomalies related to BGP, but they will not disappear after the network converges. You will need to fix the ASNs and commit the changes again to resolve the anomalies. Spine-leaf links are incorrectly set. This is possible, but not very likely, because Juniper Apstra provides connectivity templates that can be used to define the spine-leaf links based on the interface maps. You can also manually specify the spine-leaf links, but you need to ensure that they are correct and match the physical cabling. If you have incorrectly set the spine-leaf links, you may see some anomalies related to BGP, but they will not disappear after the network converges. You will need to fix the spine-leaf links and commit the changes again to resolve the anomalies. A generic system has not been configured. This is not relevant, because a generic system is a device that is not managed by Juniper Apstra, but is connected to the network. A generic system does not affect the BGP sessions between the devices that are managed by Juniper Apstra. If you have a generic system in your network, you need to configure it manually and ensure that it is compatible with the network design. A generic system does not cause any anomalies related to BGP in the main dashboard. References: Blueprint Summaries and Dashboard BGP Session Flapping Probe Probe: BGP Session Monitoring

• Question 5:

  You use Juniper Apstra to enable a new VXLAN virtual network.

  Which two components would be automatically derived in this situation? (Choose two.)

  A. IP subnet
  B. VLAN-ID
  C. VXLAN VNI
  D. Route Zone
  A. IP subnet
  C. VXLAN VNI

  ---

  Explanation/Reference:

  According to the Juniper documentation, a VXLAN virtual network is a collection of Layer 2 forwarding domains that span multiple racks in a fabric. A VXLAN virtual network requires a name and a VXLAN network identifier (VNI), which is a 24-bit number that identifies the virtual network. The VNI can be either explicitly assigned or auto- assigned from a resource pool. A VXLAN virtual network can also have Layer 3 connectivity, which enables routing between different VNIs within a routing zone. A routing zone is an L3 domain that isolates the IP traffic of different tenants. A routing zone can have one or more VNIs associated with it. To enable Layer 3 connectivity, a VXLAN virtual network needs an IP subnet, which is a range of IP addresses that can be assigned to the hosts in the virtual network. The IP subnet can be either explicitly assigned or auto- assigned from a resource pool. Therefore, the correct answer is A and C. IP subnet and VXLAN VNI are two components that would be automatically derived when enabling a new VXLAN virtual network using Juniper Apstra. References: Virtual Networks | Apstra 4.1 | Juniper Networks

• Question 6:

  Exhibit.

  

  You are working to build an ESI-LAG for a multihomed server. The ESI-LAG is not coming up as multihomed.

  Referring to the exhibit, what are two solutions to this problem? (Choose two.)

  A. The gateway IP addresses on both devices must be different.
  B. The LACP system ID on both devices must be the same.
  C. The loopback IP addresses on both devices must be the same.
  D. The ESI ID on both devices must be the same.
  B. The LACP system ID on both devices must be the same.
  D. The ESI ID on both devices must be the same.

  ---

  Explanation/Reference:

  According to the Juniper documentation, an ESI-LAG is a link aggregation group (LAG) that spans two or more devices and is identified by an Ethernet segment identifier (ESI). An ESI-LAG provides redundancy and load balancing for a multihomed server in an EVPN-VXLAN network. To configure an ESI-LAG, you need to ensure that the following requirements are met: The LACP system ID on both devices must be the same. This ensures that the LACP protocol can negotiate the LAG parameters and form a single logical interface for the server. The ESI ID on both devices must be the same. This ensures that the EVPN control plane can advertise the ESI-LAG as a single Ethernet segment and synchronize the MAC and IP addresses of the server across the devices. The VLAN ID and VNI on both devices must be the same. This ensures that the server can communicate with other hosts in the same virtual network and that the VXLAN encapsulation and decapsulation can work properly. In the exhibit, the LACP system ID and the ESI ID on both devices are different, which prevents the ESI-LAG from coming up as multihomed. Therefore, the correct answer is B and D. The LACP system ID on both devices must be the same and the ESI ID on both devices must be the same. References: ESI-LAG Made Easier with EZ-LAG, Example: Configuring an ESI on a Logical Interface With EVPN-MPLS Multihoming, Introduction to EVPN LAG Multihoming

• Question 7:

  Exhibit.

  

  The 10.100.0.0/16 route is being advertised into your BGP IP fabric. ECMP load balancing has been properly enabled on all devices

  In this scenario, how many routes will the leaf device in AS 65000 receive for the 10.100.0.0/16 prefix?

  A. 3
  B. 1
  C. 2
  D. 4
  A. 3

  ---

  Explanation/Reference:

  The leaf device in AS 65000 will receive three routes for the 10.100.0.0/16 prefix, one from each spine device in AS 65001, AS 65002, and AS 65003. Since ECMP load balancing is enabled, the leaf device will install all three routes in its

  routing table and distribute the traffic among them. The other options are incorrect because:

  1 is wrong because the leaf device will not receive only one route for the prefix. It will receive multiple routes from different spine devices and use ECMP to load balance among them.

  2 is wrong because the leaf device will not receive only two routes for the prefix. It will receive three routes from three spine devices, as explained above. D. 4 is wrong because the leaf device will not receive four routes for the prefix. It will

  receive three routes from three spine devices, as explained above. The fourth spine device in AS 65004 is not directly connected to the leaf device and will not advertise the prefix to it.

  References:

  IP Fabric Underlay Network Design and Implementation BGP Multipath load sharing iBGP and eBGP

  ECMP Load Balancing

• Question 8:

  In Juniper Apstra. which statement is correct?

  A. VMware anomaly detection is on by default.
  B. VMware anomaly detection requires a vCenter server configured under External Systems
  C. VMware anomaly detection requires a VMware hypervisor with exports enabled.
  D. VMware anomaly detection requires an Apstra server running on VMware.
  B. VMware anomaly detection requires a vCenter server configured under External Systems

  ---

  Explanation/Reference:

  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. References: VMware vCenter/vSphere Virtual Infra Anomalies (Service) A Better Experience: VMware + Juniper Apstra

• Question 9:

  Which two statements are correct regarding a pristine configuration in Juniper Apstra? (Choose two.)

  A. It is the configuration file placed on the device when decommissioning the device.
  B. It is the device's currently active configuration.
  C. It Is the configuration file on a device before acknowledgment in Apstra.
  D. It is the device's previously active configuration.
  A. It is the configuration file placed on the device when decommissioning the device.
  C. It Is the configuration file on a device before acknowledgment in Apstra.

  ---

  Explanation/Reference:

  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 network.

  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, thedevice 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 application. 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 intent.

  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 commit.

  References:

  Pristine Config

  Decommission Device Device States

• Question 10:

  You must configure a static route for traffic to exit a configured routing zone. In the Juniper Apstra Ul. where would you accomplish this task?

  A. under Active -> Virtual -> Routing Zones
  B. under Staged -> Virtual -> Routing Zones
  C. under Active -> Connectivity Templates
  D. under Staged -> Connectivity Templates
  D. under Staged -> Connectivity Templates

  ---

  Explanation/Reference:

  To configure a static route for traffic to exit a configured routing zone, you need to use the Connectivity Templates feature in the Juniper Apstra UI. A Connectivity Template is a set of configuration parameters that can be applied to a device or a group of devices in a blueprint. You can use Connectivity Templates to configure static routes, BGP, OSPF, and other network services. To create a Connectivity Template, you need to go to the Staged tab and select Connectivity

  Templates from the left menu. Then, you can click on the + icon to create a new template. You can specify the name, description, andscope of the template. The scope determines which devices or device groups the template will be applied

  to. You can also specify the order of the template, which determines the priority of the template when multiple templates are applied to the same device. After creating the template, you can add configuration items to the template. To add a

  static route, you need to select Static Route from the drop-down menu and enter the destination network, subnet mask, and next-hop IP address. You can also specify the administrative distance and the track object for the static route. After

  adding the configuration items, you need to save the template and commit the changes to the blueprint. The other options are incorrect because:

  under Active -> Virtual -> Routing Zones is wrong because this option allows you to view and modify the existing routing zones, but not to configure static routes for them.

  under Staged -> Virtual -> Routing Zones is wrong because this option allows you to create and delete routing zones, but not to configure static routes for them.

  under Active -> Connectivity Templates is wrong because this option allows you to view the existing connectivity templates, but not to create or modify them.

  References:

  Connectivity Templates

  Data Center Automation Using Juniper Apstra