Cisco

CCNA 200-301 Complete Course

Master every domain of the Cisco Certified Network Associate exam. This course covers network fundamentals, LAN switching, IP routing, IP services, security, and network automation with real-world examples and exam-aligned explanations.

Intermediate 6 modules ~40 hours

Course Modules

01
Network Fundamentals
4 lessons
OSI & TCP/IP Models

Key Concepts

  • OSI 7 Layers: Physical (bits on the wire), Data Link (frames & MAC addressing), Network (packets & IP routing), Transport (segments & reliability), Session (connection management), Presentation (data formatting & encryption), Application (user-facing protocols)
  • TCP/IP Model: A four-layer practical model — Network Access, Internet, Transport, Application — that maps directly to how the Internet works
  • TCP vs UDP: TCP provides reliable, ordered delivery with a three-way handshake (SYN, SYN-ACK, ACK) and flow control; UDP is connectionless, offering lower latency for real-time traffic like VoIP and video streaming
  • Protocol Data Units (PDUs): Data is encapsulated at each layer — data at L7-L5, segments/datagrams at L4, packets at L3, frames at L2, bits at L1
  • Common Protocols by Layer: L7: HTTP, HTTPS, DNS, DHCP, SMTP, FTP. L4: TCP (port 80, 443, 22), UDP (port 53, 67/68, 161). L3: IP, ICMP, OSPF. L2: Ethernet, 802.11 Wi-Fi
Understanding the OSI model is foundational to every CCNA topic. When troubleshooting, work from Layer 1 upward: verify the physical cable first, then check the data link (MAC/ARP), then network (IP/routing), and finally transport and application layers. The TCP/IP model is what you will encounter in production, but the OSI model provides the vocabulary used throughout the exam.
Network Topologies & Types

Key Concepts

  • LAN (Local Area Network): Connects devices in a limited geographic area such as an office floor; typically uses Ethernet (802.3) at 1 Gbps or 10 Gbps
  • WAN (Wide Area Network): Connects geographically separated LANs; technologies include MPLS, Metro Ethernet, point-to-point leased lines, and Internet VPNs
  • Star Topology: All end devices connect to a central switch. Most common in modern LANs because a single link failure only affects one device
  • Mesh Topology: Every device connects to every other device. Full mesh provides redundancy but is costly; partial mesh is more practical in WANs
  • Two-Tier vs Three-Tier Architecture: Small campuses use a collapsed core/distribution design (two-tier). Large enterprises add a core layer for high-speed backbone switching (three-tier: access, distribution, core)
The CCNA exam tests your ability to identify the right topology for a given scenario. Star topologies dominate campus LANs because they simplify management and isolate faults. For the exam, know the difference between a WAN, LAN, WLAN, SAN, and SOHO network, and understand how spine-leaf architectures are used in modern data centers as an alternative to three-tier designs.
IPv4 Addressing & Subnetting

Key Concepts

  • IPv4 Address Structure: 32-bit address written in dotted decimal (e.g., 192.168.1.1). Divided into a network portion and a host portion by the subnet mask
  • Subnet Masks & CIDR: A /24 mask (255.255.255.0) gives 254 usable hosts. CIDR notation replaced classful addressing, enabling Variable Length Subnet Masking (VLSM) for efficient IP allocation
  • Private IP Ranges: 10.0.0.0/8, 172.16.0.0/12, 192.168.0.0/16 — defined in RFC 1918, not routable on the public Internet, used with NAT
  • Subnetting Practice: Given 192.168.10.0/24, borrowing 3 bits creates 8 subnets (/27), each with 30 usable hosts. The formula: 2^(borrowed bits) = subnets; 2^(remaining host bits) - 2 = usable hosts
  • Special Addresses: Network address (all host bits 0), broadcast address (all host bits 1), loopback (127.0.0.0/8), link-local (169.254.0.0/16 for APIPA)
Subnetting is heavily tested on the CCNA. Practice until you can subnet in your head: know the powers of 2, memorize the key subnet boundaries (/25 = 128, /26 = 64, /27 = 32, /28 = 16, /29 = 8, /30 = 4), and always remember to subtract 2 for the network and broadcast addresses. VLSM lets you assign different-sized subnets to different segments, which is critical for efficient IP space usage.
IPv6 Addressing Basics

