Lesson proof
Concept, demo, checklist, lab, and assignment evidence.
Cisco / Network Automation Engineer
Cisco CCNA Automation
Prepare for network automation work with APIs, Python, JSON, YAML, Git, Cisco platforms, programmability, configuration templates, and safe change evidence.
CCNA Automation readinessAPI and Python practiceNetwork automation portfolio
Start domain mock testPlatform-wide module outputs
Every module now feeds portfolio proof and CV readiness.
Portfolio pack
Requirement, artifact, validation, risk note, and interview story.
CV signal
Role-specific skill statement linked to a score or artifact.
Review queue
Submitted evidence can support dashboard, readiness, and career exports.
Open materials
Automation foundationsLesson + portfolio pack + CV evidencePython and data formatsLesson + portfolio pack + CV evidenceREST APIs and PostmanLesson + portfolio pack + CV evidenceCisco platform programmabilityLesson + portfolio pack + CV evidenceGit-based change workflowLesson + portfolio pack + CV evidenceTesting and rollback evidenceLesson + portfolio pack + CV evidence
Certification objective coverage
Every provider-aligned module is connected to a lesson, labs, mock questions, and implementation proof.
This is the track-level audit view for blueprint alignment. Exact exam wording should still be checked against the current official provider guide before public exam-code claims are made.
cisco-ccna-automation.automation-foundations.01 / 17% weight
Apply Automation foundations decisions to Network Automation Engineer scenarios
Implementation proof
- Define Automation foundations in plain language and explain the provider service family it belongs to.
- Show how Automation foundations is implemented through a guided configuration, simulator, command, diagram, notebook, or case study.
- Capture evidence with screenshots, command output, logs, metrics, topology state, policy review, query result, or troubleshooting notes.
- Connect the evidence to a portfolio pack, CV-ready skill statement, and mock-test weak-domain recovery action.
Evidence requirements
- Correct scenario decision in mock exam
- Written explanation of the key requirement or constraint
- Hands-on lab evidence or troubleshooting proof
- Portfolio pack with requirement, artifact, validation, risk note, and interview story
- CV-ready skill statement linked to a score, artifact, or project result
cisco-ccna-automation.python-and-data-formats.02 / 17% weight
Apply Python and data formats decisions to Network Automation Engineer scenarios
Implementation proof
- Define Python and data formats in plain language and explain the provider service family it belongs to.
- Show how Python and data formats is implemented through a guided configuration, simulator, command, diagram, notebook, or case study.
- Capture evidence with screenshots, command output, logs, metrics, topology state, policy review, query result, or troubleshooting notes.
- Connect the evidence to a portfolio pack, CV-ready skill statement, and mock-test weak-domain recovery action.
Evidence requirements
- Correct scenario decision in mock exam
- Written explanation of the key requirement or constraint
- Hands-on lab evidence or troubleshooting proof
- Portfolio pack with requirement, artifact, validation, risk note, and interview story
- CV-ready skill statement linked to a score, artifact, or project result
cisco-ccna-automation.rest-apis-and-postman.03 / 17% weight
Apply REST APIs and Postman decisions to Network Automation Engineer scenarios
Implementation proof
- Define REST APIs and Postman in plain language and explain the provider service family it belongs to.
- Show how REST APIs and Postman is implemented through a guided configuration, simulator, command, diagram, notebook, or case study.
- Capture evidence with screenshots, command output, logs, metrics, topology state, policy review, query result, or troubleshooting notes.
- Connect the evidence to a portfolio pack, CV-ready skill statement, and mock-test weak-domain recovery action.
Evidence requirements
- Correct scenario decision in mock exam
- Written explanation of the key requirement or constraint
- Hands-on lab evidence or troubleshooting proof
- Portfolio pack with requirement, artifact, validation, risk note, and interview story
- CV-ready skill statement linked to a score, artifact, or project result
cisco-ccna-automation.cisco-platform-programmability.04 / 17% weight
Apply Cisco platform programmability decisions to Network Automation Engineer scenarios
Implementation proof
- Define Cisco platform programmability in plain language and explain the provider service family it belongs to.
- Show how Cisco platform programmability is implemented through a guided configuration, simulator, command, diagram, notebook, or case study.
- Capture evidence with screenshots, command output, logs, metrics, topology state, policy review, query result, or troubleshooting notes.
- Connect the evidence to a portfolio pack, CV-ready skill statement, and mock-test weak-domain recovery action.
Evidence requirements
- Correct scenario decision in mock exam
- Written explanation of the key requirement or constraint
- Hands-on lab evidence or troubleshooting proof
- Portfolio pack with requirement, artifact, validation, risk note, and interview story
- CV-ready skill statement linked to a score, artifact, or project result
cisco-ccna-automation.git-based-change-workflow.05 / 17% weight
Apply Git-based change workflow decisions to Network Automation Engineer scenarios
Implementation proof
- Define Git-based change workflow in plain language and explain the provider service family it belongs to.
- Show how Git-based change workflow is implemented through a guided configuration, simulator, command, diagram, notebook, or case study.
- Capture evidence with screenshots, command output, logs, metrics, topology state, policy review, query result, or troubleshooting notes.
- Connect the evidence to a portfolio pack, CV-ready skill statement, and mock-test weak-domain recovery action.
Evidence requirements
- Correct scenario decision in mock exam
- Written explanation of the key requirement or constraint
- Hands-on lab evidence or troubleshooting proof
- Portfolio pack with requirement, artifact, validation, risk note, and interview story
- CV-ready skill statement linked to a score, artifact, or project result
cisco-ccna-automation.testing-and-rollback-evidence.06 / 15% weight
Apply Testing and rollback evidence decisions to Network Automation Engineer scenarios
Implementation proof
- Define Testing and rollback evidence in plain language and explain the provider service family it belongs to.
- Show how Testing and rollback evidence is implemented through a guided configuration, simulator, command, diagram, notebook, or case study.
- Capture evidence with screenshots, command output, logs, metrics, topology state, policy review, query result, or troubleshooting notes.
- Connect the evidence to a portfolio pack, CV-ready skill statement, and mock-test weak-domain recovery action.
Evidence requirements
- Correct scenario decision in mock exam
- Written explanation of the key requirement or constraint
- Hands-on lab evidence or troubleshooting proof
- Portfolio pack with requirement, artifact, validation, risk note, and interview story
- CV-ready skill statement linked to a score, artifact, or project result
Test readiness
Mock test by domain
Practice every domain in this track with exam-style questions, answer keys, and explanations.
Open mock testMost in-demand certification materials
High-value certificates connected to this track.
Cisco
Cisco CCNA Automation
Needs reviewLast verified: Not verifiedNext review: Provider source review required
Network engineers and cloud engineers building API, Python, Git, and automation foundations.
Cisco CCNA Automation is mapped to platform lessons and labs, but still needs a dated official-source review.
- Network automation concept map
- Python, JSON, YAML, and API drills
- Read-only discovery script workbook
- Change validation and rollback checklist
Cisco / Open tooling
Cisco DevNet-style automation portfolio
Needs reviewLast verified: Not verifiedNext review: Provider source review required
Learners who want employer-ready automation evidence even before attempting a vendor exam.
Cisco DevNet-style automation portfolio is mapped to platform lessons and labs, but still needs a dated official-source review.
- API request and response evidence template
- Git change workflow rubric
- Automation runbook and validation report
Certification provider connections
Connect this learning path to the official exam provider.
Cisco Training and Certification
Cisco CCNA Automation
Confirm the exact Cisco exam code before booking, then use lab evidence and packet-trace work as readiness proof.
Booking partner: Pearson VUE
- Create or confirm the Cisco certification profile.
- Review the official exam guide, ID policy, delivery options, and reschedule rules.
- Add target exam date, booking status, renewal date, and certificate proof to the learner record.
Cisco Training and Certification
Cisco DevNet-style automation portfolio
Confirm the exact Cisco exam code before booking, then use lab evidence and packet-trace work as readiness proof.
Booking partner: Pearson VUE
- Create or confirm the Cisco certification profile.
- Review the official exam guide, ID policy, delivery options, and reschedule rules.
- Add target exam date, booking status, renewal date, and certificate proof to the learner record.
01 Match
Map each Daskerel track to the official provider, exam code, registration page, and verification route.
02 Prepare
Use provider objectives with Daskerel lessons, mock exams, labs, and evidence packs before booking.
03 Book
Send learners to the official scheduling partner while keeping target dates and next actions in the dashboard.
04 Verify
Capture certificate URL, badge, expiry, renewal plan, and portfolio proof after the learner passes.
Study plan
Learn structured data and API basics before writing scripts that change infrastructure.
Practise read-only discovery first: inventory, interfaces, routes, VLANs, neighbors, and health checks.
Turn every automation into a change workflow with version control, validation, approval, rollback, and evidence.
Hands-on labs
Use Python to parse JSON or YAML network inventory and produce a device summary.
Call a REST API with Postman or Python and document request, response, status, and error handling.
Create a Git workflow for network changes with branch, review, validation, deployment, and rollback notes.
Write an automation runbook that collects facts before and after a configuration change.
Track learning assets
Templates and revision tools for this path.
Exam blueprint checklistCisco CCNA Automation
Weekly study plannerCisco CCNA Automation
Command and service cheat sheetCisco CCNA Automation
Architecture pattern cardsCisco CCNA Automation
Flashcard revision setCisco CCNA Automation
Mock exam review sheetCisco CCNA Automation
Lab evidence templateCisco CCNA Automation
Interview story builderCisco CCNA Automation
Portfolio project rubricCisco CCNA Automation
Final readiness checklistCisco CCNA Automation
Practice questions
Why should network automation start with read-only discovery?
Read-only discovery reduces risk, confirms current state, builds an inventory baseline, and gives scripts reliable data before any configuration change.
Why are JSON and YAML important in network automation?
They represent structured data that scripts, APIs, templates, and configuration tools can read consistently without brittle manual parsing.