JNCIA-Junos study plan

Diagram a packet's path from client to server across a switched and routed topology, labeling the decision made at each OSI layer

Differentiate collision domains, broadcast domains, and subnet boundaries, and predict how adding a switch or router changes each

Contrast the Junos control plane and forwarding plane, naming which processes and tables live in each

Distinguish the roles of the Routing Engine and Packet Forwarding Engine when a route changes

Navigate the CLI without notes: operational vs configuration mode, command completion, context-sensitive help, and pipe filters

Build a complete configuration from factory default covering hostname, interfaces, static routes, user accounts, NTP, and syslog

Execute the candidate-config workflow end to end: edit, show | compare, commit check, commit confirmed, and commit

Recover deliberately from an uncommitted and a committed mistake using rollback 0, rollback 1, and compare

Apply configuration groups, interface ranges, and annotations, then verify how inherited values appear in the active config

Load, save, and merge configuration files, and explain the difference between load merge, load replace, and load override

Rank candidate routes using longest-match, then preference, then metric, and justify the active route chosen for six given prefixes

Configure and verify static routes including qualified-next-hop, discard, reject, and a default route

Read show route output field by field and explain what each column and flag means

Distinguish interior from exterior gateway protocols and describe the operational role of OSPF areas and BGP peer types at a conceptual level

Differentiate a routing table from a forwarding table and describe when each is populated

Trace the order of policy evaluation for import and export, and state which direction each protocol applies policies in

Write match conditions and actions with correct term ordering, correct default action, and awareness of the implicit deny

Construct a policy that redistributes static routes into OSPF with a tag and a modified metric

Predict the outcome of overlapping terms on five sample routes before applying them

Verify policy behavior operationally using show commands and route detail output

Build a stateless firewall filter whose terms match on source, destination, protocol, and port, and apply it to both an interface and the loopback

Explain and demonstrate the difference between a firewall filter and a policer, then apply a policer to a term

Predict counter increments for a three-term filter before sending traffic, then compare prediction to observed counters

Distinguish stateless filter behavior from stateful zone-based security concepts and identify which the Junos filter does not do

Place filters correctly for transit, local, and loopback traffic and explain why the loopback filter matters

Monitor device health using interface statistics, chassis alarms, log messages, and traceoptions, and interpret each output

Perform recovery tasks: password recovery, rescue configuration, configuration snapshot, and return to factory default

Use file system commands to list, copy, rename, and delete files, and verify storage with the relevant show commands

Interpret syslog severity levels and message structure and map a message to its likely cause

Describe the software upgrade workflow and how to verify success afterward

Re-drill every item on the missed-question list from weeks 1-6 until each is answered correctly twice in a row

Build one integrated lab combining OSPF, a static route, an export policy, and an interface filter

Diagnose why traffic is dropped by determining whether the cause is route selection, policy rejection, or filter discard

Complete 40 timed practice questions on routing fundamentals and policy, then categorize every error by root cause

Explain aloud, without notes, how a policy and a filter interact on the same traffic flow

Take two full-length timed practice exams under exam conditions and score each by domain

Rank domains by practice-exam accuracy and spend remaining time only on the two weakest

Re-verify the highest-risk commands and configuration syntax from memory on a blank device

Consolidate all missed items across eight weeks into a single final review sheet and clear it