Home labs & practical projects

Validate a network inventory API response

A project to do with your own tools, with guidance on what to create and capture.

Local lab Suggested time: 2–3 hoursYour own authorised environment

What you could create

An automation script reads a device inventory API. It must handle missing fields, pagination and failed requests without silently producing an incomplete report.

Example evidence format

Project evidence map (example)

API client and mock responsesScope and inputs

Automated cases for pagination and failure handlingDecisions and reasoning

Evidence record (example)

Evidence	What to capture
API client and mock responses	Show the inputs, scope and decisions behind this record. The client retrieves all pages without duplicating devices.
Automated cases for pagination and failure handling	Include the evidence supporting your conclusion. Errors are visible and secrets are absent from logs.

What you'll need

Local lab

Create a local mock HTTP API with synthetic devices, two result pages and one error response. Use dummy tokens and a small Python or JavaScript client.

Project record

Keep the working files for api client and mock responses and record assumptions as you go.

Current reference material

Use the linked provider resources to verify the features, access terms and version relevant to your project.

Access & cost

Uses your own computer. Confirm hardware capacity, software licences and download terms before setup.

Use disposable VMs, containers or a simulator. Keep the lab separate from your everyday machine and work network.

Suggested milestones

1
Plan and investigate
Parse and validate the response schema before using the records.
2
Develop your approach
Handle pagination and a temporary failure with bounded retry behaviour.
3
Verify and explain
Produce an inventory report that identifies incomplete or rejected records.

Evidence worth keeping

Keep clear, organised evidence of your design and any testing you carry out.

1
API client and mock responses
Show the inputs, scope and decisions behind this record. The client retrieves all pages without duplicating devices.
2
Automated cases for pagination and failure handling
Include the evidence supporting your conclusion. Errors are visible and secrets are absent from logs.

Label design proposals and observed results clearly.

Explain your work

Use these prompts to reflect on your decisions and what you learned.

Which part of your api client and mock responses needed the most judgement?
What observation or assumption changed your approach?
What would you improve, and what have you not verified?

Describe this as a personal project in your portfolio.

Useful resources

Use these resources to deepen your understanding and check key details.

Official certification objectives

Review the current provider requirements and relevant subject areas.

Cisco U. DevNet Associate (DEVASC) learning path

Check relevance, platform versions and current access terms.

Explore external learning resources

Find relevant providers and check features, access requirements and costs.

A useful starting point

Create a local mock HTTP API with synthetic devices, two result pages and one error response. Use dummy tokens and a small Python or JavaScript client.

What a good result looks like

The client retrieves all pages without duplicating devices.
Errors are visible and secrets are absent from logs.

Finish the project

Save sanitised evidence, then remove the lab instances or revert to the clean snapshot. Remove temporary accounts and credentials.

Independent home-project guidance, not an official vendor lab or a claim of complete exam coverage. Use your own tools and label the work accurately.