Study guide

Endpoint Devices and Network 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

Endpoint Devices and Network Roles

Key Takeaways Explain This Topic AI

An endpoint is any host that originates or receives network traffic: laptops, phones, IP phones, printers, cameras, POS terminals, sensors, virtual machines, and servers.

Clients request services (DNS, DHCP, web, print); servers and many IoT devices provide services. One device can do both, like a DHCP-client printer that serves print jobs.

Before changing anything, identify the device type, role, connection method (wired/Wi-Fi/cellular/dock/VPN), and the exact service the user expects to reach.

Endpoint intake should capture hostname, MAC, IP/mask, gateway, DNS, VLAN/SSID, the exact error, scope, and when the problem started.

CCST Networking exam 100-150 is ~50 minutes, ~40-50 mixed-format items, costs about USD 125, and lists 'describe endpoint devices' as an objective.

Last updated: June 2026

Endpoint Devices and Network Roles

An endpoint is any host that uses the network to send, receive, store, display, print, or process information. The Cisco Certified Support Technician (CCST) Networking exam, currently exam code 100-150, lists describing endpoint devices and checking host connectivity among its objectives. It is a vendor-neutral-feeling but Cisco-owned credential: a Cisco-form-varying number of mixed multiple-choice, drag-and-drop, and simulation items in 50 minutes for around USD 125. Cisco does not publish an official passing score. So when this chapter says 'identify the endpoint,' it is testing a real, scored skill, not a slogan.

Common Endpoint Types

Common endpoints include desktop PCs, laptops, tablets, smartphones, Internet Protocol (IP) phones, printers, scanners, cameras, point-of-sale (POS) terminals, badge readers, medical or industrial controllers, virtual machines (VMs), and servers. The exam-relevant question is never only "what is the device?" but "what should this device be able to reach?" A warehouse handheld scanner that cannot print a label has a different fault path than a desktop that cannot open a cloud app.

Client vs. Server Roles

Endpoint roles narrow troubleshooting fast. A client requests a service: browsing a website, resolving a name with the Domain Name System (DNS), receiving an address from Dynamic Host Configuration Protocol (DHCP), or sending a print job. A server provides a service: file storage, authentication, web, DNS, DHCP, or databases. Many devices are both. A network printer behaves like a DHCP client when it leases an address, yet behaves like a server when it listens on TCP port 9100 for raw print jobs.

  • Endpoint category Examples Typical role Support note
  • User devices Desktops, laptops, phones, tablets Client High change rate; user-reported symptoms
  • Shared office devices Printers, conference systems, scanners Client + server Affect many users when down
  • Infrastructure-adjacent Jump hosts, management PCs, monitoring Client + server Privileged; document carefully

Specialized / IoT Cameras, sensors, door controllers, POS Often server-like Static IPs, long update cycles, special VLANs

Identify the Connection Path First

Identify the connection method before changing settings: wired Ethernet, Wi-Fi, cellular, Bluetooth tethering, a Universal Serial Bus (USB) adapter, a docking station, a virtual switch, or a Virtual Private Network (VPN) tunnel. A docked laptop looks wired to the operating system even though the user thinks "my laptop." A phone may prefer Wi-Fi but silently fall back to cellular. A VM owns its own virtual network interface and IP even though it rides a physical host. These facts decide where to test and which evidence is real.

Endpoint Network Identity

An endpoint's network identity normally includes a hostname, a Media Access Control (MAC) address (Layer 2), an IP address with subnet mask or prefix length (Layer 3), a default gateway, DNS servers, and sometimes a Virtual Local Area Network (VLAN), Service Set Identifier (SSID), or VPN profile. DHCP can assign these automatically; static settings are typed by hand and are far more prone to typos and stale documentation.

A Repeatable Intake

Use a simple, repeatable intake every time:

  • Device type and operating system
  • User or location, plus whether nearby devices work
  • Wired or wireless path, dock vs. direct
  • Affected application or destination and the exact error text
  • Scope: one endpoint, one room, one SSID, one switch port, one app, or many users
  • When the problem started and what changed

Common trap: the worst CCST mistake is changing a static IP, DNS, or VPN setting before recording the original values. Capture state first; escalate to an engineer with facts, not guesses.

Why Roles Drive Uptime and Security Decisions

The role and category an endpoint falls into changes its expected uptime, patch cadence, credentials, cabling, and security posture, and the exam expects you to reason about those differences. A user laptop tolerates a reboot at lunch; a point-of-sale terminal during checkout, an IP camera covering an exit, or a manufacturing controller mid-run does not. Specialized endpoints are frequently pinned to static addresses, parked on dedicated or quarantined VLANs, and locked out of general internet access, so a connectivity report that ignores the device's role often misdiagnoses a deliberate policy as a fault.

When a badge reader "cannot reach the server," the correct first question is whether it is even supposed to, on that VLAN, with those firewall rules.

Scoping the Problem Before Touching the Device

Scoping is the single highest-value habit at CCST level because it converts a vague complaint into a bounded fault domain. Establish whether the symptom is isolated to one endpoint, one room, one SSID, one switch port, one application, or many users, and whether wired users are affected alongside wireless ones. One user down on one app while neighbors work points at that host or that application; a whole room down points at a switch, an uplink, or an access point; everyone on one SSID down points at wireless authentication or the controller.

This is the same logic an engineer uses to decide whether to dispatch a technician, restart a service, or open a carrier ticket, and recording it accurately is what makes your escalation actionable rather than a starting-over exercise.