Cisco ENWLSD 300-425 study plan

Cisco ENWLSD 300-425 · Give each week a clear focus.

8 weeks · About 7 hours per week

Week 1

Gather information from the existing network & Design the wireless network infrastructure

Inventory every data point a pre-design site survey must capture (AP counts and models, controller platform and code version, switch port and PoE budget, VLAN and subnet layout, RF neighborhood, client mix) and record why each drives a later design decision
Compute a per-AP client capacity and throughput budget for a mixed Wi-Fi 5/Wi-Fi 6 fleet, showing how channel width, spatial streams, and band steering change the number
Translate an AP count and PoE class table into switch port, uplink, and power-budget requirements for a given floor plan
Draft the questions you would ask a customer about growth, density, and coverage edge cases before sizing anything

A one-page site survey data-collection checklist with a worked capacity calculation for a 200-client floor

Week 2

Select controller deployment mode (appliance, virtual, cloud-managed, embedded) for three contrasting scenarios and justify each choice against scale, latency, and operational cost
Map a VLAN and subnet plan onto SSIDs, interfaces, and DHCP/DNS scope design, including management, AP, and client VLAN separation
Size the CAPWAP path: MTU, fragmentation, jumbo frames, and control versus data traffic behavior in local and flex mode
Compare local, flex, and fabric-enabled deployment for a branch with intermittent WAN, listing which features break in each mode

A design document section covering controller mode, VLAN plan, and CAPWAP sizing with a labeled topology description

Week 3

Produce an RF plan for a high-density auditorium: channel reuse, band plan, minimum data rate, and AP placement rationale
Design an N+1 controller and AP redundancy scheme and state the failover trigger, convergence time, and client impact for each layer
Explain AP and controller high-availability options (SSO, N+1, N+N, anchor fallback) and pick one per site tier
Calculate the licensing and throughput headroom needed so redundancy does not create a capacity cliff

An RF and high-availability design sheet for a two-building campus, including failover test steps

Week 4

Design a mobility architecture across three sites: decide where mobility groups, anchors, and guest tunnels belong and what happens when a link fails
Trace client roaming behavior across controllers and identify which configuration items must match for a clean roam
Document L2 versus L3 roaming tradeoffs, including subnet preservation and the effect on latency-sensitive applications
Build a failure matrix: for each of controller loss, anchor loss, and WAN loss, state the expected client experience

A mobility and redundancy failure matrix with a defended mobility-group diagram

Week 5

Design a guest access flow end to end: SSID, web authentication or sponsor approval, anchoring, and egress to the internet
Choose between anchor-based guest tunneling and local breakout, and justify the choice on security, latency, and scale
Apply guest network hardening: client isolation, ACLs, rate limiting, DNS restrictions, and separation from internal subnets
Map WLAN security policy to the 802.11 layer: WPA2/WPA3, 802.1X versus PSK, and where each fits by client type

A guest access design with an annotated traffic path from association to internet egress, plus a security control checklist

Week 6

Design an 802.1X deployment: RADIUS server group, EAP method choice, certificate strategy, and fallback for non-supplicant devices
Configure and reason about guest and BYOD onboarding, including device profiling and registration flows
Plan a location services design: which AP placement and density is required for accurate location, and how hyperlocation or BLE changes it
Specify the data path for location: which appliance or cloud service receives which feed, and how to verify accuracy targets

A security and location design brief covering 802.1X, onboarding, and a stated location accuracy target with the design choices that achieve it

Week 7

Revisit the week 4 mobility design and add location continuity requirements across sites, resolving conflicts between roaming and location accuracy
Design a migration path from an existing WLAN to the new design with zero-downtime cutover steps and rollback points
Validate the full design against the week 1 survey data and list every assumption that still needs customer confirmation
Practice writing design justifications in the format an exam scenario expects: constraint, option, decision, consequence

A consolidated design package with a phased migration runbook and a rollback plan

Week 8

Run a timed full-length practice set and log every missed item by domain and by failure mode (knowledge gap, misread, or design judgment)
Re-derive the ten calculations you are most likely to face: capacity, PoE, throughput, channel reuse, and redundancy headroom
Rewrite your weakest three design decisions from earlier weeks with the reasoning made explicit
Build a one-page recall sheet of design tradeoffs and verify each entry against your own notes rather than memorization

A scored practice result with a written remediation list, and a one-page design tradeoff recall sheet

Week 2: Can state, without notes, the pre-design data needed for any scenario and defend a controller deployment mode choice in under two minutes

Week 4: Can draw a multi-site mobility and redundancy topology from memory and predict client behavior for each single-point failure

Week 6: Can explain guest tunneling versus local breakout and the 802.1X certificate chain to a non-specialist, with the tradeoffs intact

Week 8: Scores at or above 85 percent on a timed full-length practice set, with no domain below 70 percent and every miss traced to a named cause