A county lake holds critical analytical datasets that must survive a regional outage. Which cloud practice best supports disaster recovery for those stores?
Select an answer to reveal the explanation.
Short Explanation
If the only copy of the city ledger sits in one flooded basement, recovery is hope, not a plan. Replicating critical analytical datasets to another region is how cloud lakes buy real DR. Paper PDFs are not a lake failover.
Full Explanation
Replicating critical analytical datasets to another region is a foundational cloud disaster-recovery practice for a county lake that must survive a regional outage. Secondary copies with tested restore or failover paths turn DR from hope into design for civic continuity of analytics. Chapter 9 continuity thinking for municipal lakes starts with geographic redundancy of critical analytical stores and clear ownership of failover.
Keeping a single unreplicated bucket in one availability zone only concentrates risk in one failure domain and fails regional-outage goals. Printing weekly PDF summaries for a filing cabinet preserves narratives, not restorable analytical datasets for jobs and dashboards. Disabling all backups once the first public dashboard ships abandons recovery the moment corruption or region loss hits production systems.
Exam caveat: replication targets must still respect residency and encryption policies, and DR drills must include identity and job-config restoration, not only object bytes. Operational check: initiate a restore or read failover from the replica region for a critical dataset in a drill, measure time-to-usable analytics against RTO, and verify checksum or row-count parity within RPO tolerance.