BigQuery Cross-Region Disaster Recovery Strategy

PDE By islever Editorial Last updated

Using a data lake.

Short answer

C Configure BigQuery cross-region dataset replication from us-central1 to us-east1 to ensure automated, low-complexity disaster recovery across regions.

Question

Your company stores vital operational sales data in a BigQuery dataset in us-central1. Your company requires a disaster recovery plan to restore this data to us-east1 with a recovery point objective (RPO) of 24 hours and a recovery time objective (RTO) of 4 hours if us-central1 experiences an outage. You need to implement the disaster recovery plan while keeping costs and complexity to a minimum. What should you do?
  1. Set up continuous queries and Pub/Sub to stream data changes from BigQuery tables in us-central1 to us-east1.
  2. Manually export data to a CSV file in a multi-regional Cloud Storage bucket daily and use bq load to restore to us-east1.
  3. Configure BigQuery cross-region dataset replication from ns-central1 to us-east1. Correct Answer
  4. Take daily BigQuery table snapshots in us-central1.

Key Takeaways

The main trap is selecting local backups (snapshots) which do not protect against regional outages, or complex streaming solutions that violate the simplicity constraint.

This question tests implementing a BigQuery disaster recovery plan using cross-region replication to meet RPO and RTO requirements while minimizing cost and complexity.

Common mistake: Choosing Option D (daily snapshots) is a common mistake; while snapshots are useful for point-in-time recovery within a region, they do not mitigate the risk of a total regional outage in us-central1.

Expert Analysis

The question asks for a disaster recovery plan that meets specific RPO and RTO targets while minimizing cost and complexity. The key constraint is the geographic scope: restoring data from us-central1 to us-east1.

Option C suggests configuring BigQuery cross-region dataset replication. While BigQuery does offer features like Cross-Region Replication (often via Dataflow or managed replication services depending on the exact timeline of the exam version), it is the only option that explicitly addresses moving data between regions in a managed, automated way suitable for meeting strict SLAs without manual intervention. However, we must scrutinize the other options.

Option A involves streaming changes via Pub/Sub. This introduces significant complexity (building pipelines, managing subscriptions) and cost, violating the 'minimize complexity' requirement. It also risks data consistency issues during an outage event.

Option B proposes manual daily exports to CSV. An RPO of 24 hours implies that losing up to one day's data might be acceptable if done daily, but the RTO of 4 hours is challenging with manual processes involving file transfer and loading. Furthermore, manual operations are high-complexity and prone to human error, failing the 'minimize complexity' test.

Option D suggests taking daily snapshots in us-central1. This keeps data in the same region. If us-central1 experiences an outage, having snapshots in the same region does not provide disaster recovery against a regional failure. Snapshots are local backups, not a geo-redundant solution.

Therefore, Option C is the best fit because it establishes a geographically distributed copy of the data, which is essential for regional disaster recovery. Although historically BigQuery didn't have a simple 'click-to-replicate' button for all datasets, modern implementations often use managed replication or automated pipelines that are considered standard practice for this scenario in certification contexts. The comment confirms C is the accepted answer, noting it provides lower RPO/RTO compared to manual methods and ensures cross-region availability.

Exam Strategy

When evaluating disaster recovery options, always first check if the solution addresses the specific failure domain (e.g., regional vs. zonal). If the failure is regional, any backup stored in the same region is invalid. Second, weigh 'complexity' heavily; manual exports or custom streaming pipelines often fail the 'minimize complexity' criterion when a managed replication feature exists.

Frequently Asked Questions

Why are daily snapshots insufficient for regional disaster recovery?

Snapshots taken in us-central1 are stored within that region. If the entire us-central1 region goes offline, those snapshots become inaccessible, providing no recovery path.

Does BigQuery support automatic cross-region replication?

Yes, BigQuery supports cross-region dataset replication features (or managed pipelines) to maintain copies of data in different regions for high availability and disaster recovery.

More PDE FAQ →

Community Votes

C
100%

100% of anonymous learners picked answer C. Votes are pick records left by other test-takers — they are not the verified answer.

Discussion 3 contributions

Compiled from public community threads and reader submissions, lightly edited for clarity. Handles and vote tallies are shown as recorded, and comments reflect the views of individual contributors.

From public community threads 3

  1. 5523042 👍 2 Answered C
    Es la correcta
  2. AwesomeGCP 👍 1 Answered C
    The correct answer is C. Configure BigQuery cross-region dataset replication from us-central1 to us-east1.
  3. Mohamed_Tareq 👍 1 Answered C
    C is the only one introducing both lower rpo and rto + it cross region which adds high availability

Reader comments & corrections

No reader corrections yet — spotted an error or have a note? Share it below.

Log in to comment, report an error, or add a note about this question.

← Back to PDE Study Guide