Courseiva

Google Professional Data Engineer (PDE) — Questions 175

890 questions total · 12pages · All types, answers revealed

Page 1 of 12

Page 2
1
MCQmedium

Your team uses a CI/CD pipeline with Cloud Build to train and deploy ML models on Vertex AI. You want to ensure that only models that pass validation checks (e.g., accuracy threshold, fairness metrics) are promoted to production. What is the best way to implement this?

A.Use Cloud Scheduler to trigger retraining and only deploy if the new model outperforms the previous one on a holdout set.
B.Use Vertex AI Model Registry's automatic promotion feature that moves models to production based on evaluation results.
C.Configure Cloud Functions to re-evaluate the model daily and promote if it passes.
D.In the Cloud Build pipeline, after training, run validation scripts. If validation passes, deploy to a staging endpoint for manual approval, then promote to production.
AnswerD

This ensures automated validation before any deployment, with optional manual gate for production.

Why this answer

It integrates validation directly into the CI/CD pipeline using Cloud Build, ensuring that only models passing specific checks (e.g., accuracy threshold, fairness metrics) are promoted. By running validation scripts after training and requiring manual approval before production promotion, this approach provides both automated gatekeeping and human oversight, aligning with MLOps best practices for safe model deployment.

Exam trap

Google Cloud often tests the misconception that Vertex AI Model Registry has built-in automatic promotion based on evaluation metrics, but in reality, it requires external orchestration (like Cloud Build) to implement such logic.

How to eliminate wrong answers

Option A is wrong because Cloud Scheduler triggers retraining on a schedule, not based on validation results, and it does not integrate with the CI/CD pipeline to enforce promotion gates. Option B is wrong because Vertex AI Model Registry does not have an automatic promotion feature based on evaluation results; it stores and manages models but requires external logic to decide promotion. Option C is wrong because Cloud Functions re-evaluating the model daily is reactive and does not tie into the build pipeline's validation step, potentially promoting a model that was not validated at the time of training.

2
MCQhard

A financial services company stream trades into Pub/Sub and processes with Dataflow. The pipeline must ensure exactly-once processing of each trade for regulatory compliance. However, Pub/Sub guarantees at-least-once delivery. Which combination of features should the Dataflow pipeline use to achieve exactly-once semantics?

A.Use Dataflow's exactly-once processing mode and implement idempotent writes in the sink
B.Enable Pub/Sub message deduplication and use at-most-once delivery
C.Use global windowing and discard late data
D.Use Pub/Sub Lite with exactly-once delivery guarantee
AnswerA

Dataflow's exactly-once mode with idempotent sinks ensures output exactly once.

Why this answer

Dataflow's exactly-once sink combined with idempotent writes ensures exactly-once output. Pub/Sub cannot guarantee exactly-once delivery, but Dataflow can deduplicate using unique IDs. Idempotent writes prevent duplicates even if Dataflow retries.

3
Multi-Selecthard

You are setting up Dataplex data quality rules for a BigQuery table. You want to define rules that check for non-null values in key columns and also validate that a column's values fall within a certain range. Which TWO rule types must you use? (Choose 2)

Select 2 answers
A.Table rule (e.g., row count)
B.Row rule (e.g., not null)
C.Partition rule
D.Column rule (e.g., value range)
E.Custom SQL rule
AnswersB, D

Row rules can enforce null checks on specific columns.

Why this answer

Dataplex data quality rules include row rules (for null checks) and column rules (for range or value checks). Table rules apply to the entire table; custom SQL can be used but row and column rules are the standard.

4
MCQhard

A data engineer needs to share a large BigQuery table with a different team, but wants to minimize storage costs. The table is 1 TB in size and is updated daily. The other team only needs read access to the data as of a specific point in time (e.g., end of each day). Which BigQuery feature should be used to provide a read-only copy without duplicating the entire table?

A.Table clone
B.Authorized views
C.Time travel using FOR SYSTEM_TIME AS OF
D.Table snapshot
AnswerD

Snapshots provide point-in-time read-only copies and share storage with the base table, minimizing cost.

Why this answer

BigQuery table clones provide a lightweight, writable copy of a table that initially shares storage with the base table and only incurs costs for changes made to the clone. Snapshots are read-only and also share storage but require the base table to be preserved until snapshot expires. For read-only point-in-time access, a snapshot is more appropriate because it is immutable and cost-effective.

5
MCQeasy

Refer to the exhibit. An auditor sees the following output from `gcloud ai models list`. What can they conclude about versioning?

A.The model is deployed on a single endpoint
B.The model has two versions with v2 being the latest
C.Only the latest version is available
D.The model is automatically scaled
AnswerB

Two distinct versions are shown; v2 has a later timestamp.

Why this answer

The `gcloud ai models list` output shows two model versions (v1 and v2) under the same model resource. The default traffic split or the listed order indicates v2 is the latest version. This directly confirms that the model has two versions, with v2 being the latest, making option B correct.

Exam trap

Google Cloud often tests that candidates confuse model versioning with endpoint deployment details, leading them to assume a single endpoint or automatic scaling from a model list output that contains no such information.

How to eliminate wrong answers

Option A is wrong because the output does not show any endpoint information; model versions can be deployed to multiple endpoints or not deployed at all. Option C is wrong because the output explicitly lists two versions (v1 and v2), so both are available, not just the latest. Option D is wrong because the output provides no scaling configuration or metrics; autoscaling is a deployment setting, not a model version property.

6
MCQhard

A company processes IoT sensor data in near real-time. They ingest data via Cloud Pub/Sub, then a Dataflow streaming pipeline writes to Bigtable for low-latency queries. Recently, they observed increased Pub/Sub message backlog during traffic spikes. What is the most effective scaling strategy?

A.Increase Pub/Sub subscription throughput by increasing the number of partitions
B.Increase Dataflow worker count and adjust autoscaling configuration
C.Use a Cloud Scheduler to throttle Pub/Sub publishing
D.Add a Cloud Function to pre-process messages before they are consumed by Dataflow
AnswerB

Dataflow autoscaling can handle backlogs if enough workers are provisioned; increasing the max number of workers allows the pipeline to catch up during spikes.

Why this answer

The increased Pub/Sub backlog during traffic spikes indicates that the Dataflow pipeline is unable to consume messages as fast as they are being published. Increasing the Dataflow worker count and adjusting autoscaling configuration allows the pipeline to scale horizontally, processing more messages per second and reducing the backlog. Pub/Sub itself is designed to handle high throughput, so the bottleneck is the consumer (Dataflow), not the ingestion layer.

Exam trap

The trap here is that candidates mistakenly think Pub/Sub's throughput is limited by partitions (like Kafka) or that throttling the publisher is a valid scaling strategy, when in fact the bottleneck is the streaming pipeline's processing capacity, which must be scaled horizontally.

How to eliminate wrong answers

Option A is wrong because Pub/Sub does not use partitions like Kafka; increasing partitions is not a valid concept for Pub/Sub subscriptions, and throughput is managed by the subscriber's ability to pull messages, not by partitioning. Option C is wrong because throttling Pub/Sub publishing with Cloud Scheduler would reduce the incoming data rate, but this is counterproductive for near real-time processing and does not address the root cause of insufficient consumer capacity. Option D is wrong because adding a Cloud Function to pre-process messages would introduce an additional processing step that could further increase latency and does not directly solve the Dataflow pipeline's inability to keep up with the message volume.

7
Multi-Selectmedium

A Dataflow streaming job is processing data from Pub/Sub and writing to BigQuery. The job is stuck with the message 'No progress has been made' for several minutes. Which TWO actions should the team take to troubleshoot and resolve the issue? (Choose TWO.)

Select 2 answers
A.Set the updateCompatibility flag to true and restart the pipeline.
B.Increase the persistent disk size for all workers to reduce I/O contention.
C.Examine the worker logs in Cloud Logging for any error messages or exceptions.
D.Force stop the pipeline and update it with a new version using the --update flag.
E.Enable Dataflow Streaming Engine to move state to the backend and reduce worker load.
AnswersC, E

Examining worker logs in Cloud Logging helps identify the root cause of the stuck pipeline, such as OOM errors, serialization failures, or worker crashes.

Why this answer

Examining worker logs in Cloud Logging helps identify the root cause of the stuck pipeline, such as OOM errors, serialization failures, or worker crashes. Option E is also correct because enabling Dataflow Streaming Engine moves state to the backend, reducing worker load and overcoming stuck progress issues caused by resource constraints. The combination of inspecting logs and offloading state allows effective troubleshooting and resolution.

Exam trap

Google Cloud often tests the misconception that increasing resources (like disk size) or restarting the pipeline is the default fix, when in reality the first step is always to inspect logs to understand the failure mode.

8
MCQhard

A company uses Pub/Sub with push subscriptions to deliver events to a Cloud Run service. Recently, the service has been returning HTTP 429 (Too Many Requests), causing messages to be retried and eventually sent to the dead letter topic. What is the MOST likely cause?

A.The subscription ackDeadline is set too low, causing messages to be redelivered
B.The push endpoint is not acknowledging messages quickly enough, causing a backlog
C.The dead letter topic is misconfigured, causing messages to be sent to it prematurely
D.The Cloud Run service needs more instances to handle the incoming request rate
AnswerD

Cloud Run scales based on requests; if max instances reached, it returns 429. Increasing instances or adjusting concurrency resolves this.

Why this answer

Push subscriptions can be rate limited by the receiving service. Increasing ackDeadline gives more time but doesn't reduce rate. Using pull subscriptions shifts the rate control to the subscriber.

Adjusting max delivery attempts only affects how many retries before dead letter, not rate limiting.

9
MCQhard

A healthcare organization stores patient data in BigQuery. They need to encrypt a specific column (e.g., SSN) using a key they manage, and decrypt it only for authorized queries via a user-defined function. Which approach should they use?

A.Use BigQuery AEAD encryption functions with a Cloud KMS key
B.Use BigQuery column-level access controls
C.Use Cloud Key Management Service (Cloud KMS) with CMEK for the BigQuery dataset
D.Use Cloud Data Loss Prevention (DLP) to de-identify the column
AnswerA

AEAD functions allow encrypting specific columns and decrypting via a SQL function, using keys from Cloud KMS.

Why this answer

BigQuery AEAD encryption functions (e.g., `AEAD.ENCRYPT` and `AEAD.DECRYPT`) allow you to encrypt a specific column using a customer-managed key stored in Cloud KMS, and then decrypt it only within a user-defined function (UDF) that enforces access controls. This meets the requirement of per-column encryption with key management and authorized decryption via a UDF.

Exam trap

A common mistake is to choose dataset-level encryption (CMEK) because it involves Cloud KMS, but CMEK does not allow per-column encryption or UDF-controlled decryption. The correct approach uses BigQuery AEAD encryption functions with a Cloud KMS key for column-level encryption and authorized decryption via a UDF.

How to eliminate wrong answers

Option B is wrong because BigQuery column-level access controls only restrict who can see the column, but they do not encrypt the data at rest or in transit, so the data remains in plaintext and does not satisfy the encryption requirement. Option C is wrong because Cloud KMS with CMEK encrypts the entire BigQuery dataset at the storage level, not a specific column, and decryption is automatic for authorized users, not controlled via a UDF. Option D is wrong because Cloud DLP de-identifies data (e.g., masking or tokenization) but is not designed for reversible encryption with a customer-managed key and UDF-based decryption; it is typically used for static de-identification, not dynamic per-query decryption.

