We’ve lastly arrived on the third and ultimate installment of this riveting weblog collection. Whereas some could also be unhappy on the disappearance of additional sleep they obtained from studying this (my prose is often an ideal remedy for insomnia), on this weblog, we’ll be masking the shiny new DCNAUTO specialization and applied sciences close to and expensive to my coronary heart. Similar to the weblog on AUTOCOR and ENAUTO 2.0, I hope that it will assist make clear the explanation and intent for the massive transforming of the examination subjects to help and support you in your research.
A fork within the street
The unique DCAUTO examination had the “shortest” checklist of examination subjects (primarily based solely on my unscientific evaluation of the quantity of textual content on a PDF), however that doesn’t imply that the examination was easy. It lined a broad set of applied sciences with disparate terminology and spanned a number of (usually) separate groups (server/compute groups often are separate from the datacenter networking groups).
However even for those who have been in a company that had ACI and UCS, more often than not you’re employed with just one know-how or the opposite, not each. This complication was solely exacerbated by the truth that the Unified Computing System (UCS) Supervisor Platform Emulator (UCSM-PE) couldn’t be related to Cisco Intersight; solely sure builds which have been out there solely to particular groups like Cisco DevNet for his or her Sandbox may achieve this.
This lead to an enormous inner choice: How do we offer an automation certification that focuses on the datacenter, covers the community know-how out there at this time, consists of platforms and gadgets, and covers the evolving realities within the datacenter (like Kubernetes and containers)? We had some robust decisions to make, however the result’s the DCNAUTO 2.0 (observe the “N” for networking)
Give it to me straight, what has been faraway from DCAUTO?
Primarily based on this picture, you possibly can see that a big chunk of the unique blueprint has been eliminated/modified not directly(the highlighted sections). In some circumstances, the subjects have been eliminated for a similar as they have been in ENCOR 2.0; subjects like Git, primary APIs, or Python digital environments have been eliminated as a result of both (a) they’re assumed information (b) lined within the core examination or (c) might be changed with different applied sciences which will work higher with bigger workflows (e.g. growth inside a container with mapped volumes can exchange digital environments inside Python).
Inside area 2.0, we eliminated most of the particular API and SDK duties as they pertain to ACI. Whereas these two strategies of automation are nonetheless legitimate, a lot of the event and integration effort inside the datacenter has been centered on Infrastructure as Code (IaC) instruments. With the ability to automate platforms and applied sciences with instruments which have multi-platform assist is necessary as a result of these datacenters are more and more heterogeneous. So understanding the way to use these instruments inside the community infrastructure turns into a important talent.
Area 3.0 obtained a light-weight contact of modifications, principally centered on refining and trimming down superfluous device-centric automation and app-hosting strategies. Whereas these capabilities are nonetheless built-in to our huge datacenter switching portfolio, we tried to deal with the commonest use-cases and applied sciences. Keep in mind, the main target of the brand new blueprints is to create practicality and applicability into exams, so we needed to trim away a number of the esoteric or much less used options and performance.
And also you dropped compute?!
Sure.
I assume you’ll be in search of a cause on this one, too. Consider me, it wasn’t a straightforward choice. We went backwards and forwards on this and there have been robust arguments to either side, however in the end, as a rule, the compute and server groups are fully totally different than community infrastructure groups, and the practitioners inside these groups had vastly totally different skillsets, making the crossover to be that rather more tough.
Moderately than weakening the depth of the take a look at (and the sensible purposes gained from it) to assist added breadth, we determined to drop the compute automation fully. I can already hear the sighs of reduction from community automation people, however I do know there are just a few people that can miss the inclusion of Intersight and the UCSM APIs (my former compute Developer Advocate counterpart included).
Sufficient about what was dropped, what do we have to examine?
Inside the datacenter, there are just a few key applied sciences that we selected to deal with. As with the AUTOCOR and ENAUTO 2.0, reference the highest paragraph of the examination subjects checklist to get an understanding of the in-scope platforms. These platforms shouldn’t come as a shock, but it surely’s useful to set context round your research.
Infrastructure as Code (IaC)
The datacenter have to be:
- Agile
- Multivendor
- Even multicloud
This implies click-ops or particular person automations for various platforms gained’t at all times be accepted. The unifying issue to all of that is one thing like Ansible or Terraform, whereby the syntax throughout platforms and clouds is identical and the one distinction is the modules/collections or suppliers in use.
The DCNAUTO examination displays this, as 25% of the examination falls inside the IaC area. This requires you to be acquainted with the instruments and management options in addition to the platforms lined by the blueprint.
On-box automation and programmability
With the scale and scale of recent datacenter networks, platforms are sometimes used to handle the material. Nonetheless, there could also be both particular community automation options or day 0 provisioning that dictate a “box-by-box” course of. Due to this, we’ve included particular examination subjects to validate a learner’s information round these “community ingredient” automation duties in Area 3.
When it comes to particular community ingredient programmability, we’ve included:
- NETCONF assist, as YANG fashions equivalent to OpenConfig are utilized in giant, doubtlessly multi-vendor or web-scale datacenters, because it normalizes configuration throughout a wide range of gadgets
- Familiarity with NETCONF and ncclient, which can be utilized to ship XML-structured payloads to a tool by way of code written in Python
- Understanding the day-0 provisioning of a tool outdoors of the usage of a controller, and the on-box programmability strategies out there inside the Nexus platform
- Data round NXAPI and the movement of making bespoke templates (which might then be utilized as coverage) inside Nexus Dashboard rounds out the area
Operations (together with Linux Networking!)
One of many bigger shifts (throughout all new CCNP-Automation exams) has been the deal with operational elements of an automation answer. In any case, what good is deploying a change with out understanding the impression of that change on the community? That is no totally different inside the datacenter and a few would argue that it’s extra necessary; datacenters are finely tuned devices to maneuver knowledge in a short time from place to put. If it doesn’t work, it’s typically costing giant sums of cash.
On this examination, we’ve not a lot “eliminated” subjects, however shifted them in complexity. The unique DCAUTO examination had components that touched on model-driven telemetry and understanding subscriptions to knowledge., together with next-generation protocols like gNMI and gRPC. We additionally embrace digital twins and pyATS validation, as now we have in different exams. To not be forgotten, we additionally cowl the flexibility to retrieve well being data by way of Python towards gadgets as nicely.
Lastly, we additionally added the requirement to troubleshoot packet flows from Linux-based hosts operating containers. Everyone knows that containers are the brand new VMs, however the hosts operating these containers don’t use the identical instruments and terminology as a Kind-1 Hypervisor; we should perceive how Linux networking works and the way it’s configured.
This consists of how interfaces, subinterfaces, and bonded interfaces are created, in addition to how customary bridges are outlined and the connection between digital Ethernet (veth) interfaces on the host stage and interfaces outlined inside the container runtime. These expertise are not non-compulsory and we felt it necessary to grasp them nicely sufficient to repair them once they break.
We needed to toss in some AI, too
Similar to with the remainder of the skilled automation specializations, some AI wanted to be included inside the examination subjects checklist; it’s being talked about in all places and our certifications must be no totally different.
- Understanding the safety implications of utilizing AI inside the datacenter is necessary to guard the huge quantities and worth of that knowledge. Right here there may very well be unintended penalties round knowledge publicity and as a vector for exfiltration.
- As agentic AI turns into mainstream, understanding how these brokers join to numerous platforms, gadgets, and controllers is a baseband job; one thing that everybody ought to perceive.
- With the prevalence of automation and orchestration inside the datacenter, describing and understanding how generative AI can be utilized to speed up prototyping and iteration over community automation options will not be an non-compulsory talent. It ought to validated for any automation skilled.
Bringing all of it collectively
By means of this weblog, and the earlier ones on the AUTOCOR and ENAUTO 2.0, I hope you’ve gained a bit bit extra perception into the certification and the particular exams (each core and focus). This isn’t simply associated to the exams and subjects themselves, but additionally the mindset shift and totally different strategy in creating the examination subjects checklist, shifting from software program engineers which might be studying “community” to community engineers which might be studying “automation.” It sounds refined, however the final result might be fairly totally different. By means of this distinction, we hope that you just discover that the brand new exams align to your automation work in a way more impactful manner.
As at all times, completely happy studying! When you’ve got any questions, please contact me on X (@qsnyder) or by the Cisco Studying Community message boards.
Efficient February 3, 2026, the 300-635 DCNAUTO examination might be up to date to v2.0 and renamed, “Automating Cisco Information Heart Networking Options v2.0.”
Join Cisco U. | Be part of the Cisco Studying Community at this time without spending a dime.
Be taught with Cisco
X | Threads | Fb | LinkedIn | Instagram | YouTube
Use #CiscoU and #CiscoCert to affix the dialog.