All certifications
Certification prep · Cisco

Cisco CCNA (200-301)

FHG University prepares you for this exam on the Network Foundations track. Here are the modules mapped to its published objectives, and the opening of one to read now.

Examination preparation — these exams are set and awarded by their issuers. FHG prepares you for them and cannot grant them.

Cisco states the last day to test on 200-301 v1.1 is 2 February 2027.

The modules mapped to it

6 modules · about 20 h 15 min estimated in all

Network Fundamentals: The Vocabulary Every Later Domain AssumesNetwork Foundations · about 3 hObjective area: Network FundamentalsPreview below
Network Access: VLANs, Trunking, Spanning Tree and WirelessNetwork Foundations · about 4 hObjective area: Network AccessMembers
IP Connectivity: Routing Tables, Static Routes and OSPFNetwork Foundations · about 3 h 30 minObjective area: IP ConnectivityMembers
Security Fundamentals: Ports, Access Control and the Device ItselfNetwork Foundations · about 3 h 30 minObjective area: Security FundamentalsMembers
IP Services: NAT, DHCP, NTP and the Protocols That Run QuietlyNetwork Foundations · about 2 h 45 minObjective area: IP ServicesMembers
Automation and Programmability: Concepts, Not ConfigurationNetwork Foundations · about 3 h 30 minObjective area: Automation and ProgrammabilityMembers
Free preview · the opening of one module

Network Fundamentals: The Vocabulary Every Later Domain Assumes

Network Foundations · about 3 h

Every objective in CCNA v1.1 domain 1.0, Network Fundamentals, taught at the depth Cisco's verbs ask: components and topologies, cabling and the interface counters that diagnose it, TCP and UDP, IPv4 and IPv6 configured and verified on IOS, switching, wireless principles and virtualization. A final section covers the client-connectivity troubleshooting that CCNA v2.0 adds from 3 February 2027, so the module serves both exam versions.

Network components and topology architectures

When a fault report arrives, the first question is which device made the decision that went wrong. That depends on knowing what each component decides, and on which information.

ComponentDecidesUsing
RouterWhich network a packet goes to next; separates broadcast domainsDestination IP against the routing table
Layer 2 switchWhich port a frame leaves on, within a VLANDestination MAC against the MAC address table
Layer 3 switchBoth, in hardware, using SVIs or routed portsMAC table within a VLAN; routing table between VLANs
Next-generation firewallWhether a flow is permitted, inspected or blockedSession state plus application, user identity, URL category and threat intelligence
IPSWhether attack traffic is droppedSignatures and anomaly detection, inline
Access pointBridges wireless clients onto the wired network802.11 frames; the SSIDs and security it is given
ControllerCentral configuration and policy for many devicesA WLC manages lightweight APs over CAPWAP; an SDN controller such as Catalyst Center manages switches and routers
Endpoints, serversGenerate and consume trafficTheir own IP configuration (see the client-OS section)

IPS versus IDS. An IPS sits inline and can drop traffic; an IDS gets a copy (from a SPAN port, for example) and can only alert. NGFWs, such as Cisco Secure Firewall, usually include an IPS engine.

PoE (1.1h). The switch, as power sourcing equipment, powers a powered device (phone, AP, camera) over the data cable. Power at the switch port: 802.3af up to 15.4 W, 802.3at (PoE+) up to 30 W, 802.3bt up to 60 W (Type 3) or 90 W (Type 4); Cisco UPOE and UPOE+ are Cisco's 60 W and 90 W implementations. The switch has a finite budget: when it is spent, a new device stays unpowered even though the link is fine. show power inline shows the budget available, used and remaining, and each port's class and draw. Per-port PoE configuration belongs to the Network Access module.

Topology architectures (1.2).

  • Two-tier (collapsed core): access switches uplink to a pair that combines distribution and core. Fits a building or small campus.
  • Three-tier: access (endpoints connect), distribution (policy, inter-VLAN routing, aggregation) and core (fast transport between distribution blocks, minimal policy). Fits large campuses.
  • Spine-leaf: data center design. Every leaf connects to every spine; leaves never interconnect, nor do spines. Servers attach to leaves, so any server reaches any other through one leaf-spine-leaf path, and capacity grows by adding spines or leaves. It suits east-west traffic between servers.
  • WAN: connects sites over distance: leased lines, MPLS, Metro Ethernet, internet VPN and SD-WAN overlays.
  • SOHO: one device often acts as router, switch, AP, firewall and DHCP server behind a broadband modem.
  • On-premises and cloud: on-premises means the organization runs the infrastructure; cloud means a provider does, as IaaS, PaaS or SaaS, public, private or hybrid. The network question becomes how sites reach it: internet, VPN or a private connection.

CCNA v2.0's exam topics do not name components or topologies as objectives. Cisco calls its list a general guide, so this stays as background for both versions.

Members · the rest of this module

You’ve read 1 of 12 sections.

Members read the rest of this module and every module listed above, in their track’s order, and each one they finish is logged in hours with a content outline. $25 a month, cancel any time.

Already a member? Sign in, then pick up from your dashboard.

Add FHG to how you study. Keep every hour on record.

Members keep a record of the modules they finish and the study time each one takes.

Preparation means the material maps to the published objectives. It is not a promise of a pass, and Cisco sets, administers and awards the exam.