10
Multi-Selecteasy

Which TWO actions can reduce the cost of running a Dataproc cluster for a nightly batch job?

Select 2 answers
A.Increase the number of worker nodes for faster processing.
B.Use high-memory machine types for master node.
C.Use preemptible VMs for worker nodes.
D.Attach local SSDs to all nodes.
E.Delete the cluster after the job completes.
AnswersC, E

Preemptible VMs are much cheaper.

Why this answer

Preemptible VMs (Option C) are significantly cheaper than standard VMs because Compute Engine can terminate them at any time, making them ideal for fault-tolerant, stateless batch jobs like nightly data processing on Dataproc. Deleting the cluster after the job completes (Option E) eliminates ongoing compute costs for idle resources, which is a best practice for ephemeral workloads.

Exam trap

Google Cloud often tests the misconception that scaling up resources (more nodes or faster hardware) always reduces cost by shortening runtime, but in reality, the increased per-hour cost usually outweighs the time savings for batch jobs.

11
MCQmedium

A company is designing a data pipeline that ingests real-time events from IoT devices and must handle late-arriving data (up to 1 hour late) while minimizing duplicate processing. They plan to use Dataflow with Pub/Sub. Which combination of windowing and trigger settings should they use?

A.Sliding windows of 10 minutes with allowed lateness of 30 minutes and accumulating panes
B.Global window with allowed lateness of 1 hour and accumulating trigger every 5 minutes
C.Fixed windows of 1 hour with allowed lateness of 1 hour and no accumulation
D.Session windows with a 10-minute gap duration and allowed lateness of 1 hour
AnswerD

Session windows group events that occur within a 10-minute gap. Allowed lateness of 1 hour ensures that late events up to an hour after the watermark advance are still included, minimizing duplicates by capturing them in the correct session.

Why this answer

Session windows naturally group events based on a gap duration, so late events within the gap extend the window. Setting the allowed lateness to 1 hour ensures that late events are still included in the correct session. Using withAllowedLateness(1 hour) allows the watermark to advance and the session to finalize after the gap, but late data within 1 hour will trigger a pane update.

12
Multi-Selecthard

A data engineer needs to create a unified table that combines data from Cloud Storage (Parquet files) and BigQuery native tables, with fine-grained access control and governance. Which three Google Cloud features should they use together? (Choose THREE.)

Select 3 answers
A.BigQuery
B.Dataproc
C.BigLake
D.Cloud Storage
E.Cloud SQL
AnswersA, C, D

BigQuery is used for both native tables and the unified query engine.

Why this answer

BigQuery is correct because it serves as the unified query engine that can read data from both Cloud Storage (via external tables or BigLake) and native BigQuery tables, enabling a single SQL interface for analysis. It also integrates with fine-grained access control through row-level security and column-level access policies, and supports governance via Data Catalog and VPC Service Controls.

Exam trap

The trap here is that candidates may confuse Dataproc (a processing engine) with a storage or query service, or think Cloud SQL can handle Parquet files, when the correct combination requires BigQuery, BigLake, and Cloud Storage to achieve unified querying and governance.

13
Multi-Selecthard

A data pipeline processes sensitive customer data. You need to ensure that only authorised users can query the data in BigQuery, and that the data is encrypted at rest and in transit. Which THREE steps should you take? (Choose three.)

Select 3 answers
A.Use a Cloud VPN to encrypt data in transit between on-premises and Google Cloud
B.Grant the bigquery.dataViewer role at the dataset level to all users
C.Create authorised views in BigQuery to restrict access to sensitive columns
D.Enable default encryption with Customer-Managed Encryption Keys (CMEK) for BigQuery
E.Use IAM conditions to restrict access based on the requester's IP address
AnswersC, D, E

Authorised views allow fine-grained access control at row/column level.

Why this answer

Encryption at rest is enabled by default with CMEK or CSEK. In-transit encryption is default for BigQuery. Authorised views provide fine-grained access control.

IAM roles control dataset access.

14
MCQeasy

A company is designing a streaming data pipeline to process real-time clickstream events. They need to aggregate events by session window with a 5-minute gap and enable exactly-once processing semantics. Which Google Cloud service should they use?

A.Cloud Pub/Sub with Cloud Functions
B.Cloud Dataflow with Apache Beam
C.Cloud Dataproc with Spark Streaming
D.Cloud Bigtable with Dataflow templates
AnswerB

Dataflow with Beam natively supports session windows and exactly-once processing via its processing guarantees.

Why this answer

Cloud Dataflow with Apache Beam is the correct choice because it provides native support for session windows with a 5-minute gap duration and exactly-once processing semantics via its sink and source integrations. Dataflow's Beam SDK allows you to define session windows using `Window.into(Sessions.withGapDuration(Duration.standardMinutes(5)))`, and its checkpointing and idempotent writes ensure exactly-once delivery even in failure scenarios.

Exam trap

Google Cloud often tests the distinction between stateless serverless services (like Cloud Functions) and stateful stream processing engines (like Dataflow), leading candidates to incorrectly choose Cloud Pub/Sub with Cloud Functions because they overlook the need for session window state management and exactly-once semantics.

How to eliminate wrong answers

Option A is wrong because Cloud Pub/Sub with Cloud Functions does not support session windowing natively; Cloud Functions are stateless and cannot maintain session state across invocations, and Pub/Sub offers at-least-once delivery, not exactly-once. Option C is wrong because Cloud Dataproc with Spark Streaming can implement session windows but requires manual state management and does not provide built-in exactly-once semantics; Spark Streaming's checkpointing can lead to duplicate outputs in failure recovery. Option D is wrong because Cloud Bigtable with Dataflow templates is a storage and template combination, not a processing service; Dataflow templates can be used for streaming but the question asks for the service to use, and Bigtable is a NoSQL database, not a stream processing engine.

15
MCQmedium

You are using Vertex AI Feature Store to serve features for online predictions. Your model requires features from multiple sources with low latency (<10ms). Which type of serving should you use?

A.Online serving with Cloud SQL
B.Offline serving with BigQuery
C.Online serving with Bigtable
D.Offline serving with Cloud Storage
AnswerC

Online serving uses Bigtable for low-latency feature retrieval.

Why this answer

Online serving (with Bigtable as backing store) provides low-latency feature retrieval. Offline serving is for batch predictions. Feature Store supports both; online is for real-time.

16
Multi-Selecthard

Which TWO metrics are most important to monitor for a real-time online prediction system to ensure service reliability and model performance?

Select 2 answers
A.Feature distribution skew between training and serving
B.Prediction latency (p50, p99)
C.Number of training examples used for the latest model version
D.Batch prediction job throughput
E.Prediction error rate (e.g., 4xx/5xx responses)
AnswersB, E

Latency is critical for real-time applications; p99 shows tail performance.

Why this answer

Prediction latency (p50, p99) is critical because it directly impacts user experience and system reliability; high tail latency (p99) can indicate resource contention or model complexity issues. Prediction error rate (4xx/5xx) is essential for detecting serving infrastructure failures, such as model server crashes or misconfigured endpoints, which degrade service reliability. Both metrics provide real-time visibility into the serving layer's health and performance, distinct from offline training metrics.

Exam trap

Google Cloud often tests the distinction between offline training metrics (like feature skew or training example count) and real-time serving metrics (like latency and error rate), trapping candidates who confuse model performance monitoring with service reliability monitoring.

17
Multi-Selectmedium

A company needs to stream data from a MySQL database to BigQuery with a latency under 10 seconds. They also need to handle schema changes automatically. Which TWO services should they combine?

Select 2 answers
A.BigQuery
B.Datastream
C.Dataflow
D.Pub/Sub
E.Cloud SQL
AnswersA, B

Target for the streamed data.

Why this answer

Datastream captures CDC and can write to BigQuery directly. Pub/Sub is not needed if Datastream writes directly.

18
MCQmedium

A company needs to predict whether a product image contains a specific defect. They have 10,000 labeled images and want to build a model quickly without writing custom code or training from scratch. Which GCP service should they use?

A.AutoML Tables
B.AutoML Vision
C.Vertex AI custom training
D.AutoML Natural Language
AnswerB

AutoML Vision is for image classification with minimal coding.

Why this answer

AutoML Vision is designed for custom image classification tasks with minimal ML expertise. It uses transfer learning and supports up to millions of images. AutoML Tables handles tabular data, not images.

Vertex AI custom training would require more effort. AutoML NLP is for text data.

19
MCQmedium

A team trained a model on a Vertex AI custom training job and wants to deploy it to an endpoint for online predictions. They have the model artifacts stored in Cloud Storage. What steps are required?

A.Upload model to Model Registry, create endpoint, deploy model
B.Directly deploy from Cloud Storage without Model Registry
C.Create endpoint, then upload model
D.Use Vertex AI Batch Prediction only
AnswerA

This is the standard workflow: register model, create endpoint, then deploy.

Why this answer

To deploy a model for online predictions on Vertex AI, you must first upload the model artifacts from Cloud Storage to the Model Registry, which creates a versioned model resource. Then you create an endpoint (or use an existing one) and deploy the model to that endpoint, specifying machine type, traffic split, and other settings. This three-step process (upload → create endpoint → deploy) is the required workflow for online serving.

Exam trap

Google Cloud often tests the misconception that you can deploy directly from Cloud Storage without the Model Registry, or that the endpoint must be created before the model is uploaded, when in fact the model must be registered first.

How to eliminate wrong answers

Option B is wrong because Vertex AI does not allow direct deployment from Cloud Storage without first registering the model in the Model Registry; the registry is required to manage model versions and associate deployment configurations. Option C is wrong because you cannot create an endpoint before uploading the model to the Model Registry, as the endpoint deployment references a model resource that must already exist. Option D is wrong because the question explicitly asks for online predictions, and batch prediction is a separate, asynchronous process that does not involve endpoints or real-time serving.

20
Multi-Selecthard

A data science team uses Cloud Build and Vertex AI to implement CI/CD for their machine learning models. Which THREE steps are essential for a production-ready operationalization pipeline? (Choose 3.)

Select 3 answers
A.Store all training artifacts in Cloud Storage without versioning.
B.Deploy the model to a staging endpoint for manual approval before promoting to production.
C.Automatically deploy every new model version directly to the production endpoint.
D.Use Vertex AI Model Evaluation to validate the new model against the current production model metrics.
E.Include unit and integration tests for the training code in the Cloud Build pipeline.
AnswersB, D, E

Staging allows human review and canary testing before full production rollout.

Why this answer

Deploying to a staging endpoint for manual approval before promoting to production is a critical step in a production-ready CI/CD pipeline. This allows data scientists to validate model behavior, performance, and fairness in a near-production environment, preventing regressions and ensuring governance compliance before the model serves live traffic.

Exam trap

Google Cloud often tests the misconception that full automation (Option C) is always better, but the trap here is that production-ready pipelines require human-in-the-loop approval for critical model changes to ensure accountability and safety.

21
MCQmedium

A data pipeline processes streaming data from Pub/Sub to BigQuery. The pipeline needs to handle late-arriving data that is up to 1 hour late. Which Dataflow feature should be used?

A.Global windows with watermark
B.Session windows
C.Sliding windows with allowed lateness
D.Fixed windows with allowed lateness
AnswerD

Fixed windows with allowed lateness (set to 1 hour) ensure late events are processed in the correct window.

