Which Cloud Storage design meets a 15-minute RPO for Dataproc Spark jobs?

PDE By islever Editorial Last updated Aug 31, 2026

Short answer

D 1. Create a dual-region Cloud Storage bucket in the us-central1 and us-south1 regions.

Question

You have an upstream process that writes data to Cloud Storage. This data is then read by an Apache Spark job that runs on Dataproc. These jobs are run in the us-central1 region, but the data could be stored anywhere in the United States. You need to have a recovery process in place in case of a catastrophic single region failure. You need an approach with a maximum of 15 minutes of data loss (RPO=15 mins). You want to ensure that there is minimal latency when reading the data. What should you do?

1. Create two regional Cloud Storage buckets, one in the us-central1 region and one in the us-south1 region.
1. Create a Cloud Storage bucket in the US multi-region.
1. Create a dual-region Cloud Storage bucket in the us-central1 and us-south1 regions.
1. Create a dual-region Cloud Storage bucket in the us-central1 and us-south1 regions.
Correct Answer

Key Takeaways

The question tests matching an RPO of 15 minutes to turbo replication on a dual-region bucket; the trap is choosing a multi-region bucket or two separate regional buckets, neither of which can guarantee that RPO.

A dual-region Cloud Storage bucket spanning us-central1 and us-south1 with turbo replication guarantees an RPO of 15 minutes while letting Dataproc Spark jobs read from a local replica for minimal latency. The community unanimously (100% of votes) agrees the correct answer is D.

Common mistake: Choosing B (US multi-region) because it sounds geo-redundant — but multi-region buckets offer no turbo replication and no 15-minute RPO guarantee, so they fail the catastrophic-failure recovery requirement.

Expert Analysis

Why the Answer Is Correct

Option D creates a dual-region Cloud Storage bucket spanning us-central1 and us-south1 and enables turbo replication, which is the only Cloud Storage configuration that guarantees an RPO of 15 minutes. Turbo replication asynchronously replicates objects to the second region in near real time, so a catastrophic failure of us-central1 loses at most 15 minutes of upstream writes. Because the dual-region bucket is a single resource, the Spark job on Dataproc in us-central1 reads from the local replica, keeping read latency minimal. In a regional outage, the Dataproc clusters can simply be redeployed in us-south1 and read from the same bucket, satisfying the disaster recovery requirement. Comment [2] reproduces the full four-step plan, confirming D includes turbo replication and same-region reads.

Why the Other Options Are Wrong

Option A (two separate regional buckets) would require an additional copy or transfer mechanism to keep them in sync; without it the second bucket cannot meet the 15-minute RPO, and it adds operational complexity and cross-region read latency. Option B (US multi-region) is geo-redundant, but it does not support turbo replication and provides no contractual 15-minute RPO, plus you cannot control which specific regions hold the data. Option C creates the same dual-region bucket but omits turbo replication, so standard cross-region replication leaves a much weaker recovery point objective that fails the stated requirement. The truncated options in this dump differ only in their later steps, and the community consensus is that D is the variant containing turbo replication.

Community Comment Notes

All visible comments vote D, giving 100% agreement with no dissent. Comment [1] (6 likes) clearly articulates the three deciding factors: turbo replication for the 15-minute RPO, same-region reads for minimal latency, and seamless Dataproc redeployment to us-south1 for disaster recovery. Comment [2] (3 likes) spells out the complete option D text, which is valuable because the options are truncated in the question dump. Comments [3] and [4] simply reinforce the unanimous consensus on D.

Official Reference

These links open the official vendor documentation in a new tab.

Exam Strategy

Whenever a question states an RPO of 15 minutes, immediately map it to a dual-region Cloud Storage bucket with turbo replication — it is the only storage option that guarantees that recovery point. Then verify the compute layer (here, Dataproc) reads from a region contained in the bucket to satisfy any minimal-latency requirement. Watch for distractors that use multi-region buckets or omit the turbo replication step.

Community Votes

100%

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

Discussion 4 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 4

raaad 👍 6 Answered D

- Rapid Replication: Turbo replication ensures near-real-time data synchronization between regions, achieving an RPO of 15 minutes or less. - Minimal Latency: Dataproc clusters can read from the bucket in the same region, minimizing data transfer latency and optimizing performance. - Disaster Recovery: In case of regional failure, Dataproc clusters can seamlessly redeploy to the other region and continue reading from the same bucket, ensuring business continuity.
scaenruy 👍 3 Answered D

D. 1. Create a dual-region Cloud Storage bucket in the us-central1 and us-south1 regions. 2. Enable turbo replication. 3. Run the Dataproc cluster in a zone in the us-central1 region, reading from the bucket in the same region. 4. In case of a regional failure, redeploy the Dataproc clusters to the us-south1 region and read from the same bucket.
Matt_108 👍 2 Answered D

Option D, answers all needs from the request
JyoGCP 👍 1 Answered D

Option D

Reader comments & corrections

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

← Back to PDE Study Guide