Study guide

1.1 Enterprise Network Design: Two-Tier, Three-Tier, Fabric, and Cloud Architectures

Cisco ENCOR 350-401 CCNP Enterprise Core

Track your progress as you read

Finished sections get a check mark.

1 Introduction & Exam Overview

0.1 Cisco 350-401 ENCOR Exam Logistics, Blueprint Structure, and Certification Paths 0.2 Preparation Strategy, Lab Environment Setup, and Practical Test Pacing

2 Enterprise Campus Architecture and High Availability

1.1 Enterprise Network Design: Two-Tier, Three-Tier, Fabric, and Cloud Architectures 1.2 High Availability Architecture: Device Redundancy, FHRPs, and Stateful Switchover (SSO) 1.3 Quality of Service (QoS) Architecture, Classification, Queuing, and Configuration Interpretation

3 Cisco Software-Defined Architecture: SD-WAN and SD-Access

2.1 Cisco Catalyst SD-WAN: Control, Management, and Data Planes 2.2 Cisco SD-Access Architecture: Control Plane, Data Plane, and Fabric Node Roles 2.3 SD-Access Campus Interoperability: Integrating Traditional Networks with Fabric

4 Device and Network Virtualization Technologies

3.1 Device Virtualization: Type 1/2 Hypervisors, Virtual Machines, and Virtual Switching 3.2 Data Path Virtualization: VRF-Lite, GRE Tunneling, and IPsec VPN Fundamentals 3.3 Network Virtualization Overlays: LISP and VXLAN Encapsulation Mechanics

5 Layer 2 Infrastructure: Trunking, EtherChannel, and Spanning Tree

4.1 802.1Q Trunking, Native VLAN, and Dynamic Trunking Protocol Troubleshooting 4.2 EtherChannel Bundling: Static, LACP, and PAgP Implementation and Verification 4.3 Spanning Tree Architecture: RSTP, MST, and STP Protection Mechanisms

6 Layer 3 Routing: OSPF Multi-Area and Protocol Comparison

5.1 Enterprise Routing Principles: Distance Vector vs. Link-State, EIGRP, and OSPF 5.2 OSPFv2 and OSPFv3 Multi-Area Architecture: LSAs, Area Types, and Summarization 5.3 Policy-Based Routing (PBR) Architecture, Configuration, and Route-Maps

7 Exterior Routing: BGP Peering and Path Selection

6.1 External BGP (eBGP) Peering, States, Neighbor Adjacencies, and Timers 6.2 BGP Path Attributes and the Step-by-Step Best Path Selection Algorithm

8 IP Services and First-Hop Redundancy

7.1 Time Synchronization: Network Time Protocol (NTP) and Precision Time Protocol (PTP) 7.2 Network Address Translation: Static NAT, Dynamic NAT, and PAT/Overload 7.3 First Hop Redundancy Protocols: HSRP and VRRP Implementation and Failover

9 IP Multicast Architecture and Protocols

8.1 Multicast Addressing, IGMPv2/v3 Host Membership, and the RPF Check 8.2 Protocol Independent Multicast Sparse Mode (PIM-SM) and Rendezvous Point Discovery 8.3 Anycast RP with MSDP, Source-Specific Multicast (SSM), and Bidirectional PIM

10 Network Diagnostics, Monitoring, and Telemetry

9.1 Network Diagnostic Tools: Conditional Debugging, Traceroute, SNMPv3, and Syslog Logging 9.2 Flexible NetFlow (FNF) Architecture: Flow Records, Exporters, and Monitors 9.3 Switched Port Analyzer: Local SPAN, Remote SPAN (RSPAN), and Encapsulated RSPAN (ERSPAN)

11 Performance Monitoring and Model-Driven Assurance

10.1 IP Service Level Agreements (IP SLA) Probes, Responder, and Route Tracking 10.2 Cisco Catalyst Center: Assurance Dashboards, AI Analytics, and Machine Reasoning Workflows 10.3 Model-Driven Telemetry and Programmable Interfaces: NETCONF and RESTCONF Verification

12 Device Access Control and AAA Architecture

11.1 Device Line Protection: Console, Aux, VTY, Local Authentication, and Privilege Levels 11.2 AAA Architecture: Comparing RADIUS vs. TACACS+ and Method List Configuration