Why this answer

Fixed windows with allowed lateness are the correct choice because the pipeline needs to handle late-arriving data up to 1 hour late while processing data in fixed time intervals (e.g., 1-hour windows). The `allowedLateness` parameter in Dataflow (Apache Beam) allows late data to be included in the appropriate fixed window for up to the specified duration after the watermark passes the window end. This ensures that late Pub/Sub messages are correctly joined with their original window in BigQuery.

Exam trap

Google Cloud often tests the distinction between window types and lateness handling, and the trap here is that candidates confuse 'allowed lateness' as a feature exclusive to sliding windows or global windows, when in fact it is a parameter that can be applied to fixed windows to handle late data within a bounded delay.

How to eliminate wrong answers

Option A is wrong because global windows with watermark process all data in a single unbounded window and rely on watermark to trigger output, but they cannot segment data into fixed time intervals for BigQuery loading, and late data handling is not as precise for per-window aggregation. Option B is wrong because session windows group events based on gaps of inactivity, which is not suitable for processing data in fixed time intervals as required by the pipeline. Option C is wrong because sliding windows produce overlapping windows that emit multiple outputs per element, which is unnecessary and inefficient for a simple fixed-interval pipeline, and allowed lateness is a property of fixed windows, not sliding windows in this context.

22
MCQeasy

You need to estimate the cost of a BigQuery query before running it. Which command or feature should you use?

A.Check the BigQuery jobs list for similar queries.
B.Use the BigQuery cache to estimate if the query is cached.
C.Run EXPLAIN on the query to see the query plan.
D.Use the bq command with the --dry_run flag.
AnswerD

Dry run estimates the bytes processed, allowing cost estimation without running the query.

Why this answer

The `bq` command with the `--dry_run` flag allows you to estimate the amount of data a BigQuery query will process before actually executing it. This dry run does not read any data or incur charges; it simply returns the estimated bytes to be processed, which you can use to calculate the cost based on BigQuery's pricing model.

Exam trap

A common trap is confusing the EXPLAIN command (which shows the query plan) with the `--dry_run` flag (which estimates bytes processed and cost).

How to eliminate wrong answers

Option A is wrong because checking the BigQuery jobs list for similar queries only gives you historical cost data, not an estimate for the specific query you are about to run, and it assumes a similar query exists. Option B is wrong because the BigQuery cache stores results of previously run queries, but it does not provide an estimate of cost or data processed; it only indicates whether results might be served from cache. Option C is wrong because running EXPLAIN on the query shows the query plan and execution steps, but it does not provide a cost estimate or the amount of data that will be scanned.

23
MCQhard

A company runs a daily batch data processing pipeline using Cloud Dataproc. The pipeline reads 10 TB of CSV files from Cloud Storage, performs a heavy aggregation (GroupBy) and joins with a small reference table, then writes the results to BigQuery. The cluster consists of 20 n1-standard-8 nodes, including 10 preemptible workers for cost savings. Recently, the job completion time has doubled from 30 minutes to over an hour. The job logs show many tasks being retried, and the Shuffle spill ratio is high. No significant data volume change was observed. What is the most likely root cause?

A.The cluster's HDFS is running out of space due to intermediate shuffle data.
B.Data skew has developed, causing a few tasks to process most of the data.
C.Preemptible workers are being reclaimed, causing YARN container failures and task retries.
D.The reference table has increased in size, causing more data to be broadcast to all workers.
AnswerC

Preemptible nodes can be taken at any time; Shuffle-heavy jobs suffer greatly from lost intermediate data.

Why this answer

Preemptible workers are frequently reclaimed by Google Cloud, causing YARN containers to fail and tasks to be retried. This leads to increased job completion time and a high shuffle spill ratio, as partial shuffle data is lost and must be recomputed. The doubling of job time without data volume change strongly points to infrastructure instability rather than data or configuration issues.

Exam trap

The trap here is that candidates may attribute high shuffle spill and task retries to data skew or HDFS space, but the key clue is the unchanged data volume and the use of preemptible workers, which directly cause container failures and retries.

How to eliminate wrong answers

Option A is wrong because Cloud Dataproc uses Cloud Storage for intermediate shuffle data by default (via the 'spark.shuffle.useOldFetchProtocol' or 'spark.shuffle.manager' settings), not HDFS, so HDFS space is not a bottleneck. Option B is wrong because data skew would cause a few tasks to process most data, but the symptom of many tasks being retried and high shuffle spill ratio is more consistent with container failures, not skew; skew typically manifests as a few long-running tasks, not widespread retries. Option D is wrong because the reference table is described as small, and even if it increased, broadcasting more data would not cause task retries or high shuffle spill; it would instead increase memory pressure on executors, not trigger widespread failures.

24
Drag & Dropmedium

Drag and drop the steps to configure a VPC network with private Google access for on-premises connectivity using Cloud VPN into the correct order.

Drag steps to the numbered slots on the right, or tap a step then tap a slot.

Steps
Order
1Step 1
2Step 2
3Step 3
4Step 4

Why this order

Private Google Access allows on-premises hosts to reach Google APIs via VPN without public IPs.

25
MCQeasy

A company uses Cloud Dataflow to process streaming data from Pub/Sub into BigQuery. The pipeline uses a side input from a Cloud Bigtable table containing user profile information to enrich the events. The side input is updated every hour. Which approach should the company use to ensure that the pipeline uses the latest profile data without causing high memory usage?

A.Use a side input that is periodically refreshed by reading the Cloud Bigtable table at a regular interval.
B.For each incoming event, read the corresponding profile from Cloud Bigtable using a synchronous call.
C.Use a CoGroupByKey transform to join the stream with a bounded PCollection created from the Cloud Bigtable table.
D.Stream the profile updates into a separate BigQuery table and use a BigQuery streaming query to join in real-time.
AnswerA

Using a side input that is periodically refreshed is the correct approach. Dataflow allows side inputs to be refreshed at specified intervals by re-reading the source. This keeps the data up-to-date without keeping the entire set in memory for the pipeline's lifetime; instead, it is cached and rebuilt only when refreshed.

Why this answer

Cloud Dataflow supports periodically refreshing side inputs by reading from an external source like Cloud Bigtable at a specified interval. This approach keeps the profile data up-to-date without storing the entire side input in memory for the lifetime of the pipeline; instead, the side input is rebuilt and cached only when refreshed, controlling memory usage.

Exam trap

Google Cloud often tests the misconception that side inputs are static and cannot be updated, leading candidates to choose per-element lookups (Option B) or complex joins (Option C), when in fact Dataflow's side input refresh mechanism is the correct, efficient solution for periodically updated reference data.

How to eliminate wrong answers

Option B is wrong because making a synchronous call to Cloud Bigtable for every incoming event would introduce high latency and potentially overwhelm Bigtable with thousands of read requests per second, leading to performance degradation and increased cost. Option C is wrong because CoGroupByKey requires both inputs to be bounded PCollections; the streaming Pub/Sub source is unbounded, and joining it with a bounded Bigtable snapshot would not reflect updates to the profile data over time. Option D is wrong because streaming profile updates into a separate BigQuery table and using a streaming query to join in real-time would add unnecessary complexity and latency, and BigQuery is not designed for high-frequency per-event joins in a streaming pipeline.

26
MCQmedium

A production model deployed on Vertex AI Endpoint is experiencing high latency during traffic spikes. The current configuration uses a single replica. What is the most efficient solution?

A.Set a higher min replica count (e.g., 3)
B.Enable autoscaling with minReplicaCount=1 and maxReplicaCount=10
C.Use a larger machine type (e.g., n1-highmem-8)
D.Switch to batch prediction to handle spikes
AnswerB

Autoscaling adjusts replicas based on load, balancing latency and cost.

Why this answer

Enabling autoscaling with minReplicaCount=1 and maxReplicaCount=10 allows Vertex AI Endpoint to dynamically add replicas during traffic spikes, distributing inference requests across multiple instances and reducing latency. This is the most efficient solution as it scales resources up only when needed, avoiding over-provisioning and minimizing cost during low traffic periods.

Exam trap

A common mistake is thinking that manually increasing the minimum replica count or using a larger machine type (static scaling) is the best way to reduce latency during spikes. However, Vertex AI Endpoint's autoscaling (with minReplicaCount=1 and maxReplicaCount=10) dynamically adjusts replicas based on traffic, avoiding over-provisioning and reducing cost. This is a key operational excellence principle in Google Cloud: design for elasticity.

How to eliminate wrong answers

Option A is wrong because setting a higher min replica count (e.g., 3) would keep three replicas running at all times, increasing cost without addressing the root cause of latency during spikes—it does not provide dynamic scaling beyond the fixed minimum. Option C is wrong because using a larger machine type (e.g., n1-highmem-8) increases per-request throughput but does not handle concurrent request bursts; a single replica, even with more memory, can still be overwhelmed by a spike, leading to queuing and high latency. Option D is wrong because batch prediction is designed for asynchronous, offline processing of large datasets and is not suitable for real-time inference; switching to batch prediction would introduce unacceptable delays for live traffic and does not solve the latency problem during spikes.

27
Multi-Selectmedium

Which TWO configurations are required to enable online prediction for a model deployed on Vertex AI Endpoints?

Select 2 answers
A.A feature store must be attached to the endpoint.
B.The endpoint must be configured with a machine type (e.g., n1-standard-2).
C.The model must be trained on Vertex AI.
D.A model must be deployed to an endpoint.
E.Autoscaling must be enabled.
AnswersB, D

A machine type must be specified to allocate resources for serving.

Why this answer

Vertex AI Endpoints require a machine type to be specified when deploying a model. The machine type determines the compute resources (CPU/memory) allocated to the serving container, which is essential for handling prediction requests. Without a machine type, the endpoint cannot provision the underlying infrastructure to serve online predictions.

Exam trap

The trap here is that candidates often confuse optional features (like Feature Store or autoscaling) with mandatory configurations, or assume the model must be trained on Vertex AI, when in fact only the machine type and model deployment are strictly required for online prediction.

28
MCQmedium

You are building a Dataflow pipeline in Python that reads messages from Pub/Sub, enriches them with data from a BigQuery table, and writes the results to BigQuery. The enrichment lookup table is large and changes infrequently. Which approach minimizes cost and latency?

A.Use a CoGroupByKey transform to join the incoming stream with a stream from BigQuery.
B.Use BigQuery IO to query the table for every incoming message.
C.Use a side input that reads the BigQuery table periodically and caches it.
D.Use a stateful DoFn and store the lookup in state per key.
AnswerC

Side inputs are ideal for distributing a static lookup table to all workers. The data can be refreshed on a schedule.

Why this answer

Using a side input that periodically reads the BigQuery table and caches it avoids querying BigQuery for every incoming message, which would be prohibitively expensive and high-latency. The side input is refreshed at a configurable interval (e.g., every 10 minutes) via a pipeline option, and the cached data is broadcast to all workers, enabling fast, in-memory lookups without per-element I/O. This approach minimizes cost by reducing BigQuery API calls and minimizes latency by avoiding synchronous queries for each message.

Exam trap

Google often tests the misconception that querying BigQuery per message is acceptable in streaming pipelines, but the trap here is that candidates overlook the cost and latency implications of per-element I/O, especially with BigQuery's pricing model and query latency.

How to eliminate wrong answers