Key Concepts

  • IPv6 Address Format: 128-bit address written as eight groups of four hex digits separated by colons (e.g., 2001:0DB8:ACAD:0001:0000:0000:0000:0001). Leading zeros can be omitted; one group of consecutive all-zero fields can be replaced with ::
  • Address Types: Global Unicast (GUA, 2000::/3) is the equivalent of public IPv4. Link-Local (FE80::/10) is auto-configured on every interface and used for neighbor discovery. Unique Local (FC00::/7) is similar to RFC 1918 private addresses
  • EUI-64: A method to auto-generate the 64-bit interface ID from the 48-bit MAC address by inserting FFFE in the middle and flipping the 7th bit
  • SLAAC & DHCPv6: Stateless Address Autoconfiguration uses Router Advertisements to provide the prefix; DHCPv6 can supply additional information (stateless) or manage full addressing (stateful)
  • NDP (Neighbor Discovery Protocol): Replaces ARP in IPv6 using ICMPv6 messages — Neighbor Solicitation (NS), Neighbor Advertisement (NA), Router Solicitation (RS), and Router Advertisement (RA)
IPv6 is a significant portion of the CCNA 200-301 exam. Unlike IPv4, IPv6 has no broadcast — it uses multicast and anycast instead. Remember the key multicast addresses: FF02::1 (all nodes), FF02::2 (all routers), FF02::1:FF00::/104 (solicited-node). For the exam, be comfortable shortening IPv6 addresses, identifying address types by their prefix, and explaining how SLAAC works with NDP.
02
Network Access
4 lessons
Ethernet & Switching Concepts

Key Concepts

  • MAC Addresses: 48-bit hardware addresses (e.g., AA:BB:CC:DD:EE:FF) burned into the NIC. The first 24 bits are the OUI (vendor), the last 24 bits are the device identifier
  • Switch Forwarding Methods: Store-and-forward (receives full frame, checks CRC, then forwards) vs cut-through (forwards as soon as it reads the destination MAC, lower latency but no error checking)
  • MAC Address Table: Switches learn source MACs dynamically and associate them with the ingress port. Unknown unicast frames are flooded out all ports except the source port
  • Full Duplex & Speed: Modern switches auto-negotiate speed (10/100/1000 Mbps) and duplex. Duplex mismatches cause collisions and poor performance — a common troubleshooting scenario
  • Ethernet Frame: Preamble (7 bytes), SFD (1 byte), Destination MAC (6), Source MAC (6), Type/Length (2), Payload (46-1500), FCS (4). The minimum frame size is 64 bytes
Switches are Layer 2 devices that make forwarding decisions based on MAC addresses. When a frame arrives, the switch looks up the destination MAC in its MAC address table. If found, it forwards out the specific port; if not, it floods the frame. Understanding this process is essential because VLANs, STP, and port security all build on top of basic switch forwarding behavior.
VLANs & Trunking

Key Concepts

  • VLANs: Logically segment a single physical switch into multiple broadcast domains. Each VLAN acts as a separate LAN — traffic between VLANs requires a Layer 3 device (router or L3 switch)
  • Access Ports: Assigned to exactly one VLAN. The switch strips any VLAN tag before delivering the frame to the end device. Configured with switchport mode access and switchport access vlan X
  • Trunk Ports (802.1Q): Carry traffic for multiple VLANs between switches. Each frame is tagged with a 4-byte 802.1Q header (TPID + TCI with 12-bit VLAN ID). The native VLAN is sent untagged
  • Native VLAN: Frames on the native VLAN (default VLAN 1) cross the trunk untagged. Native VLAN mismatches between switches cause traffic leakage. Best practice: change the native VLAN from VLAN 1 and match it on both ends
  • Inter-VLAN Routing: Router-on-a-stick uses subinterfaces on a single router port, each configured with a VLAN encapsulation and gateway IP. SVIs (Switch Virtual Interfaces) on a Layer 3 switch are more efficient
VLANs are one of the most heavily tested CCNA topics. Remember that VLANs are locally significant to each switch; you need a trunk link to extend a VLAN across switches. Always verify trunk status with show interfaces trunk and VLAN assignment with show vlan brief. A common exam trap: DTP (Dynamic Trunking Protocol) can auto-negotiate trunk links, but best practice is to manually configure trunks and disable DTP with switchport nonegotiate.
Spanning Tree Protocol

