Objective 3.3

N10-009

Explain disaster recovery (DR) concepts.

Objective 3.3 sits in Network Operations, which carries 19% of the Network+ exam. The questions below are original, written from the official objective title above, and each explanation cites the CompTIA page it rests on.

Objective title verbatim from the official objectives. CompTIA exam page ↗

A worked example

Shown solved, with the whole explanation open: this is what every question here carries.

3-3Network Operations

A team keeps replicated backups at a second site but nothing else. During a failover test, rebuilding servers by hand pushes recovery past the agreed window. What fixes the shortfall without adding running capacity?

Raise the retention period on the existing backupsLonger retention helps with corruption found late. It has no effect on rebuild time.
Shorten the interval between backup snapshotsMore frequent snapshots cut how much data is lost, which is the other objective entirely.
Define the recovery site build as infrastructure codeCorrect · your answerCorrect. It removes the manual rebuild that is consuming the window.
Add a second replication target in a third siteA third copy of the data adds durability and does nothing for the speed of the rebuild.

Correct.

Checked against docs.aws.amazon.com, August 2026

Concept

Two different clocks govern a recovery. One measures how much data is lost, and shorter backup intervals move it. The other measures how long the rebuild takes, and only removing manual steps from the rebuild moves that one.

Why C

Restoring at the recovery site means redeploying infrastructure, configuration and application code as well as data. Deploying that from code is what makes the rebuild quick and repeatable, and its absence is what stretches recovery time.

Source

To enable infrastructure to be redeployed quickly without errors, you should always deploy using infrastructure as code (IaC) using services such as AWS CloudFormation or the AWS Cloud Development Kit (AWS CDK). Without IaC, it may be complex to restore workloads in the recovery Region, which will lead to increased recovery times and possibly exceed your RTO.

AWS Whitepaper: Disaster recovery options in the cloud, checked August 2026
#disaster-recovery#rto#backup-and-restore

Now you: objective 3.3 questions

No account needed. The explanation opens when you answer.

Sample question 1 of 3

3-3Network Operations

Two designs both hold replicated data and a copy of the application at a second site. One can take traffic the moment it is needed, the other cannot. Which distinction separates them?

Sample question 2 of 3

3-3Network Operations

A budget-constrained team wants its core databases and storage live at the recovery site while application servers stay unpowered until needed. Which strategy is that?

Sample question 3 of 3

3-3Network Operations

Which recovery strategy has users served from every site it is deployed to at the same time?

Full Network+ question bank coming

We’re writing the complete bank from the official objectives right now. Leave your email and we’ll tell you when it ships, nothing else, ever.

Read the sources

These are the official pages the questions above cite. Reading them is studying the objective from the primary source, which is what the explanations point you toward anyway.

More objectives in Network Operations