Option A is wrong because CoGroupByKey requires both inputs to be bounded or both unbounded streams; here, the BigQuery table is a bounded dataset, and Pub/Sub is unbounded, so CoGroupByKey would not work without windowing and would introduce unnecessary complexity and latency. Option B is wrong because querying BigQuery for every incoming message would cause extremely high API costs (BigQuery charges per byte processed) and high latency (each query takes hundreds of milliseconds to seconds), making it impractical for a streaming pipeline. Option D is wrong because storing the lookup in state per key would require partitioning the lookup table across keys, which is inefficient for a large, infrequently changing table; state is per-key and not shared across keys, so each worker would need to load and maintain its own copy, leading to memory waste and complex state management.

29
Multi-Selecthard

You are designing a data pipeline that ingests streaming data from Pub/Sub, processes it with Dataflow, and writes to BigQuery. You need to ensure that schema changes in the incoming data (new fields) are handled without pipeline failure. Which THREE steps should you take? (Choose THREE.)

Select 3 answers
A.Set the BigQuery table schema to allow automatic addition of new fields by using 'ignore_unknown_values'.
B.Configure the BigQuery table to require all fields, causing the pipeline to fail on unknown fields.
C.Use ALTER TABLE ADD COLUMN DDL statements to add nullable columns for new fields.
D.Configure the Dataflow pipeline to update the BigQuery table schema when new fields are detected.
E.Set all columns in the BigQuery table as NULLABLE from the start.
AnswersA, C, D

This option tells BigQuery to ignore unknown fields and allows schema auto-detection.

Why this answer

To handle schema drift, BigQuery allows schema relaxation (adding nullable columns) via DDL. Dataflow can update the destination table schema using BigQuery APIs (e.g., set the schema to include unknown fields). Alternatively, using BigQuery's automatic schema detection with 'ignore_unknown_values' can allow new fields to be added automatically.

Setting all fields to NULLABLE in advance is not practical. Setting the table to require all fields causes failures on unknown fields.

30
MCQhard

A financial services firm processes sensitive transactions using Cloud Dataflow. The pipeline reads from Pub/Sub, performs stateful processing (e.g., fraud detection), and writes to Cloud Spanner. Compliance requires exactly-once processing semantics. Which configuration ensures exactly-once processing?

A.Configure Pub/Sub to use exactly-once delivery mode.
B.Use Pub/Sub with at-least-once delivery and Dataflow with at-least-once processing mode.
C.Set Dataflow pipeline to exactly-once mode and design Spanner writes to be idempotent.
D.Enable Dataflow's streaming engine and use Spanner's built-in retry logic.
AnswerC

Exactly-once mode with idempotent sinks prevents duplicates.

Why this answer

Exactly-once processing in a Dataflow pipeline requires the pipeline itself to be set to exactly-once mode (which uses consistent snapshots and transactional sinks) and the output writes to Spanner to be idempotent. This combination ensures that even if a record is reprocessed due to failures, the final state in Spanner remains consistent, satisfying compliance requirements.

Exam trap

The trap here is that candidates often assume Pub/Sub's exactly-once delivery alone is sufficient, but they overlook that Dataflow's internal processing and output writes must also be idempotent or transactional to achieve end-to-end exactly-once semantics.

How to eliminate wrong answers

Option A is wrong because Pub/Sub's exactly-once delivery mode only guarantees that a message is delivered exactly once to the subscriber, but it does not prevent duplicate processing within the Dataflow pipeline due to retries or checkpoint recovery. Option B is wrong because using at-least-once delivery in Pub/Sub combined with at-least-once processing in Dataflow inherently allows duplicates, violating exactly-once semantics. Option D is wrong because enabling Dataflow's streaming engine improves scalability and latency but does not enforce exactly-once processing, and Spanner's built-in retry logic only handles transient failures, not duplicate writes from reprocessing.

31
MCQhard

A company runs a streaming Dataflow pipeline that reads from Pub/Sub, enriches data with a side input from BigQuery, and writes to BigQuery. After updating the pipeline code (adding a new field to the output), the engineer notices that the new pipeline version is not picking up the updated code because the job was started from a template. The engineer wants to update the streaming pipeline without draining it. What should the engineer do?

A.Use the gcloud dataflow jobs update command with the new Flex Template.
B.Stop the pipeline, update the template, and restart with the same job name.
C.Modify the original template and redeploy it as a new job with the same pipeline name.
D.Use the gcloud dataflow jobs drain command, then restart with the new template.
AnswerA

Dataflow supports updating a running streaming job from a Flex Template by specifying --update and the job ID. This allows code changes without draining.

Why this answer

The `gcloud dataflow jobs update` command allows you to update a running streaming Dataflow pipeline with a new Flex Template without draining or stopping the job. This command performs an in-place update, preserving the job's state and checkpointing, so the pipeline continues processing with the new code. Since the original job was started from a template, using this command with the new Flex Template ensures the updated code is picked up seamlessly.

Exam trap

A common misconception is that you must drain or stop a streaming Dataflow pipeline to update it, but the `gcloud dataflow jobs update` command is specifically designed for in-place updates of streaming jobs started from templates.

How to eliminate wrong answers

Option B is wrong because stopping the pipeline and restarting with the same job name would cause data loss or duplication due to the loss of checkpointing state, and it violates the requirement to update without draining. Option C is wrong because modifying the original template and redeploying as a new job with the same pipeline name does not update the running job; it creates a separate job, and Dataflow does not allow two jobs with the same name to run concurrently. Option D is wrong because draining the job (using `gcloud dataflow jobs drain`) gracefully stops the pipeline, which contradicts the requirement to update without draining; after draining, you would need to restart, which is not an in-place update.

32
MCQmedium

You need to perform a one-time migration of historical data from an on-premises Teradata data warehouse to BigQuery. The data volume is 50 TB and you have a high-speed network connection (10 Gbps). What is the most efficient way to load the data?

A.Export data from Teradata to CSV files, upload to GCS using gsutil, then load into BigQuery.
B.Use Dataproc to run a Spark job that reads from Teradata and writes to BigQuery.
C.Use Transfer Appliance to ship the data offline.
D.Use BigQuery Data Transfer Service for Teradata
AnswerD

This service automates the transfer from Teradata to BigQuery, handling schema and data types.

Why this answer

BigQuery Data Transfer Service for Teradata is designed for this purpose; it can directly connect to Teradata and transfer data to BigQuery. Exporting to CSV then loading via gsutil is possible but less efficient. Transfer Appliance is for offline transfer but you have high-speed network.

Dataproc is not needed.

33
Multi-Selectmedium

An organization is using BigQuery for analytics. They have a table that is 500 GB and is frequently queried by 'date' and 'region'. They want to optimize query performance and reduce costs. Which TWO actions should they take?

Select 2 answers
A.Use an authorized view
B.Use a wildcard table
C.Use materialized views
D.Cluster the table by region
E.Partition the table by date
AnswersD, E

Clustering by region within each partition improves query performance for region filters.

Why this answer

Partitioning by date enables partition pruning to scan only relevant partitions. Clustering by region further reduces data scanned within partitions.

34
MCQmedium

A company uses Workflows to orchestrate a series of Google Cloud services for data processing. They need to call an external HTTP API as part of the workflow and handle potential failures with retries. Which Workflows feature should they use?

A.Retry policy on the step
B.Subworkflows
C.Parallel steps
D.Conditional steps
AnswerA

Retry policy allows specifying retry conditions and limits for a step.

Why this answer

Workflows provides a built-in retry policy that can be configured on individual steps to automatically retry an HTTP call upon transient failures (e.g., 5xx server errors or network timeouts). This allows the workflow to handle external API failures without custom code, using exponential backoff and a maximum retry count.

Exam trap

Google Cloud Workflows often tests the distinction between workflow orchestration features (retry, subworkflows, parallel, conditional) and candidates mistakenly choose parallel steps or subworkflows thinking they inherently provide fault tolerance, but only a retry policy directly addresses automatic retries on failure.

How to eliminate wrong answers

Option B is wrong because subworkflows are used to encapsulate reusable sequences of steps, not to handle retries on a single HTTP call. Option C is wrong because parallel steps execute multiple branches concurrently, which does not provide retry logic for a single failing step. Option D is wrong because conditional steps (e.g., switch/if-else) control the flow based on conditions but do not automatically retry a failed HTTP request.

35
Multi-Selectmedium

Your organization is designing a data lake on Google Cloud using Cloud Storage. You need to choose a file format for storing raw data that supports schema evolution, is splittable for parallel processing, and is optimized for query performance in BigQuery. Which TWO formats meet these requirements? (Choose 2.)

Select 2 answers
A.Avro
B.CSV
C.Parquet
D.JSON (newline-delimited)
E.ORC
AnswersA, C

Avro supports schema evolution, is splittable, and BigQuery can read Avro files efficiently.

Why this answer

Both Avro and Parquet support schema evolution (through schemas) and are splittable. Parquet is columnar and highly optimized for BigQuery performance. Avro is row-oriented but also splittable and supports schema evolution.

CSV and JSON do not natively support schema evolution and are less performant for BigQuery. ORC is not natively supported by BigQuery.

36
MCQhard

A data science team is operationalizing a batch prediction job using Vertex AI Batch Prediction. The model uses a custom container that requires a specific GPU for inference. The job processes a large dataset stored in Cloud Storage. The team wants to minimize cost while ensuring the job completes within a 2-hour window. Which configuration should they choose?

A.Use a custom training job with a GPU worker pool and run the inference as a custom job.
B.Use a custom machine type with a GPU accelerator in the batch prediction request.
C.Use a high-memory machine type (e.g., n1-highmem-32) without GPU to reduce cost.
D.Configure a Vertex AI endpoint with GPU and submit batch requests to the endpoint.
AnswerA

This approach allows GPU usage and is cost-effective for batch processing within a time window.

Why this answer

Vertex AI Batch Prediction does not support custom containers with GPU accelerators; it only supports CPUs for batch prediction jobs. To run GPU-accelerated inference on a large dataset, the team must use a custom training job (which supports GPU worker pools) and run inference as a custom job. This approach allows them to leverage GPU hardware for the 2-hour window while minimizing cost by using preemptible VMs or choosing the smallest GPU instance that meets throughput requirements.

Exam trap

Google Cloud often tests the misconception that Vertex AI Batch Prediction supports GPU accelerators because it is a managed service, but in reality, GPU support is only available for online prediction endpoints and custom training jobs, not for batch prediction.

How to eliminate wrong answers

Option B is wrong because Vertex AI Batch Prediction does not allow attaching GPU accelerators to custom machine types; the batch prediction service only supports CPU-based machine types. Option C is wrong because a high-memory CPU-only machine type would likely be too slow for GPU-required inference, causing the job to exceed the 2-hour window or require many more instances, increasing cost. Option D is wrong because configuring an endpoint with GPU and submitting batch requests would incur ongoing endpoint deployment costs (even when idle) and is designed for online prediction, not cost-efficient batch processing; it also introduces unnecessary latency and scaling complexity.

37
MCQhard

Your team has a Dataflow pipeline that reads from BigQuery, transforms data, and writes to GCS. The pipeline is failing with 'Out of Memory' errors on the worker nodes. The input data is large but fits within the total cluster memory. Which configuration change is most likely to resolve the issue without increasing costs significantly?

A.Use a worker machine type with more memory, such as n2-highmem.
B.Shard the input into smaller reads using a BigQuery query.
C.Increase the disk size per worker.
D.Enable Dataflow Prime with vertical autoscaling.
AnswerA

