Study guide
Infrastructure Device Roles
CCST Networking Study Guide Exam
Track your progress as you read
Finished sections get a check mark.
1 Orientation, Official Sources, and Exam Strategy
Official Exam Profile and Source Hierarchy Registration, Delivery, Attempts, and Results Using the Six Official Topic Areas Building a Practical Study Plan Exam Strategy Without Unsupported Shortcuts Ethical Preparation and Path Forward
2 Network Standards, Models, and Common Protocols
Network Building Blocks OSI and TCP/IP Models Frames, Packets, Segments, and Data Flow Network Types and Scope Cloud, On-Premises, Protocols, and Ports Bandwidth, Throughput, Latency, and Jitter
3 Chapter 3: IPv4, IPv6 Addressing, and Subnet Formats
3.1 Public, Private, and Local Addressing 3.2 IPv4 Dotted Decimal and Binary Basics 3.3 Subnet Masks, CIDR, and Prefix Lengths 3.4 Subnet Logic, Host Ranges, and Gateways 3.5 IPv6 Address and Prefix Formats 3.6 MAC vs IP in Addressing Troubleshooting
4 Endpoints, Media, Cabling, and Client Connectivity
Endpoint Devices and Network Roles Network Interface Cards and Link Status Copper, Fiber, Coax, and Connector Basics Wired, Wi-Fi, and Cellular Access Methods Interference, Signal Quality, and Physical Reliability Client Connectivity Checks by Operating System
5 Infrastructure Devices, Ports, and Physical Installation
Infrastructure Device Roles Ports, Connectors, and Device Identification Cisco Device LEDs and Status Checks Network Diagrams and Cabling Instructions Power over Ethernet and Powered Devices Racks, Patch Panels, and Installation Basics
6 Switching, Routing, and Network Services
Basic Switching and MAC Learning VLANs and Local Boundaries Routing, Default Gateway, and ARP DNS, DHCP, and NAT Services Transport-Layer Services Small Network Traffic Flow
7 Troubleshooting Methodology, Ticketing, and Documentation
Help Desk Intake and Information Gathering Scope, Impact, and Prioritization Reproduce, Isolate, and Escalate Ticket Quality and Operational Documentation User Communication and Change History Physical, Data Link, and Network Layer Triage
8 Diagnostic Commands, Packet Capture, and Device Data
Command-Line Triage and Ping Path and Client Configuration Commands DNS and Socket Diagnostics Wireshark Capture and Save Device Access and Data Collection Basic Cisco Show Commands
9 Security, Firewalls, Wireless, and Safe Defaults
Firewall Filtering and Traffic Policy Least Privilege, AAA, Passwords, and MFA Wireless Security, WPA2, WPA3, and WPAx Guest Networks, Segmentation, and Shared Devices Common Threats and Safe User Practices Secure Home Router Baseline
10 Integrated Small Network Build and Repair Labs
Lab 1: Build a Basic Office LAN Lab 2: Repair No Internet After an Office Move Lab 3: Wireless Clients Cannot Reach Local Resources Lab 4: DHCP, DNS, and Default Gateway Symptoms Lab 5: Switch, Router, and Service Boundaries Lab 6: Escalation, Documentation, and Handoff
11 CCST to CCNA Career Path and Operational Readiness
Entry-Level Networking Roles and Expectations CCST vs CCNA and the Cisco Roadmap NetAcad 70-Hour Path and Study Plan Lab Habits for Real Operational Readiness Ethical Preparation, Portfolio, and Logbook Exam Scheduling Calendar and Readiness Check
12 Final Review, Exam Day, and Remediation Plan
Final Review Map to Official Objectives 50-Minute Exam Day Timing Unsupported Facts and Ethical Preparation Retake Planning Before the First Attempt Post-Fail Remediation Workflow Post-Pass Next Steps and Validity
Infrastructure Device Roles
Key Takeaways Explain This Topic AI
Routers forward between networks (Layer 3); switches forward frames inside one LAN (Layer 2); the two roles are distinct even inside one combo box.
Access points bridge wireless clients onto the wired LAN and almost always depend on a switch uplink and, often, PoE.
Firewalls enforce policy between zones; modems and ONTs terminate the provider circuit and convert it to Ethernet.
On the CCST Networking exam (100-150), expect to identify a device's role from a symptom or diagram before recommending any cable or setting change.
Last updated: June 2026
Why device roles matter on the CCST
The Cisco Certified Support Technician (CCST) Networking exam (number 100-150 , 50 minutes, a question count Cisco says varies by exam form, no publicly published passing score, US price $125) tests entry-level support skills. Domain 5, Infrastructure , asks you to identify devices and their roles before touching anything. A support technician who mislabels a router as a switch will trace the wrong cable and escalate to the wrong team, so role identification is the first reflex.
Every device sits at a layer of the network model. A switch operates mainly at Layer 2 (Data Link) , forwarding Ethernet frames by MAC address inside a single broadcast domain. A router operates at Layer 3 (Network) , forwarding packets by IP address between different networks and serving as a subnet's default gateway . Confusing these is the single most common beginner error.
The core infrastructure devices
- Device Primary role Layer Tells the technician
- Switch Connect wired endpoints in one LAN 2 (sometimes 3) Frame forwarding, VLANs, often PoE
- Router Forward between networks; default gateway 3 Inter-subnet and internet path
- Wireless access point (AP) Bridge Wi-Fi clients onto wired LAN 2 Needs switch uplink, often PoE
- Firewall Enforce policy between zones 3-7 Security boundary, do not bypass
- Modem Terminate cable/DSL provider circuit 1-2 Demarcation to ISP
- ONT (optical network terminal) Terminate a fiber circuit 1-2 Fiber-to-Ethernet conversion
- WLC (wireless LAN controller) Manage many APs centrally 2-3 APs register to it
- Combined home/small-office devices
In homes and small offices a single plastic box often combines a modem (or ONT), router, switch, wireless AP, and firewall . The exam still expects you to reason about each function separately. If Wi-Fi fails but a wired PC on the same box works, the switch and router functions are fine while the AP radio function is suspect — even though it is one chassis.
Reasoning from symptoms
Use a quick decision flow:
Can the host reach other devices on the same subnet ? If yes, the local switch path works.
Can it reach a different subnet or the internet ? If no, suspect the router / default gateway or the path through the firewall .
Is only Wi-Fi affected? Suspect the AP (radio, SSID, controller registration, or authentication), not the wired switch.
Is the whole site down? Suspect the modem/ONT and the provider circuit at the demarcation point .
Common traps
Trap: assuming an AP that has power and an Ethernet link is healthy. It may still fail to register to its WLC, broadcast no SSID, or reject client authentication.
Trap: bypassing a firewall to "restore connectivity." The firewall is part of the approved security design; bypassing it can violate policy and expose protected systems. Escalate instead.
Trap: calling a modem a router. A modem terminates the ISP circuit; it does not route between your internal subnets the way a dedicated router does. The CCST rewards the technician who names the exact role and stays inside their support scope.
Layers, again, because it pays off
The distinction between Layer 2 and Layer 3 underlies nearly every infrastructure question. A switch builds a MAC address table by learning which device lives on which port; it floods unknown unicast and broadcast frames to every port in the VLAN. A router instead consults a routing table of networks and next hops, decrementing the time-to-live field and rewriting the Layer 2 header at each hop. A firewall layers stateful inspection on top, tracking connection state and permitting return traffic only for sessions the inside started.
When a symptom appears, ask which layer it lives at: a bad cable or dead port is Layer 1-2, a wrong default gateway or subnet mask is Layer 3, and a blocked application is often a firewall policy at Layers 4-7.
Scope and escalation
A support technician's job is to observe accurately, make only approved changes, and escalate clearly. Identifying the device role tells you who owns the fix : a Wi-Fi coverage complaint goes to the wireless team that manages the APs and controller; a site-wide outage with a dead modem light goes to the carrier; a blocked business application that pings fine but will not load goes to the security team that owns firewall policy. Naming the role correctly routes the ticket to the right owner the first time and prevents wasted truck rolls.
The exam frequently frames this as a short scenario with one user-reported symptom, and the right answer is the device role whose failure best explains that exact symptom — not the most powerful device or the one nearest the user. Train yourself to map symptom to layer to device role, then to owner, and the infrastructure questions become routine. A useful habit is to restate the symptom in terms of reach: can the host reach itself, its local neighbors, its gateway, a remote subnet, and the internet, in that order?
Each rung that fails points at a specific role, so the answer almost always falls out of the reachability ladder rather than from guessing at hardware.