Study Disaster Recovery, RTO/RPO & Testing for Network+ (N10-009)

Disaster-recovery questions are priority questions. CompTIA wants to know whether you can map business expectations to the right recovery design instead of choosing the most expensive-sounding option every time. The strongest answer usually balances downtime tolerance, data-loss tolerance, and operational reality.

RPO: Recovery point objective, the maximum acceptable amount of data loss measured in time.

RTO: Recovery time objective, the maximum acceptable time to restore service after an outage.

MTTR: Mean time to repair, the average time needed to restore a failed service or device.

What CompTIA is really testing

The exam usually wants you to separate:

• downtime tolerance from data-loss tolerance
• cold, warm, and hot recovery options
• active-passive from active-active design
• written DR plans from actually tested DR plans

Recovery design starts with business impact

    flowchart TD
	  A["Service fails"] --> B["How fast must service return?"]
	  B --> C["How much data loss is acceptable?"]
	  C --> D["Choose site model and replication approach"]
	  D --> E["Test the recovery plan"]

What to notice:

• the right answer starts with requirements, not technology branding
• low RTO and low RPO usually require more investment and more operational discipline
• testing is part of the design, not a separate optional phase

Keep these measures distinct

Small planning example

1services:
2  dhcp:
3    rto: 15m
4    rpo: n/a
5    model: warm-standby
6  file-share:
7    rto: 4h
8    rpo: 1h
9    model: replicated-secondary

What to notice:

• not every service needs the same recovery target
• some services care more about rapid restoration than data loss
• CompTIA often rewards answers that fit the service importance instead of overbuilding everything

Why testing matters so much

A documented DR plan that nobody has exercised is weak in at least three ways:

• the runbook may be outdated
• the dependencies may be incomplete
• the staff may not know the real order of operations

That is why Network+ includes testing and validation language, not just site terminology.

Common traps

• mixing up RTO and RPO
• choosing a hot-site answer when the scenario only needs moderate recovery speed
• treating active-active as automatically correct without checking cost or complexity
• assuming a written plan is strong even if it has never been tested

What strong answers usually do

• start with business impact and service criticality
• map recovery speed and data-loss tolerance separately
• choose the simplest recovery model that meets the requirement
• include testing, documentation, and failback thinking in the answer

Quiz

Continue with 3.7 Core Network Services to keep the domain flow intact.