Most Recent Juniper JN0-480 Exam Dumps

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, and scope 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:

A) 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.

B) 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.

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

Connectivity Templates

Data Center Automation Using Juniper Apstra

In the Juniper Apstra UI, the Resources menu allows you to create and manage global and local resources that are used for various elements of the network design and configuration. The Resources menu includes the following three types of resources that can be assigned to the network devices and virtual networks:

ASN pools: These are pools of autonomous system numbers (ASNs) that are used for the underlay routing protocol (EBGP) between the leaf and spine devices. You can create ASN pools with either 2-byte or 4-byte ASNs, and assign them to the logical devices in the blueprint.

VNI pools: These are pools of virtual network identifiers (VNIs) that are used for the overlay network (VXLAN) between the end hosts. You can create VNI pools with a range of VNIs, and assign them to the virtual networks in the blueprint.

IP address pools: These are pools of IPv4 or IPv6 addresses that are used for various purposes in the network, such as the loopback addresses for the devices, the IP prefixes for the virtual networks, the host IP addresses for the end hosts, and the gateway IP addresses for the IRB interfaces. You can create IP address pools with a range of IP addresses, and assign them to the logical devices and virtual networks in the blueprint.

The following two types of resources are not assigned under the Resources menu:

VTEP pools: These are not resources that can be created or assigned by the user. VTEPs are VXLAN tunnel endpoints that are automatically generated by the Apstra server based on the loopback IP addresses of the devices. VTEPs are used as the source and destination IP addresses for the VXLAN tunnels in the overlay network.

Logical device pools: These are not resources that can be created or assigned by the user. Logical device pools are groups of logical devices that share the same role, interface map, and resource assignments in the blueprint. Logical device pools are used to simplify the network design and configuration by applying the same settings to multiple devices.

Resources Introduction

ASN Pools (Resources)

VNI Pools (Resources)

IP Address Pools (Resources)

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

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

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 needed24.Reference:

LLDP Overview

Edit Cabling Map (Datacenter)

Generic Devices

Import / Export Cabling Map (Datacenter)

According to the Juniper documentation1, a generic system is a device that is not managed by Juniper Apstra and does not have a specific role or type assigned to it. A generic system can be used to represent a server, a firewall, a load balancer, or any other device that is not part of the fabric. In the exhibit, the device shown is a generic system, as indicated by its role, system type, and management level. Therefore, the correct answer is B. The device shown is a generic system.

According to the Juniper documentation2, a LAG is a link aggregation group that bundles multiple physical interfaces into a single logical interface. A LAG can provide increased bandwidth, redundancy, and load balancing for the network traffic. In the exhibit, the device shown has four physical interfaces that are part of a LAG, as indicated by their description and li_type. The LAG is facing the leaf pair, which are the two switches that connect to the device. Therefore, the correct answer is C. Four physical interfaces exist in a LAG facing the leaf pair.Reference:Generic Systems (Datacenter Design),Form LAG | Apstra 4.1 | Juniper Networks

According to the Juniper documentation1, a five-stage Clos architecture allows for large-scale topologies with an additional aggregation layer that interconnects multiple pods into a single fabric. A pod is a group of racks that share the same spine devices. A rack is a group of leaf devices that connect to the same servers. To create a five-stage Clos network using Juniper Apstra, you need to choose the pod-based fabric type in the template creation wizard. This will allow you to specify the number of pods, planes, spines, and leaves for your network design. Therefore, the correct answer is D. pod-based.Reference:5-Stage Clos Architecture | Apstra 4.1 | Juniper Networks