3.4 Explain the importance of resilience and recovery in security architecture

Domain 3: Security Architecture

Resilience and recovery covers keeping systems running and bringing them back. Know high availability (load balancing versus clustering), site considerations (hot, warm, cold, geographic dispersion), platform diversity, multi-cloud, and continuity of operations. Capacity planning spans people, technology, and infrastructure. Testing methods include tabletop exercises, failover tests, simulations, and parallel processing. Backups carry detail: onsite versus offsite, frequency, encryption, snapshots, recovery, replication, and journaling. Power resilience means generators and UPS. The exam tests cost-versus-recovery-time trade-offs: a hot site restores fastest but costs most; a cold site is cheap but slow; a warm site splits the difference. Distinguish load balancing (distributes active traffic) from clustering (nodes ready to take over), and a snapshot (point-in-time state) from replication (continuous copy). Tabletop exercises are discussion-based and non-disruptive, which is why they appear as the answer when the scenario forbids downtime. Journaling questions focus on replaying transactions to a point in time.

What you must know

common pitfall · Candidates rank recovery sites by cost or speed alone and miss that the scenario's stated recovery time objective determines which site type is correct.

Try a sample question

A business impact analysis sets a 15-minute recovery point objective for a company's order database, which is currently protected only by a nightly full backup. Which change to the recovery design is required to meet this objective?

  • A Store the nightly backup media at a geographically distant storage facility
  • B Add a warm site that can be staffed within four hours of a declared disaster
  • C Replicate database transactions to a secondary system in near real time
  • D Test the existing nightly backups quarterly to verify they can be restored
Show answer & explanations
  • A Offsite media storage protects against loss of the primary site, but the backup is still taken once per day, so up to 24 hours of transactions could be lost.
  • B A warm site shortens how quickly service can be restored, which addresses the recovery time objective, not how much recent data survives the failure.
  • C correct ·Correct. Near-real-time replication keeps a secondary copy within seconds or minutes of the primary, so no more than 15 minutes of order data would ever be lost.
  • D Testing restores verifies backup integrity, which is valuable practice, but it does not change the fact that a nightly backup can still lose a full day of data.

sample item — the full bank runs 450+ questions at exam difficulty

Is objective 3.4 your weak spot?

The free readiness check finds your weakest objectives in 15 adaptive questions — then full access drills them until the gauge clears the cut line.

Check my readiness — free