Study guide
DR and HA Concepts: RPO, RTO, MTTR, MTBF, Sites, Failover, and Testing
CompTIA Network+ N10-009
Track your progress as you read
Finished sections get a check mark.
1 Introduction & Exam Overview
Current Exam Facts and Applied Networking Judgment Official Domain Weights and an 8-12 Week Study Plan How to Use Labs, Practice, and PBQ Workflow Missed-Question Notebook and Final Readiness Metrics
2 Domain 1: Networking Concepts (23%)
OSI and TCP/IP Models with Device and Protocol Mapping Networking Appliances and Where They Operate Ports and Protocol Decision Table Traffic Types and Encapsulation Flow
3 Domain 1: Media, Connectors, Transceivers, and Network Architectures
Copper, Fiber, Coax, and DAC Media Connector and Transceiver Selection Network Topologies and Design Patterns Cloud and Virtual Networking Concepts
4 Domain 1: IP Addressing and Subnetting Mastery
IPv4 Classes, Private/Public, APIPA, and Loopback CIDR, VLSM, and Subnet Math IPv6 Address Types and Notation Routing Basics and Longest Prefix Match
5 Domain 2: Network Implementation - Routing
Static vs Dynamic Routing and Route Selection OSPF, EIGRP, and BGP Basics at Network+ Depth NAT/PAT, VIP/FHRP, and Subinterfaces Routing PBQs and Troubleshooting Route Table Clues
6 Domain 2: Network Implementation - Switching
VLANs, Access Ports, Trunks, and Native VLAN STP/RSTP Loop Prevention and Bridge Roles Port Aggregation/LACP, MTU, Jumbo Frames, and Interface Settings Switch Implementation PBQs and Common Misconfigurations
7 Domain 2: Network Implementation - Wireless and Physical Implementation
Wi-Fi Standards, Bands, and Channels SSID Security, Guest Networks, and Authentication Antennas, Coverage, Roaming, Interference, and Site Surveys Physical Installation Implications
8 Domain 2: Network Implementation - Services Implementation
DNS Record Types and Troubleshooting Cues DHCP, DHCPv6, SLAAC, Scopes, Leases, and Relay NTP, PTP, NTS, and Time-Sensitive Networking Service Implementation PBQs: DNS, DHCP, VLANs, and Firewall Direction
9 Domain 3 Part A: Network Operations Documentation and Governance
Physical, Logical, Rack, Cable, Wireless Diagrams, and IPAM Asset Inventory, Baselines, SLAs, SOPs, and Runbooks Change Management and Request Tracking Lifecycle, EOL, EOS, Decommissioning, and Configuration Management
10 Domain 3 Part B: Monitoring, Remote Access, and Resilience
SNMP, Flow, Syslog, Packet Capture, Log Aggregation, APIs, and Port Mirroring Baselines and Performance Metrics Remote Access, Management Paths, and Secure Admin Habits DR and HA Concepts: RPO, RTO, MTTR, MTBF, Sites, Failover, and Testing
11 Domain 4: Logical Security and Secure Access (14%)
Encryption in Transit, Encryption at Rest, PKI, and Certificates IAM, MFA, SSO, Directory Services, and AAA Authorization, Least Privilege, RBAC, Geofencing, and Time-Based Access VPNs and Secure Management Design
12 Domain 4: Segmentation, Risk, and Network Attacks (14%)
Segmentation for Guest, BYOD, IoT, IIoT, SCADA, ICS, and OT Risk, Compliance, Audit, Data Locality, PCI, and GDPR Network Attacks and Scenario Cues Attack-to-Mitigation PBQ Tables
13 Domain 4: Security Controls and Hardening (14%)
Firewalls, IDS, IPS, Security Zones, and Screened Subnets ACLs, Filtering, NAC, Hardening, and Key Management Deception Technologies and Physical Security Zero Trust, SASE, and Trusted or Untrusted Zone Decisions
14 Domain 5: Troubleshooting Methodology and Tools (24%)
Official Troubleshooting Methodology and Evidence Handling Command-Line Tools: ping, traceroute, nslookup, dig, ipconfig, ifconfig, ip, arp, netstat, ss, and route Packet, Protocol, and Wi-Fi Analyzers Choosing the Right Tool by Symptom PBQs
15 Domain 5: Physical, Interface, and Wireless Troubleshooting (24%)
Cable Issues: Type, Attenuation, Crosstalk, Termination, and TX/RX Interface Issues: Errors, Discards, Duplex, Speed, Port Status, and PoE Transceiver, Fiber, and Signal Strength Troubleshooting Wireless Troubleshooting: Interference, Channels, Roaming, RSSI/SNR, Security, and Captive Portals
16 Domain 5: Network Services, Switching, Routing, and Performance Troubleshooting (24%)
DHCP, DNS, NTP, and IP Addressing Issues VLAN, STP, Trunk, Native VLAN, and ACL Issues Routing, Default Gateway, Route Table, and NAT Issues Congestion, Latency, Jitter, Packet Loss, and Application Performance Clues
17 Performance-Based Question Labs
Subnetting and VLSM Design Lab VLAN, Trunk, Router-on-a-Stick, and Firewall Rule Lab Wireless Deployment and Troubleshooting Lab Monitoring, Log Triage, and Route or Service Troubleshooting Lab
18 High-Yield Reference and Final Study Plan
High-Yield Ports and Protocols Table Wi-Fi, Cabling, Connectors, and Transceivers Quick Table Acronyms and Command-Line Tool Quick Table Final 7-Day Review Plan and Readiness Checklist
19 Final Synthesis: Strategy, Remediation, and Readiness
Mixed-Set Decision Strategy for Qualifiers and Close Answers Missed-Question Remediation Notebook by Error Type Exam-Day Time Management and PBQ Order 100-Question Readiness Simulation Blueprint Mapped to N10-009 Weights
DR and HA Concepts: RPO, RTO, MTTR, MTBF, Sites, Failover, and Testing
Key Takeaways Explain This Topic AI
RPO defines acceptable data loss in time; RTO defines acceptable time to restore service — do not swap them on the exam.
MTTR is mean time to repair/recover and MTBF is mean time between failures; both are reliability measurements, not requirements.
Cold, warm, and hot sites trade cost against readiness: cold is cheapest and slowest, hot is most expensive and fastest.
First Hop Redundancy Protocols (FHRP) such as VRRP and HSRP provide gateway failover; clustering and load balancing provide service redundancy.
DR/HA plans must be tested — tabletop, walk-through, simulation, failover, and restore — and a hot site never removes the need for backups.
Last updated: June 2026
Disaster Recovery, High Availability, and Testing
Network+ objective 3.3 ties business requirements to resilient design. The right architecture depends on how much downtime, data loss, cost, and complexity the organization can tolerate. The exam tests four buckets: the recovery metrics, recovery sites, HA designs, and testing types.
Recovery and reliability terms
Term Meaning Example
RPO Recovery Point Objective — max acceptable data loss, measured in time Lose no more than 15 minutes of transactions
- RTO Recovery Time Objective — target time to restore service Restore VPN within 1 hour
- MTTR Mean Time To Repair/Recover — average restore time 45 minutes to swap a failed switch
- MTBF Mean Time Between Failures — expected reliability interval A power supply rated 100,000 hours
The single most-tested distinction: RPO is about data (how far back), RTO is about time (how long down). A nightly backup gives an RPO of up to 24 hours; if the requirement is "lose no more than 5 minutes," nightly backup fails and you need frequent replication. RPO and RTO are requirements set by the business ; MTTR and MTBF are measurements used to evaluate supportability.
Recovery sites
- Site type Readiness Cost Recovery speed
- Cold Space and power, little or no equipment Lowest Slowest (days)
- Warm Some hardware and connectivity, partial data Medium Moderate (hours)
- Hot Fully equipped, current data, rapid failover Highest Fastest (minutes)
A cold site fits a low-priority function with a long RTO; a hot site is required when both RTO and RPO are short. A cloud / DRaaS option can blur these lines by spinning up capacity on demand.
High availability designs
- Design Description Note
- Redundant component Dual power supply, link, switch, firewall, ISP Removes a single point of failure
- Load balancing Spreads requests across nodes Scale and availability
- Clustering Multiple nodes act as one service Supports failover
- Active-active All nodes carry production traffic Efficient but complex
- Active-passive Standby waits for failover Idle capacity, simpler planning
- FHRP (VRRP / HSRP) Redundant default gateway Hosts keep one virtual gateway IP
- Geographic redundancy Service runs/recovers in another region Survives site loss
HA reduces downtime from component failures; DR addresses larger disruptions such as site loss, mass corruption, or disaster. First Hop Redundancy Protocols — VRRP (open standard) and HSRP (Cisco) — present one virtual gateway IP so clients keep working when the active router fails.
Failover and split-brain
Failover moves service from a failed component to a standby or peer and must define health checks, triggers, state synchronization , routing/DNS changes, and failback. Cluster designs must prevent split-brain , where two nodes both believe they are primary and accept conflicting writes — usually solved with a quorum or witness.
Testing methods
- Test What happens
- Tabletop Stakeholders discuss a scenario and decisions
- Walk-through Team reviews procedures step by step
- Simulation Realistic inputs without full production impact
- Failover test Service is actively moved to standby
- Restore test Data/config is restored and validated
- Full interruption Production is intentionally stopped under control
A tabletop validates decisions and communication , not the technical failover — only a failover or full-interruption test proves the systems actually cut over. Testing must produce evidence: timings, gaps, failed assumptions, and updated runbooks. An untested plan is only a theory.
Practical scenario
An ordering system must recover within 30 minutes (RTO) and lose no more than 5 minutes of orders (RPO) . That points to a warm or hot design with frequent replication, FHRP or clustered gateways, tested failover, and current documentation. A nightly offline backup cannot meet the 5-minute RPO and would fail an audit.
Why a hot site still needs backups
A frequent exam misconception is that real-time replication to a hot site removes the need for backups. It does not, because replication faithfully copies everything — including a malicious encryption by ransomware, an accidental table drop, or a corrupted file. Within seconds the same damage exists at both sites, leaving no clean copy to restore from. Backups protect a different threat: they provide point-in-time recovery to a moment before the corruption, satisfying the RPO.
The resilient design therefore layers both — replication for fast failover against hardware and site loss, and versioned, ideally immutable or offline, backups against logical corruption and deletion.
Translating requirements into design
The exam often hands you an RTO and RPO and asks for the matching architecture. A long RTO and long RPO can be met cheaply with a cold site and nightly backups. A short RTO with a short RPO forces near-continuous replication, clustered or load-balanced services, FHRP gateway redundancy, and a warm or hot site with tested failover. The discipline is to let the business numbers drive the spend rather than over-engineering every service to active-active, which wastes money on functions that could tolerate hours of downtime.
Common exam traps
RTO is time to restore ; RPO is acceptable data loss . Do not swap them.
Active-active is not always best — it adds cost and complexity; requirements drive design.
A hot site does not eliminate backups; replication can copy corruption or a deletion.
A tabletop test does not prove technical failover; only a failover/full-interruption test does.
MTTR and MTBF are measurements, not requirements; RPO and RTO are the requirements the business sets.