Prepare and test your skills

Prepare and test your skills

Free sample question, answered and explained below. The Professional Data Engineer practice bank has 1,353 more like it. Try 10 free: instant score, no account.
An enterprise runs mission-critical analytical workflows on Cloud Composer in the us-central1 region. The data engineering team must implement an automated cross-region disaster recovery (DR) strategy to fail over orchestration to us-east4 in the event of an outage.
The solution must satisfy the following technical requirements:
Which architecture and recovery workflow should the team deploy?
This option attempts to use Asynchronous Persistent Disk replication at the Compute Engine/GKE node storage layer to replicate raw disk blocks across regions and manually reattach them to a new cluster.
You were implementing disaster recovery for a custom, self-managed database running on standalone Compute Engine instances with attached secondary data disks.
Disaster recovery for Cloud Composer requires saving and loading higher-level environment snapshots rather than block-level disk replication of ephemeral Kubernetes worker nodes.
This solution establishes a resilient cross-region disaster recovery architecture for Cloud Composer workflows using environment snapshots, Terraform infrastructure as code (IaC), Cloud Monitoring alerting, and Cloud Functions for automated failover orchestration.
us-central1) and secondary (us-east4) environments share identical Cloud Composer versions, Airflow builds, environment sizes, and PyPI dependencies.Snapshot creation count metric filtered by result = SUCCEEDED guarantees proactive alerting if automated snapshot capture fails.us-east4 failover environment, and applying regional connection overrides.This approach aligns with Google Cloud site reliability engineering best practices by combining immutable infrastructure definitions, automated monitoring triggers, decoupled multi-region backups, and idempotent workflow design.
This option stores snapshots directly in the primary environment's bucket, uses Cloud Scheduler for custom snapshot exports, and attempts to upgrade the Airflow and Composer versions during failover execution.
/dags, /data) ties snapshot availability to the primary environment; if the primary region suffers an outage or bucket access fails, snapshots cannot be retrieved.You were executing a planned, non-emergency environment version upgrade in a staging environment rather than an emergency disaster recovery failover.
Google Cloud DR guidelines specifically state: 'Don't perform a failover to a later version of Cloud Composer or Airflow, because this might require additional changes related to compatibility.'
us-central1, stream Airflow metadata logs to Cloud Logging, and rely on Cloud SQL automatic cross-zone failover without snapshot restoration or separate secondary environments.This approach relies solely on intra-region High Resilience mode and Cloud SQL zonal failover within the us-central1 region to provide high availability.
us-central1.us-east4).The scenario only required high availability (HA) against localized zonal disruptions within a single region rather than a comprehensive cross-region disaster recovery strategy.
While High Resilience mode is recommended for production environments to handle zonal failures transparently, cross-region DR explicitly requires off-site snapshots and failover environments.
Answer them yourself and get your score the moment you finish. No account needed.
Full access includes
Keep the momentum going with these hand-picked practice scenarios
Last updated Validated