From DevNet Professional to CCNP Automation
Cisco’s DevNet Professional branding ended with the transition to CCNP Automation on 3 February 2026. This was not just a label change. Cisco revised the professional core blueprint to reflect how modern network engineers design, develop, test and operate automation systems. Historical material about the old 350-901 DEVCOR examination can help explain the roots of the track, but it cannot be substituted for the current AUTOCOR v2.0 curriculum.
The current CCNP Automation route requires the 350-901 AUTOCOR core examination and a qualifying automation concentration. Cisco lists the 300-435 ENAUTO v2.0 enterprise automation route and 300-635 DCNAUTO v2.0 data-center automation route among those concentrations. Professional-level preparation should therefore be scoped as a core systems-engineering foundation plus the area in which the learner actually works. Older DevNet study plans may omit recently introduced methods, tooling and operating assumptions.
Existing holders of active DevNet credentials were covered by Cisco’s rebranding transition; that does not mean a candidate can now sit the old DEVCOR version. When comparing course catalogs, distinguish historic certification names, current exam identities and the version of each published blueprint. A title that mentions “DevNet Professional” may be historically accurate while its schedule or exam-outline information is no longer valid.
Treat infrastructure as a managed software system
The strongest network automation teams express what infrastructure should do and make that intent reviewable. Inventory quality, source-controlled configuration, repeatable change plans, access control and testing are part of one system. Writing a Python script to log in to routers is useful for learning, but a production deployment must account for concurrent changes, partial failures, missing devices, drift, and the ability to return to a known-safe state.
Infrastructure as code does not remove the importance of network fundamentals. A change to an access-control list, routing policy or interface configuration still has operational consequences. Automation increases the speed at which those consequences can spread. Before a pipeline deploys a change, engineers should test the proposed state against topology, reachability, security requirements and known platform constraints.
A useful professional exercise takes a small network topology, defines desired interface and routing properties, stores them in a version-controlled repository, generates a reviewed change, applies it in a test environment and verifies the results. This provides better evidence of competence than memorizing the command-line syntax of a single framework.
APIs, structured data and integration contracts
Network automation depends on reliable interfaces. REST APIs, RESTCONF, NETCONF, YANG data models and controller-based platforms allow software to read and modify structured state, but each interface comes with authentication, error handling and version compatibility requirements. A successful HTTP response is not proof that the intended network behavior has been achieved.
Engineers should validate schemas, handle pagination, respect rate limits, and distinguish missing or stale data from real device conditions. Credentials must be scoped and rotated; diagnostic logs should not leak secrets or tokens. API wrappers should expose meaningful failures rather than hiding them behind ambiguous success flags.
The core skill is integration design. A controller, inventory system, orchestration service and device may describe the same network object differently. Build a canonical mapping, identify the authoritative source for each attribute and test how synchronization behaves when two systems disagree. These principles apply whether the implementation uses a vendor SDK, direct calls, Ansible or another automation environment.
Verification, observability and continuous delivery
Automation is incomplete until it can prove the result. Compare intended and observed state, test connectivity and business-critical traffic flows, and capture metrics that establish whether the change improved or harmed operations. Unit tests can verify transformations; integration tests can exercise APIs; topology or lab tests can catch routing and policy mistakes that a parser cannot detect.
Continuous integration can lint configuration definitions, check secrets and schemas, run pyATS-style validations, and require human approval when a change carries material risk. Production deployment should include a bounded change window, rollback or roll-forward criteria, and clear incident ownership. A green pipeline status alone is not sufficient evidence of a healthy network.
Operational reporting matters when automation runs repeatedly. Track execution success, mean change duration, drift, unexpected device state, rollback frequency and service impact. Logs need enough correlation to reconstruct a failed run, but not so much sensitive data that troubleshooting introduces a new security exposure.
The new role of AI in automation workflows
The refreshed Cisco automation curriculum acknowledges AI-adjacent workflows, including the use of models and tools within bounded automation systems. An AI assistant may draft configuration or help interpret telemetry, but it should not become an uncontrolled privileged network operator. Treat generated recommendations as untrusted until validated against policy, the intended topology and an independent observation of actual state.
Model Context Protocol–style tooling can expose carefully scoped functions to an assistant. The security boundary remains crucial: limit the available operations, require explicit approval for high-impact changes, log who requested the action, and verify what happened. The principle is the same as with any other API client, but prompt ambiguity and generated output add failure modes that deterministic programs do not have.
An effective AI-assisted automation test should include refusal or escalation when the tool is asked to cross a trust boundary. For example, a diagnostic assistant may read interface health but should not modify production routing without a supported authorization path and prechange review. Engineers responsible for the system must be able to explain and reproduce the result without relying on a model’s narrative alone.
Choose the concentration that matches real work
Enterprise automation work emphasizes campus, branch, WAN and associated controllers, with policy and validation concerns across distributed environments. Data-center automation work intersects with fabric networking, APIs and platform integration in more centralized environments. Cisco’s current ENAUTO and DCNAUTO blueprints should determine exactly which technologies and task weights are in scope for each concentration.
It is more valuable to study the concentration connected to an actual operational responsibility than to choose an exam merely because a training provider promises it will be easier. Build a map between each official objective, the platform on which you can practice it and the evidence you expect from a successful lab exercise.
Teams should keep a separate architecture view of how automation interacts with change management, security operations, identity administration, CI pipelines and hardware lifecycle. Those cross-team concerns rarely fit neatly under a single tool name, yet they determine whether the automation program can scale safely.
A focused preparation and practice plan
Begin with the current 350-901 AUTOCOR objectives and identify the areas that demand design reasoning rather than product familiarity alone. Make practical labs with API calls, infrastructure-as-code repositories, network test environments, observability and controlled rollback. Use the same approach for the chosen ENAUTO or DCNAUTO concentration: match each objective to a concrete activity and a repeatable verification step.
Assess readiness by reviewing failed changes and explaining their root causes. If a configuration test passes but the application remains unreachable, the next step is not to memorize a different answer—it is to inspect traffic, routing, permissions and dependencies. Record the diagnostic evidence and revise the automation so the failure would be detected earlier next time.
Because Cisco changed the professional track substantively in February 2026, verify the live core and concentration documents again before purchasing a course or scheduling an exam. Use older DevNet Professional material selectively for persistent technologies such as REST APIs, Python, model-driven programmability and safe testing, but do not treat historic DEVCOR questions as a current AUTOCOR blueprint.
Designing resilient automation services
A scalable automation service needs a reliable control plane as well as reliable device commands. Define whether the inventory service, source-of-truth repository or orchestration platform owns each attribute. Set explicit behavior for stale records, deleted devices and concurrent requests. Queueing operations can protect devices from a burst of activity, but the queue must also expose progress, timeout and cancellation states to operators.
Deploy changes as small, reversible units whenever possible. A production network may contain heterogeneous software versions, unresponsive interfaces and partial configuration support. Have the automation detect its target capabilities, validate a candidate diff, and record which systems did not reach the intended state. A failed operation across twenty switches should not leave an ambiguous “mostly successful” log entry.
Event-based workflows require similar discipline. A link flap may generate many telemetry events, some duplicated or delayed. Deduplicate where appropriate, use thresholds or dampening, and make remediation idempotent. An automated response that repeatedly resets a healthy interface because of stale alerts can amplify the initial problem. Test these feedback loops in a simulator before connecting them to real actions.
One worthwhile design review is a network-intent change that crosses several device families. Start by defining the desired configuration in a source-of-truth record, validate input schema and policy constraints, then generate device-specific changes only after a human-readable diff is produced. If one target responds with an unexpected API error, the workflow should stop or isolate that failure according to an explicit policy; it should not silently continue until the network is inconsistent. Test the retry and rollback behavior against noncritical equipment before treating the automation as a production pattern.
An effective rollout plan separates source-of-truth changes from the code that interprets them. Engineers should know which repository update will trigger a pipeline, what approval evidence is required, and how to stop a deployment before a large number of devices is affected. Run a canary against a noncritical target, compare device state with intended policy, and expand only after the result has been reviewed. Preserve the prechange snapshot and test the rollback before treating the design as reusable.