Cisco’s 2022 certification changes marked a shift from describing network skill solely through configuration commands toward recognizing software development, API use and automation as separate engineering responsibilities. This article is a historical guide to that transition. It does not claim a 2022 launch is still upcoming or that a 2022 exam code names the same 2026 assessment. For a current learner, the right starting point is the work they need to perform: operate a network safely, automate repetitive configuration, create integrations or design a tested deployment. Cisco’s present examination catalog, not a historical announcement, controls the available track and objectives.

Why the 2022 restructuring mattered

Cisco’s Associate, Professional and Expert credentials have different expectations about technical breadth and operating responsibility. The Specialist designation made it possible to recognize a narrower field such as a professional-level core subject without implying the candidate had completed every exam in a larger track. DevNet provided an additional home for developers and engineers using Cisco platforms through software interfaces. The change mattered because production networks need both configuration competence and software practices.

That distinction still matters to teams. A network operator may need routing, switching and failure-domain analysis, while an automation engineer needs API contracts, authentication, configuration validation and rollback. A single engineer can develop both skills, but a training plan should not confuse writing scripts with understanding the devices those scripts can change.

Keep the core network path separate from the automation path

A learner building foundational Cisco networking skills can compare the Cisco CCNA 200-301 certification path against the exact current issuer exam blueprint. Lab work should include IP addressing, VLAN boundaries, route selection, access control, monitoring and structured troubleshooting. Before creating an automation that changes those devices, the engineer should be able to explain the expected packet and routing behavior without running the script.

Then choose one repetitive but reversible task—for example collecting interface health or checking allowed VLANs—and add automation gradually. Record pre-change evidence, use read-only API calls first and add failure handling before writing configurations. The key educational progression is from a correct manual operating model to a tested software workflow, not from one credential title to another.

DevNet Expert was announced as a new challenge

Cisco described an Expert-level DevNet path in the 2022 period, with a written qualifying exam and a practical lab evaluating software design, implementation, deployment, maintenance and network automation. The then-described Cisco 350-901 DEVCOR label reflects that historic program. Cisco’s current catalog may attach a different name and blueprint to the 350-901 number, so a candidate must verify both the code and official title before buying a course.

For a modern practical drill, create a small automation that gathers device state through an authenticated API, detects one intentional policy mismatch, proposes a minimal configuration change and validates the resulting service. Include a safe rollback, a failed authentication case, idempotence and a second run that proves no redundant change occurs. Those operational controls are the transferable part of the original Expert-level idea.

Check the current Cisco credential before registering

The official Cisco examination list shows the Cisco 350-901 AUTOCOR exam under current Automation offerings. This is not an invitation to silently rename the historical DEVCOR training in older articles: preserve its context and separately name the modern route when it is relevant. The official training catalog describes Automation Core as designing, deploying and managing network automation systems.

When checking a blueprint, capture the date, code, title, version and required combination of exams. Current tracks can be reorganized, and course pages or cached catalog entries sometimes lag behind the schedule. Use the issuer’s registration and exam details as the authority for live appointment choices, especially around transitions.

Build a portfolio that shows controlled network changes

A strong automation portfolio demonstrates a request, a constraint, an observed result and a recovery. One example is collecting route and interface state before an upgrade, comparing it with an approved baseline and refusing a configuration push when a critical invariant fails. Another is a read-only diagnostic that correlates interface errors, link state and reachability to identify whether a fault is in transport or routing.

Keep the exact API input, tool version, sanitized output and rollback conditions. Do not claim an unsupervised lab was executed if the evidence is only a proposed design. This makes the 2022 DevNet history useful to current practitioners while avoiding unsupported promises about salary, prestige, eligibility or exam availability.