Juniper JN0-480 Data Center, Specialist (JNCIS-DC) Online Training

Question #11

Juniper Apstra has indicated an anomaly with respect to cabling.

What are two ways to remediate the issue? (Choose two.)

A . Manually edit the cabling map.
B . Redeploy the errant device.
C . Set the invalid ports to a disabled state.
D . Have Apstra autoremediate the cabling map using LLDP.

Reveal Solution Hide Solution

Question #12

Exhibit.

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

A . A valid ESI value for Server A is 0x00.00.00.00.00.00.00.00.00.00.
B . A valid ESI value for Server B is 0x00.20.20.20.20.20.20.20.20.20.
C . A valid ESI value for Server A is 0x00.10.10.10.10.10.10.10.10.10.
D . A valid ESI value for Server B is 0x00.00.00.00.00.00.00.00.00.00.

Reveal Solution Hide Solution

Correct Answer: C D
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. Thefollowing 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.

References:

– 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

Question #13

What is the purpose of using a routing zone inside Juniper Apstra software?

A . A routing zone is used to enable L4-L7 inspection inside the fabric.
B . A routing zone is defined to secure the routing protocols.
C . A routing zone defined at the Apstra manager level requires firewalls to be deployed.
D . A routing zone is used to enable the communication between two VNIs within a VRF.

Reveal Solution Hide Solution

Question #14

Which two statements are correct about Time Voyager? {Choose two.)

A . Time Voyager retains all of the blueprint revisions from the last Juniper Apstra backup.
B . Time Voyager retains the five most recent blueprint commits.
C . Time Voyager retains the last ten blueprint commits.
D . Time Voyager retains up to twenty-five saved revisions.

Reveal Solution Hide Solution

Question #15

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?

A . Acknowledge the device.
B . Take the device out of maintenance mode.
C . Install the agent for the device.
D . Take the device out of drain state.

Reveal Solution Hide Solution

Question #16

What does EVPN use lo identity which remote leaf device advertised the EVPN route?

A . a route distinguisher value
B . a community tag
C . a route target value
D . a VRF target value

Reveal Solution Hide Solution

Question #17

You are installing a Juniper Apstra server in your data center. You have multiple users that will be expected to configure, manage, and carry out operational tasks in your data center. You have decided to implement remote user authentication for the role-based access control of your Apstra server.

In this scenario, which three methods are supported? (Choose three.)

A . TACACS+
B . LDAP
C . RADIUS
D . SAML
E . Auth0

Reveal Solution Hide Solution

Question #18

You want to make a widget appear on the main dashboard in Juniper Apstra. In this scenario, which statement is correct?

A . When creating the widget, select the Add to Blueprint Dashboard option.
B . On the blueprint dashboard, click on the Add Widget option.
C . Widgets automatically appear on the blueprint dashboard.
D . Set the Default toggle switch to On for the desired widget.

Reveal Solution Hide Solution

Correct Answer: B
B

Explanation:

In Juniper Apstra, a widget is a graphical element that displays data from an intent-based analytics (IBA) probe. A widget can be used to monitor different aspects of the network and raise alerts to any anomalies. A widget can be viewed by itself or added to an analytics dashboard. A dashboard is a collection of widgets that can be customized and organized according to the user’s preference1.

The main dashboard in Juniper Apstra is the blueprint dashboard, which is the default view that shows the network information and configuration for the active blueprint. A blueprint is a logical representation of the network design and intent. The blueprint dashboard can display the system-generated dashboards, the user-generated dashboards, and the individual widgets that are relevant to the network2.

To make a widget appear on the main dashboard in Juniper Apstra, the user needs to set the Default toggle switch to On for the desired widget. This will add the widget to the blueprint dashboard, where it can be viewed along with other network information. The user can also remove the widget from the blueprint dashboard by setting the Default toggle switch to Off for the widget3. Therefore, the statement D is correct in this scenario.

The following three statements are incorrect in this scenario:

– When creating the widget, select the Add to Blueprint Dashboard option. This is not true, because there is no such option when creating a widget in Juniper Apstra. The user can only select the widget type, the probe, and the display mode when creating a widget4. To add the widget to the blueprint dashboard, the user needs to set the Default toggle switch to On for the widget after creating it3.

– On the blueprint dashboard, click on the Add Widget option. This is not true, because there is no such option on the blueprint dashboard in Juniper Apstra. The user can only view, edit, or delete the existing widgets and dashboards on the blueprint dashboard2. To add a widget to the blueprint dashboard, the user needs to set the Default toggle switch to On for the widget from the widgets table view3.

– Widgets automatically appear on the blueprint dashboard. This is not true, because widgets do not automatically appear on the blueprint dashboard in Juniper Apstra. The user needs to manually add the widgets to the blueprint dashboard by setting the Default toggle switch to On for the widgets that they want to see on the blueprint dashboard3. The only exception is the widgets that are part of the system-generated dashboards, which are automatically created and added to the blueprint dashboard based on the state of the active blueprint2.

References:

– Widgets Overview

– Blueprint Summaries and Dashboard

– Widgets Introduction

– Create Widget

Question #19

In the Juniper Apstra Ul. which two resource types would be created in the Resources menu? (Choose two.)

A . bridge domain identifier (BDI)
B . DHCP pools
C . ASN pools
D . IP pools

Reveal Solution Hide Solution

Question #20

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.

Reveal Solution Hide Solution

Correct Answer: B
B

Explanation:

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