Key Concepts

  • Purpose of STP (802.1D): Prevents Layer 2 loops by placing redundant ports in a blocking state. Without STP, broadcast storms would saturate the network, and MAC address tables would become unstable
  • Root Bridge Election: The switch with the lowest Bridge ID (priority + MAC address) becomes the root bridge. Default priority is 32768; configure a lower priority to control root bridge placement
  • Port Roles: Root port (best path toward the root bridge), Designated port (best port on each segment, forwards traffic), Alternate/Blocked port (redundant path, does not forward)
  • Port States: Blocking (receives BPDUs only), Listening (processes BPDUs, no MAC learning), Learning (learns MACs but does not forward), Forwarding (fully operational). Classic STP convergence takes 30-50 seconds
  • Rapid STP (802.1w): Reduces convergence to a few seconds using proposal/agreement mechanism. Port roles include Alternate (backup root port) and Backup (backup designated port). Port states simplified to Discarding, Learning, Forwarding
STP is critical for any switched network with redundant links. For the exam, know how the root bridge is elected (lowest priority wins, then lowest MAC as tiebreaker), how path cost determines root and designated ports (the lower the cost, the better), and the differences between classic STP, RSTP, and PVST+. Cisco uses Per-VLAN Spanning Tree Plus (PVST+) by default, running a separate STP instance per VLAN. Rapid PVST+ is the recommended mode for modern networks.
EtherChannel

Key Concepts

  • Purpose: Bundles multiple physical links into a single logical channel, increasing bandwidth and providing redundancy. STP treats the bundle as one link, so no ports are blocked
  • LACP (802.3ad): Industry-standard negotiation protocol. Interfaces can be set to Active (initiates) or Passive (responds). At least one side must be Active for the channel to form
  • PAgP (Cisco proprietary): Uses Desirable (initiates) and Auto (responds) modes. At least one side must be Desirable. Not compatible with non-Cisco devices
  • Static (mode on): Forces the EtherChannel without negotiation. Both sides must be set to on. No protocol messages exchanged, so misconfigurations are harder to detect
  • Load Balancing: EtherChannel distributes traffic based on a hash of source/destination MAC, IP, or port. Verify the method with show etherchannel load-balance
All member interfaces in an EtherChannel must share identical speed, duplex, VLAN configuration, and trunk settings. A mismatch causes the channel to fail or enter a suspended state. Always prefer LACP over PAgP because it is the open standard and supports up to 16 links (8 active + 8 standby). Verify status with show etherchannel summary and look for the (SU) flag indicating the port-channel is Layer 2, in use, and bundled correctly.
03
IP Connectivity
4 lessons
Static & Default Routing

Key Concepts

  • Routing Table Components: Each entry contains the destination network, subnet mask, next-hop IP or exit interface, administrative distance (AD), and metric. The router uses the longest prefix match to select the best route
  • Administrative Distance (AD): Determines route trustworthiness when multiple sources advertise the same prefix. Lower AD wins: Connected (0), Static (1), EIGRP (90), OSPF (110), RIP (120)
  • Static Routes: Manually configured with ip route [network] [mask] [next-hop | exit-interface]. Useful for stub networks, backup paths (floating static with higher AD), and small networks
  • Default Route: A static route to 0.0.0.0/0 that acts as the gateway of last resort. Matches any destination not found in the routing table. Essential for Internet connectivity
  • IPv6 Static Routes: Configured with ipv6 route [prefix/length] [next-hop | exit-interface]. Link-local next hops require specifying the exit interface as well
Static routes are the simplest form of routing but do not adapt to topology changes. Use them in small networks, for default routes, and as floating static routes (set AD higher than the dynamic protocol, e.g., ip route 10.0.0.0 255.0.0.0 192.168.1.1 200 as a backup to OSPF). For the exam, practice reading routing table output from show ip route and identifying the source code (C for connected, S for static, O for OSPF, etc.).
OSPF Single-Area

