Search the practice set
126 questions, 454 terms and 400 topics in 20 areas.
15 results for “Disaster Recovery”
Disaster Recovery
The plan and capability for restoring service after an event that takes out a whole site, region or system.
Failback
Returning to the primary region after a failover, including reconciling the data written while it was unavailable — the half of DR that is usually unplanned.
Pilot Light
A disaster recovery posture where core data is continuously replicated and minimal infrastructure runs, with the rest provisioned only on failover.
RTO and RPO
How long recovery may take (RTO) and how much data may be lost (RPO), the two numbers that determine the cost of a resilience design.
Point-in-Time Recovery
Restoring a database to any moment within a retention window by replaying transaction logs onto a base backup, rather than only to a snapshot boundary.
Backup Strategy
A plan for what is copied, how often, where to, how long it is kept, and — the part that decides whether it is real — how the restore is verified.
Containment vs Eradication
Stopping an attacker's ongoing access versus removing their foothold entirely — sequential phases with different urgency and different risks of doing them wrong.
Half-Open State
The circuit breaker state that allows a limited number of trial requests through to test whether a failed dependency has recovered.
A team tells you backups run nightly and are retained for 30 days. What is missing from that answer?
What the interviewer is testing Whether you know that a backup is not a control until it has been restored — one of the most reliable ways to find an unrecovere
Maersk rebuilt roughly 4,000 servers and 45,000 PCs in about ten days after NotPetya in 2017, and recovered its directory only because one data centre had been offline during the attack. What does this say about DR design?
The case, as publicly reported In June 2017 the NotPetya malware — destructive rather than financially motivated — propagated through Maersk's network, encrypti
A team says "backups run nightly and are retained for 30 days". You have one hour to assess whether they could actually recover. What do you check?
The checks, in the order that finds problems fastest 1. When was a restore last performed, and how long did it take? The single most informative question. If th
After adding circuit breakers, a partial outage now lasts three times longer than it used to. What is likely happening?
The likely mechanism: breaker oscillation The dependency is recovering slowly — it can serve some traffic but not full load. The breaker opens, waits out its co
Disaster Recovery
Backup-restore, pilot light, warm standby and active-active postures.
Caching for Performance
Layer choice, hit ratio as a first-class metric, and cold-cache recovery.
RTO & RPO
How long recovery may take and how much data may be lost.