JN0-481 Exam dumps PDF | Exam-Dumps.net (Page: 2)

QUESTION: 9

In the Juniper Apstra UI, what are two aspects that you are able to query under the Active tab within a blueprint? (Choose two.)

ARP
Virtual Network
Routing Zone
MAC

Answer(s): A,D

Explanation:

In Apstra 5.1, the Active view represents the operational state of the deployed fabric (as opposed to the intended state being edited in Staged). Within Active, the Query function is designed for day-2 operations where an operator needs to quickly locate endpoint-related information and validate forwarding/neighbor state derived from the fabric. The query choices exposed in the UI are focused on operational lookup primitives rather than design objects. Specifically, Apstra supports querying MAC and ARP (and also VMs when virtual infrastructure integration is present).

MAC queries help identify where a Layer 2 endpoint is being learned in the fabric--useful for troubleshooting EVPN-VXLAN fabrics where MAC learning and advertisement can determine reachability and mobility behavior. ARP queries help identify IP-to-MAC bindings and validate whether hosts are being resolved correctly, which is critical when troubleshooting first-hop behavior (for example, IRB gateway adjacency, endpoint onboarding, or unexpected IP conflicts).

By contrast, "Virtual Network" and "Routing Zone" (VRF) are primarily design constructs managed in Staged and validated/assured by analytics and intent checks; they are not the direct query selectors in the Active > Query tool. Therefore, the two correct Active-query aspects from the given options are ARP and MAC.

Verified Juniper sources (URLs):

https://www.juniper.net/documentation/us/en/software/apstra5.1/apstra-user- guide/topics/task/query-active.html

Reveal Solution Next Question

QUESTION: 10

Which type of generic system should you select when adding a new server inside an existing rack type?

Internal generic
Rack generic
External generic
Embedded generic

Answer(s): A

Explanation:

In Apstra 5.1, servers that connect to leaf switches are represented as generic systems so Apstra can model links, apply connectivity templates, attach virtual networks, and validate intent. The selection of generic system type depends on whether the endpoint is considered part of the rack's internal topology or an external attachment.
When you add a new server inside an existing rack type, that server is treated as a component of the rack topology (that is, it lives "within" the rack alongside leaf switches and any other rack-internal endpoints). Apstra documentation refers to such systems as internal generic systems.

Internal generic systems are not managed like switches (no full device management), but they are first-class topology objects: they occupy ports on leaf switches, can be tagged with roles, and can be associated with link definitions that drive correct interface intent (LAG vs single link, VLAN tagging, and virtual network association). This modeling is essential in EVPN-VXLAN fabrics because correct endpoint attachment on leaf ports determines VLAN/VNI mapping and the resulting Junos v24.4 configuration rendered by Apstra.

External generic systems, by contrast, represent devices outside the rack topology (often used for external routers, firewalls, or other non-rack-contained endpoints). Because the question explicitly places the server inside an existing rack type, the correct choice is Internal generic.

Verified Juniper sources (URLs):

https://www.juniper.net/documentation/us/en/software/apstra5.1/apstra-user-guide/topics/topic- map/internal-generic-system-create.html

Reveal Solution Next Question

QUESTION: 11

You want to assign resources to your blueprint during the deployment phase. In this scenario, which statement is correct?

To assign resources in the blueprint, you must have completed the device profile and device assignments.
To assign resources in the blueprint, you must have already created them under global resources.
All resources are created and assigned under the blueprint's Resources tab.
All resources are automatically assigned values from the available resource pools.

Answer(s): D

Explanation:

In Apstra 5.1, "resources" (such as ASNs, IP addressing, and VNIs) are allocated to blueprint elements using resource pools. The blueprint does not require you to manually craft every individual resource value; instead, Apstra's workflow is to have you indicate which pool(s) should be used for the blueprint, and then Apstra automatically pulls and assigns the required values. This automation is fundamental to Apstra's intent-based model: once the blueprint knows which pools to consume, it can deterministically allocate unique values across the fabric and generate consistent Junos configuration for the assigned devices.

Option D best matches this behavior because it reflects the documented mechanism: required resources are automatically pulled from the selected pool(s) and assigned in a fast, bulk transaction. This is what enables repeatable deployments--especially in EVPN-VXLAN data center fabrics-- because resource collisions and manual tracking are avoided.

Option A is not the defining prerequisite for resource assignment; device profile and device assignment are important overall build steps, but the correctness of resource assignment is tied to pool selection and availability rather than being strictly gated by those tasks. Option B is incorrect because pools can be created and managed beyond only "global" contexts, and Apstra also supports creating additional pools from within the blueprint when needed. Option C is misleading because resources are governed by pools and allocation, not only by manual creation under a single tab.

Verified Juniper sources (URLs):

