JNCIS-MistAI-Wired study plan

Map each layer-2 concept tested by the exam (VLANs, trunking, 802.1Q tagging, spanning tree variants, link aggregation) to a one-line definition you can recite without notes

Draw from memory the packet-walk of a frame crossing an access port, an 802.1Q trunk, and a LAG bundle, labeling where tags are added and stripped

Configure two VLANs, an 802.1Q trunk, and a LACP bundle on lab switches and verify forwarding with show commands

Differentiate RSTP, STP, and MSTP port roles and convergence behavior well enough to predict which port blocks in a given topology

Explain how a Mist-supported switch is adopted, what the claim code does, and which states a switch passes through from unclaimed to connected

Describe how switch configuration is derived from site settings, templates, and per-port profiles, and predict which layer wins when they conflict

Configure PoE budgets, port profiles, and trunk/access assignments for a mixed wired/wireless closet in the lab

Compare static, LACP, and LAG behavior on uplinks and justify which to choose for a given closet topology

Identify how LLDP and MAC-derived data feed the Mist cloud inventory and why that matters for visibility

Set up a Mist organization, site, and switch template from scratch and document each step with screenshots or notes

Configure switch-level and port-level settings through the dashboard, then apply the same intent via site templates and confirm the result

Build port profiles for access, trunk, and AP uplink use cases and reuse them across multiple switches

Validate that a newly adopted switch inherits the intended configuration and explain any drift you observe

Configure and verify a Mist edge/cloud connection path for a switch, including what happens when the cloud is unreachable

Use the dashboard switch insights, port statistics, and event logs to answer three troubleshooting scenarios you invent

Explain how firmware upgrade policies work and stage a controlled upgrade on a lab switch

Interpret PoE negotiation and power-budget alarms and resolve one simulated over-budget condition

Trace a wired client through the client page: MAC learning, VLAN assignment, DHCP, and authentication state

Configure 802.1X or MAC-based access on a switch port and read the resulting authentication events

Use Marvis or the AI-driven insights to diagnose a simulated port-down or flapping-link issue, and verify the recommendation against raw logs

Distinguish symptoms of a physical layer fault, a VLAN mismatch, and a spanning tree loop by the evidence each leaves

Build a short list of the metrics you would watch for proactive wired monitoring and where each lives in the UI

Use the Mist REST API to list sites, read switch statistics, and pull port configuration with an API token

Script a bulk port-profile update across several switches and verify the change in the dashboard

Explain webhook subscriptions and configure one to receive switch events into a local listener

Describe how Mist integrates with NAC or RADIUS and where the switch sits in that flow

Compare API-driven configuration against template-driven configuration and state when each is appropriate

Automate a recurring operational task such as pulling port error counters or auditing VLAN consistency across closets

Design an alerting rule set that surfaces real wired problems without flooding, and justify each rule

Re-run your week 5 diagnostic tree using only API and automation outputs to confirm it still holds

Document an escalation path from automated alert to dashboard investigation to resolution

Review every domain against your own notes and close the gaps you flagged in weeks 1 through 7

Complete timed practice sets weighted to your weakest domain and log every miss with the underlying concept

Re-teach the three concepts you got wrong most often out loud or in writing until you can explain them cleanly

Walk through a full end-to-end scenario: design a closet, deploy it, troubleshoot a fault, and automate a check