An enterprise data platform running on Google Cloud utilizes Google Cloud Backup and DR Service to protect business-critical databases and data workloads across multiple zones and regions. The analytics engineering team establishes stringent business continuity metrics: Recovery Point Objective (RPO): Under 1 hour for high-change transactional staging data Recovery Time Objective (RTO): Near-instantaneous recovery to enable fast failover and data validation during disaster recovery drills During high-volume periods, the backup storage snapshot performance pool approaches safe capacity thresholds due to rapid snapshot creation and high data change rates. Which strategy should the team implement to alleviate snapshot pool exhaustion while preserving the defined RPO and near-zero RTO targets?

Configure backup templates to create OnVault images of snapshots before expiring local snapshot copies, while deleting unneeded mounts and clones.: What Google Cloud Backup and DR Snapshot Lifecycle Management Is Google Cloud Backup and DR Service manages data protection using high-performance snapshot pools for immediate operational recovery and cost-effective OnVault long-term object storage pools. Snapshot pools provide local point-in-time recovery capabilities essential for low RTOs, while OnVault offers secondary protection across regions. How it Meets the Recovery Objectives (RPO and RTO) Meeting RPO Requirements: Moving snapshots to OnVault images before expiring them ensures that the recovery points are safely offloaded to object storage without sacrificing point-in-time granularity (RPO). Preserving RTO and Relieving Pool Capacity: Deleting unnecessary mounts, clones, and live-clones immediately reclaims allocated performance staging capacity. Retaining active snapshots for recent windows while rotating older points into OnVault keeps fast-mount capabilities intact for low RTO. Preventing Safe Threshold Breaches: Applications with high change rates generate massive incremental differences; flushing older snapshots to OnVault frees performance pool blocks efficiently. Key Advantages Optimized Pool Utilization: Reclaims vital block storage within snapshot pools without breaking scheduled capture cadences. Maintained Data Fidelity: Preserves all historical recovery points in secondary object tiers. Disaster Recovery Readiness: Facilitates multi-region redundancy by moving snapshot data to durable cloud storage.

Backup Dr Snapshot Pool Rpo Rto Optimization | Professional Cloud Data Engineer

AdvancedProfessional Cloud Data Engineer

An enterprise is designing a mission-critical financial data ingestion and processing system on Google Cloud. The system must withstand both zonal and complete regional infrastructure failures with an RPO close to zero and an automated, minimal RTO without requiring manual failover procedures. Which architecture meets these requirements?

Disaster recovery and fault tolerance

AdvancedProfessional Cloud Data Engineer

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: Maintain configuration and version parity across the primary and failover environments. Continuously validate and monitor automated snapshot creation, alerting on any failures. Orchestrate automated snapshot loading, environment configuration updates, and execution handoff during a failover event. Prevent inconsistent state and side effects caused by re-executing tasks that ran after the latest snapshot. Which architecture and recovery workflow should the team deploy?

Disaster recovery and fault tolerance

AdvancedProfessional Cloud Data Engineer

A retail enterprise is architecting an enterprise data platform on Google Cloud to ingest both real-time clickstream events and daily batch transactional files from acquired entities. The platform design must satisfy the following technical requirements: Ingestion and Transformation: Support continuous streaming and scheduled batch processing with schema validation, writing invalid records to error tables for forensic analysis without halting the pipeline. Orchestration: Coordinate multi-stage operational extract, transform, and load (ETL) workflows with complex dependencies and automated scheduling. Quality and Governance: Unify distributed assets into logical data lakes and automatically validate data quality rules without moving data into a single consolidated system. Lifecycle Management: Automatically enforce retention policies by purging raw staging records after 90 days and archiving curated analytical tables. Which architectural approach satisfies all of these requirements while adhering to Google Cloud best practices?

Building a data platform based on requirements by using Google Cloud tools (e.g., Dataplex, Dataplex Catalog, BigQuery, Cloud Storage)

AdvancedProfessional Cloud Data Engineer

An enterprise is establishing a data analytics platform on Google Cloud and needs to assign the appropriate processing engine for three distinct pipeline workloads: Workload 1: Migrating an existing portfolio of legacy Apache Spark jobs and Hadoop dependencies with minimal code changes while leveraging ephemeral clusters to optimize compute costs. Workload 2: Processing real-time unbounded event streams alongside bounded batch datasets using a fully managed serverless runtime with exactly-once processing semantics. Workload 3: Enabling business analysts to visually design, deploy, and manage ETL/ELT pipelines using a point-and-click graphical interface backed by open-source CDAP. Which service mapping should the enterprise select for Workload 1, Workload 2, and Workload 3, respectively?

Identifying the services (e.g., Dataflow, Apache Beam, Dataproc, Cloud Data Fusion, BigQuery, Pub/Sub, Apache Spark, Hadoop ecosystem, and Apache Kafka)

AdvancedProfessional Cloud Data Engineer

A data engineering team operates an enterprise data pipeline on Google Cloud that ingests transactional records into analytical storage. During recent pipeline runs, upstream schema mismatches and partial extraction failures caused silent data corruption and missing records, which went undetected until downstream reports failed. The team needs to establish a proactive observability and alerting strategy to rapidly detect data completeness, freshness, and consistency anomalies. The strategy must: Track validation statistics, processing latencies, and error patterns emitted during pipeline execution. Automatically trigger notifications to on-call teams when consistency or completeness thresholds are breached. Consolidate time-series pipeline metrics, relevant log entries, and active incident states into a unified view for rapid triage. Which strategy should the team implement?

Preparing for data corruption and missing data

AdvancedProfessional Cloud Security Engineer

An enterprise uses an external continuous deployment (CD) pipeline to deploy build artifacts into a specific Google Cloud Storage bucket (bucket-prod-artifacts). The designated service account (deployer-sa@project-id.iam.gserviceaccount.com) has the Storage Object Admin role at the project level. To adhere to least-privilege security principles, the security engineer must implement a solution that fulfills the following requirements: The external pipeline workload must authenticate securely without using downloadable, long-lived service account keys. Only the specific external pipeline identity mapped in the Workload Identity Pool is permitted to impersonate deployer-sa. The short-lived OAuth 2.0 access token issued for each pipeline execution must be restricted so that it can only read and write objects within bucket-prod-artifacts, preventing access to any other buckets. Which strategy should the security engineer implement?

Managing and creating short-lived credentials.

Professional Cloud Data Engineer

Backup Dr Snapshot Pool Rpo Rto Optimization

Related questions

Professional Cloud Data Engineer

Backup Dr Snapshot Pool Rpo Rto Optimization

What Google Cloud Backup and DR Snapshot Lifecycle Management Is

How it Meets the Recovery Objectives (RPO and RTO)

Key Advantages

Related questions

What Google Cloud Backup and DR Snapshot Lifecycle Management Is

How it Meets the Recovery Objectives (RPO and RTO)

Key Advantages