CCNA Skills You Can Verify

Completing a CCNA lab is not the same as demonstrating a networking skill. A configuration can be accepted by Cisco IOS while an interface remains down, a host is assigned to the wrong VLAN, an OSPF route is missing or an ACL permits traffic that the requirement meant to deny. Meaningful practice starts with the expected network behavior and ends with evidence that the result is correct, including an appropriate negative test.

These exercises develop verifiable skills relevant to Cisco CCNA 200-301 v1.1, the current examination through February 2, 2027. Use Packet Tracer, another authorized lab environment or disposable devices you may configure. Do not test unknown networks or expose training services to public infrastructure. This article is a lab evidence framework, separate from a personalized study order or a troubleshooting story about an existing incident.

Define the property and evidence before the command

For every exercise record the target topology, expected permitted traffic, expected denied traffic, baseline state, planned configuration change, observation and cleanup. A short prediction should explain which device makes the critical decision. If a failed test could be caused by several layers, note the independent evidence that would distinguish them rather than interpreting one timeout as conclusive.

Use a simple lab with two switches, a router or Layer 3 switch, several isolated client networks and a synthetic application. Document interface names and addresses rather than relying on a diagram copied from another lab. Save device state before making changes so you can restore it without affecting unrelated experiments.

Keep one evidence row per learning claim. For example, “VLAN 20 is carried between switches” should be supported by port mode, allowed VLAN state, MAC-learning behavior and an appropriate client test. “Client A is authorized to reach service B” needs the relevant traffic observation and perhaps a denied control flow. Neither claim is proved solely by a successful configuration command.

Lab 1: prove addressing and local forwarding

Assign two hosts to the same isolated IPv4 subnet and a third to another subnet. Before connecting them, calculate network and host boundaries from their masks. Predict which destination causes a local ARP resolution and which requires a gateway. Then compare the actual neighbor and forwarding results with the prediction.

Use a temporary wrong subnet mask on one disposable host. Observe whether it misclassifies a destination as local or remote. Correct the mask and retest. This exercise shows why IPv4 subnetting changes real forwarding decisions, not merely the way address ranges are written.

Add an IPv6 variation with an appropriate unicast address and prefix. Record neighbor discovery and relevant gateway behavior rather than assuming IPv6 works exactly like IPv4 ARP. A failure in the IPv6 test should be explained using the actual address and neighbor states, not treated as a generic “IPv6 is broken” outcome.

The portfolio artifact is a small source-to-destination table showing expected local or remote behavior, observed resolution and the specific configuration that changed the result.

Lab 2: establish VLAN membership and trunk carriage

Place two clients in separate VLANs on the first switch and equivalent clients on the second. Configure the intended access ports and a trunk that carries the required VLANs. Verify that same-VLAN traffic works across the switches while distinct VLANs remain separate without a Layer 3 route.

Now remove one lab VLAN from the trunk’s allowed list. Affected clients on opposite switches should no longer have the intended Layer 2 path, while traffic on the unaffected VLAN may still work. Record the allowed-VLAN state and interface status as well as the client symptom. The test demonstrates what the trunk controls and what it does not.

For a redundant topology, inspect Spanning Tree state before and after connecting another permitted test link. Do not create unmanaged physical loops in a real production network. The objective is to explain how loop-prevention and port state affect forwarding rather than to cause an uncontrolled broadcast storm.

Finish by restoring the intended trunk and verifying both VLANs. The useful result is a causal chain from port membership to allowed trunk carriage and endpoint behavior, not a copied show vlan output with no interpretation.

Lab 3: verify routing and the return path

Create two or three routed prefixes and predict which route each destination will use. Start with a connected route, then add an appropriate static route under controlled conditions. Record the selected next hop, outgoing interface and the return path. A route to the destination alone may not be sufficient when the destination cannot reach the source network.

Add a more-specific prefix and compare the chosen path with the previous less-specific route. CIDR prefix matching makes the result predictable. Do not explain the outcome only by the order commands were typed; route specificity and the platform’s selection process matter.

For a small single-area OSPF experiment, form a controlled neighbor relationship and verify the expected prefix reaches another router’s routing table. Then remove a network advertisement in the disposable setup and observe how neighbor health can remain different from specific prefix reachability.

