You are designing a Dataflow pipeline for a batch processing job. You want to mitigate multiple zonal failures at job submission time. What should you do?

Question

Options

• ASubmit duplicate pipelines in two different zones by using the --zone flag.
• BSet the pipeline staging location as a regional Cloud Storage bucket.
• CSpecify a worker region by using the --region flag.
• DCreate an Eventarc trigger to resubmit the job in case of zonal failure when submitting the job.

• A
  15% (4)
• B
  4% (1)
• C
  74% (20)
• D
  7% (2)

Explanation

Specifying a worker region with --region tells Dataflow to manage worker placement across multiple zones within that region automatically, so if one or more zones fail, the service can schedule workers in healthy zones without manual intervention. Option A is wrong because manually duplicating pipelines in two zones creates redundancy for only those specific zones and introduces operational overhead - it doesn't give you automatic failover. Option B is wrong because the staging location's bucket type (regional vs. multi-regional) affects data durability, not compute zone resilience during job submission. Option D is wrong because Eventarc would only react after a failure has already caused the job to fail, rather than preventing the zonal failure impact at submission time.

Memory tip: Think "region = resilience" - a region spans multiple zones, so --region hands zone selection to Google's infrastructure, which is always aware of live zone health. Any time an exam question mentions zonal failure mitigation, look for the answer that operates at the region level rather than pinning to a specific zone.

No community discussion yet for this question.