High-memory machines provide more memory per core, addressing OOM.

Why this answer

The default Dataflow worker machine type may have insufficient memory per core for the pipeline's operations. Using a high-memory machine type (e.g., n2-highmem) increases memory per worker without necessarily increasing the number of workers, thus controlling costs.

38
MCQhard

You are running a Dataproc cluster for batch processing. The job is not latency-sensitive and you want to minimize cost. You notice that the cluster is underutilized during the job. Which configuration change would reduce costs most effectively?

A.Resize the cluster to use larger machines
B.Switch to single-node cluster
C.Use preemptible workers for the worker nodes
D.Enable autoscaling
AnswerC

Preemptible workers significantly reduce costs and are ideal for batch jobs that can tolerate interruptions.

Why this answer

Using preemptible workers in Dataproc reduces cost by about 60-80% compared to standard VMs. They are suitable for fault-tolerant batch jobs because they can be terminated at any time.

39
MCQhard

A team is implementing CI/CD for their ML models using Google Cloud. They want to automatically retrain and deploy a new model version when new training data arrives in Cloud Storage. Which combination of services should they use?

A.Cloud Storage triggers, Cloud Functions, and Vertex AI Pipelines
B.Cloud Scheduler and Vertex AI Training
C.Cloud Pub/Sub and Cloud Composer
D.Cloud Storage notifications and Cloud Build
AnswerA

Event-driven pipeline with managed ML services.

Why this answer

Cloud Storage triggers fire an event when new data arrives, which invokes a Cloud Function that can start a Vertex AI Pipeline for retraining and deploying the model. This combination provides a fully managed, event-driven CI/CD pipeline for ML models without manual intervention.

Exam trap

Google Cloud often tests the distinction between event-driven triggers (Cloud Storage triggers) and time-based scheduling (Cloud Scheduler), leading candidates to choose B or D when they overlook the need for automatic retraining upon data arrival.

How to eliminate wrong answers

Option B is wrong because Cloud Scheduler is for time-based scheduling, not event-driven triggers from Cloud Storage, so it cannot automatically retrain when new data arrives. Option C is wrong because Cloud Pub/Sub and Cloud Composer (Apache Airflow) are more suited for complex workflow orchestration with multiple dependencies, not a simple event-driven retraining trigger from Cloud Storage. Option D is wrong because Cloud Build is designed for building and testing application code, not for orchestrating ML training pipelines with Vertex AI, and it lacks native integration for model deployment.

40
MCQmedium

Refer to the exhibit. What is the most likely cause of the error?

A.The model artifact was not uploaded to Cloud Storage
B.The endpoint does not exist
C.The service account lacks permissions
D.The model ID is invalid
AnswerA

The error explicitly states the artifact URI is missing.

Why this answer

The error occurs because the model artifact must be uploaded to Cloud Storage before it can be deployed to an endpoint. Vertex AI requires the model to be stored in a Cloud Storage bucket, and the deployment process references that artifact. Without the artifact in Cloud Storage, the endpoint creation or model deployment fails with an error indicating the resource is missing.

Exam trap

Google Cloud often tests the distinction between resource existence errors (like missing artifact) and permission or configuration errors, leading candidates to incorrectly choose permission issues when the actual problem is a missing prerequisite resource.

How to eliminate wrong answers

Option B is wrong because if the endpoint did not exist, the error would typically be a 404 Not Found or a message stating the endpoint resource is not found, not a generic error about missing artifact. Option C is wrong because a lack of permissions would result in a 403 Forbidden error or an IAM-related message, not an error about a missing model artifact. Option D is wrong because an invalid model ID would produce an error like 'Model not found' or 'Invalid model ID', not an error indicating the artifact is missing from Cloud Storage.

41
MCQmedium

A company uses Looker Studio to build dashboards from BigQuery data. They notice that queries take several seconds to return. They want to improve performance without changing the schema or adding materialized views. Which option should they use?

A.Enable BigQuery BI Engine on the relevant project.
B.Move the data to Cloud SQL.
C.Switch to BigQuery Omni for cross-cloud queries.
D.Use APPROX_COUNT_DISTINCT to speed up distinct counts.
AnswerA

BI Engine provides in-memory analysis for Looker Studio, reducing query latency.

Why this answer

BI Engine accelerates sub-second query response times in Looker Studio by caching data in memory within the BigQuery region.

42
MCQmedium

You are designing a data quality pipeline that must inspect PII in BigQuery tables and de-identify sensitive columns before sharing with analysts. Which GCP service should you use?

A.Dataplex
B.Cloud Data Catalog
C.Cloud DLP
D.Dataflow
AnswerC

Cloud DLP inspects and de-identifies sensitive data in BigQuery, Cloud Storage, and other sources.

Why this answer

Cloud DLP (Data Loss Prevention) is the correct choice because it is purpose-built for inspecting, classifying, and de-identifying sensitive data such as PII. It integrates natively with BigQuery via inspection jobs and de-identification templates, allowing you to scan tables for over 150 built-in infoTypes (e.g., email, SSN) and apply transformations like masking, tokenization, or encryption before sharing data with analysts.

Exam trap

The trap here is that candidates often confuse Dataplex's data governance features (like policy tags and metadata) with actual de-identification, but Dataplex cannot transform data—it only applies access controls, whereas Cloud DLP performs the actual masking or tokenization of sensitive values.

How to eliminate wrong answers

Option A is wrong because Dataplex is a data fabric service for managing, governing, and cataloging data across lakes and warehouses, but it does not perform de-identification or PII inspection itself; it can integrate with Cloud DLP for such tasks but is not the primary tool. Option B is wrong because Cloud Data Catalog is a metadata management service for discovering and tagging assets, but it lacks native de-identification capabilities and cannot transform sensitive data. Option D is wrong because Dataflow is a stream/batch processing service that can be used to build custom de-identification pipelines, but it requires manual implementation of DLP logic and is not the out-of-the-box service for inspecting and de-identifying PII in BigQuery tables.

43
MCQmedium

A company uses Cloud Dataproc to run nightly Spark ETL jobs that process about 500 GB of data each night. The jobs currently take 4 hours to complete. The company wants to reduce the runtime to under 2 hours to meet a new SLA. The cluster is configured with 10 worker nodes (n1-standard-4) and 1 master node (n1-standard-4). The jobs are CPU-bound and use only default settings. The cluster is deleted after each job and recreated. The data is stored in Cloud Storage. The company is open to increasing cost but wants the most cost-effective solution to meet the SLA. Which approach should they take?

A.Use a regional Cloud Storage bucket to improve read throughput.
B.Replace worker nodes with n1-highmem-16 instances to increase memory.
C.Increase the number of worker nodes to 20 and use preemptible VMs for half of them.
D.Change machine type to n2-standard-8 for all nodes.
AnswerC

Doubles processing power cost-effectively.

Why this answer

Adding more worker nodes (from 10 to 20) directly increases parallelism for CPU-bound Spark jobs, and using preemptible VMs for half of them reduces cost while still meeting the SLA. Since the job is CPU-bound and uses default settings, scaling horizontally with a mix of standard and preemptible VMs is the most cost-effective way to halve runtime, as Spark can efficiently distribute the workload across more cores.

Exam trap

The trap here is that candidates may assume CPU-bound jobs require faster CPUs (Option D) or more memory (Option B), but horizontal scaling with preemptible VMs is the most cost-effective way to increase parallelism in Cloud Dataproc.

How to eliminate wrong answers

Option A is wrong because using a regional Cloud Storage bucket improves data durability and availability but does not significantly increase read throughput for a single job; the bottleneck is CPU, not I/O. Option B is wrong because the job is CPU-bound, not memory-bound; increasing memory with n1-highmem-16 instances does not address the CPU bottleneck and adds unnecessary cost. Option D is wrong because changing to n2-standard-8 (8 vCPUs per node) doubles vCPUs per node but only increases total vCPUs from 40 to 80, which may not halve runtime, and is less cost-effective than using 20 n1-standard-4 nodes (80 vCPUs) with preemptible VMs for half.

44
MCQeasy

You need to schedule a simple workflow that fetches data from an API every hour, transforms it using Cloud Functions, and writes the result to Cloud Storage. The workflow has no complex branching or retry logic beyond basic retries. Which orchestration service is the MOST cost-effective and simplest to implement?

A.Cloud Scheduler
B.Workflows
C.Cloud Composer
D.Dataflow
AnswerB

Workflows is serverless, cost-effective (pay per execution), and sufficient for simple linear workflows with basic retries.

Why this answer

Workflows is serverless, pay-per-execution, and defined in YAML/JSON. It integrates natively with Cloud Functions and Cloud Storage. Cloud Composer is overkill for simple linear workflows and incurs cluster costs.

Cloud Scheduler alone cannot orchestrate multiple steps. Dataflow is for data processing, not orchestration.

45
MCQeasy

A data science team has trained a TensorFlow model for image classification and wants to deploy it to production with minimal latency. They have already exported the model as a SavedModel directory. Which service should they use to create an online prediction endpoint?

A.Cloud Functions
B.Vertex AI Endpoints
C.AI Platform Prediction (legacy)
D.Cloud Dataflow
AnswerB

Vertex AI Endpoints provide scalable, low-latency online prediction serving.

Why this answer

Vertex AI Endpoints is the correct service for deploying a TensorFlow SavedModel to an online prediction endpoint with minimal latency. It provides managed, autoscaling infrastructure optimized for real-time inference, including GPU/TPU support, request batching, and automatic health checking, which are essential for production deployment.

Exam trap

The trap here is that candidates may confuse Vertex AI Endpoints with AI Platform Prediction (legacy) or think Cloud Functions can serve models, but the Google Professional Data Engineer exam tests that Vertex AI is the modern, fully managed service for online prediction with minimal latency, while the others are either deprecated or designed for different workloads.

How to eliminate wrong answers

Option A is wrong because Cloud Functions is a serverless compute service for event-driven, short-lived functions, not designed for hosting persistent ML models with low-latency prediction endpoints; it lacks built-in model serving, batching, and autoscaling for inference workloads. Option C is wrong because AI Platform Prediction (legacy) is the older, deprecated service that has been replaced by Vertex AI; while it could serve models, it is no longer the recommended or supported path for new deployments, and Vertex AI offers superior latency optimization and integration. Option D is wrong because Cloud Dataflow is a batch and stream data processing service based on Apache Beam, intended for ETL and data pipelines, not for hosting online prediction endpoints; it cannot serve real-time inference requests with sub-second latency.

46
Multi-Selecteasy

A company uses Cloud Datastream to replicate data from a MySQL database to BigQuery in near real-time. Which TWO BigQuery features are automatically used by Datastream for optimal performance and consistency? (Choose TWO.)

Select 2 answers
A.BigQuery Data Transfer Service
B.BigQuery legacy streaming inserts
C.A Dataflow pipeline to transform the data
D.BigQuery Storage Write API
E.A materialized view that merges the change stream into the final table
AnswersD, E

Datastream uses the Storage Write API for streaming replication.

Why this answer

Datastream uses the BigQuery Storage Write API (option D) to stream change data capture (CDC) events into BigQuery with exactly-once semantics and high throughput. It also automatically creates a materialized view (option E) that merges the change stream into the final table, ensuring consistent, near real-time replication without manual merge logic.

Exam trap

