Google Professional Cloud Developer PCD Questions 976–980 | Page 14/14

976

MCQeasy

You need a managed database service for a lift-and-shift migration of an on-premises SQL Server 2019 OLTP application with up to 64 TB of data. Which Google Cloud database should you choose?

A.Cloud Bigtable

B.AlloyDB

C.Cloud Spanner

D.Cloud SQL

AnswerD

Cloud SQL supports SQL Server 2019 and offers up to 64 TB storage.

Why this answer

Cloud SQL is the correct choice because it supports SQL Server 2019, provides managed database services with up to 64 TB of storage (via the Enterprise Plus tier with 64 TB SSD capacity), and is ideal for lift-and-shift migrations of OLTP workloads without requiring application changes. It offers high availability, automated backups, and compatibility with SQL Server features like T-SQL and linked servers, making it a direct replacement for on-premises SQL Server.

Exam trap

The trap here is that candidates often confuse Cloud Spanner's global scalability with a general-purpose relational database, but the question specifies a lift-and-shift migration of SQL Server 2019, which requires native SQL Server compatibility that only Cloud SQL provides among the options.

How to eliminate wrong answers

Option A is wrong because Cloud Bigtable is a NoSQL, wide-column database designed for large-scale analytical and operational workloads (e.g., time-series, IoT) with low-latency reads/writes, not for relational OLTP applications requiring SQL Server compatibility and ACID transactions. Option B is wrong because AlloyDB is a PostgreSQL-compatible database optimized for high-performance transactional and analytical workloads, but it does not support SQL Server T-SQL or the lift-and-shift of a SQL Server 2019 application without significant schema and query changes. Option C is wrong because Cloud Spanner is a globally distributed, horizontally scalable relational database with strong consistency, but it is not designed for lift-and-shift migrations of SQL Server workloads due to its proprietary SQL dialect, lack of SQL Server compatibility, and higher cost/complexity for a single-region OLTP application with up to 64 TB of data.

Full explanation →

977

MCQeasy

A data engineer is migrating a Teradata data warehouse to BigQuery. They need to transfer historical data and set up continuous replication. Which service should they use?

A.Cloud Storage Transfer Service

B.Cloud Data Fusion

C.BigQuery Data Transfer Service

D.Database Migration Service

AnswerC

BigQuery Data Transfer Service has a Teradata connector that supports both historical backfill and continuous replication.

Why this answer

BigQuery Data Transfer Service supports scheduled and continuous transfers from Teradata to BigQuery, including incremental data loads.

Full explanation →

978

MCQeasy

A developer wants to automatically deploy a new version of an application to App Engine Standard every time code is pushed to the main branch of a Cloud Source Repositories repository. Which service should be used?

A.Cloud Build

B.Cloud Run

C.Cloud Scheduler

D.Cloud Deploy

AnswerA

Cloud Build can automatically trigger on source repo pushes and deploy to App Engine.

Why this answer

Cloud Build is the correct service because it is a fully managed CI/CD platform that integrates natively with Cloud Source Repositories and App Engine Standard. You can configure a Cloud Build trigger to automatically build and deploy your application whenever code is pushed to the main branch, using a cloudbuild.yaml file that specifies the build steps and the `gcloud app deploy` command.

Exam trap

The trap here is that candidates confuse Cloud Deploy (which is for GKE/Cloud Run delivery pipelines) with Cloud Build (the actual CI/CD service that can deploy to App Engine), or they mistakenly think Cloud Run can deploy to App Engine Standard when it is a separate compute platform.

How to eliminate wrong answers

Option B (Cloud Run) is wrong because Cloud Run is a serverless compute platform for running containers, not a CI/CD service for building and deploying to App Engine Standard. Option C (Cloud Scheduler) is wrong because Cloud Scheduler is a cron job service for scheduling tasks, not a continuous deployment tool triggered by code pushes. Option D (Cloud Deploy) is wrong because Cloud Deploy is a delivery pipeline service for GKE and Cloud Run, not for App Engine Standard, and it does not directly integrate with Cloud Source Repositories triggers.

Full explanation →

979

MCQhard

An operations team is configuring a Cloud Monitoring alerting policy for a critical application. They want to ensure that alerts are only fired when an anomaly persists for at least 5 minutes to reduce noise. Which condition configuration should they use?

A.Configure 'Evaluation Missing Data' to '5 minutes'.

B.Use a 'Metric Threshold' condition and set the 'for' parameter to 300 seconds.

C.Set the condition type to 'Metric Absence' with a 5-minute duration.

D.Use 'Never retrigger' state with 5-minute window.

AnswerB

This ensures the alert fires only if condition holds for 5 minutes.

Why this answer

Option B is correct because the 'for' parameter in a Metric Threshold condition specifies the duration (in seconds) that a metric must continuously violate the threshold before the alert fires. Setting it to 300 seconds ensures the anomaly persists for at least 5 minutes, reducing noise from transient spikes. This is the standard approach in Cloud Monitoring for sustained condition evaluation.

Exam trap

Cisco often tests the distinction between 'for' (sustained condition duration) and 'Evaluation Missing Data' (data gap handling), leading candidates to confuse the two when asked about reducing noise from transient anomalies.

How to eliminate wrong answers

Option A is wrong because 'Evaluation Missing Data' controls how the system treats gaps in metric data (e.g., treat as 'no data' or 'not breaching'), not the duration a condition must hold before alerting. Option C is wrong because 'Metric Absence' triggers when data stops reporting for a specified duration, not when a metric exceeds a threshold persistently. Option D is wrong because 'Never retrigger' is a notification channel setting that prevents repeated alerts for the same incident, not a condition configuration for sustained anomaly detection.

Full explanation →

980

MCQhard

A Cloud Spanner database has a table Orders with a child table OrderItems. Queries often join Orders and OrderItems on OrderID. Which schema design optimizes performance for these joins?

A.Define a secondary index on OrderItems.OrderID

B.Use a global index on Orders.OrderID

C.Denormalize OrderItems data into the Orders table

D.Make OrderItems an interleaved table under Orders

AnswerD

Interleaving stores child rows with parent rows in the same split, minimizing join latency.

Why this answer

Interleaved tables store child rows with their parent row in the same split, colocating related data and reducing cross-node communication. This is the correct optimization for parent-child joins.

Full explanation →

Google Professional Cloud Developer (PCD) — Questions 976–980