Key Concepts

  • OSPF Overview: Open Shortest Path First is a link-state protocol using Dijkstra's SPF algorithm. It uses cost (based on bandwidth) as its metric and supports VLSM and CIDR. OSPF operates over IP protocol 89
  • OSPF Neighbors: Routers must agree on Hello interval (default 10s on broadcast), Dead interval (default 40s), area ID, subnet, authentication, and stub flags. Neighbors are discovered via Hello packets sent to 224.0.0.5
  • Neighbor States: Down, Init, 2-Way, ExStart, Exchange, Loading, Full. A stable adjacency reaches the Full state. On broadcast networks, routers remain at 2-Way with non-DR/BDR neighbors
  • DR/BDR Election: On multi-access segments, a Designated Router (DR) and Backup DR reduce OSPF traffic. Elected by highest priority (default 1), then highest Router ID. Priority 0 means the router cannot be DR/BDR
  • OSPF Configuration: router ospf [process-id], network [address] [wildcard] area [area-id]. Alternatively, use ip ospf [process-id] area [area-id] directly on the interface
OSPF is the only dynamic routing protocol tested in depth on the CCNA 200-301. For single-area OSPF, all interfaces belong to Area 0 (backbone). Understand the cost formula: Reference Bandwidth (default 100 Mbps) / Interface Bandwidth. For modern networks, adjust the reference bandwidth with auto-cost reference-bandwidth 10000 to differentiate between gigabit and 10-gigabit links. Verify OSPF with show ip ospf neighbor and show ip ospf interface.
OSPF Multi-Area

Key Concepts

  • Why Multi-Area: Dividing a large OSPF domain into multiple areas reduces the size of the link-state database (LSDB), limits SPF recalculations, and summarizes routes at area boundaries
  • Area 0 (Backbone): All areas must connect to Area 0, either directly or via a virtual link. ABRs (Area Border Routers) sit between Area 0 and non-backbone areas
  • LSA Types: Type 1 (Router LSA) stays within an area. Type 2 (Network LSA) for multi-access segments. Type 3 (Summary LSA) advertised by ABRs between areas. Type 5 (External LSA) redistributed into OSPF by ASBRs
  • Route Types: O (intra-area), O IA (inter-area from ABR), O E1/E2 (external routes). E2 routes have a fixed metric regardless of internal cost; E1 adds internal cost to the external metric
  • Router Roles: Internal router (all interfaces in one area), ABR (interfaces in multiple areas including Area 0), ASBR (redistributes from another protocol), Backbone router (at least one interface in Area 0)
Multi-area OSPF is tested at an awareness level on the CCNA. You need to understand why areas exist, how ABRs summarize routes between areas, and how to identify route types in the routing table. Remember that all non-backbone areas must attach to Area 0 — a virtual link is the workaround when direct attachment is not possible. For troubleshooting, verify area assignments match on both sides of a link using show ip ospf interface brief.
First Hop Redundancy

Key Concepts

  • Problem Statement: End devices are configured with a single default gateway IP. If that router fails, all hosts lose connectivity. FHRP protocols provide a virtual IP shared between two or more routers for seamless failover
  • HSRP (Cisco): Hot Standby Router Protocol uses an Active/Standby model. The router with the highest priority (default 100) becomes Active. Preemption must be explicitly enabled. Timers: Hello 3s, Hold 10s. Uses virtual MAC 0000.0c07.acXX
  • VRRP (Open Standard): Virtual Router Redundancy Protocol uses a Master/Backup model. Preemption is enabled by default. The router whose real IP matches the virtual IP is automatically the Master (priority 255)
  • GLBP (Cisco): Gateway Load Balancing Protocol provides both redundancy and load balancing by assigning different virtual MACs to different hosts via the AVG (Active Virtual Gateway) and AVF (Active Virtual Forwarder) roles
  • HSRP Versions: HSRPv1 uses group numbers 0-255 and multicast 224.0.0.2. HSRPv2 supports groups 0-4095, uses multicast 224.0.0.102, and supports IPv6
HSRP is the FHRP most tested on the CCNA. Know how to configure it: standby [group] ip [virtual-ip], standby [group] priority [value], and standby [group] preempt. Without preemption, a recovered higher-priority router will not reclaim the Active role. Verify with show standby. While VRRP and GLBP are tested at an awareness level, understand their key differences from HSRP, especially that VRRP preempts by default and GLBP provides load balancing.
04
IP Services
4 lessons
NAT & PAT