13 Infrastructure Security: ACLs, CoPP, and API Security

12.1 IPv4 and IPv6 Access Control Lists (ACLs): Standard, Extended, and Named Rules 12.2 Control Plane Policing (CoPP): Protecting the Route Processor with MQC 12.3 REST API Security: Token Authentication, TLS Transport, and Rate Limiting

14 Enterprise Network Security Design: ISE, TrustSec, and MACsec

13.1 Endpoint Security Architecture: 802.1X, Cisco ISE Posture, and Profiling 13.2 Next-Generation Firewalls (FTD) and Enterprise Threat Defense Design 13.3 Cisco TrustSec (Security Group Tags) and MACsec (802.1AE) Layer 2 Encryption

15 Network Automation Fundamentals: Python, JSON, and YANG

14.1 Python Fundamentals for Network Engineers: Data Types, Control Flow, and Libraries 14.2 JSON Data Encoding: Syntax, Formatting Rules, and Python Serialization 14.3 YANG Data Modeling: Modules, Tree Structures, and Data Representation

16 Controller REST APIs and RESTCONF Implementation

15.1 Cisco Catalyst Center Intent APIs and Authentication Workflows 15.2 Cisco Catalyst SD-WAN Manager (vManage) REST APIs and Device Interaction 15.3 RESTCONF Protocol Operations: HTTP Verbs, Datastores, and Response Codes

17 Event-Driven Automation and Infrastructure Orchestration

16.1 Cisco Embedded Event Manager (EEM) Applet Architecture and Event Detectors 16.2 Configuration Management: Comparing Ansible, Puppet, Chef, and SaltStack 16.3 Infrastructure as Code (IaC) Principles with Terraform in Enterprise Networks

1.1 Enterprise Network Design: Two-Tier, Three-Tier, Fabric, and Cloud Architectures

Key Takeaways Explain This Topic AI

Hierarchical three-tier campus networks decouple transport into Access, Distribution, and Core layers, establishing modular failure domains and deterministic routing boundaries.

Collapsed core (two-tier) designs consolidate distribution and core functionality into a single switching layer, lowering capital expense for small-to-midsize campuses while maintaining dual-homed access links.

Spine-and-leaf Clos fabrics provide equidistant, non-blocking, predictable latency across all endpoints using Equal-Cost Multi-Path (ECMP) Layer 3 transport, ideal for dense east-west traffic patterns.

Routed access layer architectures shrink Layer 2 broadcast domains to the access switch edge, replacing Spanning Tree loop-resolution mechanisms with sub-second routed convergence.

Cloud edge connectivity bridges enterprise campus environments to SaaS, PaaS, and IaaS workloads through dedicated co-location interconnects, secure IPsec overlays, and automated cloud onramps.

Last updated: October 2026

Enterprise Network Design: Two-Tier, Three-Tier, Fabric, and Cloud Architectures

Enterprise campus networks must support expanding collections of client endpoints, IoT devices, wireless access points, and low-latency application workloads. Modern campus design requires a structured architecture that balances high availability, deterministic traffic routing, operational simplicity, and modular scalability.

Hierarchical Three-Tier Campus Model

The classic three-tier hierarchical architecture divides enterprise networking functions into three discrete layers: Access, Distribution, and Core. This modular separation isolates faults, simplifies troubleshooting, and establishes predictable traffic paths. +-------------------------------------------------------------+

  • | CORE LAYER |
  • | (High-Speed Transport, No Packet Filters) |
  • +-------------------------------------------------------------+
  • | |
  • | | Redundant 40G/100G Links
  • | |
  • +-------------------------------------------------------------+
  • | DISTRIBUTION LAYER |
  • | (Policy Boundary, Routing, ACLs, Summarization) |
  • +-------------------------------------------------------------+
  • | |
  • | | Dual-Homed Uplinks (L2 or L3)
  • | |
  • +-------------------------------------------------------------+
  • | ACCESS LAYER |
  • | (Endpoint Connectivity, 802.1X, PoE, Port Security) |
  • +-------------------------------------------------------------+
  • Access Layer

The access layer represents the network edge where user endpoints connect directly to campus infrastructure. Primary responsibilities include:

