CompTIA SY0-701 Bundle

Offline or immutable backups protect recovery copies against deletion or tampering by an attacker with ordinary administrative access. They improve recoverability but do not by themselves define how much recent transaction history the business may lose. A nightly immutable copy could still be far older than the allowed 15-minute data-loss window.

Recovery time objective limits how long a service may be unavailable after disruption. Restoring operations in two hours could still lose yesterday's transactions if recoverable data copies are old. The statement here explicitly limits lost transaction history, so the correct metric is recovery point objective rather than elapsed downtime.

A hot site can provide quickly available infrastructure and reduce service restoration time. That does not guarantee that its data replica is current within 15 minutes or that a logical deletion was not replicated. The required maximum transaction loss must be quantified as RPO and validated independently of standby-site readiness.

Geographically separated recovery locations reduce the chance that a single flood, power event or regional outage disables both primary and standby facilities. Location diversity is important, but does not by itself mean synchronized, immediately available computing capacity has already been provisioned. The scenario specifies both readiness and synchronization, pointing to a hot recovery site.

Offline or immutable backup copies preserve recoverable information against accidental deletion or attacker destruction of reachable snapshots. Recovery from backups usually requires restoration and validation before applications become available. Those operations do not meet an immediate failover requirement unless independent running capacity and current data are also in place.

A warm site has some infrastructure and connectivity available but may require application activation, additional configuration or data restoration before use. It is more ready than a cold site yet may not satisfy the hospital's immediate synchronized-capacity requirement. Warm recovery could be acceptable if the business tolerated a longer activation delay.

Scheduled restore exercises validate that backup files can be recovered and that procedures still work after system changes. They do not name the standby architecture where servers and connectivity are already provisioned but data restoration is still required. Testing should be part of that architecture, but it is not the recovery-site classification asked for.

A hot site is generally maintained with very current application data and preprovisioned capacity intended for rapid resumption. The retailer's site still needs to restore data during failover, adding a material activation step. That is more characteristic of a warm site than a continuously synchronized hot arrangement.

Geographic separation reduces correlated disaster risk between primary and recovery locations. It does not specify whether standby servers are ready, current datasets are synchronized or restoration work remains. A geographically remote site may be hot, warm or cold; the readiness details in the scenario identify a warm site.

A hot site can reduce startup time by maintaining ready application capacity and synchronized information. If it sits beside the primary facility on the same floodplain, however, one regional flood can disable both. Readiness cannot compensate for a shared geographic hazard, so the principal design change is location diversity.

An RPO of 15 minutes defines a maximum acceptable loss of recent data after an outage. It does not prevent two datacenters in neighboring buildings from being destroyed by the same flood. Data-loss objectives should be considered separately from correlated physical disaster exposure.

A warm site provides partially ready infrastructure that can be activated after additional restoration work. If both sites are on the same floodplain, this readiness level still leaves them vulnerable to one disaster. Changing hot versus warm classification does not address the common location risk.

A hot site provides rapid alternate computing and often continuously synchronized data. It may also replicate corrupted or encrypted files and can share administrative attack paths with production. Without independent protected historical copies, a ransomware operator with high privilege may destroy recovery options at both sites.

A warm recovery site offers partially provisioned infrastructure but generally requires restoring datasets before service can resume. Having standby machines does not solve the fact that every reachable backup snapshot has been deleted. Protected offline or immutable copies are still required for reliable restoration.

Scheduled restore exercises verify that copies can be recovered and identify broken dependencies, which is an essential operational assurance. But testing cannot recover data from backups that attackers have already erased. The first missing safeguard is protected backup retention beyond the compromised administrative domain.

A scenario-based disaster recovery simulation or tabletop exercises team decision-making against a hypothetical outage. It is useful for checking roles, escalation and recovery order but can be completed without actually restoring a database. The untested technical restore after a platform migration is the risk that needs direct validation.

