You are conducting a stakeholder and user-centric analysis for an enterprise migrating its legacy data warehouse to Google Cloud. Through your analysis, you have documented the following requirements and constraints: Business Analysts (Downstream Users): Require immediate performance improvements for their BI dashboards. Their interaction pattern involves heavy concurrent querying. Data Engineering Team: Currently manages complex batch ETL pipelines writing to the legacy warehouse. They lack the capacity to rewrite these upstream pipelines for at least six months. Business Leadership: Requires measurable success criteria showing user adoption of BigQuery within the next 30 days. How should you design the initial phase of the migration to satisfy these stakeholder requirements?

Offload the use case by migrating the schema and historical data to BigQuery. Establish an incremental data synchronization from the legacy warehouse to BigQuery, and repoint the analysts' dashboards to BigQuery.: What offloading a use case is Offloading a use case is an iterative migration strategy where downstream consumption (like querying and reporting) is moved to the new cloud data warehouse first, while the upstream data ingestion and transformation pipelines remain temporarily anchored to the legacy system. Data is synchronized between the legacy system and the new environment to keep it fresh. How it meets the requirements Business Analysts: They gain immediate access to BigQuery's superior concurrent querying performance because their dashboards are repointed to the migrated data. Data Engineering Team: The complex upstream batch ETL pipelines remain entirely unchanged, satisfying the six-month capacity constraint. Business Leadership: User adoption and measurable success criteria can be achieved within 30 days because the downstream migration is decoupled from the heavy engineering effort of rewriting pipelines. Key advantages/capabilities Faster time-to-value: Delivers business benefits (faster reports) without waiting for a complete architectural overhaul. Risk mitigation: Decouples the migration of the storage/compute layer from the data integration layer. Iterative modernization: Allows the organization to place the upstream pipelines into a backlog to be fully migrated in a subsequent iteration. Minimal disruption: Downstream users experience a seamless transition to the new system. Why this is optimal When stakeholder needs conflict—such as the business demanding immediate performance while engineering requires time to rebuild pipelines—an iterative offloading approach is the only way to satisfy both parties. It bridges the gap between current technological constraints and desired user workflows.

Stakeholder Analysis Data Warehouse Migration Offload

AdvancedProfessional Cloud Data Engineer

You are formulating a target state migration plan to move an on-premises data processing environment to Google Cloud VMware Engine. The environment consists of interconnected data integration applications, large database servers, and several VMs with pending system updates. You need to design a phased migration roadmap that minimizes downtime, avoids multiple power cycles for VMs, and mitigates the risk of resource contention in the target architecture. Which strategy should you incorporate into your migration plan?

Analyzing current stakeholder needs, users, processes, and technologies, and creating a plan to get to desired state

AdvancedProfessional Cloud Data Engineer

Your organization is planning to migrate a legacy data warehouse to BigQuery. Before migrating, you need to perform a technical inventory of the source system to determine migration complexity and identify optimization opportunities. You have the following requirements for the assessment: Identify tables and databases that are frequently accessed together in a single query to understand data dependencies. Discover tables with no recent usage or writes to potentially exclude them from the migration and reduce storage costs. Identify low-latency queries that could be accelerated using BigQuery BI Engine. Which solution should you implement to achieve these requirements?

Analyzing current stakeholder needs, users, processes, and technologies, and creating a plan to get to desired state

AdvancedProfessional Cloud Data Engineer

An enterprise runs a Dataflow streaming pipeline that ingests audit logs from Pub/Sub, applies in-flight transformations using a JavaScript User-Defined Function (UDF), and exports the events to an external monitoring endpoint (Splunk HEC). During a system alert triggered by high backlog on the unprocessed dead-letter subscription, a data engineer analyzes Cloud Logging and error attributes attached to failed records: Several worker log entries display Splunk write status code: 503 and Read timed out. Messages in the unprocessed dead-letter topic have errorMessage attributes showing Splunk write status code: 403 and ReferenceError: device_id is not defined. How should the data engineer classify these errors and remediate the pipeline to ensure full data recovery?

Troubleshooting error messages, billing issues, and quotas

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

Your organization uses a custom on-premises visualization tool to generate business intelligence reports. The tool currently connects to relational databases using standard SQL protocols and does not natively support the BigQuery API. You need to integrate this tool with BigQuery to analyze large datasets. Security policies mandate that the connection must not traverse the public internet, and BigQuery resources must be protected from data exfiltration by restricting access strictly to your hybrid network environment. How should you securely integrate the on-premises tool with BigQuery?

Connecting to tools

FundamentalAssociate Data Practitioner

BigQuery ML Model Lifecycle

Plan a standard ML project (e.g., data collection, model training, model evaluation, prediction)

Professional Cloud Data Engineer

Stakeholder Analysis Data Warehouse Migration Offload

Related questions

BigQuery ML Model Lifecycle

Professional Cloud Data Engineer

Stakeholder Analysis Data Warehouse Migration Offload

What offloading a use case is

How it meets the requirements

Key advantages/capabilities

Why this is optimal

Related questions

BigQuery ML Model Lifecycle

What offloading a use case is

How it meets the requirements

Key advantages/capabilities

Why this is optimal