Business continuity in the face of a natural disaster fundamentally depends on ensuring that a usable copy of critical data exists somewhere outside the geographic scope of the disaster, so that operations can be resumed even if the primary site is destroyed or rendered inaccessible. Storing a copy of data at a remote site directly satisfies this requirement, providing the geographic separation necessary to survive a regional event and enabling recovery operations to proceed from the unaffected location. This is the foundational practice underpinning disaster recovery and business continuity planning. Restricting access to all types of data (A) is a security and confidentiality control, addressing unauthorized disclosure, not the risk of physical data loss from a natural disaster, and does not itself preserve data against destruction. Keeping all data onsite, even with encryption (B), fails to address the core risk entirely, since encryption only protects confidentiality; a fire, flood, or similar disaster destroys encrypted and unencrypted data equally if all copies remain within the same physical site. Using archives for all data (D) mischaracterizes the requirement, since archiving is a retention strategy for inactive fixed content, not a comprehensive business continuity mechanism for actively used, changing operational data. Storing a remote copy is correct.
Reference topic: Data Protection and Management Introduction - Business Continuity Through Remote Data Copies.
Contribute your Thoughts:
Chosen Answer:
This is a voting comment (?). You can switch to a simple comment. It is better to Upvote an existing comment if you don't have anything to add.
Submit