EXAMTOPICS / TECHNOLOGY INSIGHTS

From DevNet Associate to CCNA Automation: Practical Learning Path

“DevNet Associate” is the former name of Cisco’s associate network automation certification. Cisco renamed the pathway CCNA Automation in February 2026 while retaining the 200-901 associate exam family under the CCNAAUTO designation. This article presents an evidence-based skill-development roadmap rather than claiming that an unverified first-person pass story establishes a current exam requirement.

First build networking context for software automation

A useful automation engineer can interpret interface state, addressing, VLAN assignment, routing behavior and security policy. Without those foundations, an API script may successfully update the wrong resource. Start with a small lab whose expected connectivity and rollback behavior are clearly defined.

Make one authenticated API request understandable

Inspect the request method, endpoint, authentication mechanism, status code, JSON payload and error handling. A successful HTTP response does not alone prove the network reached its desired state. Compare the returned configuration to what the device reports operationally.

Show what an automation API response actually proves. Make the first project a read-only interface inventory rather than a fleet-wide configuration script. Request a list of interfaces, record which device and timestamp produced the data, validate required response keys, and reject a record that has no interface name or status field. Record a 401 authorization response, a 404 unsupported endpoint and a delayed response as different failure conditions; treating them all as an empty list could lead a later automation task to conclude incorrectly that a device has no interfaces.

Next compare the returned inventory with a versioned expectation. An interface listed as administratively down is not equivalent to a cable failure, and an interface reported as up does not prove that routing or application reachability works. Show an operator the proposed change, the permissions it would require, the pre-change evidence and a rollback procedure before advancing beyond read-only access. Those practices belong to real network automation whether or not the original certification label appears on the learner’s résumé.

Turn scripts into controlled workflows

  • Keep device inventory and secrets out of hard-coded scripts.
  • Validate input values and display intended changes before execution.
  • Use Git history and tests to detect errors before a release.
  • Capture before and after state for every network change.
  • Report partial failure and provide a rollback strategy rather than silently continuing.

Choose the correct current certification

Cisco CCNA Automation 200-901 (CCNAAUTO) is the active associate-level exam, distinct from the former DevNet Associate branding. CCNP Automation requires the distinct AUTOCOR 350-901 core examination and a concentration. Traditional Cisco CCNA 200-301 remains the broad networking foundation. Choose based on whether your role requires basic network operations, programmatic automation or systems-level automation design.

Design a small change so another engineer can review it. A practical starter project gathers device interface status through an API, compares the result to a versioned inventory and produces a difference report. Before attempting an update, it should identify unmanaged devices, missing credentials, invalid data and the consequences of partial failure.

Publish the source code in a private or public repository only after removing secrets and internal network details. Provide a README covering intended permissions, non-production testing, response-code handling and how to reproduce the evidence. This lets an interviewer evaluate working habits rather than relying on an unverifiable exam story.

A good learning artifact is a small repository that inventories interfaces, validates intended state and records errors. Its value can be evaluated independently of any marketing claim about salary or guaranteed exam performance.

Build evidence of automation competency rather than a success anecdote

Plan a small automation exercise with one inventory input, one read-only device API and a clearly defined expected result. Capture both normal data and a failure response. Validate the output schema, avoid printing credentials in logs, and show which records were skipped because data was incomplete. A short README should explain the assumptions and how to repeat the run. This demonstrates the difference between writing a Python script and delivering an operational tool.

A second exercise can stage a configuration change in an isolated lab. Keep an explicit human approval point, inspect the proposed diff, apply only supported changes and verify actual network state afterward. Record rollback instructions before the change.

Evaluate the current certification against the job you want

The older personal-journey framing of DevNet Associate should not be presented as an authenticated first-person exam result. In 2026 Cisco’s associate automation certification is CCNA Automation 200-901 CCNAAUTO. Compare its published domains with tasks such as inventory collection, API integration, controller use and safe deployment, then identify gaps in your own hands-on experience.

A candidate seeking network engineering work may need deeper routing and switching fundamentals before specializing in APIs. An experienced application developer may need the reverse: practical interface, route and policy knowledge before automating equipment. Preparation should address that genuine gap rather than promise a fixed number of study days or a passing score.

Build an automation portfolio that can be evaluated independently

An example learning portfolio can begin with a read-only data-collection script rather than a configuration push. Connect to one authorized lab device or sandbox API, retrieve the interface inventory and operational status, then serialize the normalized result with a timestamp and device identifier. Handle an empty response, a missing field and an authentication failure explicitly. The deliverable is not just the script; it is a small test that shows the output is interpreted correctly even when the API returns incomplete data.

The second exercise can compare device state against a written expectation. For example, define which VLANs should exist, which uplink interfaces should be operational and which management addresses should be reachable. Report differences instead of silently changing them. Include sample responses that cover the intended and unintended cases and store credentials outside the source repository. This teaches a key network-automation skill: read, validate, report and get an authorized change decision before writing to a device.

Only after observation works should a third lab attempt a reversible change. Use a test VLAN or interface description on a nonproduction device, show the proposed diff, request explicit approval in the lab workflow, apply the change and verify both the configuration and operational effect. Record how the change would be backed out. A command returning an HTTP success code is not proof that the resulting network function is correct.

The Cisco certification program renamed DevNet Associate to CCNA Automation in February 2026. A present-day reader choosing an examination needs the 200-901 CCNAAUTO objectives and current issuer training material rather than an older DevNet-branded announcement. Personal anecdotes can illustrate motivation, but without attributable first-person evidence they should not be used as the factual basis for an assessment of exam difficulty, cost or career outcomes.

Make automation quality visible through negative tests. An automation demonstration is incomplete if it only handles a working API. Create test responses for HTTP authentication failure, rate limiting, an empty JSON collection and a response missing a required field. The client should exit with an informative status, keep secrets out of the logs and avoid incorrectly declaring the target network healthy. An operator reading the summary must be able to distinguish no anomalies observed from the collection did not succeed. For asynchronous collection jobs, include timeouts and device identity so one stalled host does not obscure the status of all others.

When the workflow recommends a change, define a review boundary. A report may propose correcting an interface description or restoring a test VLAN membership, but that recommendation should remain visible as a diff until an authorized operator accepts it. Keep configuration writes out of the observation phase, and make rollback instructions specific to the actual device software or API. Record pre-change state, desired state, executed action and post-change operational verification as separate artifacts. This makes failures diagnosable and supports peer review.

A portfolio can then demonstrate three different competencies with the same network: data acquisition, evidence interpretation and a controlled configuration change. This is closer to what employers need from practical network automation than an anecdote about quickly completing a Python course. Because Cisco renamed DevNet Associate to CCNA Automation in 2026, refer candidates to the current 200-901 exam topics for test preparation; the portfolio remains useful even as vendor product APIs and exam versions change.

Avoid unsupported autobiographical claims

A first-person article should describe experiences that can be attributed to a real author. Without evidence of a specific candidate’s dates, exam attempts or employment outcomes, an editorially safe revision should present testable workflows and clearly labeled hypothetical exercises instead of inventing a personal success story. A strong portfolio supports its claims with reproducible scripts, sample API responses, limitations and test results. Keep the certification branding current while preserving historical naming where it explains a real program transition.

Show how to review your own automation work

A useful portfolio review asks a peer to change the test fixture or API response so the expected result is no longer true. If the script still reports success, its validation is inadequate. Store representative failing outputs with the corresponding test assertions, then explain the change that made the system distinguish correct state, incomplete collection and an actual configuration drift. This can demonstrate durable engineering judgment even when a chosen Cisco library or exam name changes.