AdvancedPublished 2026-08-30
CCNA Break/Fix Capstone: One Symptom, Two Faults
Archive lab
Lab 7 of 7 in CCNA Break/Fix: Diagnose and Repair · ← Previous
CCNA exam domain: Network Access
A branch user in VLAN 10 cannot reach the data center's line-of-business server, stalling the end-of-day batch upload. Two faults sit behind the one complaint, and clearing either alone leaves the user where they started. The client gets no answer from its own gateway either.
Learning objectives
- Trace forwarding hop by hop from CLIENT10 to SRV-APP01 with ping and traceroute.
- Verify that a link carries the VLANs the design requires.
- Compare each router's routing table against the addressing plan.
- Prove a repair from the hosts at both ends, not between devices.
Troubleshooting focus
- CLIENT10 gets no reply from 10.10.10.1, yet
show ip interface briefon RTR-BR1 reads it up/up. An interface can be up and still not hear the client —show interfaces trunkon SW-BR-ACC1. - RTR-BR1 and RTR-DC1 ping each other across the transit and CLIENT10 still gets nothing back. A working transit says nothing about what either router knows —
show ip routeon both, against the addressing plan. - CLIENT10 now reaches 10.10.10.1 and the server is still unreachable — one fault is cleared, the complaint is not. Run
traceroute -nfrom both hosts and compare where each stops.
Topology
Subscribe to preview this lab's topology.
See plansGrade your work
How this lab is graded
- Build it your way. Where a lab lets you choose a value — a VLAN name, an interface description — grading checks that you configured it, not which name you picked. Names that another line has to reference, like an ACL applied with
access-class, are stated in the guide and do have to match. - Addresses, modes and protocol keywords are exact. An IP address, a subnet mask,
switchport mode trunk, an encapsulation — these carry the meaning of the lab, so they are graded as written in the guide. - Grading reads your saved configuration. Export the lab from CML after you have configured it, and make sure anything you set is in the
running-config— a change that only exists in a terminal session never reaches the grader. - You can submit as many times as you like. Your best score stands, and each attempt tells you which checks passed so you can work the gaps.
- Scored something you believe is correct? Use Report an issue on this page — that is exactly how the grading fixes in the changelog got found.
Create a free account to submit your lab for grading.
Create a free accountFound a problem with this lab?
Please sign in to report a problem — tying it to your attempts lets us reproduce and fix it faster.