Key Concepts

  • Static NAT: One-to-one mapping between a private (inside local) and public (inside global) IP address. Used for servers that need consistent reachability from the Internet. Configured with ip nat inside source static [local] [global]
  • Dynamic NAT: Maps private IPs to a pool of public IPs on a first-come, first-served basis. Uses an ACL to define which inside addresses are translated and a pool to define the available public addresses
  • PAT (Port Address Translation): Also called NAT overload. Many private IPs share a single public IP, differentiated by unique source port numbers. This is the most common form of NAT used in home and enterprise networks
  • NAT Terminology: Inside Local (private IP on the inside network), Inside Global (translated public IP), Outside Local (destination as seen from inside), Outside Global (actual destination on the Internet)
  • Verification: show ip nat translations displays the active translation table. show ip nat statistics shows hit counts, misses, and pool usage. clear ip nat translation * flushes all entries
NAT is essential because IPv4 address exhaustion means organizations must translate private addresses to public ones. The exam frequently tests NAT terminology — make sure you can identify the four address types (inside local, inside global, outside local, outside global) in a given scenario. PAT is by far the most widely deployed; configure it with ip nat inside source list [ACL] interface [outside-if] overload. Do not forget to mark interfaces as ip nat inside or ip nat outside.
DHCP & DNS

Key Concepts

  • DHCP DORA Process: Discover (client broadcast to find servers), Offer (server proposes an IP), Request (client formally requests the offered IP), Acknowledge (server confirms the lease). All four messages are broadcast in the initial exchange
  • DHCP Relay: When the DHCP server is on a different subnet, the router uses ip helper-address [server-ip] on the client-facing interface to forward DHCP broadcasts as unicast to the server
  • DHCP Configuration on IOS: ip dhcp pool [name], network [subnet] [mask], default-router [gateway], dns-server [ip]. Exclude addresses with ip dhcp excluded-address [start] [end]
  • DNS Record Types: A (hostname to IPv4), AAAA (hostname to IPv6), CNAME (alias to another hostname), MX (mail exchange server), NS (authoritative name server), PTR (reverse lookup, IP to hostname)
  • DNS Resolution: Client queries local DNS resolver, which checks its cache, then performs recursive queries to root servers, TLD servers, and authoritative servers. DNS uses UDP port 53 (TCP for zone transfers and large responses)
DHCP is almost guaranteed to appear on the CCNA exam. Memorize the DORA process and know that the client initially uses 0.0.0.0 as the source and 255.255.255.255 as the destination. If a client gets a 169.254.x.x address (APIPA), DHCP has failed. For DNS, understand that it translates human-readable domain names to IP addresses and be able to identify common record types. Both DHCP (67/68) and DNS (53) are UDP-based protocols.
NTP & SNMP

Key Concepts

  • NTP (Network Time Protocol): Synchronizes clocks across network devices using a hierarchical stratum model. Stratum 0 is an atomic clock; stratum 1 servers connect directly to it. Each additional hop adds one stratum level. Cisco IOS: ntp server [ip]
  • NTP Importance: Accurate timestamps are critical for log correlation, certificate validation, authentication protocols (Kerberos), and troubleshooting. Clock skew can cause syslog events to be misinterpreted
  • SNMP (Simple Network Management Protocol): Enables centralized monitoring and management. The NMS (Network Management System) polls agents on devices. Key components: MIB (Management Information Base), OIDs (Object Identifiers), community strings
  • SNMP Versions: SNMPv1/v2c use community strings (plaintext, insecure). SNMPv3 provides authentication (AuthNoPriv) and encryption (AuthPriv) and is the recommended version for production networks
  • SNMP Operations: Get (retrieve a specific OID), GetNext (walk through the MIB), Set (modify a value), Trap (unsolicited alert from agent to NMS), Inform (trap with acknowledgment)
NTP and SNMP are both tested at the foundational level. For NTP, know that lower stratum values are more accurate, and always configure at least two NTP servers for redundancy. For SNMP, the exam focuses on the differences between versions: v2c is widely deployed but insecure; v3 is the only version that provides encryption. Read-only community strings allow monitoring; read-write strings allow configuration changes and must be protected carefully.
QoS Concepts

