Study Cisco CCST Networking standards and concepts: network building blocks, network types, bandwidth, throughput, cloud, applications, and protocols.
Standards and Concepts is the vocabulary layer of CCST Networking. The exam expects you to explain how networks operate before you troubleshoot them.
| Topic | What to know |
|---|---|
| Network building blocks | endpoints, media, switches, routers, wireless access, protocols, and services |
| Network types | LAN, WAN, MAN, CAN, PAN, WLAN |
| Performance words | bandwidth, throughput, latency, delay, jitter, packet loss |
| Applications and protocols | DNS, DHCP, HTTP/S, SSH, email, file sharing, and common service behavior |
| Cloud vs on-premises | where applications run, who operates the infrastructure, and how users reach services |
Bandwidth is the theoretical capacity of the path. Throughput is what the user actually gets after protocol overhead, congestion, interference, device limits, and application behavior.
For example, a laptop connected to a 1 Gbps switch port may still download much more slowly because the wireless hop is weak, the internet circuit is saturated, the server is throttling, or the application uses a chatty protocol. CCST questions often reward the answer that separates the advertised link speed from the measured user experience.
When an application fails, avoid jumping straight to one device. Follow the service chain:
| Question | Why it matters |
|---|---|
| Can the endpoint reach the local network? | separates local media/addressing problems from wider service problems |
| Can it reach the default gateway? | proves the local path to off-subnet traffic |
| Can it resolve a name? | separates DNS failure from IP reachability |
| Can it reach the destination port or service? | separates network reachability from application availability |
| Are many users affected? | separates endpoint-specific issues from infrastructure or provider issues |
You do not need deep packet-level mastery for CCST Networking, but you should know what a protocol is trying to accomplish.
| Protocol or service | Support clue |
|---|---|
| DHCP | If the host has no usable address, wrong gateway, or wrong DNS server, check address assignment. |
| DNS | If IP works but names fail, check name resolution. |
| HTTP/HTTPS | If a website fails after DNS works, check service reachability, proxy, firewall, or certificate symptoms. |
| SSH | Used for secure management access; failure may involve credentials, reachability, or permitted management policy. |
| ICMP | Often used by ping for reachability testing, but blocking ICMP does not always mean the destination service is down. |
| Network type | Exam cue |
|---|---|
| LAN | local office, switch, internal devices, same site |
| WAN | connections between sites or to a provider |
| WLAN | Wi-Fi access, SSID, signal, radio interference |
| PAN | short-range personal device connectivity |
| CAN | campus environment with multiple buildings |
| MAN | city or metro-area network |
When a user says “the network is slow,” do not assume the internet connection is the only cause. Check the endpoint, Wi-Fi signal, link speed, DNS behavior, application path, and whether the issue affects one user or many.