Someone preparing for Cisco ENCOR with a course recorded in 2024 can spend many hours studying access-point discovery, wireless roaming, and controller authentication. Those subjects matter in enterprise wireless engineering, but they are no longer the right priority for the current ENCOR core exam. Cisco moved the wireless objectives out of the 350-401 v1.2 blueprint effective March 19, 2026. The exam still addresses wide-area networking through Cisco Catalyst SD-WAN, so the practical challenge is to separate what remains in the core from what now belongs in dedicated wireless study.<\/p>\n
The current 350-401 ENCOR<\/a> architecture objective asks candidates to explain the working principles of Catalyst SD-WAN, including control- and data-plane elements plus benefits and limitations. It does not ask them to configure an entire Catalyst SD-WAN deployment or troubleshoot wireless client association as a core wireless objective. This article explains that boundary, then develops the network reasoning needed to interpret an SD-WAN design without carrying obsolete exam assumptions forward.<\/p>\n A conventional WAN might use private circuits, site-to-site VPNs, and per-router routing policy to connect headquarters, branches, and cloud services. As an enterprise grows, maintaining similar policy at dozens of sites can become difficult. User traffic also becomes more diverse: branch employees access SaaS platforms directly, reach applications in multiple cloud regions, and continue to use internal systems behind corporate boundaries. A design that backhauls every packet through one data center may create unnecessary delay or a large failure domain.<\/p>\n An SD-WAN architecture separates the concerns of transport reachability, overlay control, central policy, and traffic forwarding. Multiple physical or provider networks can provide transport, while the overlay creates a logical communication structure between participating sites. The system can make transport choices according to policy and available path information, subject to the product’s capabilities and configuration. It is not magic bandwidth. If all provider paths are failing, overlay policy cannot create healthy transport from nothing.<\/p>\n Ask which application the branch is trying to reach, which paths are available, where security inspection occurs, and what happens when an underlay path degrades rather than fully fails. An answer that states only \u201cSD-WAN uses the internet instead of MPLS\u201d misses the central architecture decisions.<\/p>\n Management functions help operators define intent, monitor the estate, and coordinate changes across sites. Control-plane functions distribute information that participating nodes need for overlay reachability and policy. Data-plane functions carry the actual application packets along the selected transport paths. These roles are conceptually separate even when the deployed components and high-availability arrangements differ across designs.<\/p>\n Cisco’s current naming is worth using consistently. Older learning materials may say vManage, vSmart, and vBond; the modern equivalents are called SD-WAN Manager for management, SD-WAN Controller for overlay control, and SD-WAN Validator for connection onboarding. A candidate should recognize legacy names when reading existing diagrams but describe the present architecture with the newer labels. Cisco’s revision notes also changed the umbrella product name from Cisco SD-WAN to Cisco Catalyst SD-WAN.<\/p>\n An operations question exposes why the planes matter. If centralized management becomes unavailable, existing forwarding may continue according to established state, depending on the actual failure and deployment. If an overlay control relationship fails, route or policy updates may be affected even while underlay links remain up. If a branch edge loses its transport interface, packets cannot flow over that path regardless of management status. The engineer must identify the failed plane before prescribing a remedy.<\/p>\n Traditional routing selects paths according to protocol decisions and installed forwarding information. SD-WAN adds an overlay policy context that can consider application requirements and measured transport behavior. The difference is not absolute: routing remains part of both the underlay and participating devices. SD-WAN uses those foundations rather than replacing IP forwarding.<\/p>\n Consider a regional office with two broadband providers and a private circuit. A voice application may be sensitive to delay variation and loss, while nightly backups tolerate delay but demand capacity. A policy could prefer different paths for those classes, but only if the infrastructure collects the necessary quality indicators and has suitable viable alternatives. A poorly chosen threshold could cause traffic to flap between links, harming the very service the policy was intended to protect.<\/p>\n Designers should also consider symmetry and stateful inspection. Sending forward and return traffic through different security enforcement points can break some sessions. If the branch has direct internet egress, the security design must account for it; centralization of routing policy does not automatically centralize inspection. Performance claims are credible only when tied to measured application behavior and clear path assumptions.<\/p>\n Central configuration and overlay policy can reduce repetitive device work, but they introduce control, management, and certificate dependencies that must be operated reliably. Branch equipment may need secure onboarding, compatible software, sufficient processing capacity for encapsulation and encryption, and predictable connectivity to required services. A design dependent on one overloaded edge or unsuitable provider path can remain fragile despite sophisticated policy controls.<\/p>\n Troubleshooting can also become more layered. The engineer may need to distinguish physical link health, underlay routing, tunnel establishment, overlay route learning, application policy, and security filtering. A dashboard that says a tunnel is \u201cup\u201d does not mean all applications work. The business question is whether the expected traffic reaches its destination with the required quality and protection.<\/p>\n Cost analysis should include operational complexity, licensing, branch lifecycle work, security integration, and provider diversity, not just the price of the WAN links. SD-WAN is particularly useful when its central policy and transport flexibility match a genuine distributed-enterprise need. It is not a reason to abandon a stable design for a small, simple site without a corresponding benefit.<\/p>\n Cisco’s v1.1-to-v1.2 release notes removed objectives that covered wireless network design principles, WLAN deployment models, location services, client density, radio-frequency fundamentals, access-point modes, access-point discovery and join, roaming, wireless client troubleshooting, wireless segmentation, and specific wireless-security tasks. The update also removed wireless framing from certain QoS material. These are important changes because training platforms and older articles may still display them beside ENCOR topics.<\/p>\n A candidate should not respond by deleting all wireless knowledge from their career plan. Enterprise networking still involves wireless users, and a campus architect must understand how wired infrastructure supports wireless services. The distinction concerns the current exam’s assessed objectives. Practical context may remain useful, but spending scarce ENCOR preparation time on omitted WLAN tasks at the expense of infrastructure, security, or automation is a poor allocation.<\/p>\n Existing material on wireless LAN controllers<\/a> remains valuable for engineers whose responsibilities actually include WLANs. It should be labeled as specialist or legacy-to-ENCOR context rather than presented as a direct v1.2 requirement. That preserves the usefulness of older explanations without misleading current candidates.<\/p>\n The 350-401 ENCOR core exam serves the CCNP Enterprise pathway, while Cisco now operates CCNP Wireless as a separate professional credential. The historical wireless concentration exams 300-425 ENWLSD<\/a> and 300-430 ENWLSI<\/a> were retired after March 18, 2026. Cisco maps them to the current 300-110 WLSD and 300-120 WLSI exams, with 350-101 WLCOR as the wireless core. Keeping the old and new exams distinct matters because an article about an earlier wireless pathway must not suggest that a retired code can still be booked.<\/p>\nUnderstand why a WAN overlay exists<\/h2>\n
Separate management, control, and forwarding roles<\/h2>\n
Compare transport selection with ordinary routing<\/h2>\n
Understand SD-WAN’s limits before recommending it<\/h2>\n
Know precisely which wireless objectives moved<\/h2>\n
Separate certification pathways as well as topics<\/h2>\n