Key Concepts

  • Why QoS: Network links have finite bandwidth. Without QoS, all traffic is treated equally (best effort), and latency-sensitive applications like VoIP suffer during congestion. QoS provides prioritization and bandwidth guarantees
  • QoS Mechanisms: Classification (identify traffic types), Marking (tag packets with priority values), Queuing (schedule transmission order), Shaping & Policing (control bandwidth), Congestion avoidance (WRED drops before queue fills)
  • Marking Values: Layer 2: CoS (Class of Service) in the 802.1Q tag, 3 bits (0-7). Layer 3: DSCP (Differentiated Services Code Point) in the IP header, 6 bits (0-63). Common DSCP values: EF (46) for voice, AF classes for data, CS values for backward compatibility
  • Trust Boundaries: Define where in the network QoS markings are trusted. Typically at the access switch closest to the endpoint. Untrusted traffic gets re-marked at the boundary to prevent abuse
  • Queuing: Weighted Fair Queuing (WFQ) allocates bandwidth proportionally. Low Latency Queuing (LLQ) adds a strict priority queue for real-time traffic. Class-Based WFQ (CBWFQ) allows custom bandwidth allocation per traffic class
QoS is tested at a conceptual level on the CCNA. You do not need to configure complex QoS policies, but you must understand the end-to-end QoS model: classify and mark traffic as close to the source as possible, then honor those markings at every hop. Know that voice traffic requires less than 150ms one-way latency, less than 30ms jitter, and less than 1% packet loss. DSCP is the modern standard for marking; the older IP Precedence field uses only 3 bits.
05
Security Fundamentals
4 lessons
Network Security Concepts

Key Concepts

  • CIA Triad: Confidentiality (data is accessible only to authorized parties — achieved through encryption), Integrity (data is not tampered with — verified through hashing like SHA-256), Availability (services are accessible when needed — protected via redundancy and DDoS mitigation)
  • Common Threats: Phishing (social engineering via email), DDoS (flooding a target to deny service), Man-in-the-Middle (intercepting traffic between two parties), Malware (viruses, ransomware, trojans), Password attacks (brute force, dictionary)
  • Defense in Depth: Multiple layers of security controls: firewalls, IPS/IDS, endpoint protection, access control, encryption, physical security. No single layer is sufficient alone
  • Firewalls: Stateful firewalls track connection state and allow return traffic automatically. Next-Generation Firewalls (NGFW) add application awareness, intrusion prevention, and URL filtering
  • VPNs: Site-to-site VPNs connect entire networks over encrypted tunnels (IPsec). Remote access VPNs allow individual users to securely connect to the corporate network (SSL/TLS or IPsec)
The CCNA security domain is broad but tested at a conceptual level. Understand the CIA triad as the foundation of all security decisions. Know the difference between IDS (detection, passive, out-of-band) and IPS (prevention, inline, can drop packets). For VPNs, be familiar with IPsec concepts: AH provides authentication only, ESP provides encryption and authentication. GRE tunnels are unencrypted but can be combined with IPsec for encrypted site-to-site connectivity.
Access Control Lists

Key Concepts

  • Standard ACLs (1-99, 1300-1999): Filter traffic based on source IP address only. Place as close to the destination as possible to avoid unintentionally blocking traffic to other destinations
  • Extended ACLs (100-199, 2000-2699): Filter by source IP, destination IP, protocol (TCP/UDP/ICMP), and port numbers. Place as close to the source as possible to drop unwanted traffic early
  • Named ACLs: More readable and maintainable than numbered ACLs. Created with ip access-list standard|extended [name]. Support sequence numbers for inserting and reordering entries
  • ACL Processing: Entries are evaluated top-down; the first match wins. Every ACL has an implicit deny any at the end. At least one permit statement is needed or all traffic is blocked
  • Applying ACLs: Applied to an interface with ip access-group [name|number] in|out. Inbound ACLs filter traffic entering the interface; outbound ACLs filter traffic leaving. Only one ACL per interface, per direction, per protocol
ACLs are heavily tested on the CCNA. The most common mistake is placing a standard ACL too close to the source, which blocks traffic to all destinations. Remember the rule of thumb: standard ACLs near the destination, extended ACLs near the source. When writing ACLs, always include a remark (remark [description]) for documentation. Use show access-lists to verify match counts and show ip interface [interface] to confirm ACL application direction.
AAA & 802.1X

