Week 2 · Lesson 11

Network Architectures

A topology says how devices can be connected; an architecture says how they should be connected for a given scale, budget, and goal. This lesson tours the campus models (two-tier and three-tier), the data-centre spine-leaf fabric, the WAN connection shapes, the SOHO all-in-one, and the split between on-premises and cloud.

CCNA 200-301 Domain 1.0 Network Fundamentals Verified 2026-10-11
Part 1

Why architecture matters

The word topology describes how nodes can be arranged — star, mesh, ring, and so on (Lesson 12 covers these in detail). An architecture goes further: it is a proven design pattern that combines topologies, layers, and roles so that the network stays fast, scalable, and manageable as it grows from tens of devices to tens of thousands.

The central idea in almost every campus and enterprise design is hierarchy. If every device connected directly to every other device, the number of links (and the cost, and the configuration work) would explode, and changes in one corner would ripple everywhere. Instead, engineers group devices by role into layers, and each layer talks mostly to the layer above and below it.

Scalability

Add a new access switch without redesigning the core.

Manageability

Policy lives in one consistent place — the distribution layer.

Availability

Redundant paths at each layer survive a single device or link failure.

Definition — network architecture. A structured design that assigns devices to roles or layers (access, distribution, core; or leaf and spine) and defines how those layers interconnect, so the network can scale while remaining reliable and easy to operate.
Part 2

The three-tier campus model

The classic enterprise campus design uses three layers. Each has a distinct job, and the exam expects you to know which job belongs to which layer.

Campus hierarchy · select a layer
Core Distribution A Distribution B Access A1 Access A2 Access B1 Access B2 End devices connect here

LayerJobTypical devices
AccessConnects end devices (PCs, phones, access points, printers) to the network. Enforces port-level policy: VLAN assignment, port security, Power over Ethernet, and access lists.Layer 2 access switches
DistributionAggregates the access switches and is the layer of policy: inter-VLAN routing, filtering, QoS, route summarisation, and redundancy between access and core.Layer 3 switches / routers
CoreThe high-speed backbone that moves large volumes of traffic between distribution blocks and out to the WAN and data centre. It should forward quickly and touch traffic as little as possible.High-end Layer 3 switches

A useful mental model: the access layer is the front door where users arrive, the distribution layer is where the building’s rules are enforced, and the core is the motorway that carries everything quickly between blocks.

Exam tip. Match the job to the layer. Access = connect hosts and enforce port policy. Distribution = policy, inter-VLAN routing, aggregation, and summarisation. Core = fast transport, minimal manipulation. If a question mentions “connecting end devices” the answer is access; if it mentions “policies between access blocks” the answer is distribution.
Part 3

Two-tier and the spine-leaf fabric

The two-tier (collapsed core) model

For small and medium sites, a dedicated core is overkill — it adds devices, links, and cost for traffic volumes that do not need it. The two-tier or collapsed core design merges the core and distribution jobs into a single collapsed-core layer, leaving two layers: access and collapsed core.

This cuts latency (fewer hops), cost, and management overhead, which is why it dominates small campuses and branch sites. The trade-off is scale: as traffic and the number of blocks grow, a single collapsed layer becomes a bottleneck and a bigger failure domain, and a dedicated core becomes worthwhile again.

Decision rule. Choose two-tier (collapsed core) when the site is small enough that one layer can handle both policy and transport. Move to three-tier when the core must carry traffic between many distribution blocks independently of any single block’s policy decisions.

Spine-leaf for the data centre

The traditional campus hierarchy was designed for north–south traffic (users reaching servers). A modern data centre is dominated by east–west traffic: servers talking to other servers, virtual machines migrating, storage replicating. For that pattern a different fabric is used: spine-leaf.

A spine-leaf fabric has two device roles: a row of spine switches (the backbone), and a row of leaf switches that connect to the servers and storage.

Spine-leaf fabric · select a server to trace its path
Spine 1 Spine 2 Leaf 1 Leaf 2 Leaf 3 Leaf 4 Server 1 Server 2 Server 3 Server 4

The rule that defines the design: every leaf connects to every spine, and leaves never connect to each other; spines never connect to each other. Keep it fixed. That rule gives:

Note. Spine-leaf is a form of full mesh between its two layers: the leaves form one tier and the spines another, and every device in one tier links to every device in the other. It is not a full mesh between all devices — that would be far more cabling than this structured pattern.
Part 4

WAN topologies

A wide area network (WAN) joins sites that are far apart, usually over links leased from a service provider. Three shapes recur, and each is a trade-off between cost and redundancy.

How many links? · set the site count

WAN topologyHow it is wiredStrengthWeakness
Hub-and-spokeEvery remote site (spoke) connects only to a central site (hub).Cheap, simple, easy to manage; one place to apply policy.The hub is a single point of failure and a bottleneck; spokes cannot talk directly.
Full meshEvery site connects directly to every other site.Maximum redundancy and best path between any two sites.Very expensive; links grow as n(n−1)/2.
Partial meshSome sites are fully interconnected; others connect to one or two.Balances redundancy against cost; common in real WANs.Requires careful routing so traffic takes the path you intend.

Recall from Lesson 12 that the link count for a full mesh of n devices is n(n−1)/2. Four sites need 4×3/2 = 6 links; six sites need 15 links. That rapid growth is exactly why full mesh is reserved for high-value core links and partial mesh is used everywhere else.

Watch out. Hub-and-spoke is efficient but hides a risk: if the hub or its WAN link fails, every spoke is cut off. A production hub-and-spoke normally uses a redundant hub or a backup path so the centre is not a single point of failure.
Part 6

The SOHO architecture, and on-premises vs cloud

A small office / home office (SOHO) does not stack separate devices the way an enterprise does. Instead, one inexpensive box — often called a residential gateway or integrated services router — performs every role at once.

RoleWhat it does
RouterForwards traffic between the home LAN and the ISP.
SwitchProvides a few wired Ethernet LAN ports.
Wireless access pointLets Wi-Fi hosts join the LAN.
Firewall and NATBlocks unwanted inbound traffic and lets many private hosts share one public address (Week 6 covers NAT).
DHCP serverAutomatically hands out addresses, masks, and a default gateway to hosts.

On the outside, the SOHO connects to the ISP through whatever access technology is available: cable, DSL, fibre to the home, fixed wireless, satellite, or cellular. The whole design favours low cost and zero administration over the redundancy and policy control of an enterprise campus.

On-premises vs cloud

Where the servers and services live is itself an architectural choice.

AspectOn-premisesCloud
Who owns the hardwareThe organisation buys, houses, powers, and maintains it.A provider owns and operates it; the customer consumes it over the network.
Cost modelLarge up-front capital expense (CapEx).Ongoing operating expense (OpEx), pay for what you use.
ScalingSlow and costly — buy and install capacity.Fast and elastic — add or release resources on demand.
Control and responsibilityFull control; the organisation owns all security and maintenance.Shared responsibility; the provider secures the platform, the customer secures what it puts on it.

Cloud services are usually grouped into three models: IaaS (infrastructure as a service — virtual machines, storage, networks), PaaS (platform as a service — a managed environment to deploy applications), and SaaS (software as a service — ready-made applications such as webmail). Many organisations run a hybrid design, keeping sensitive or legacy systems on-premises while moving elastic workloads to the cloud.

Exam tip. The five essential characteristics of cloud computing, straight from the NIST definition, are: on-demand self-service, broad network access, resource pooling, rapid elasticity, and measured service. Expect any of these as a correct option.
Part 7 · Your turn

Review

Check what you have learned with these review questions.

Review · 6 questions

Sources

Sources & references

  1. Cisco. CCNA (200-301) Exam Topics, Domain 1.0 Network Fundamentals. cisco.com.
  2. Cisco. Campus Network Design — Hierarchical Design Model, Cisco Validated Designs. cisco.com.
  3. NIST. SP 800-145: The NIST Definition of Cloud Computing (2011). csrc.nist.gov.
  4. IANA. Autonomous System (AS) Numbers registry. iana.org.

Target exams: CCNA 200-301 v1.1 · CyberOps Associate 200-201. Last content verification: 2026-10-11.