Google often tests the misconception that Datastream requires an intermediate Dataflow pipeline or legacy streaming inserts, when in fact it natively leverages the Storage Write API and materialized views for optimal performance and consistency.

47
MCQmedium

A company runs Apache Spark jobs on Dataproc. They want to reduce costs by using preemptible instances for worker nodes. The jobs are fault-tolerant and can handle occasional node loss. However, the cluster must remain available for interactive querying during business hours. Which Dataproc cluster configuration meets these requirements?

A.Use a single-node cluster that automatically scales with preemptible instances
B.Use a standard cluster with preemptible instances as secondary workers
C.Use standard cluster with master and worker nodes as preemptible instances
D.Use a high-availability cluster with preemptible instances for primary workers
AnswerB

Secondary workers (preemptible workers) are ideal for fault-tolerant batch jobs. They do not store HDFS data, so losing them does not affect data durability. The cluster remains available because primary workers and master nodes are regular instances.

Why this answer

Dataproc clusters support multiple node types. Primary workers run the NodeManager and DataNode daemons; using preemptible instances for them is risky because they are critical for HDFS and YARN. However, secondary workers (preemptible workers) are designed for stateless processing and can be lost without affecting cluster availability.

Preemptible instances cannot be used for master nodes.

48
Multi-Selectmedium

An e-commerce company uses BigQuery to analyze customer behavior. They need to compute the number of distinct customers per day, approximate quantiles of purchase amounts, and assign a row number per customer partition by date. Which BigQuery SQL functions should they use? (Choose THREE)

Select 3 answers
A.APPROX_COUNT_DISTINCT(customer_id)
B.NTILE(4) OVER (ORDER BY purchase_amount)
C.APPROX_QUANTILES(purchase_amount, 100)
D.ROW_NUMBER() OVER (PARTITION BY customer_id ORDER BY date)
E.COUNT(DISTINCT customer_id)
AnswersA, C, D

Approximate distinct count scales better.

Why this answer

APPROX_COUNT_DISTINCT for approximate distinct counts, APPROX_QUANTILES for approximate quantiles, ROW_NUMBER for row numbering within partitions.

49
MCQmedium

A team wants to ingest streaming data from millions of IoT devices and store historical data in BigQuery for analysis. They need near real-time analytics on the most recent data, with sub-second latency. Which architecture should they use?

A.Use Pub/Sub to receive data, then stream directly into BigQuery using the streaming API, and use standard SQL queries for real-time analytics.
B.Use Pub/Sub, then a Dataflow pipeline that filters and transforms data, writing to Cloud Bigtable for real-time queries and to Cloud Storage for periodic BigQuery loads.
C.Use Pub/Sub to ingest data into a Dataproc Spark Streaming job that writes to both Bigtable and BigQuery.
D.Use Cloud SQL to store the latest data and periodically move historical data to BigQuery via cron jobs.
AnswerB

Bigtable provides sub-millisecond latency for real-time queries, and BigQuery handles large-scale analytics.

Why this answer

It uses Cloud Bigtable for sub-second latency on recent data, which is ideal for near real-time analytics on streaming IoT data. Dataflow provides the necessary stream processing, filtering, and transformation before writing to Bigtable for low-latency queries and to Cloud Storage for periodic batch loads into BigQuery for historical analysis. This architecture decouples real-time and historical paths, meeting both latency and storage requirements.

Exam trap

Google Cloud often tests the misconception that BigQuery's streaming API can provide sub-second query latency, but in reality, BigQuery is a columnar analytics engine optimized for large scans, not for low-latency point reads, which is why a separate low-latency store like Bigtable is required for real-time access.

How to eliminate wrong answers

Option A is wrong because streaming directly into BigQuery via the streaming API does not guarantee sub-second latency for queries; BigQuery is optimized for analytical queries on large datasets, not for real-time point lookups or low-latency access to the most recent data. Option C is wrong because Dataproc Spark Streaming adds unnecessary operational overhead and latency compared to a managed service like Dataflow, and writing directly to both Bigtable and BigQuery from Spark can cause contention and complexity without the built-in exactly-once semantics and auto-scaling of Dataflow. Option D is wrong because Cloud SQL is not designed for high-throughput streaming ingestion from millions of devices and cannot handle the scale; also, periodic cron jobs to move data to BigQuery introduce latency that violates the sub-second requirement for near real-time analytics.

50
MCQhard

You need to set up a BigQuery reservation that provides a baseline of 500 slots for daily workloads and can automatically scale up to 1000 slots during peak times. You want to pay only for the slots used beyond the baseline. Which reservation configuration should you choose?

A.Create a reservation with 500 committed slots and another with 500 flex slots.
B.Use on-demand pricing with a maximum query cost limit.
C.Purchase 1000 committed use slots to ensure consistent capacity.
D.Create a reservation with 500 baseline slots and enable autoscaling up to 1000 slots.
AnswerD

This configuration provides baseline committed slots and on-demand autoscaling.

Why this answer

BigQuery reservations support baseline slots with autoscaling, which allows you to set a committed baseline of 500 slots and automatically scale up to 1000 slots during peak demand. You are billed only for the additional slots used beyond the baseline, which matches the requirement of paying only for slots used beyond the baseline.

Exam trap

Candidates often confuse committed use slots (always billed) with autoscaling (pay only for additional slots used beyond baseline) for variable workloads, leading them to incorrectly select flex slots or committed slots.

How to eliminate wrong answers

Option A is wrong because creating two separate reservations (500 committed + 500 flex) does not provide automatic scaling; flex slots are pre-purchased capacity, not on-demand, so you would pay for the full 500 flex slots regardless of usage. Option B is wrong because on-demand pricing does not use slots or reservations; it charges per byte processed and has no concept of baseline or autoscaling, and a maximum query cost limit only caps spending, not capacity. Option C is wrong because purchasing 1000 committed slots forces you to pay for all 1000 slots at all times, even when only 500 are needed, which does not meet the requirement of paying only for slots used beyond the baseline.

51
Multi-Selecteasy

A team is deploying a TensorFlow model for online predictions on AI Platform Prediction. They want to monitor for data drift and model performance degradation. Which TWO Google Cloud services should they use?

Select 2 answers
A.Cloud Composer
B.AI Platform Continuous Evaluation
C.Cloud Monitoring
D.AI Platform Pipelines
E.Cloud Logging
AnswersB, C

Provides automated drift detection and model evaluation.

Why this answer

AI Platform Continuous Evaluation (option B) is correct because it is a managed service specifically designed to detect data drift and model performance degradation in deployed models. It automatically compares incoming prediction data against the training data distribution and monitors metrics like accuracy over time, triggering alerts when significant drift is detected. Cloud Monitoring (option C) is correct because it provides the underlying metrics and alerting infrastructure that can track model performance indicators (e.g., prediction latency, error rates) and integrate with Continuous Evaluation for comprehensive observability.

Exam trap

Google Cloud often tests the distinction between services that orchestrate pipelines (Composer, Pipelines) versus services that monitor and evaluate deployed models (Continuous Evaluation, Monitoring), leading candidates to mistakenly choose orchestration tools for monitoring tasks.

52
Matchingmedium

Match each data pipeline term to its definition.

Drag a concept onto its matching description — or click a concept then click the description.

Concepts
Matches

Extract, Transform, Load

Extract, Load, Transform

Raw data storage in native format

Optimized storage for structured analytics

Why these pairings

Common data pipeline concepts: Data Pipeline moves data; ETL transforms before loading; ELT loads then transforms; Data Warehouse stores structured processed data; Data Lake stores raw data. Distractors swap definitions between ETL/ELT and Data Warehouse/Data Lake.

53
Multi-Selectmedium

A team is debugging a sudden increase in prediction latency for a model deployed on Vertex AI Endpoints. Which TWO metrics in Cloud Monitoring should they examine first? (Choose two.)

Select 2 answers
A.CPU utilization
B.Memory utilization
C.gRPC port errors
D.Number of predictions
E.Prediction request latency
AnswersA, B

High CPU utilization can cause processing delays.

Why this answer

CPU utilization (A) is correct because a sudden increase in prediction latency often stems from the model consuming excessive CPU cycles during inference, especially for compute-intensive models like deep neural networks. Monitoring CPU utilization helps identify whether the endpoint's compute resources are saturated, causing requests to queue and latency to spike. Memory utilization (B) is correct because insufficient memory can lead to swapping or garbage collection pauses, directly increasing latency.

Vertex AI Endpoints autoscales based on these metrics, so examining them first pinpoints resource bottlenecks.

Exam trap

Google Cloud often tests the distinction between symptom metrics (like prediction request latency) and root-cause metrics (like CPU/memory utilization), trapping candidates who select the symptom as a diagnostic metric instead of the underlying resource indicators.

54
MCQeasy

A team wants to retrain a model weekly using new data stored in BigQuery. They want to minimize manual effort. Which approach should they use?

A.Use Cloud Scheduler to trigger a Cloud Function that retrains
B.Retrain manually in a notebook each week
C.Use Cloud Composer to orchestrate retraining
D.Create a Vertex AI Pipeline scheduled via Cloud Scheduler
AnswerD

Pipelines automate retraining end-to-end.

Why this answer

Vertex AI Pipelines allow you to define a repeatable, automated ML workflow that can be triggered on a schedule via Cloud Scheduler. This minimizes manual effort by handling data extraction from BigQuery, model retraining, and deployment without human intervention, while also providing versioning and monitoring capabilities.

Exam trap

Google Cloud often tests the distinction between simple scheduling (Cloud Scheduler + Cloud Function) and full ML orchestration (Vertex AI Pipelines), where candidates mistakenly choose the simpler option without considering the need for a managed, scalable ML workflow.

How to eliminate wrong answers

Option A is wrong because Cloud Scheduler triggering a Cloud Function is suitable for lightweight tasks, but retraining a model typically requires more complex orchestration, dependency management, and resource handling that a Cloud Function alone cannot efficiently provide. Option B is wrong because manual retraining in a notebook each week introduces significant manual effort and is error-prone, directly contradicting the goal of minimizing manual effort. Option C is wrong because Cloud Composer (based on Apache Airflow) is a powerful orchestration tool but is overkill for a simple weekly retraining schedule; it adds unnecessary complexity and cost compared to a Vertex AI Pipeline scheduled via Cloud Scheduler.

55
MCQmedium

A company has a Cloud Functions function that triggers on new files in Cloud Storage and writes a message to Pub/Sub for downstream processing. Recently, the function has been timing out after 60 seconds. The downstream processing is critical. What is the best solution?

A.Replace Cloud Functions with a Cloud Run job that has longer timeout
B.Increase the function memory to 2 GB to speed up execution
C.Reduce the function timeout to 30 seconds to force faster execution
D.Increase function timeout to 540 seconds and delegate heavy processing to Cloud Dataflow
AnswerD

This addresses both timeout and heavy processing.'

Why this answer

Cloud Functions has a maximum timeout of 540 seconds (9 minutes) for HTTP-triggered functions, and by increasing the timeout you allow the function to complete its work. Delegating heavy processing to Cloud Dataflow offloads the computationally intensive tasks, preventing future timeouts and ensuring scalable, reliable downstream processing for critical workloads.

Exam trap

Google Cloud often tests the misconception that increasing memory or reducing timeout directly solves performance issues, but the real solution is to extend the timeout and delegate heavy processing to a scalable service like Dataflow.

How to eliminate wrong answers