Hot alternate capacity can improve recovery speed but does not prove that archived database backups are readable on the current software platform. Even a ready compute cluster may fail to load a backup created in an earlier format. The specific assurance gap is the lack of a practical restoration test.

Offline or immutable backup copies can protect retained data against accidental deletion or ransomware. They still might be incomplete, incompatible or missing required keys after migration. Protection against destruction is not the same as confirming the backup can actually be restored on a target database instance.

Geographically separate recovery sites reduce the chance of one flood damaging both primary and backup facilities. The exercise needs a way to rehearse the restoration sequence without switching live customer traffic, not a different physical site location. Site diversity is background resilience but not the requested testing method.

A warm site has partially provisioned infrastructure and may require restoring data before activation. That could be a setting for a disaster rehearsal, but it does not describe how to examine the cross-system restore order without touching production. The requirement is a safe simulation of failure dependencies.

Scheduled restore exercises actually load backups into a test environment and verify that they can be recovered. That is valuable for individual systems, but the case emphasizes a hypothetical regional flood and multi-system restoration order rather than proof that one database backup opens. A scenario simulation better checks coordination and sequencing without customer cutover.

Standby failover with tested promotion allows a service to shift to a secondary node when its primary application component fails. If the whole datacenter loses extended power, both nodes may stop simultaneously. Application redundancy cannot compensate for a missing or failed backup electrical source.

Multiple active serving nodes improve tolerance of individual server failures and can distribute requests. Placing all nodes behind the same exhausted UPS and faulty generator leaves a common-cause outage. Compute redundancy is useful but the incident points to electricity as the shared dependency needing redesign.

Diverse network paths and redundant switches protect against carrier and equipment faults. Those paths may remain available while servers, storage and cooling lose power after generator failure. Network redundancy does not supply electricity, so it does not directly correct this datacenter's extended-outage weakness.

Mean time to repair or recover measures the average duration required to return a failed component or service to operation. It is useful for setting repair expectations, but it does not eliminate the distribution switch that cuts both Internet carriers during its failure. The architectural answer must remove that shared network dependency.

Diverse power sources and generators protect equipment during electrical disruption. They do not directly provide an alternate traffic path around a failed distribution switch if both ISP circuits terminate on that same hardware. Power hardening is important, but physical network redundancy addresses the failure demonstrated.

Running multiple application nodes increases service capacity and tolerance of individual backend failures. If every node relies on the same distribution switch for Internet connectivity, all become unreachable simultaneously when that switch fails. Network path diversity must be repaired before active-active application architecture can deliver end-to-end availability.

Multiple simultaneously serving healthy nodes describe active-active availability, where more than one application instance carries traffic. The question asks for a measurement of average repair time, not a redundancy topology. Active-active service may reduce observed downtime but does not define the duration technicians need to restore a failed server.

Mean time between failures (MTBF) describes the average operating interval between failures for repairable equipment under stated conditions. It helps estimate reliability and maintenance frequency but not how long each failure takes to resolve. A device may have high MTBF and still require lengthy restoration when an incident happens.

Versioned known-good recovery points provide historical database or system states from which to restore after corruption. They are recovery assets, not a numerical average of server repair time. Restore points can lower MTTR when well tested but do not themselves express the desired metric.

Mean time to repair or recover concerns how quickly failed equipment returns to operation after an incident. Procurement wants to compare how long equipment families run before failure under similar conditions. Repair duration can affect maintainability but does not represent the requested reliability interval.

Capacity planning and load testing help verify that standby resources can handle peak traffic after failover. These exercises address throughput and availability under changed operating conditions, not the average failure interval between comparable hardware models. A system may have ample failover capacity yet suffer frequent device breakdowns.

Multiple active serving nodes help a service withstand individual component loss, even if each node has a relatively short operating lifetime. Active-active architecture is an availability strategy rather than a measured reliability property of the hardware families being procured. The question asks for the interval between component failures.