Domain 3.0 · Security Architecture · 18% of the exam

Security+ 3.4: Resilience and recovery

Official objective: 3.4 Explain the importance of resilience and recovery in security architecture

Keeping services running and getting them back: high availability, site considerations, platform diversity, multi-cloud, continuity of operations, capacity planning, testing, backups and power.

What to know

High availability
Load balancing (spread load across active nodes) versus clustering (nodes that fail over for each other).
Site considerations
Hot site (ready to run now), warm site (equipment, needs data and setup), cold site (space and power only). Geographic dispersion avoids one disaster taking out both.
Platform diversity and multi-cloud
Different vendors and providers so one flaw or outage does not stop everything.
Capacity planning
Enough people, technology and infrastructure to run in a disruption.
Testing
Tabletop exercises (talk through), failover tests, simulations and parallel processing.
Backups
On-site and off-site, frequency, encryption, snapshots, recovery testing, replication and journaling.
Power
Generators for long outages; UPS for short gaps and clean shutdown.

Where people lose marks

Practise 3.4

Free questions on this objective, each with the answer and why every option is right or wrong:

More from domain 3.0

Objective codes and titles are CompTIA's published SY0-701 exam objectives. The explanations are our own. SY0-701 is offered until it retires; see SY0-701 or SY0-801 to pick your version.