Test both forward and return traffic after correcting the fault. A useful log lists the expected network, route source, next hop and real observation, including any ACL or filter that could still prevent the application from working despite a valid route.

Lab 4: distinguish DHCP, DNS, NAT and NTP outcomes

Configure a supported DHCP service for a lab subnet. Verify the address, mask, default gateway and DNS resolver issued to the client. If the DHCP server is on another subnet, test the required relay arrangement in the isolated environment. A retained old lease may make an otherwise broken server path look healthy until renewal, so record the event sequence rather than only the final address.

Build a synthetic hostname and compare a name lookup with direct IP reachability. Change the name record in the test resolver and observe the effect while leaving routing unchanged. This demonstrates that DNS resolution answers a different question from packet forwarding.

Where NAT or PAT is part of the lab, capture the expected translation and confirm the traffic uses it from the intended source. A translated address does not establish application authorization or guarantee a DNS query is accurate. NTP can be tested separately by comparing time synchronization and its effect on event-log correlation.

The evidence should name exactly what each service provided. A successful hostname request can involve all of them, but their configuration, symptoms and corrections should remain distinguishable.

Lab 5: require one allowed and one denied security result

Write an explicit traffic policy: one source network may access a synthetic HTTPS service, another must be denied, and approved administrator hosts may use secure device management. Configure suitable lab access rules at a defined interface and direction. Record the rule ordering and predicted matches before testing.

Run a permitted application connection and a prohibited one from the correct sources. Inspect the applicable ACL state or counters and confirm whether the result matches expectations. A rule that rejects every source is not a pass when the business still requires legitimate service; a rule that permits both sources is not a pass merely because the approved test succeeds.

Check that remote management uses appropriate security and authentication. A host can have network reachability to a device while its account lacks authorization to change configuration. An ACL controls selected network flows, whereas device login and application permissions impose different constraints.

Restore test rules after completion, and avoid leaving permissive management access in a shared training environment. Record one limitation of your test, such as a different protocol or source that was not evaluated.

Lab 6: observe wireless as part of the wired path

In a controller simulator or permitted wireless lab, define a test WLAN and its expected authentication and client network placement. Confirm that a client obtains the intended address and gateway and reaches an approved service. Inspect whether the wireless association succeeded independently of whether the downstream routed application works.

Change a harmless wireless security or VLAN-assignment condition and predict the symptom. A client that cannot join an SSID differs from a client that joins successfully but receives the wrong subnet or cannot route to the application. These conditions require different verification steps.

Where radio behavior can be safely simulated or observed, compare signal strength, band, channel selection and potential interference without claiming a single measurement proves the entire wireless design. The CCNA-level skill is recognizing how access and radio conditions connect to the same IP and security boundaries used by wired clients.

Lab 7: inspect automation against effective device state

Use a version-controlled description of a small approved configuration, such as interface descriptions or permitted VLAN assignments, and apply it through an authorized tool or simulator. Compare the intended target list with the actual devices modified. A successful automation job is not evidence that traffic matches the requirement.

Change one setting in the disposable template and inspect the resulting interface and client behavior. If the template is wrong, the impact can spread to more than one device. The distinction between Ansible and Terraform is useful when deciding how changes and desired state should be managed, but neither tool eliminates the need for network reasoning.

Record the applied change, expected effect, actual verification and rollback. If an AI-powered assistant suggests a configuration, treat the suggestion as an untrusted plan until a qualified operator validates the prefix, interface, policy and approved scope. Automation reduces repeated manual work only when its intent is correct.

Assemble a portfolio that can be independently challenged

For each lab, preserve one page with expected behavior, configuration summary, observed result, negative test, causal explanation and cleanup. Do not paste dozens of identical command outputs with no accompanying argument. Another engineer should be able to identify what was proved and which related properties remain untested.

Retest with changed addresses, VLAN numbers, route preferences or failure locations. If the correct explanation survives those changes, the candidate has learned a network mechanism rather than a particular simulator exercise. A lab portfolio is strongest when it includes a few honest failed hypotheses followed by a supported correction.

The current Cisco 200-301 v1.1 exam remains the relevant scope in October 2026, even though Cisco has announced v2.0 for February 2027. The exam’s configuration and verification verbs make sense when every skill is attached to observable network behavior. A completed lab is the beginning of the evidence, not the end of the learning.