Option A is wrong because Cloud Run jobs are designed for batch workloads that run to completion, not for event-driven triggers like Cloud Storage; replacing Cloud Functions with a Cloud Run job would require a different invocation pattern and does not directly solve the timeout issue. Option B is wrong because increasing memory may improve performance for memory-bound tasks but does not guarantee faster execution for I/O-bound or CPU-bound operations, and the function still has a 60-second timeout limit. Option C is wrong because reducing the timeout to 30 seconds would force the function to fail even faster, making the timeout problem worse and potentially losing critical messages.

56
MCQhard

Refer to the exhibit. A data engineer sees these metrics from Cloud Monitoring for a deployed Vertex AI Endpoint. What is the most effective action to reduce latency?

A.Switch to batch prediction
B.Increase the number of replicas
C.Reduce the machine type
D.Enable model quantization
AnswerB

Adding replicas scales horizontally, reducing load per replica and improving latency.

Why this answer

The metrics show high CPU utilization and increasing latency, indicating the current instance is overloaded. Increasing the number of replicas distributes the inference requests across multiple instances, reducing per-replica load and lowering response times. This is the most direct way to scale horizontally and address latency caused by resource saturation.

Exam trap

Google Cloud often tests the misconception that model optimization (quantization) or switching to batch mode is the primary fix for latency, when the metrics clearly point to a scaling bottleneck.

How to eliminate wrong answers

Option A is wrong because batch prediction is designed for asynchronous, large-scale processing and does not reduce real-time endpoint latency; it actually increases latency for individual requests. Option C is wrong because reducing the machine type would decrease compute capacity, worsening CPU saturation and increasing latency further. Option D is wrong because model quantization reduces model size and inference time per request but does not address the root cause of high concurrent load; it may help marginally but is less effective than scaling out replicas.

57
Multi-Selectmedium

Which THREE steps are required to set up a continuous training pipeline on Google Cloud using Vertex AI?

Select 3 answers
A.Run training on a single Compute Engine VM with a cron job.
B.Create a Vertex AI Pipeline to orchestrate data preprocessing, training, and model evaluation.
C.Set up a trigger (e.g., Cloud Scheduler or Cloud Build) to start training on a schedule or new data.
D.Manually upload the model to Vertex AI Model Registry after each training run.
E.Configure model evaluation and promotion rules (e.g., if accuracy > threshold, deploy to endpoint).
AnswersB, C, E

Pipeline orchestrates the steps.

Why this answer

Vertex AI Pipelines provide a managed, repeatable, and scalable way to orchestrate the entire ML workflow, including data preprocessing, training, and model evaluation. This is essential for a continuous training pipeline, as it automates the sequence of steps and ensures consistency across runs.

Exam trap

Google Cloud often tests the distinction between manual, ad-hoc automation (like cron jobs) and fully managed, integrated orchestration services (like Vertex AI Pipelines), leading candidates to incorrectly select simpler but non-scalable options.

58
Multi-Selecthard

Which TWO are common causes of prediction bias in a deployed machine learning model in production?

Select 2 answers
A.Model accuracy is too high.
B.Data drift between training and serving data distributions.
C.Model is overfitted to training data.
D.Low latency predictions.
E.Training-serving skew due to differences in feature engineering.
AnswersB, E

Changes in the real-world data distribution can cause the model to produce biased results.

Why this answer

Data drift refers to changes in the statistical properties of the input features between the training and serving environments. When the distribution of real-world data shifts (e.g., seasonal trends, user behavior changes), the model's predictions become biased even if the model itself hasn't changed. This is a primary cause of prediction bias in production ML systems.

Exam trap

Google Cloud often tests the distinction between training-time issues (like overfitting) and production-time causes (like data drift and training-serving skew), so candidates mistakenly select overfitting as a production bias cause.

59
MCQmedium

An organization wants to integrate BigQuery Omni to query data stored in AWS S3. They have set up the necessary connections. What is the primary benefit of using BigQuery Omni over simply copying the data to BigQuery?

A.Ability to use BigQuery ML models on data in S3 without moving data.
B.Automatic encryption of data at rest in S3.
C.Lower latency queries due to in-memory caching.
D.Support for real-time streaming inserts into S3.
AnswerA

BigQuery Omni supports BigQuery ML, allowing you to train and run models on cross-cloud data.

Why this answer

BigQuery Omni allows you to query data across clouds without moving it, providing a unified analytics experience. It reduces data egress costs and avoids duplication.

60
Multi-Selectmedium

A company uses Pub/Sub to ingest events from multiple sources. They need to ensure that messages from a specific source are processed in order (per source partition). They also need to deduplicate messages. Which TWO features should they use?

Select 2 answers
A.Set a message schema to enforce ordering
B.Use a dead letter topic to handle out-of-order messages
C.Enable exactly-once delivery on the subscription
D.Use a pull subscription with a large ack deadline
E.Enable message ordering by setting an ordering key
AnswersC, E

Exactly-once delivery ensures that each message is delivered only once, providing deduplication.

Why this answer

Pub/Sub ordering keys ensure messages with the same ordering key are delivered in order. Message deduplication is achieved via exactly-once delivery (Pub/Sub now supports this). Dead letter topics are for undeliverable messages.

Schemas enforce structure, not ordering.

61
Multi-Selectmedium

A company has a data lake on Cloud Storage with raw data in the 'raw' bucket, curated data in 'curated', and processed data in 'processed'. They want to implement lifecycle management to reduce costs. Which TWO actions should they take? (Choose 2)

Select 2 answers
A.Set a lifecycle rule to change storage class from Standard to Nearline after 30 days for the 'raw' bucket.
B.Enable object versioning on all buckets to automatically delete older versions.
C.Set a partition expiration on BigQuery tables that reference data in the 'processed' bucket.
D.Set a lifecycle rule to delete objects older than 365 days in the 'curated' and 'processed' buckets.
E.Set a lifecycle rule to change storage class from Standard to Archive after 30 days for the 'raw' bucket.
AnswersA, D

Nearline has a 30-day minimum storage duration, ideal for data accessed less than once a month.

Why this answer

Setting a lifecycle rule to change storage class from Standard to Nearline after 30 days for the 'raw' bucket reduces costs while maintaining quick access to frequently needed raw data. For 'curated' and 'processed' buckets, deleting objects older than 365 days is appropriate because these datasets are typically intermediate or final and can be removed after a retention period. Option B (object versioning) does not automatically delete older versions; it preserves them.

Option C (partition expiration on BigQuery) applies to BigQuery tables, not Cloud Storage objects. Option E (changing to Archive after 30 days) is less cost-effective than Nearline for raw data that may still be accessed occasionally.

Exam trap

Candidates may confuse BigQuery table expiration with Cloud Storage lifecycle rules, or assume that Archive storage is always cheaper than Nearline without considering access needs.

62
MCQhard

A real-time recommendation system uses a custom container deployed on AI Platform Prediction. The model requires a large in-memory embedding lookup table that is loaded from Cloud Storage at startup. The current startup time is over 5 minutes, causing prediction requests to timeout. Which strategy would most effectively reduce startup time?

A.Increase the machine type to one with more memory and CPU.
B.Preload the embedding table into a persistent disk and attach it to the container.
C.Reduce the size of the embedding table by using a smaller embedding dimension or fewer categories.
D.Use a faster storage class for the Cloud Storage bucket, such as Standard instead of Nearline.
AnswerC

Smaller table loads faster, directly addressing startup time.

Why this answer

The root cause of the startup timeout is the time required to load the large embedding table from Cloud Storage into memory. Reducing the embedding dimension or the number of categories directly shrinks the data size, which proportionally reduces the load time and avoids the 5-minute startup bottleneck. This is a model architecture change that addresses the fundamental performance constraint without relying on infrastructure workarounds.

Exam trap

Google often tests the misconception that scaling up infrastructure (more memory, faster disks) is the best fix for data-loading bottlenecks, when the real solution is to reduce the data size at the model level.

How to eliminate wrong answers

Option A is wrong because increasing machine memory and CPU does not reduce the amount of data that must be transferred from Cloud Storage; it only provides more resources once the data is loaded, so the startup time remains dominated by network transfer and disk I/O. Option B is wrong because preloading the embedding table into a persistent disk still requires the container to read that disk at startup, and the disk attach operation itself adds latency; moreover, the data must still be loaded into memory from the disk, so the total startup time is not effectively reduced. Option D is wrong because Cloud Storage storage class (Standard vs.

Nearline) affects retrieval cost and availability, not the latency of a single large read; the bottleneck is the size of the data and the network bandwidth, not the storage tier.

63
MCQhard

Refer to the exhibit. The feature store 'my_fs' responds to offline queries but online serving requests fail. What is the most likely cause?

A.Create a new feature store with online serving enabled
B.Use Cloud Bigtable directly
C.Update the existing feature store to enable online serving
D.Re-import features into a new store
AnswerC

Online serving can be enabled by setting appropriate scaling configuration.

Why this answer

The feature store 'my_fs' responds to offline queries but not online serving requests, which indicates that online serving is not enabled for the feature store. In Vertex AI Feature Store, online serving requires a dedicated endpoint and underlying infrastructure (e.g., Bigtable) to serve low-latency requests. Updating the existing feature store to enable online serving (option C) is the correct fix, as it activates the necessary serving resources without recreating the store.

Exam trap

Google Cloud often tests the misconception that a feature store's offline and online serving are automatically coupled, leading candidates to think a new store or data re-import is required when online serving fails, rather than recognizing that online serving is an optional configuration that must be explicitly enabled on the existing store.

How to eliminate wrong answers

Option A is wrong because creating a new feature store with online serving enabled is unnecessary and wasteful; the existing store can be updated to enable online serving without data re-import. Option B is wrong because using Cloud Bigtable directly bypasses the feature store's managed serving layer, losing integration with Vertex AI's serving APIs, monitoring, and consistency guarantees. Option D is wrong because re-importing features into a new store does not address the root cause—the existing store simply needs its online serving configuration enabled, not a full data migration.

64
MCQmedium

Refer to the exhibit. A Dataflow streaming pipeline subscribes to this Pub/Sub subscription. The pipeline occasionally takes more than 10 seconds to process a message. Which behavior will occur?

A.The message will be sent to the dead letter topic immediately.
B.The message will be retried with exponential backoff as per retry policy.
C.The message will be redelivered after 10 seconds if not acknowledged.
D.The message will be dropped after 10 seconds due to expiration policy.
AnswerC

The ack deadline is 10 seconds; if processing exceeds that, Pub/Sub redelivers the message.

Why this answer

Pub/Sub delivery requires an acknowledgment within the configurable `ackDeadlineSeconds` (default 10 seconds). If the pipeline takes longer than the ack deadline to process a message, Pub/Sub considers the message unacknowledged and redelivers it. This is the standard behavior for at-least-once delivery in Google Cloud Pub/Sub.

Exam trap

Google Cloud often tests the distinction between ack deadline expiration and dead letter topics, trapping candidates who assume any processing delay immediately triggers a dead letter or that Pub/Sub uses exponential backoff like some other messaging systems.

How to eliminate wrong answers

Option A is wrong because a dead letter topic is only triggered after a message has been retried the maximum number of times (configurable via `maxDeliveryAttempts`), not immediately upon exceeding the ack deadline. Option B is wrong because Pub/Sub does not use exponential backoff for redelivery; it uses a fixed or configurable `ackDeadlineSeconds` and redelivers after that deadline expires, with no built-in exponential backoff retry policy. Option D is wrong because the expiration policy (`messageRetentionDuration`) controls how long unacknowledged messages are retained in the subscription, not a 10-second drop; messages are retained for up to 7 days by default.