End-Station Connectivity: Connecting desktop computers, IP phones, wireless access points, network printers, and surveillance cameras via 1 Gbps, 2.5 Gbps, 5 Gbps (mGig), and 10 Gbps Ethernet interfaces.

Identity and Security: Enforcing 802.1X port-based authentication, Dynamic ARP Inspection (DAI), DHCP Snooping, IP Source Guard, and MAC-based port security.

Power Delivery: Supplying inline Power over Ethernet (PoE, PoE+, and 802.3bt UPoE/UPoE+) to access points and VoIP handsets.

QoS Marking: Performing initial Layer 2 Class of Service (CoS) and Layer 3 Differentiated Services Code Point (DSCP) classification and marking at the edge trust boundary.

Distribution Layer

The distribution layer aggregates uplinks from multiple access switches and serves as the primary policy demarcation boundary. Responsibilities include:

Policy Enforcement: Applying Access Control Lists (ACLs) to filter traffic between different campus departments or security zones.

Routing and Gateway Services: Acting as the default gateway for access subnets using First Hop Redundancy Protocols (HSRP or VRRP) in traditional Layer 2 access models, or terminating Layer 3 routed access uplinks.

Route Summarization: Summarizing contiguous access-layer subnets before advertising them into the enterprise core, shielding the core routing table from localized link flaps.

Broadcast Containment: Defining the boundary of Layer 2 broadcast domains to prevent broadcast storms from propagating across the campus.

Core Layer (Network Backbone)

The core layer provides high-speed, non-blocking transport between distribution blocks, centralized data centers, and the enterprise edge. Core design is governed by two strict mandates: maximum throughput and minimal latency .

Keep Policy Out of the Core: Cisco campus design keeps the core simple: no per-user ACLs, inspection, or other policy. Even when a switch can apply ACLs in hardware, putting policy in the core adds complexity and lets one mistake affect every distribution block, so policy belongs at the distribution and access layers.

Deterministic Redundancy: Core nodes employ dual-homed, fully meshed Layer 3 point-to-point links with sub-second routing protocol convergence (such as tuned OSPF or IS-IS).

Two-Tier Collapsed Core Design

In smaller enterprise environments, deploying separate physical switching platforms for core and distribution layers is unnecessary and cost-prohibitive. The collapsed core design combines the distribution and core layers into a single consolidated switching tier.

Access switches connect directly to the collapsed core switches over redundant Layer 2 trunks or Layer 3 routed links. This approach provides significant capital and operational savings while preserving dual-homed fault tolerance for campus endpoints.

Comparison: Two-Tier vs. Three-Tier Architectures

Design Dimension Two-Tier (Collapsed Core) Three-Tier (Core-Distribution-Access)

Target Scale Smaller campuses where one switch pair can act as both distribution and core Larger, multi-building campuses where a separate core interconnects many distribution blocks

Hardware Footprint Consolidated; reduces switch count, power, and rack space Discrete platforms dedicated to backbone transport vs. policy

Failure Domain Shared policy and transport failure domain Strictly bounded; access or distribution flaps do not reach the core

Routing Boundary Layer 3 default gateways reside on the collapsed core switches Layer 3 gateways terminate on distribution or access switches

Expansion Capability Limited; adding access blocks eventually oversubscribes the core Modular; new distribution blocks attach without core redesign

Capital & Operational Cost Lower initial capital expenditure and simpler management Higher hardware expenditure, requires structured operational teams

Spine-and-Leaf Clos Fabric Topologies

Traditional multi-tier architectures were optimized for client-server communication. However, modern workloads—including private cloud virtualization, storage replication, containerized microservices, and peer-to-peer enterprise collaboration—generate massive horizontal traffic volumes.

To eliminate the scaling limitations of Spanning Tree, modern enterprise fabrics implement a two-tier spine-and-leaf topology based on Charles Clos mathematical network designs. +-----------------+ +-----------------+

  • | Spine Switch 1 | | Spine Switch 2 |
  • +-----------------+ +-----------------+
  • / | \ / | \
  • / | \ / | \
  • / | \ / | \
  • +--------+ +--------+ +--------+ +--------+ +--------+
  • | Leaf 1 | | Leaf 2 | | Leaf 3 | | Leaf 4 | | Leaf 5 |
  • +--------+ +--------+ +--------+ +--------+ +--------+
  • | | | | |
  • [Servers / Endpoints / APs] [Servers / Endpoints / APs]
  • Architectural Rules of Spine-and-Leaf