https://www.juniper.net/documentation/us/en/software/apstra5.1/apstra-user- guide/topics/concept/resources.html https://www.juniper.net/documentation/us/en/software/apstra5.1/apstra-user- guide/topics/concept/freeform-resource-management.html https://www.juniper.net/documentation/us/en/software/apstra5.1/apstra-user- guide/topics/ref/resource-pools-api.html

Reveal Solution Next Question

QUESTION: 12

In Juniper Apstra terminology, to which network operating system concept does a routing zone refer?

IRB
VRF
VLAN
Access list

Answer(s): B

Explanation:

In Apstra 5.1, a routing zone is the primary construct used to represent an L3 domain for multitenant isolation. In traditional network operating system terms, that maps to a VRF (Virtual Routing and Forwarding instance). Each routing zone is placed "in its own VRF," which provides independent routing tables and isolates IP traffic so that different tenants can reuse overlapping IP subnets without conflict. This is central to modern EVPN-VXLAN data center design, where tenants typically require clean separation of routing and policy boundaries.

Within a routing zone, you can create one or more virtual networks (often mapped to VXLAN

segments) that provide L2 extension across racks while still being contained by the tenant's VRF. If L3 gateway services are enabled for those virtual networks, their gateway interfaces (for example, IRB interfaces on Junos v24.4 leaf switches) are associated with the routing zone's VRF so that inter- subnet routing occurs within the tenant boundary.

This terminology distinction is important: an IRB is an interface construct used to provide L3 gateway functionality for a VLAN/VXLAN segment; a VLAN is a Layer 2 segmentation mechanism; and an access list is a policy enforcement tool. A routing zone, however, defines the tenant's L3 routing context, which is precisely what a VRF provides on Junos.

Verified Juniper sources (URLs):

https://www.juniper.net/documentation/us/en/software/apstra5.0/apstra-user- guide/topics/concept/routing-zones.html https://www.juniper.net/documentation/us/en/software/apstra4.2/apstra-user- guide/topics/concept/routing-zones.html

Reveal Solution Next Question

QUESTION: 13

What does clicking the indicated icon shown in the exhibit accomplish?

It refreshes the screen.
It fetches the discovered Link Layer Discovery Protocol (LLDP) data.
It erases the entire cable map to start over.
It changes the speed of existing links.

Answer(s): B

Explanation:

In Apstra 5.1, the Staged > Physical > Links workspace is where you build and validate the cabling (link) intent for the fabric before committing changes. During deployment and day-0/1 build, Apstra can leverage LLDP neighbor discovery from the connected devices to accelerate and validate the cabling map. The indicated toolbar icon in the Links view is used to fetch discovered LLDP data from the devices so Apstra can compare the discovered neighbor relationships with the intended topology and, depending on workflow, help populate or validate link endpoints.

This is particularly important in leaf-spine IP fabrics because correct physical connectivity underpins the entire underlay--interface states, point-to-point addressing, and BGP sessions. In an EVPN- VXLAN design running Junos v24.4, broken or mis-cabled links quickly manifest as missing underlay adjacencies and failed EVPN control-plane signaling. Pulling LLDP discovery into Apstra helps you identify mismatches early (wrong neighbor, wrong port, missing neighbor) and reduces manual cabling errors.

This action is not merely a UI refresh, it does not wipe the cable map, and it does not modify link speeds. Its operational purpose is to import discovered LLDP neighbor information into the blueprint's physical link view so Apstra can assist with accurate topology validation and deployment readiness.

Reveal Solution Next Question

QUESTION: 14

What is correct about the selected device shown in the exhibit?

It is a peer switch.
It is an external generic system.
It is an internal generic system.
It is an access switch.

Answer(s): C

Explanation:

The exhibit shows node100 (Generic System) selected, with links from that generic system to two fabric leaf switches (for example, a leaf participating in an ESI pair and another leaf node). In Apstra 5.1, a Generic System represents an endpoint that is not managed as a network device by Apstra (such as a server, appliance, or host), but it is still modeled so Apstra can apply interface intent (LAG vs single link), connectivity templates, and virtual network attachments.

Because the device is shown as a generic system connected on leaf-facing ports inside the fabric topology, this aligns with an internal generic system. Internal generic systems are used for servers or endpoints that reside "inside" the rack/fabric context and consume leaf switch ports as access-facing connections. This is the common representation for endpoints in EVPN-VXLAN data center designs, where the leaf switches provide the VLAN/VNI mapping and, if required, IRB gateway services within the tenant VRF (routing zone).

An external generic system is typically used for devices outside the fabric boundary--most commonly external routers, firewalls, or upstream networks attached at border leafs--where the intent is external connectivity rather than server access. The selected node is neither a peer switch nor an access switch (those are network infrastructure roles), and the UI explicitly labels it as a Generic System, confirming the correct classification as an internal generic system.