65
MCQeasy

A company wants to version its ML models and track lineage from training data to deployed model. Which Google Cloud service should they use?

A.Cloud Storage with object versioning
B.Data Catalog
C.Artifact Registry
D.Vertex AI ML Metadata
AnswerD

ML Metadata tracks artifacts, lineage, and metadata for ML models.

Why this answer

(Vertex AI ML Metadata) is correct because it provides a managed service for tracking model lineage, artifacts, and metadata across the ML lifecycle. Option A (Cloud Storage with object versioning) only stores model files but does not track lineage or relationships. Option B (Data Catalog) is for discovering and managing metadata for data assets, not ML models.

Option C (Artifact Registry) is designed for storing container images and build artifacts, not ML model metadata or lineage.

66
Multi-Selecthard

A company is migrating on-premises Hadoop Hive workloads to Google Cloud. They want to use Dataproc for Spark processing and require a managed Hive metastore that can be shared across multiple Dataproc clusters. Which TWO components should they use?

Select 1 answer
A.Cloud Bigtable
B.Dataproc on GKE
C.Dataproc Metastore
D.Dataproc Serverless
E.Cloud SQL for MySQL
AnswersC

Dataproc Metastore is a managed Hive metastore that can be shared across clusters.

Why this answer

The question specifies a managed Hive metastore that can be shared across multiple Dataproc clusters. Dataproc Metastore is a fully managed service that provides a Hive metastore, requiring no manual setup. Cloud SQL for MySQL can serve as a metastore backend, but it is not a managed service—it requires manual configuration, maintenance, and is not a dedicated metastore service.

Therefore, only Dataproc Metastore meets the criteria of a managed Hive metastore.

67
MCQmedium

A company uses Cloud Spanner and needs to store a parent-child relationship where the child table is frequently queried together with the parent. The parent has millions of rows and the child billions. Which Spanner feature optimizes performance for this pattern?

A.Partitioned tables
B.Interleaved tables
C.Secondary indexes
D.Change streams
AnswerB

Interleaved tables store child rows physically with the parent row, optimizing joins.

Why this answer

Interleaved tables in Cloud Spanner co-locate parent and child rows on the same split, reducing cross-node communication when joining. Secondary indexes are for lookups, not co-location. Partitioning is not a Spanner concept.

68
MCQeasy

Which BigQuery SQL function returns the rank of a row within a window, with gaps in the ranking for ties?

A.RANK()
B.NTILE()
C.DENSE_RANK()
D.ROW_NUMBER()
AnswerA

RANK() handles ties with gaps.

Why this answer

RANK() assigns the same rank to ties and leaves gaps (e.g., 1,1,3). ROW_NUMBER() assigns unique consecutive numbers. DENSE_RANK() does not leave gaps.

69
MCQeasy

Which Dataflow feature automatically scales the number of workers based on the pipeline's current workload, and also selects the optimal machine type for each worker based on the pipeline's resource requirements?

A.Dataflow Shuffle
B.Dataflow Prime
C.Dataflow Streaming Engine
D.Dataflow Flex Templates
AnswerB

Dataflow Prime offers vertical autoscaling and right-fitting of worker machine types.

Why this answer

Dataflow Prime is the correct answer because it is the only Dataflow feature that provides both automatic worker scaling (horizontal autoscaling) and intelligent machine type selection (vertical autoscaling). It dynamically adjusts the number of workers based on the pipeline's current workload and selects the optimal machine type (e.g., CPU, memory, or accelerator-optimized) for each worker based on the pipeline's resource requirements, such as CPU utilization, memory pressure, or shuffle throughput.

Exam trap

Google often tests the distinction between horizontal autoscaling (adding/removing workers) and vertical autoscaling (changing machine type), and the trap here is that candidates assume Dataflow Shuffle or Streaming Engine handle scaling, when in fact they only optimize specific pipeline phases (shuffle or state management) without affecting worker count or machine type.

How to eliminate wrong answers

Option A is wrong because Dataflow Shuffle is a service that separates the shuffle operation from worker VMs, improving scalability and reliability, but it does not handle worker scaling or machine type selection. Option C is wrong because Dataflow Streaming Engine moves state storage and computation away from worker VMs for streaming pipelines, reducing resource overhead, but it does not automatically scale workers or select machine types. Option D is wrong because Dataflow Flex Templates allow you to package and reuse pipeline code with custom container images, but they do not provide any autoscaling or machine type optimization; scaling is handled separately by the Dataflow service.

70
MCQmedium

Your Dataflow streaming job is experiencing high system lag. You want to identify the root cause. Which Cloud Monitoring metrics should you examine first? (Choose the best option.)

A.Data freshness and worker CPU utilization
B.System lag and worker CPU utilization
C.Element count and data freshness
D.Backlog bytes and system lag
AnswerB

High system lag combined with high CPU suggests workers are bottlenecked; low CPU may indicate other issues.

Why this answer

For streaming Dataflow jobs, system lag measures the maximum time between the event timestamp and when it is processed. High system lag typically indicates that the pipeline cannot keep up with the input rate. Worker CPU utilization is a key metric to check if workers are overloaded.

Data freshness is for batch pipelines. Element count alone doesn't show lag. Backlog bytes could be useful but worker CPU is more directly indicative of processing capacity issues.

71
MCQeasy

Refer to the exhibit. What is the most likely cause?

A.The model container does not support this prediction route
B.The request format is incorrect
C.The model was built for batch prediction only
D.The endpoint ID is wrong
AnswerA

The error indicates the prediction method is not supported by the model, likely due to container configuration.

Why this answer

The error indicates that the model container does not have a route configured to handle the specific prediction request. In Vertex AI or similar MLOps platforms, each model container must expose a prediction endpoint (e.g., /predict or /v1/models/{model}:predict) via a route defined in the serving configuration. If the container only supports batch prediction (e.g., via a custom gRPC service) or lacks the required HTTP route, the request will fail with this error.

Exam trap

Google often tests the misconception that a 'batch-only model' error is about the model type, when in fact the root cause is a missing or misconfigured prediction route in the container.

How to eliminate wrong answers

Option B is wrong because an incorrect request format would typically produce a 400 Bad Request or a schema validation error, not a message about the container not supporting the prediction route. Option C is wrong because even if the model was built for batch prediction, the container can still support online prediction if the correct route is exposed; the error specifically points to a missing route, not a batch-only limitation. Option D is wrong because a wrong endpoint ID would result in a 404 Not Found or an authentication error, not a container-level route support issue.

72
MCQeasy

A data pipeline ingests streaming data from Pub/Sub into BigQuery via Dataflow. Recently, the pipeline has been failing with 'deadline exceeded' errors. What is the most likely cause?

A.The BigQuery streaming quota is exceeded.
B.Dataflow workers are underutilized due to batch size settings.
C.Dataflow autoscaling is disabled.
D.The Pub/Sub subscription's acknowledgement deadline is too short for the processing time.
AnswerD

A short acknowledgment deadline causes messages to be redelivered, leading to repeated processing attempts and eventual deadline exceeded errors.

Why this answer

'deadline exceeded' errors in a Dataflow pipeline reading from Pub/Sub indicate that the subscriber is taking longer to process messages than the acknowledgement deadline allows. When the deadline expires, Pub/Sub redelivers the message, causing duplicate processing and eventual pipeline failure. This is a common issue when processing time exceeds the default 10-second acknowledgement deadline.

Exam trap

Google Cloud often tests the distinction between resource quota errors (like BigQuery streaming quota) and Pub/Sub-specific timeout errors, trapping candidates who confuse 'deadline exceeded' with general quota exhaustion.

How to eliminate wrong answers

Option A is wrong because BigQuery streaming quota exceeded would produce 'quota exceeded' or 'rate limit exceeded' errors, not 'deadline exceeded' errors. Option B is wrong because underutilized workers due to batch size settings would cause poor performance or backpressure, not 'deadline exceeded' errors; the error is about processing time vs. acknowledgement deadline, not worker utilization. Option C is wrong because disabled autoscaling would lead to resource exhaustion or latency, but the specific 'deadline exceeded' error is tied to Pub/Sub's acknowledgement mechanism, not Dataflow's scaling behavior.

73
MCQhard

Your team is processing a large dataset with Apache Beam on Dataflow. The pipeline sometimes fails due to transient errors when writing to a BigQuery sink. You need to ensure that failed records are not lost and can be reprocessed later without blocking the pipeline. What is the best approach?

A.Configure the pipeline to use at-least-once semantics and rely on Dataflow to retry the entire bundle.
B.Increase the number of workers to reduce the chance of transient errors.
C.Use a try-catch block in the DoFn and log the error; continue processing other elements.
D.Use a side output (e.g., via TupleTag) to write failed records to a dead letter sink (e.g., GCS or Pub/Sub) and continue processing the main output.
AnswerD

This pattern isolates bad records, allows the pipeline to continue, and stores the failed records for later reprocessing.

Why this answer

Using a dead letter pattern with a side output to write failed records to a GCS bucket (or Pub/Sub) allows the pipeline to continue processing healthy records while failed records are stored for later analysis and reprocessing.

74
MCQmedium

A retail company is using a machine learning model for inventory forecasting. They observe that the model's predictions become less accurate over time, especially during holiday seasons. Which monitoring metric should they prioritize?

A.Model latency
B.Prediction counts
C.Resource utilization
D.Prediction drift (feature drift)
AnswerD

Monitoring feature drift helps detect when training data distribution shifts, leading to accuracy loss.

Why this answer

Prediction drift (feature drift) is the correct metric because it directly measures changes in the input data distribution over time, which is the root cause of degrading model accuracy during holiday seasons. When customer behavior shifts (e.g., buying patterns during holidays), the features the model relies on drift, causing predictions to become less accurate. Monitoring prediction drift allows the team to detect when retraining or updating the model is necessary.

Exam trap

Google Cloud often tests the misconception that model latency or resource utilization are the primary concerns for accuracy degradation, when in fact drift monitoring is the key metric for detecting data shifts that cause performance decay.

How to eliminate wrong answers

Option A is wrong because model latency measures the time taken for a single prediction, which is unrelated to accuracy degradation over time. Option B is wrong because prediction counts track the volume of predictions made, not the quality or drift of those predictions. Option C is wrong because resource utilization (CPU, memory, etc.) monitors infrastructure health, not model performance or data distribution shifts.

75
MCQhard

A Dataflow pipeline with multiple steps uses a side input from a slowly changing reference table stored in BigQuery. The side input is updated every hour. To avoid reprocessing the entire pipeline on each update, which approach should you use?

A.Use a side input with a custom 'AsIterable' and a 'Repeatable' trigger that refreshes the side input every hour
B.Use a side input with a periodic refresh via a DoFn that reads BigQuery on each element
C.Use the side input with a default trigger and 'withAllowedLateness'
D.Use a global window with a trigger that fires every hour
AnswerA

This pattern reads the side input periodically (e.g., using a global window with a trigger) and uses AsIterable for efficient lookup.

Why this answer

The side input should be read periodically using a side input pattern with a Repeatable trigger. This refreshes the side input without restarting the pipeline.

Page 1 of 12

Page 2