A company is planning to decommission a few old switches that are no longer under support. The admin wants to remove them from Mist to keep the inventory accurate. What is the correct way to remove a switch from the Mist organization?

Disable the switch in the configuration template.

Delete the switch from the inventory page in the Mist portal.

Wait for the switch to be automatically removed after a period of inactivity.

Unassign the switch from its site and leave it in the inventory.

In Mist, how are VLANs typically created and managed on switches?

Through the Mist portal or API, and applied via templates or port profiles

By editing the switch configuration file directly

By manually configuring each switch via SSH

By using a third-party VLAN management tool

Where can an administrator view the inventory of all switches in the Mist organization?

In the 'Site Configuration' section

In the 'Inventory' section of the Mist portal

An organization is deploying a new VoIP system and needs to ensure that voice traffic is prioritized over data traffic on the access switches. The admin wants to configure QoS settings for the voice VLAN. What is the best way to do this using Mist?

Configure QoS globally on the switch using the configuration template.

Create a port profile for voice ports and enable QoS with DSCP marking for the voice VLAN.

Use the switch's default QoS settings and rely on the phone to mark traffic.

Set the voice VLAN as the native VLAN on all ports.

An organization has a fleet of EX2300 switches that are running an outdated firmware version. The admin wants to upgrade all switches to a newer, recommended firmware version to address security vulnerabilities. The admin wants to minimize disruption and ensure the upgrade is successful. What should the admin do?

Upgrade only the switches that are in production, leaving test switches on the old firmware.

Use the Mist 'upgrade all' button and monitor the progress.

Upgrade a few switches first, verify they are stable, then upgrade the rest.

Upgrade all switches simultaneously using Mist's firmware upgrade feature.

Juniper NetworksCertified Specialist, Mist AI Wired (JNCIS-MistAI)

Domain 3Objective 1

Managing Switches JN0-460 Practice Questions (Page 5)

Part of the Wired Assurance Management or Operations domain, which makes up ~24% of our current practice bank. Juniper Networks does not publish an official question count, but from its 90-minute exam (~35–60 total, ~8–14 in this domain), expect 1–2 from this objective — we provide 31 practice questions to prepare you well beyond it. (estimate)

31questions here

7free pages

8concepts

Questions 21–25

21application · medium
A company is planning to decommission a few old switches that are no longer under support. The admin wants to remove them from Mist to keep the inventory accurate. What is the correct way to remove a switch from the Mist organization?
Select an answer first
22foundation · easy
In Mist, how are VLANs typically created and managed on switches?
Select an answer first
23foundation · easy
Where can an administrator view the inventory of all switches in the Mist organization?
Select an answer first
24expert · hard
An organization is deploying a new VoIP system and needs to ensure that voice traffic is prioritized over data traffic on the access switches. The admin wants to configure QoS settings for the voice VLAN. What is the best way to do this using Mist?
Select an answer first
25application · medium
An organization has a fleet of EX2300 switches that are running an outdated firmware version. The admin wants to upgrade all switches to a newer, recommended firmware version to address security vulnerabilities. The admin wants to minimize disruption and ensure the upgrade is successful. What should the admin do?
Select an answer first

Finished these 5 questions?

Review the revealed explanations, or continue through the curriculum.

Next 5 questions →Back to JN0-460

Free Basic Practice is a study aid with revealable answers — not a scored exam. Examers.io is independent and not affiliated with or endorsed by Juniper Networks. “JN0-460” is a trademark of its owner, used for identification only.