Key Concepts

  • AAA Framework: Authentication (who are you?), Authorization (what can you do?), Accounting (what did you do?). Can be implemented locally on the device or centrally via an external server
  • RADIUS: Open standard (UDP 1812/1813). Combines authentication and authorization in a single response. Encrypts only the password field. Widely used for network access (Wi-Fi, VPN, 802.1X)
  • TACACS+ (Cisco): Uses TCP port 49. Separates authentication, authorization, and accounting into independent processes. Encrypts the entire payload. Preferred for device administration (managing routers and switches)
  • 802.1X Port-Based Access Control: Three roles — Supplicant (the client device), Authenticator (the switch), Authentication Server (RADIUS). The switch port stays unauthorized until the client successfully authenticates via EAP
  • EAP Methods: EAP-TLS (mutual certificate authentication, most secure), PEAP (server certificate + client password), EAP-FAST (Cisco, uses PAC for fast reauthentication)
For the CCNA, understand the differences between RADIUS and TACACS+: RADIUS is best for network access control, TACACS+ is best for device administration. In an 802.1X deployment, the switch acts as a middleman — it does not make the authentication decision itself but relays EAP messages between the supplicant and the RADIUS server. Until authentication succeeds, the port only allows EAPOL (EAP over LAN) frames. Know that ISE (Identity Services Engine) is Cisco's enterprise AAA and policy platform.
Wireless Security

Key Concepts

  • WPA2 (802.11i): Uses AES-CCMP encryption. WPA2-Personal uses a pre-shared key (PSK) suitable for home networks. WPA2-Enterprise uses 802.1X with a RADIUS server for per-user credentials
  • WPA3: Successor to WPA2. WPA3-Personal uses SAE (Simultaneous Authentication of Equals) which protects against offline dictionary attacks. WPA3-Enterprise uses 192-bit cryptographic suite for sensitive environments
  • Port Security: Limits the number of MAC addresses on a switch port. Violation modes: Protect (drops, no log), Restrict (drops + syslog), Shutdown (disables port, default). Configure with switchport port-security
  • DHCP Snooping: Prevents rogue DHCP servers by classifying ports as trusted (toward legitimate DHCP server) or untrusted (toward clients). Builds a binding table used by Dynamic ARP Inspection (DAI)
  • Wireless Architecture: Autonomous APs manage themselves. Lightweight APs (LAPs) are managed centrally by a Wireless LAN Controller (WLC) using CAPWAP (Control and Provisioning of Wireless Access Points) tunnels
Wireless security and Layer 2 security features are both part of this exam domain. For wireless, know that WPA2-Enterprise with 802.1X is the recommended approach for organizations. WPA3-Personal's SAE handshake is a significant improvement over WPA2-Personal's 4-way handshake because it prevents offline brute-force attacks. For port security, the default violation mode is shutdown, which err-disables the port. Recovery requires shutdown then no shutdown on the interface, or configure errdisable recovery.
06
Automation & Programmability
4 lessons
Network Automation Basics

Key Concepts

  • Why Automate: Manual CLI configuration does not scale. Automation reduces human error, ensures consistency across hundreds of devices, enables faster deployment, and supports version-controlled infrastructure
  • Controller-Based Networking: Separates the control plane (decisions about where to send traffic) from the data plane (actual packet forwarding). A centralized controller manages the network programmatically through APIs
  • Cisco DNA Center: Cisco's intent-based networking controller for campus networks. Provides automation, assurance (monitoring), policy management, and device provisioning through a GUI and APIs
  • Traditional vs Controller-Based: Traditional networks configure each device individually via CLI. Controller-based networks push configurations from a central point, offering single-pane-of-glass management and network-wide visibility
  • Infrastructure as Code (IaC): Network configurations stored as code files, versioned in Git, reviewed through pull requests, and deployed automatically. This brings software development practices to network operations
The automation domain is worth approximately 10% of the CCNA exam. You need to understand concepts rather than write code. Know the three planes: management plane (SSH, SNMP, APIs for accessing the device), control plane (routing protocols, STP, ARP), and data plane (actual forwarding of packets). Controller-based architectures centralize the control plane, making the network programmable and easier to manage at scale.
REST APIs & JSON

