JNCDS-WAN study plan

Break the published blueprint into a weighted tracker that logs hours and confidence per objective

Distinguish business, technical, and operational constraints using three contrasting customer scenarios

Draft discovery questions that surface growth, budget, compliance, and timeline constraints before any topology is chosen

Translate one messy scenario into a structured requirements document separating must-haves from nice-to-haves

Map each captured requirement to a concrete design decision and note the trade-off it forces

Identify which requirements create security obligations early, before topology selection

Compare placing enforcement at the SRX gateway, at the access layer, or both, and justify one choice per site class

Write acceptance criteria that a design could be tested against after deployment

Design zone-based segmentation for a branch with guest, corporate, IoT, and voice traffic

Choose between route-based and policy-based IPsec for hub-and-spoke and for full mesh, and justify each

Lay out a policy matrix that states which zones may talk, on which ports, and where logging happens

Size and place security services so encrypted traffic paths do not create asymmetric routing

Design a redundant topology using Virtual Chassis at the access layer and redundant WAN edges at the branch

Choose OSPF, BGP, or static routing per site tier and state the convergence expectation for each

Define the management plane: which platform handles onboarding, monitoring, and configuration backup, and what happens when it is unreachable

Specify ZTP and telemetry so a new branch can be brought up without a truck roll

Design a campus switching hierarchy that states port counts, uplink oversubscription, and stacking or fabric choices per building

Build a VLAN and subnet plan sized for the next three years of growth

Calculate a PoE budget per closet and flag any switch that cannot cover worst-case draw

Wire 802.1X and guest onboarding into the access design, naming the enforcement point and fallback behavior

Compare MPLS, internet with IPsec overlay, and an SD-WAN overlay across cost, SLA, and operational effort

Design the branch WAN edge so application traffic is steered by policy rather than by default route only

Size WAN links from measured or estimated busy-hour demand and state the oversubscription assumption

Define QoS classes end to end and identify where marking, queuing, and policing occur

Design an IP fabric underlay with a documented addressing and routing scheme

Layer EVPN-VXLAN over that fabric and explain where Layer 2 ends and Layer 3 begins

Choose between multichassis aggregation and an EVPN-based approach for server dual-homing, and justify it

Integrate the data center with the WAN edge, showing where policy is enforced and how failure is contained

Re-run the weakest three objectives from the tracker and close each gap with a written explanation

Reconcile every earlier deliverable so the whole design set tells one consistent story

Take a full timed mock exam and classify each wrong answer as a knowledge gap or a reading error

Build a one-page recall sheet of the facts most often missed