Cloud Composer Cross Region Disaster Recovery Snapshots 2

Worked example. The correct answer is already marked and every option is explained below, so there is nothing to select here. To answer questions yourself, start the free trial.

Your enterprise runs critical batch data processing pipelines orchestrated by Cloud Composer in the us-central1 region. You are tasked with designing a cross-region disaster recovery (DR) architecture that can restore workflow orchestration in us-east4 if an entire region experiences an outage.

The design must satisfy the following criteria:

Maintain DAG execution history and pipeline state across regions.
Ensure configuration consistency and minimize workflow restoration time.
Prevent inconsistent data states caused by re-executing tasks that ran after the last backup.

Which strategy should you implement?

Deploy Cloud Composer in High Resilience mode in us-central1, which automatically replicates the Airflow metadata database to secondary regions and handles automatic cross-region failover.

Configure scheduled environment snapshots to a multi-region Cloud Storage bucket, deploy a failover Cloud Composer environment in us-east4 with identical Airflow and Composer versions, design DAG tasks to be idempotent, and load the latest snapshot into the failover environment upon failure.

Deploy dual active-active Cloud Composer environments in us-central1 and us-east4 behind a global Cloud Load Balancer to automatically route and distribute DAG scheduling tasks evenly between regions.

Configure Regional Persistent Disks to synchronously replicate the Cloud Composer environment bucket and database storage from us-central1 to us-east4, then force-attach the replicated disk to a Compute Engine instance.

Professional Cloud Data Engineer

Cloud Composer Cross Region Disaster Recovery Snapshots 2

Related questions