Key Concepts

  • REST API Fundamentals: Representational State Transfer uses HTTP methods to interact with resources. Stateless: each request contains all the information needed. Resources are identified by URIs (e.g., /api/v1/devices)
  • HTTP Methods: GET (retrieve data, safe/idempotent), POST (create a new resource), PUT (replace an entire resource), PATCH (partial update), DELETE (remove a resource). Response codes: 200 OK, 201 Created, 400 Bad Request, 401 Unauthorized, 404 Not Found
  • JSON (JavaScript Object Notation): Lightweight data format using key-value pairs. Objects use curly braces {}, arrays use square brackets []. Values can be strings, numbers, booleans, null, objects, or arrays. Example: {"hostname": "R1", "interfaces": [{"name": "Gi0/0", "ip": "10.1.1.1"}]}
  • YAML: Human-readable data serialization using indentation instead of braces. Often used in Ansible playbooks and configuration files. YAML is a superset of JSON
  • XML: Uses opening and closing tags (like HTML). More verbose than JSON but still used in NETCONF and some legacy APIs. Example: <hostname>R1</hostname>
For the CCNA, you must be able to read and interpret JSON output from a REST API. Know what each HTTP method does and which are idempotent (GET, PUT, DELETE produce the same result when called multiple times; POST does not). Understand that CRUD operations map to HTTP methods: Create = POST, Read = GET, Update = PUT/PATCH, Delete = DELETE. Be able to compare JSON, YAML, and XML data formats and identify their syntax differences.
Configuration Management Tools

Key Concepts

  • Ansible: Agentless (uses SSH), written in Python, configurations defined in YAML playbooks. Push model: the control node connects to managed devices and applies changes. Most popular for network automation due to its simplicity and agentless nature
  • Puppet: Agent-based (requires a Puppet agent on managed nodes), uses its own declarative language (Puppet DSL). Pull model: agents check in with the Puppet master for configuration updates. Strong in large-scale server environments
  • Chef: Agent-based, configurations written in Ruby (called recipes and cookbooks). Pull model: the Chef client on each node pulls configurations from the Chef server. Common in DevOps environments
  • Key Differences: Ansible is agentless (biggest advantage for networking); Puppet and Chef require agents. Ansible uses YAML; Puppet uses its own DSL; Chef uses Ruby. All three enforce desired state — they make the device match the defined configuration
  • Idempotency: Running the same automation task multiple times produces the same result. If the device already matches the desired configuration, no changes are made. This prevents configuration drift
The CCNA tests your awareness of these tools, not your ability to write playbooks or recipes. The key exam points are: Ansible is agentless and push-based (best for network devices that cannot run agents), Puppet and Chef are agent-based and pull-based. All three tools are idempotent and declarative — you define the desired end state, not the step-by-step commands. Ansible is the most widely used tool for network automation because network devices (routers, switches) typically support SSH but not custom agents.
Software-Defined Networking

Key Concepts

  • SDN Architecture: Application layer (business apps), Control layer (SDN controller), Infrastructure layer (network devices). Northbound APIs connect apps to the controller; Southbound APIs/protocols connect the controller to devices
  • Southbound Interfaces: OpenFlow (original SDN protocol, directly programs forwarding tables), NETCONF (uses XML over SSH, port 830, supports get-config and edit-config operations), RESTCONF (RESTful interface to NETCONF datastores, uses JSON or XML over HTTPS)
  • Cisco SD-WAN: Extends SDN principles to the WAN. Components: vManage (management), vSmart (control plane), vBond (orchestration), vEdge/cEdge (data plane routers). Provides centralized policy, transport independence, and application-aware routing
  • Cisco SD-Access: SDN solution for campus networks built on DNA Center. Uses VXLAN fabric for overlay networking and LISP for endpoint location. Automates microsegmentation through Scalable Group Tags (SGTs)
  • Benefits of SDN: Centralized management, programmability via APIs, consistent policy enforcement, faster provisioning, network-wide visibility, and the ability to integrate with DevOps toolchains and CI/CD pipelines
SDN concepts are tested at a high level. Know the three-layer SDN architecture and the direction of the APIs: northbound (controller to application, typically REST) and southbound (controller to device, e.g., OpenFlow, NETCONF, RESTCONF). For Cisco SD-WAN, understand that vManage provides the GUI, vSmart handles control-plane policy, and vEdge routers form the data plane. NETCONF uses YANG data models to define the structure of configuration and operational data — YANG is to NETCONF what MIB is to SNMP.

Ready to test your knowledge?

Put your CCNA skills to the test with our free practice questions covering all six exam domains.

Start Practice Exam →