Skip to main content
Certifications Juniper JNCIA Home projects Back to certification

Home labs & practical projects

Commit a routing change with a tested recovery path

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

Vendor environment Suggested time: 90–120 minutesYour own authorised environment
01

What you could create

A junior network engineer needs to change a route on a Junos training device without losing management access.

Example evidence format
Project evidence map (example)
Annotated configuration sessionScope and inputs
Route validation and recovery recordDecisions and reasoning
Evidence record (example)
EvidenceWhat to capture
Annotated configuration sessionShow the inputs, scope and decisions behind this record. The evidence distinguishes candidate from active configuration.
Route validation and recovery recordInclude the evidence supporting your conclusion. Management access and forwarding are both checked after the change.
02

What you'll need

Vendor environment

Use an authorised Junos lab environment and a saved baseline. Identify the management path and a harmless test destination before making changes.

Project record

Keep the working files for annotated configuration session 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

Access may require a licence, trial or training subscription. Confirm availability and permitted use before committing; no free tenant is assumed.

Use an authorised training tenant with test identities and synthetic data. If access is unavailable, document the plan and label it untested.

03

Suggested milestones

  1. 1

    Plan and investigate

    Inspect the candidate configuration and predict the route change.

  2. 2

    Develop your approach

    Use the platform’s documented validation and recovery workflow.

  3. 3

    Verify and explain

    Verify the new route and demonstrate restoration of the previous configuration.

04

Useful resources

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

Turn the project into evidence

Keep your artefacts and reasoning together so you can explain what you did.

A useful starting point

Use an authorised Junos lab environment and a saved baseline. Identify the management path and a harmless test destination before making changes.

What a good result looks like
  • The evidence distinguishes candidate from active configuration.
  • Management access and forwarding are both checked after the change.

Finish the project

Remove test identities, policies and data, restore the initial configuration, and check trial expiry or renewal settings.

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.