An enterprise is planning a multi-workload migration strategy to Google Cloud and must select the optimal data transfer mechanisms based on data source type, transfer volume, and network availability: Workload 1: A 350 TB historical file archive stored on an on-premises Network Attached Storage (NAS) system. The archive must be moved to Cloud Storage within two weeks, but the facility's available outbound internet bandwidth is constrained to 100 Mbps and cannot be upgraded. Workload 2: A mission-critical on-premises transactional PostgreSQL database that powers an active production system. It must be migrated to Cloud SQL for PostgreSQL with minimal downtime using continuous replication until the final cutover. Workload 3: Ongoing daily reporting feeds from SaaS advertising platforms (Google Ads and Salesforce) that must be automatically ingested on a recurring schedule directly into analytical tables without maintaining custom ETL infrastructure. Which combination of services should the organization select for these workloads?

Workload 1: Transfer Appliance; Workload 2: Database Migration Service; Workload 3: BigQuery Data Transfer Service: ### What the Recommended Services Are This architecture uses **Transfer Appliance** for high-volume offline physical data transport, **Database Migration Service (DMS)** for minimal-downtime relational database replication, and **BigQuery Data Transfer Service (DTS)** for scheduled, managed SaaS analytics ingestion. ### How It Meets Each Requirement * **Workload 1 (350 TB Archive over 100 Mbps within 2 weeks):** Transferring 350 TB over a 100 Mbps uplink would theoretically require over 320 days of continuous transfer. **Transfer Appliance** solves network throughput bottlenecks by providing high-capacity, encrypted physical hardware shipped on-site to capture data locally and ingest it into Cloud Storage. * **Workload 2 (PostgreSQL to Cloud SQL with minimal downtime):** **Database Migration Service** is purpose-built for relational database migrations, utilizing initial snapshot seeding followed by continuous Change Data Capture (CDC) replication to keep Cloud SQL synchronized until a quick, low-downtime cutover window. * **Workload 3 (Scheduled SaaS ingestion to BigQuery):** **BigQuery Data Transfer Service** natively supports out-of-the-box, fully managed connectors for Google Ads, Salesforce, and third-party sources to automate scheduled recurring loads into BigQuery without code. ### Key Advantages * **Overcomes Network Bandwidth Limits:** Transfer Appliance avoids crippling production bandwidth while meeting tight time constraints. * **Near-Zero Downtime OLTP Cutover:** Database Migration Service replicates database changes in flight. * **No-Code Data Warehousing:** BigQuery Data Transfer Service automates scheduled loads and partition management. ### Why This Is Optimal Each selected tool maps directly to the specific data volume, change velocity, and network profile of the respective workload.

Select Migration Services Data Type Volume Transfer Windows | professional-cloud-data-engineer

AdvancedProfessional Cloud Data Engineer

Your team is executing a zero-downtime database migration from an on-premises sharded relational database to Cloud Spanner. The forward migration strategy uses continuous Change Data Capture (CDC) replication to keep Cloud Spanner in sync with the source database. To ensure business continuity during cutover, you must implement a robust fallback mechanism that allows the application to fail back to the source database with minimal downtime and without data loss if issues occur after cutover. Which strategy should you implement for the reverse replication and validation framework?

Planning migration and validation to Google Cloud (e.g., BigQuery Data Transfer Service, Database Migration Service, Transfer Appliance, Google Cloud networking, Datastream)

AdvancedProfessional Cloud Data Engineer

Your enterprise is planning a large-scale migration of several petabytes of transactional and analytical data from an on-premises data center to Google Cloud. The migration architecture must satisfy the following technical and operational requirements: Throughput and Latency: Provide dedicated 10 Gbps+ bandwidth with low, predictable latency to meet tight migration cutover windows. Security and Privacy: Ensure migration traffic remains completely private and never traverses the public internet. Google Services Access: Enable on-premises migration agents to transfer data directly into Google Cloud storage and database services without assigning public IP addresses to internal hosts. Cost Optimization: Minimize network egress and data transfer costs during validation and ongoing replication phases. Which network architecture should you configure to support this data migration?

AdvancedProfessional Cloud Data Engineer

A data engineering team operates a 24/7 streaming Cloud Dataflow pipeline written in Java that ingests high-volume JSON event streams from Pub/Sub and writes structured rows into BigQuery. Recently, unexpected schema changes upstream have caused malformed JSON payloads, leading to uncaught runtime parsing exceptions inside a DoFn that cause streaming worker tasks to retry indefinitely and stall the pipeline. The team needs to update the Apache Beam pipeline architecture to validate incoming records, immediately divert uncorrectable corrupt payloads to a dead-letter storage sink for auditing and reprocessing, and ensure that valid data continues to flow to BigQuery without pipeline disruption. Which design pattern should the team implement?

AdvancedProfessional Cloud Data Engineer

Your organization manages a BigQuery dataset containing a customer transactions table with sensitive Personally Identifiable Information (PII), including columns for tax_id, email_address, and credit_card_number. You are preparing this data for enterprise-wide visualization and reporting. You have the following security and access requirements: BI Analysts must be able to query the table to build dashboards and perform aggregations, but must only receive real-time obfuscated (masked) values for sensitive columns. Compliance Auditors must be able to inspect and view the unmasked, cleartext values of these sensitive columns. Unauthorized Users without explicit permissions must be blocked from querying the sensitive columns entirely. The security controls must be centrally managed and applied dynamically at query runtime without maintaining duplicate tables, views, or ETL pipelines. Which solution should you implement?

AdvancedProfessional Cloud Data Engineer

Your organization runs three distinct BigQuery workloads: Data Science, ELT, and Business Intelligence (BI). Currently, all queries use the default on-demand pricing model, resulting in highly variable and unpredictable monthly costs. You need to implement a cost-optimized processing architecture that provides predictable pricing while guaranteeing dedicated compute capacity for each workload. Additionally, to maximize resource utilization, any idle compute capacity from one workload must be automatically available to the others. What should you do?

AdvancedProfessional Cloud DevOps Engineer

A DevOps team is troubleshooting intermittent performance bottlenecks and latency spikes on a production Cloud SQL for PostgreSQL database hosting a critical microservice. The lead engineer intends to use conversational AI in the Google Cloud console via Gemini Cloud Assist to diagnose query latency, detect query anomalies, and receive index and configuration recommendations. However, upon opening the Cloud SQL monitoring dashboards and the Gemini Cloud Assist panel, the engineer observes that AI-assisted troubleshooting insights and query anomaly detection are unavailable for this database instance. Which configuration state explains why AI-assisted troubleshooting and query anomaly detection cannot be utilized on this instance?

Professional Cloud Data Engineer

Select Migration Services Data Type Volume Transfer Windows

Related questions