Reveal Solution Next Question

QUESTION: 15

You are using Juniper Apstra to create security policies that create ACLs on the fabric devices.
What are two valid objects that would be used within Apstra in this scenario? (Choose two.)

Virtual network
Domain name
Routing zone
Application signature

Answer(s): A,C

Explanation:

In Apstra 5.1, Security Policies express traffic-permit/deny intent between defined fabric endpoints, and Apstra compiles that intent into ACL enforcement on the appropriate switches (for example, on gateway interfaces for east-west segmentation and on border leaf interfaces for north-south controls). The objects you use to define that policy intent must correspond to fabric connectivity constructs that Apstra understands as endpoints in the blueprint's logical model.

Two such valid objects are Virtual Networks and Routing Zones. A virtual network represents a tenant segment (typically mapped into EVPN-VXLAN constructs such as VNI and associated IRB gateway when L3 is enabled). Policies between virtual networks are a common way to implement micro-segmentation or tier-based segmentation (web/app/db) within the same tenant boundary. A routing zone represents the L3 tenancy boundary (mapped to a VRF) and can be used to group and control connectivity at the tenant level, especially where policy needs to be expressed for aggregated tenant domains or for controls involving external connectivity.

"Domain name" and "application signature" are not endpoint objects for Apstra Security Policies in this context. They may exist in other security ecosystems, but Apstra's security intent model for ACL generation is based on topology and blueprint objects (routing zones, virtual networks, and endpoint definitions), which can then be rendered into Junos v24.4 firewall filterstyle enforcement on the fabric devices.

Verified Juniper sources (URLs):

https://www.juniper.net/documentation/us/en/software/apstra5.1/apstra-user-guide/topics/topic- map/policy-security.html https://www.juniper.net/documentation/us/en/software/apstra5.1/apstra-user- guide/topics/concept/routing-zones.html https://www.juniper.net/documentation/us/en/software/apstra5.1/apstra-user- guide/topics/concept/virtual-networks.html

Reveal Solution Next Question

QUESTION: 16

You want to gracefully take a device out of service to perform an OS upgrade. How would you accomplish this task using Juniper Apstra?

After selecting the device in the Staged tab, you would select Deploy Mode then Upgrade.
After selecting the device in the Active tab, you would select Deploy Mode then Drain.
After selecting the device in the Dashboard tab, you would select Deploy Mode then Upgrade.
After selecting the device in the Staged tab, you would select Deploy Mode then Drain.

Answer(s): B

Explanation:

In Apstra 5.1, the correct operational method to gracefully remove a switch from service for maintenance is to set its Deploy Mode to Drain. Drain is a day-2 operational control that tells Apstra to adjust intent so the fabric can continue operating while the targeted device is logically taken out of service as much as the design allows. This is especially relevant in EVPN-VXLAN leaf-spine fabrics where taking down a spine or a leaf can disrupt underlay BGP adjacencies and overlay reachability if traffic is not shifted first.

This action is performed from the blueprint's Active view because Drain affects the currently deployed, running fabric state (not a staged design change). Selecting the device under Active and changing Deploy Mode to Drain initiates the workflow that prepares the device for maintenance by reducing its role in forwarding and/or withdrawing dependent services according to the blueprint's modeled redundancy (for example, shifting server-facing traffic to an MLAG/ESI peer where applicable, or reducing reliance on the device for transit). After the device is drained, an OS upgrade can be performed with less impact, and the device can later be returned to service by switching Deploy Mode back to Deploy and committing the change.

The "Upgrade" action is not the deploy-mode mechanism described for graceful removal; the key is Deploy Mode Drain from Active, which is explicitly intended for maintenance and decommissioning scenarios.

Verified Juniper sources (URLs):

https://www.juniper.net/documentation/us/en/software/apstra5.1/apstra-user- guide/topics/task/device-drain.html https://www.juniper.net/documentation/us/en/software/apstra4.2/apstra-drain-mode/apstra-drain- mode-guide/topics/concept/apstra-drain-mode-activate-or-disable-drain.html

Reveal Solution Next Question

Juniper JN0-481 Exam (page: 2) Juniper Data Center, Specialist (JNCIS-DC) Updated on: 31-Mar-2026

QUESTION: 9

Explanation:

QUESTION: 10

Explanation:

QUESTION: 11

Explanation:

QUESTION: 12

Explanation:

QUESTION: 13

Explanation:

QUESTION: 14

Explanation:

QUESTION: 15

Explanation:

QUESTION: 16

Explanation:

Juniper JN0-481 Exam (page: 2)
Juniper Data Center, Specialist (JNCIS-DC)
Updated on: 31-Mar-2026