Strict Interconnection Rules: Every leaf switch connects to every spine switch. Leaf switches never connect directly to other leaf switches. Spine switches never connect to other spine switches.

Equidistant Two-Hop Latency: Every leaf switch is exactly two hops away from any other leaf switch across the spine (Ingress Leaf -> Spine -> Egress Leaf), guaranteeing uniform, low latency.

Layer 3 Underlay with ECMP: All inter-switch links operate as routed Layer 3 interfaces. Equal-Cost Multi-Path (ECMP) routing utilizes all available bandwidth simultaneously, completely eliminating Spanning Tree blocking.

Overlay Decoupling: Overlay encapsulation protocols (such as VXLAN with BGP EVPN or LISP in Cisco SD-Access) carry user subnets and segmentation policies over the physical Layer 3 underlay without extending Layer 2 Spanning Tree domains.

Traffic Flow Patterns: North-South vs. East-West

Network traffic distribution fundamentally dictates switch backplane capacity and uplink sizing.

Characteristic North-South Traffic East-West Traffic

Primary Direction Vertical flow between clients and external networks Horizontal flow between internal endpoints or servers

Typical Endpoints Campus workstations accessing SaaS, Internet, or public cloud VM-to-VM replication, database sync, distributed storage

Traversed Layers Traverses Access -> Distribution -> Core -> Enterprise Edge Traverses Leaf -> Spine -> Leaf directly within the fabric

Design Driver High-throughput WAN edge routers, stateful firewalls, NAT Non-blocking bisectional bandwidth, ECMP, predictable latency

Typical Dominance Dominant in classic client-server campuses Dominant in virtualized data centers and fabric designs

Enterprise Edge and Cloud Connectivity

The Enterprise Edge represents the secure boundary connecting internal campus resources to outside networks. It encompasses Internet aggregation, demilitarized zones (DMZ), remote access VPN concentrators, and Software-Defined WAN (SD-WAN) routers.

Enterprise organizations connect to cloud service models through distinct connectivity options:

Infrastructure as a Service (IaaS): Enterprise infrastructure hosted in virtualized environments (e.g., AWS EC2, Azure VMs). Connected via secure IPsec tunnels or dedicated private links.

Platform as a Service (PaaS): Managed application platforms (e.g., AWS RDS, Azure SQL).

Software as a Service (SaaS): Hosted enterprise applications (e.g., Microsoft 365, Salesforce).

Cloud Connectivity Architectures

Direct Cloud Interconnects: Dedicated private Layer 2/Layer 3 circuits (such as AWS Direct Connect or Azure ExpressRoute) provisioned through carrier-neutral co-location facilities (e.g., Equinix). Direct connects bypass the public Internet to provide provider-backed Service Level Agreements (SLAs), predictable latency, and high bandwidth.

Cloud Onramps (SD-WAN): Cloud onramp technology monitors real-time loss, latency, and jitter across multiple ISP circuits, dynamically routing traffic over the fastest, most reliable path to cloud endpoints.

Carrier-Neutral Co-Location Exchanges: Enterprises deploy routing and security infrastructure inside shared exchange facilities to aggregate multi-cloud links directly at regional peering hubs.

Failure Domain Boundaries and Routed Access

A failure domain defines the physical and logical portion of a network impacted when a critical device, link, or software component fails. In legacy campus designs, extending Layer 2 VLANs across multiple access switches creates large failure domains subject to broadcast storms and Spanning Tree loops.

Routed Access Layer (Layer 3 Access)

The routed access model moves the Layer 3 routing boundary from the distribution switches down to the access layer switches:

Access switches act as Layer 3 routers; uplinks to distribution switches operate as routed point-to-point IP links running an IGP (OSPF or EIGRP).

User VLANs terminate locally on the single access switch. Broadcast traffic cannot escape the local switch.

Spanning Tree Protocol (STP) is isolated to individual access switch ports and is completely disabled on uplinks.

Distribution uplinks utilize Layer 3 ECMP for immediate, sub-second failover upon link loss, drastically shrinking the campus failure domain.