Free Practice Questions for Juniper JN0-460 Exam

When a switch is successfully onboarded into Mist Cloud but shows“Unassigned,”it means the device has been claimed into the organization but hasnot yet been assigned to a specific site.

“After claiming switches into an organization, you must assign each switch to a site for it to transition from Unassigned to Connected state and begin receiving configuration and telemetry updates.”

Option A:Incorrect — rescanning is not needed once the device is claimed.

Option B:Incorrect — reboots are unnecessary for assignment recognition.

Option C:Incorrect — these commands are for connectivity troubleshooting, not site assignment.

Option D:Correct— assigning each switch to itsintended siteenables full Mist management and connectivity state.

Abrownfield adoptionin Mist AI refers to onboarding existing Juniper switches (with existing configurations) into the Mist Cloud for management and monitoring. For the switch to connect successfully, it must be able to reach Mist Cloud services usingDNSandInternet connectivity.

“To onboard existing (brownfield) switches into Mist Cloud, the device must have outbound Internet connectivity and DNS resolution to discover Mist Cloud service endpoints.”

Option A:Correct— DNS is required for the switch to resolve Mist Cloud URLs.

Option B:Correct— Internet access is required for registration and telemetry exchange.

Option C:Incorrect — templates can be applied later but are not required for adoption.

Option D:Incorrect — Mist uses TCP ports 2200 or 443, not UDP 1280.

Wired AssurancedefinesSLEs (Service Level Expectations)to provide measurable performance indicators for wired networks. These metrics identify root causes of network degradation by monitoring switch health, connection success, and throughput performance.

“Juniper Mist Wired Assurance delivers AI-driven insights across key wired SLEs including Successful Connects, Throughput, and Switch Health, giving visibility into user experience and switch performance.”

Option A (Capacity):Incorrect — capacity is used in wireless SLEs, not wired.

Option B (Successful Connects):Correct— tracks connection success rate and anomalies.

Option C (Switch Health):Correct— monitors hardware, software, and PoE status.

Option D (Coverage):Incorrect — pertains to wireless SLEs.

Option E (Throughput):Correct— measures data transfer rate, latency, jitter, and loss.

EVPN, when used with VXLAN, leveragesBGP MPLS/VXLAN control plane mechanisms. To prevent overlapping IP prefixes between different tenants or sites, EVPN uses aRoute Distinguisher (RD).

“In EVPN-VXLAN, the route distinguisher (RD) makes routes unique when overlapping IP prefixes or MAC addresses are advertised between multiple tenants or sites.”

Option A(designated forwarder) applies to multi-homing in EVPN, not prefix uniqueness.

Option B(Layer 2 gateway) does not prevent IP overlap; it bridges VLANs.

Option D(ESI) is used for identifying multi-homed Ethernet segments, not to differentiate overlapping subnets.

Option C(Route Distinguisher) is correct, as it uniquely identifies routes even if the IP addresses are the same across sites.

During campus fabric deploymentin Mist AI, switches are onboarded usingclaim codesand must beassigned to the correct siteandonlineso that Mist can push configurations and validate connectivity.

“All switches to be included in a campus fabric must be claimed, online, and assigned to the target site before launching the Campus Fabric wizard. Mist Cloud automatically discovers their roles and builds the topology.”

Option A:Incorrect — switches must be site-assigned before fabric creation.

Option B:Correct— switches must beonlineto receive configurations from Mist.

Option C:Incorrect — offline devices cannot be configured or validated in the fabric wizard.

Option D:Correct— switches must beassigned to the correct sitefor topology creation.

Wired Assurance in Mist Cloud provides automated configuration for Juniper EX Series switches. The automation is built on open APIs and supports programmable workflows, which allow seamless integration with external systems and reduce manual configuration errors.

“Wired Assurance leverages 100% open APIs, enabling integration with third-party automation and orchestration tools. Combined with programmable workflows, this provides a consistent and scalable automation framework for switch deployment and management.”

Option A (100% open APIs): Correct — APIs enable automation and external integration.

Option C (programmable workflows): Correct — workflows automate repetitive tasks and provisioning.

Option B (client SLEs): Incorrect — this is part of user experience monitoring, not automation.

Option D (switch insights): Incorrect — this relates to telemetry and visibility, not automation.

Mistwebhooksprovide real-time integration with external systems by streamingalertsandSLE (client) metrics.

They allow automation tools to react immediately to network health or performance changes.

According to Juniper documentation, a route distinguisher (RD) is a critical address qualifier used to ensure that network layer reachability information (NLRI) remains unique within a Multiprotocol BGP (MP-BGP) control plane, especially in multitenant environments. In a service provider network, different tenants may use identical, overlapping private IP address spaces (such as 192.168.1.0/24). If these routes were advertised without a qualifier, BGP—which typically only considers the IP prefix—would treat them as the same route and potentially overwrite one with the other based on standard BGP best-path selection.

The route distinguisher solves this by prepending an 8-byte field to the tenant's IP address, effectively transforming a 32-bit IPv4 prefix into a unique 96-bit VPN-IPv4 address. This 8-byte value is typically configured in formats such as as-number:number or ip-address:number. Because the resulting VPN-IPv4 prefix is unique to that specific routing instance, the service provider's BGP infrastructure can carry and distinguish between overlapping routes from multiple customers simultaneously.

It is important to differentiate the RD from a route target (RT). While the RD's sole purpose is to provide uniqueness so that routes are not discarded or overwritten, the route target is an extended community attribute used to control the import and export of these routes into the correct virtual routing and forwarding (VRF) tables on remote PE routers. In Juniper's Junos OS, each routing instance of type vrf or evpn must have a unique RD associated with it; failing to configure a unique RD or attempting to use the same RD across different instances will result in a configuration commit failure. This fundamental separation of "making routes unique" (RD) and "directing routes to the right place" (RT) allows for the scalable, isolated multitenancy required in modern EVPN-VXLAN campus and data center fabrics.

Juniper Mist AI for Wired uses group-based policy (GBP) to enforce segmentation within a single VRF, without requiring separate VRFs per user group. GBP tags classify endpoints logically (e.g., employees, guests, IoT devices) and enforce security rules across the EVPN-VXLAN fabric.

“Group-Based Policy (GBP) provides scalable segmentation by assigning tags to endpoints based on attributes such as user type, role, or device type. These GBP tags are then used in policies to control communication between groups.”

Option A is inefficient: assigning unique tags per endpoint is not scalable.

Option C is incorrect: GBP is identity-based segmentation, not location-based.

Option D is incorrect: assigning a single tag defeats the purpose of segmentation.

Option B is correct: the best practice is to assign GBP tags based on endpoint type (e.g., servers, staff, IoT, guests), which then drives policy enforcement.

When a switch is claimed into a Mist organization, it appears in one of several states depending on connectivity and site assignment.

“After claiming, switches initially appear asUnassignedif they are not yet linked to a site. Once online and connected to Mist Cloud, they transition toConnectedstatus and begin receiving configurations and telemetry.”

Option A (Connected):Correct— indicates the switch is online and communicating with Mist Cloud.

Option B (Inactive):Incorrect — not a valid device state in Mist.

Option C (Active):Incorrect — “Active” is not a device state label in Mist.

Option D (Unassigned):Correct— indicates the switch has been claimed but not yet assigned to a site.