Endpoints and Media Types

Endpoints and Media Types is the physical and access layer of the exam. CCST candidates should be able to identify devices, cables, connectors, wireless access types, and the first checks for host connectivity.

Endpoint examples

Media chooser

Failure patterns by access type

Endpoint role matters

A printer, IP phone, laptop, and server can all be “endpoints,” but they fail differently. A laptop issue may be user profile, Wi-Fi, DHCP, or VPN. An IP phone may depend on PoE and a voice VLAN. A printer may be reachable by IP while name discovery or driver configuration fails. A server may have a working network path but a stopped service or host firewall rule.

CCST answers often prefer the first observable check for the endpoint type rather than an advanced redesign. If the scenario says a phone has no power, think PoE or cable before DNS. If a laptop cannot associate to Wi-Fi, think SSID, credentials, signal, or authentication before routing.

First checks

Before escalating, gather what a support technician can observe:

• link light or Wi-Fi association
• correct cable and port
• IP address, gateway, and DNS
• whether one endpoint or many are affected
• recent move, cable change, password change, or configuration change

Documentation cues

Good endpoint documentation records the device name, user, location, cable or SSID, switch port if known, IP address, MAC address when relevant, and what changed before the issue started. This is not paperwork trivia: it lets the next technician connect the symptom to topology, access type, and support history.

Exam traps to avoid

• Do not assume a wireless issue is caused by the router before checking association and signal.
• Do not treat copper and fiber as interchangeable cable types.
• Do not ignore PoE when an IP phone or access point has no power.
• Do not escalate without recording the endpoint, access method, and first checks already performed.