DevNet Professional study plan

Map every objective in domain 1 to a concrete lab artifact you can build locally (script, model, or test).

Build a Python environment with requests, netmiko, ncclient, and pytest; verify each import works.

Write a data-model comparison note covering YANG, OpenConfig, and native models, citing at least three concrete device examples.

Implement a first RESTCONF GET against a sandbox router and print the parsed JSON payload.

Configure a local Git repository with a .gitignore, README, and one commit per lab artifact.

Compare NETCONF, RESTCONF, and gNMI by writing one script per protocol against the same sandbox device.

Explain and demonstrate the difference between configuration datastores (running, candidate, startup) in a lab.

Use Cisco DevNet sandbox credentials to authenticate and retrieve interface inventory via at least two APIs.

Document the authentication flow (token, basic auth, or OAuth) for each API you exercised.

Write down five failure modes you observed (timeouts, 401s, namespace errors) and how you resolved them.

Exercise the Cisco DNA Center or Meraki API to list devices and retrieve one configuration detail.

Exercise a Cisco IOS XE or NX-OS REST API endpoint and capture the response schema.

Refactor your week-1 and week-2 scripts into reusable modules with functions and error handling.

Add pytest unit tests that mock HTTP responses so tests run without a live device.

Create a simple CLI wrapper (argparse) that lets you choose device and operation.

Set up a CI pipeline (GitHub Actions or GitLab CI) that runs linting and pytest on every push.

Add a pre-commit hook that blocks commits failing flake8 or black.

Write a design document explaining how you would promote automation code from dev to prod.

Implement idempotency checks so re-running your configuration script produces no changes.

Define rollback steps for a failed configuration push and test them in the lab.

Model a small network (three devices) as structured data (YAML or JSON) and drive configuration from it.

Implement a template-based configuration generator using Jinja2 with at least two device roles.

Add validation that rejects malformed inventory before any device is touched.

Compare declarative and imperative approaches in a written note with concrete trade-offs.

Run a dry-run mode that prints intended changes without applying them.

Implement a health-check script that polls device state and alerts on drift from the intended model.

Integrate at least one Cisco platform API (DNA Center, Meraki, or SD-WAN) into your health-check flow.

Add structured logging and a simple metrics output (JSON or Prometheus text format).

Write runbooks for the two most likely operational failures in your pipeline.

Test your health check against a deliberately misconfigured device and confirm detection.

Take two full-length practice exams under timed conditions and record per-domain scores.

For every missed question, write a one-paragraph explanation of the correct concept.

Re-read the weakest two domains' notes and rebuild one lab artifact for each.

Update your repo README to summarize each lab artifact and the concept it proves.

Identify any objective you still cannot demonstrate and schedule a focused lab for it.

Complete one end-to-end capstone: inventory to template to CI to deploy to health check.

Record a short walkthrough (video or written) of the capstone explaining each design decision.

Re-run the full CI pipeline from a clean clone to prove reproducibility.

Do a final timed practice exam and confirm all domains are above your target threshold.

Freeze the repo, tag a release, and write a final one-page exam-readiness summary.