Courseiva

Google Professional Data Engineer (PDE) — Questions 826–890

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

Take a mock examExam hub
Page 11

Page 12 of 12

826
MCQhard

A company needs to process sensitive healthcare data with strict compliance requirements. They want to use Cloud Dataflow but must ensure data is encrypted end-to-end and audit logs are retained. Which combination of features should they enable?

A.Use Customer-Managed Encryption Keys (CMEK) and VPC Service Controls.
B.Use Data Loss Prevention API to redact sensitive data.
C.Enable Cloud Audit Logs and VPC Service Controls.
D.Enable default encryption at rest and in transit.
AnswerA

Provides control and exfiltration prevention.

Why this answer

Customer-Managed Encryption Keys (CMEK) allow the company to control the encryption keys used to protect data at rest in Cloud Dataflow, while VPC Service Controls provide a security perimeter that prevents data exfiltration and ensures end-to-end encryption boundaries. Together, they address the compliance requirement for encryption control and audit logging by restricting data movement within a VPC service perimeter and using customer-managed keys for data encryption.

Exam trap

The trap here is that candidates often assume default encryption (Option D) or audit logs alone (Option C) satisfy compliance requirements, but they overlook the need for customer-managed keys and network-level exfiltration controls that VPC Service Controls provide.

How to eliminate wrong answers

Option B is wrong because the Data Loss Prevention (DLP) API is used for inspecting and redacting sensitive data (e.g., PII), not for ensuring end-to-end encryption or audit log retention; it does not provide encryption key management or network-level controls. Option C is wrong because while Cloud Audit Logs capture API activity and VPC Service Controls provide a security perimeter, this combination lacks customer-managed encryption keys (CMEK), which are required for the 'encrypted end-to-end' and key control compliance mandate. Option D is wrong because default encryption at rest and in transit uses Google-managed keys, not customer-managed keys, and does not include VPC Service Controls to enforce data exfiltration prevention or audit log retention policies.

Full explanation →
827
MCQhard

A company is running a Dataflow streaming pipeline that reads from Pub/Sub and writes to BigQuery. They notice that the number of workers is not scaling up to handle increased throughput, causing latency spikes. The pipeline uses a GlobalWindow with default triggering. What is the most likely cause of the under-scaling?

A.The pipeline includes a GroupByKey that creates a hot key, limiting parallelism
B.The Pub/Sub subscription has a large backlog, but Dataflow automatically scales to handle it
C.The pipeline uses the default worker machine type, which is too small
D.The pipeline is using legacy streaming inserts instead of the Storage Write API
AnswerA

Hot keys prevent splitting the work across workers, causing underutilization and scaling issues.

Why this answer

Dataflow's autoscaling is based on CPU utilization and throughput. If the pipeline uses a GroupByKey with hot keys, parallelism is limited and workers may not scale effectively.

Full explanation →
828
MCQmedium

Refer to the exhibit. What is the cause of this error?

A.The machine type flag is only used during model deployment, not endpoint creation
B.The endpoint name already exists
C.The user must specify a model name
D.The region is missing
AnswerA

Correct: machine type is a property of the deployed model, not the endpoint.

Why this answer

The error occurs because the `machine_type` flag is only valid during model deployment (when creating a deployment in Vertex AI), not during endpoint creation. When creating an endpoint, you specify the endpoint name and region, but the machine type is configured later when deploying a model to that endpoint. Attempting to set `machine_type` during endpoint creation causes a validation error because the API does not accept that parameter at that stage.

Exam trap

Google Cloud tests the distinction between endpoint creation and model deployment parameters in Vertex AI. Candidates often mistakenly assume that machine type can be set during endpoint creation, but it is only valid when deploying a model to the endpoint.

How to eliminate wrong answers

Option B is wrong because if the endpoint name already exists, the error would be a 409 Conflict or 'Already exists' message, not a validation error about an invalid parameter. Option C is wrong because a model name is not required when creating an endpoint; the endpoint is a container that can host multiple models, and models are specified during deployment. Option D is wrong because the region is a required parameter for endpoint creation, and if it were missing, the error would indicate a missing required field, not an invalid parameter like `machine_type`.

Full explanation →
829
MCQmedium

A company deploys a model to Vertex AI Endpoint. They want to run a canary deployment to test a new model version with 10% of traffic. How should they configure this?

A.Deploy to a new endpoint and update the application to call both
B.Use Cloud Load Balancing to route traffic
C.Deploy the new model to the same endpoint and set traffic split
D.Deploy to Cloud Run and use gradual rollout
AnswerC

Traffic splitting allows canary.

Why this answer

Vertex AI Endpoints natively support traffic splitting between model versions deployed to the same endpoint. By deploying the new model version to the same endpoint and setting a traffic split of 10% to the new version and 90% to the current version, the company can perform a canary deployment without changing the application code or infrastructure.

Exam trap

Google Cloud often tests the misconception that canary deployments require separate endpoints or external load balancers, when in fact Vertex AI Endpoints provide a built-in traffic splitting feature that handles this at the model version level.

How to eliminate wrong answers

Option A is wrong because deploying to a new endpoint and updating the application to call both endpoints adds unnecessary complexity and defeats the purpose of a canary deployment, which should be transparent to the application. Option B is wrong because Cloud Load Balancing operates at the network layer and cannot route traffic based on model version within a single Vertex AI Endpoint; it is designed for distributing traffic across regional endpoints or backends, not for model version canary testing. Option D is wrong because deploying to Cloud Run and using gradual rollout is not the native way to manage model versions in Vertex AI; Vertex AI Endpoints provide built-in traffic splitting for model versions, which is the recommended approach for canary deployments in this context.

Full explanation →
830
MCQeasy

Which BigQuery feature allows you to share query results with specific users without giving them direct access to the underlying tables?

A.IAM roles
B.Authorized views
C.Dataset access controls
D.Materialized views
AnswerB

Authorized views allow sharing query results securely.

Why this answer

Authorized views allow sharing results without granting access to the base tables.

Full explanation →
831
Multi-Selecthard

A company stores data in a Cloud Storage bucket with versioning enabled. They want to automatically delete objects that are noncurrent (i.e., previous versions) after 30 days, and also delete the current version if it is older than 365 days. Which three Object Lifecycle Management conditions can be used together? (Choose three.)

Select 3 answers
A.lastAccessTime: 30
B.age: 365
C.numNewerVersions: 1
D.daysSinceCustomTime: 30
E.noncurrentTimeBefore: 30
AnswersB, C, E

Deletes current version when older than 365 days.

Why this answer

The `age` condition in Object Lifecycle Management specifies the number of days since object creation, and setting it to 365 will delete the current version when it is older than 365 days. This directly meets the requirement to delete current versions older than a year.

Exam trap

Google Cloud Storage lifecycle conditions are distinct from AWS S3 lifecycle conditions. Candidates mistakenly select `lastAccessTime` (an S3-only feature) or confuse `daysSinceCustomTime` with `noncurrentTimeBefore`.

Full explanation →
832
MCQhard

You are building a machine learning pipeline for credit risk assessment. The dataset has a severe class imbalance (1% default rate). You want to use AutoML Tables on Vertex AI. Which strategy should you incorporate to handle imbalance?

A.Downsample the majority class to a 50-50 ratio
B.Apply SMOTE in a Dataflow pipeline before training
C.Upsample the minority class using BigQuery SQL
D.Use the `class_weight` parameter in the AutoML Tables model
AnswerD

AutoML Tables supports adjusting class weights to handle imbalance.

Why this answer

AutoML Tables automatically applies class imbalance handling (e.g., class weighting) by default. You can adjust the weight strategy. SMOTE is not directly supported in AutoML Tables; you would need custom training.

Downsampling and upsampling are manual steps not needed.

Full explanation →
833
MCQeasy

A data engineer wants to automatically detect when the distribution of input features to a production model has shifted significantly. Which Vertex AI feature should they enable?

A.Vertex AI Vizier
B.Vertex AI Model Monitoring
C.Vertex AI Explainable AI
D.Vertex AI Feature Store
AnswerB

Monitors prediction and feature drift/skew.

Why this answer

Vertex AI Model Monitoring is the correct service because it is specifically designed to continuously detect feature distribution drift and prediction skew in production models. It automatically compares the current input feature distribution against a baseline (e.g., training data) and triggers alerts when significant statistical shifts occur, enabling proactive retraining or investigation.

Exam trap

The trap here is that candidates confuse 'monitoring model performance' (e.g., accuracy, latency) with 'monitoring input feature distribution drift', leading them to incorrectly choose Vertex AI Vizier or Explainable AI, which address different aspects of model lifecycle management.

How to eliminate wrong answers

Option A is wrong because Vertex AI Vizier is a hyperparameter tuning service that optimizes model performance through black-box optimization, not for monitoring distribution shifts in production. Option C is wrong because Vertex AI Explainable AI provides feature attributions and explanations for individual predictions, but it does not monitor aggregate distribution changes over time. Option D is wrong because Vertex AI Feature Store is a centralized repository for storing, serving, and sharing feature data, but it lacks built-in drift detection or alerting capabilities.

Full explanation →
834
Multi-Selectmedium

A data engineer needs to perform a one-time migration of 10 TB of data from on-premises Hadoop HDFS to Cloud Storage. The network link is 1 Gbps. Which TWO services or tools should they consider? (Choose 2)

Select 2 answers
A.Dataproc with DistCp
B.Cloud Storage Transfer Service
C.BigQuery Data Transfer Service
D.gsutil rsync with parallel composite uploads
E.Transfer Appliance
AnswersA, E

Dataproc with DistCp is a standard method to copy data from HDFS to Cloud Storage, using Hadoop's distributed copy tool for efficient parallel transfer.

Why this answer

For a one-time migration of 10 TB from on-premises HDFS to Cloud Storage over a 1 Gbps link, the most appropriate services are Dataproc with DistCp and Transfer Appliance. Dataproc with DistCp is a proven method for copying data from HDFS to Cloud Storage, leveraging Apache Hadoop's distributed copy tool. Transfer Appliance is ideal for large data volumes when network bandwidth is limited, as it physically ships the data.

Cloud Storage Transfer Service does not support HDFS as a source directly, so it is not suitable. gsutil rsync with parallel composite uploads could be used but would be slower and less efficient for this volume.

Full explanation →
835
MCQhard

You manage a team that deploys multiple versions of a computer vision model for A/B testing on Vertex AI Endpoints. You need to route a small percentage of traffic to a canary version while the rest goes to the stable version. You also need to gradually increase the canary traffic over time based on performance metrics. Which approach should you take?

A.Create two separate endpoints, one for each version, and use a separate load balancer to route a percentage of requests to the canary endpoint.
B.Deploy both models to the same endpoint and configure traffic splitting percentages using the Vertex AI console or API.
C.Use Cloud Armor with weighted backend services to route a portion of requests to the canary version.
D.Implement feature flags in the application code to randomly select the model version for each prediction request.
AnswerB

Vertex AI endpoints natively support traffic splitting between deployed models, allowing gradual rollout and canary testing.

Why this answer

Vertex AI Endpoints natively support traffic splitting between model versions deployed to the same endpoint. This allows you to assign a percentage of traffic (e.g., 5%) to a canary version and the remainder to the stable version, and then adjust the split over time via the console or API as performance metrics dictate. This approach avoids the complexity and latency of external load balancers or application-level routing.

Exam trap

Google often tests the misconception that you need an external load balancer or separate endpoints for canary deployments, when in fact Vertex AI's native traffic splitting is the correct and simplest approach.

How to eliminate wrong answers

Option A is wrong because creating two separate endpoints with an external load balancer adds unnecessary infrastructure complexity, latency, and cost; Vertex AI already provides built-in traffic splitting within a single endpoint. Option C is wrong because Cloud Armor is a web application firewall and DDoS protection service, not a traffic routing mechanism for model versions; it cannot perform weighted backend routing for Vertex AI endpoints. Option D is wrong because implementing feature flags in application code for model selection bypasses Vertex AI's managed traffic splitting, introduces custom logic that must be maintained, and does not leverage the platform's native canary deployment capabilities.

Full explanation →
836
MCQmedium

A company has a Dataflow pipeline that reads from Pub/Sub, applies transformations, and writes to BigQuery. The pipeline is failing with 'deadline exceeded' errors during peak hours. The team suspects that the pipeline cannot keep up with the incoming data rate. They also notice that the autoscaling algorithm sets maxNumWorkers to 10, but the pipeline only scales to 5 workers. What is the most likely cause of the inadequate scaling?

A.The maxNumWorkers setting is too low and should be reduced to trigger more aggressive scaling
B.BigQuery streaming quota is limiting the number of concurrent writes
C.The Pub/Sub subscription has a per-subscriber throughput limit of 5 workers
D.The pipeline is CPU-bound and the autoscaler evaluates that adding more workers would not improve throughput
AnswerD

Autoscaler uses utilization metrics; if workers are already saturated, it may not add more.

Why this answer

The autoscaler in Dataflow evaluates CPU utilization and throughput per worker. If the pipeline is CPU-bound, adding more workers does not reduce per-worker CPU load or improve throughput, so the autoscaler stops at 5 workers even though maxNumWorkers is 10. This is a classic symptom of a bottleneck that cannot be parallelized further, such as a single-threaded transformation or a hot key in a GroupByKey operation.

Exam trap

The trap here is that candidates assume autoscaling always scales to maxNumWorkers when there is a backlog, but the autoscaler only adds workers if they will actually improve throughput, and a CPU-bound pipeline is a common reason for scaling to stall.

How to eliminate wrong answers

Option A is wrong because reducing maxNumWorkers would further restrict scaling, not trigger more aggressive scaling; the autoscaler already has permission to scale to 10 but chooses not to. Option B is wrong because BigQuery streaming quota limits the rate of inserts, not the number of concurrent workers; quota exhaustion would cause insert errors, not prevent the autoscaler from adding workers. Option C is wrong because Pub/Sub subscriptions have a per-subscriber throughput limit that is very high (typically hundreds of MB/s per subscriber), and the pipeline is not hitting that limit; the limit is on throughput, not on the number of subscribers.

Full explanation →
837
MCQhard

A BigQuery table has a REQUIRED column 'user_id' that now needs to accept NULL values due to upstream data changes. You want to alter the schema with minimal downtime and no data loss. What should you do?

A.Run `ALTER TABLE dataset.table ALTER COLUMN user_id DROP NOT NULL;`
B.Use the bq command: `bq update --set_nullable_fields user_id dataset.table`
C.Create a view that casts user_id to NULLABLE and use the view instead.
D.Drop the table and recreate it with the column as NULLABLE.
AnswerA

This BigQuery DDL statement changes the column to nullable without downtime or data loss.

Why this answer

BigQuery allows changing a column from REQUIRED to NULLABLE using the ALTER TABLE ALTER COLUMN SET DATA TYPE statement. This operation is a metadata change and does not require table recreation or data copy. Dropping and recreating the table would cause downtime and data loss.

Using a view is a workaround but doesn't change the underlying schema. Exporting and reloading is disruptive.

Full explanation →
838
Multi-Selecthard

A company uses Workflows to orchestrate a multi-step data pipeline. One step calls an HTTP endpoint that may take up to 10 minutes, but the default Workflows timeout is too short. They also need to handle transient errors with retries. Which TWO configurations should they apply? (Choose 2)

Select 2 answers
A.Set a step timeout of 600 seconds for the HTTP call step
B.Configure a dead letter queue for failed steps
C.Use the default retry policy on the step
D.Set the workflow execution timeout to 600 seconds
E.Add a retry policy on the step with appropriate conditions for transient errors
AnswersA, E

This extends the timeout for that specific step to 10 minutes.

Why this answer

To extend the timeout, set a step timeout of 600 seconds (10 minutes). To handle transient errors, use a retry policy with appropriate conditions. Setting the entire workflow timeout to 10 minutes is not necessary if individual step timeouts are set.

The default retry policy does not cover all transient errors. Adding a dead letter queue is for event-driven patterns, not Workflows.

Full explanation →
839
MCQeasy

A team has trained a scikit-learn model and wants to deploy it to AI Platform Prediction for online predictions. What is the required format for the model artifact?

A.A model.joblib file (or model.pkl) along with any custom code.
B.A single .h5 file containing the model weights.
C.A SavedModel directory containing the model for TensorFlow.
D.A model.pt file for PyTorch models.
AnswerA

AI Platform supports joblib/pickle for scikit-learn.

Why this answer

AI Platform Prediction (now Vertex AI) supports scikit-learn models natively. The required artifact format is a serialized model file (model.joblib or model.pkl) optionally accompanied by any custom code dependencies. This is because scikit-learn models are pickled objects, and the platform deserializes them using the same Python environment specified in the runtime version.

Exam trap

Candidates often mistakenly believe that a single universal model file format (e.g., .h5 or SavedModel) works for all frameworks on Vertex AI, but each framework has its own required format. For scikit-learn, it must be a .joblib or .pkl file.

How to eliminate wrong answers

Option B is wrong because .h5 files are specific to Keras/TensorFlow models, not scikit-learn; AI Platform Prediction expects a SavedModel or a serialized pickle for scikit-learn. Option C is wrong because a SavedModel directory is the required format for TensorFlow models, not for scikit-learn models. Option D is wrong because model.pt files are PyTorch serialization format; AI Platform Prediction requires a SavedModel for PyTorch or a custom container, not a raw .pt file.

Full explanation →
840
Multi-Selecteasy

A company is designing a data processing pipeline for real-time sensor data. They want to ensure low latency and exactly-once processing semantics. Which two Google services should they combine to achieve this? (Choose 2)

Select 2 answers
A.Cloud Dataproc with Spark Streaming
B.Cloud Functions with Cloud Pub/Sub triggers
C.Cloud Pub/Sub with exactly-once delivery
D.Cloud Dataflow with exactly-once processing mode
E.Cloud IoT Core with device gateways
AnswersC, D

Pub/Sub can be configured for exactly-once delivery to subscribers.

Why this answer

Cloud Pub/Sub with exactly-once delivery (Option C) ensures that each message is delivered to subscribers exactly once, preventing duplicates in the pipeline. Cloud Dataflow with exactly-once processing mode (Option D) provides end-to-end exactly-once semantics by leveraging consistent snapshots and idempotent sinks, which is critical for real-time sensor data pipelines requiring low latency and accuracy.

Exam trap

Google Cloud often tests the misconception that Cloud Pub/Sub alone provides end-to-end exactly-once processing, but candidates must recognize that Pub/Sub only guarantees delivery exactly once to subscribers, while Dataflow is needed to ensure processing exactly once across transformations and sinks.

Full explanation →
841
MCQhard

A Dataflow streaming pipeline reads from Pub/Sub, processes events with a fixed window of 1 minute, and writes to BigQuery. Some events arrive late due to network issues. You need to ensure late events are still included in the correct window but the pipeline must not wait indefinitely. What configuration should you use?

A.Set allowed lateness to 5 minutes and use the default trigger
B.Use a sliding window of 1 minute with a 1-minute period
C.Use a global window with a trigger that fires every 10 seconds
D.Increase the watermark estimate to 10 minutes
AnswerA

This allows late events up to 5 minutes after the window end, and the default trigger fires at the end of the window plus allowed lateness.

Why this answer

Setting a watermark estimate and allowed lateness with a trigger controls how long the pipeline waits for late data. The default trigger fires at the end of the window, and with allowed lateness, late events are still processed until the allowed time expires.

Full explanation →
842
MCQmedium

A data engineer is designing a batch ETL pipeline using Cloud Composer and Dataflow. The pipeline must be self-healing and retry on failures. Which Composer feature should they configure?

A.Use Cloud Tasks for retries
B.Retry policy on the DAG
C.Cloud Composer with high availability
D.Dataflow retries
AnswerB

Composer DAGs can have retry policies for tasks.

Why this answer

Cloud Composer (based on Apache Airflow) allows you to configure a retry policy directly on the DAG or individual tasks. This enables the pipeline to automatically retry failed tasks according to parameters like `retries`, `retry_delay`, and `retry_exponential_backoff`, making the ETL pipeline self-healing without external services.

Exam trap

Google Cloud often tests the distinction between orchestration-level retries (Composer DAG) and execution-level retries (Dataflow), leading candidates to pick Dataflow retries (Option D) when the question explicitly asks for a Composer feature.

How to eliminate wrong answers

Option A is wrong because Cloud Tasks is a fully managed queue service for asynchronous task execution, not a feature of Cloud Composer; it would introduce unnecessary complexity and is not the native way to handle retries within a Composer DAG. Option C is wrong because high availability (HA) for Cloud Composer ensures the Airflow components are resilient to zone failures, but it does not configure task-level retry behavior for pipeline failures. Option D is wrong because Dataflow retries handle failures at the Dataflow job level (e.g., worker failures), but the question asks for a Composer feature to manage retries of the overall pipeline orchestration, not the underlying data processing job.

Full explanation →
843
Matchingmedium

Match each BigQuery feature to its description.

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

Concepts
Matches

Sorting data within partitions to improve query performance

Dividing tables into segments based on a date/timestamp column

Unit of computational capacity in BigQuery

Pre-computed query results for faster access

Why these pairings

BigQuery uses slots for compute, partitioning and clustering for storage optimization, and materialized views for query performance. Common confusions include mixing clustering with materialized views or partitioning with BI Engine.

Full explanation →
844
MCQeasy

A company uses Cloud Dataflow to process streaming data. They notice that the pipeline's throughput is lower than expected and the system is experiencing high latency. What is the most likely cause?

A.Using batch mode instead of streaming mode
B.Too many workers
C.Too few workers
D.Incorrect watermark setting
AnswerC

Insufficient workers cause backpressure and latency.

Why this answer

In Cloud Dataflow, streaming pipelines require sufficient worker resources to handle the incoming data rate and maintain low latency. When too few workers are provisioned, the pipeline cannot process data quickly enough, leading to increased backlog and higher latency. This is the most likely cause of reduced throughput and high latency in a streaming pipeline.

Exam trap

A common misconception is that adding more workers always improves performance, but the key insight here is that too few workers directly cause high latency and low throughput in a streaming pipeline. The trap is to overlook the importance of sufficient worker scaling.

How to eliminate wrong answers

Option A is wrong because batch mode is a separate execution mode for bounded data, and using batch mode instead of streaming mode would not cause high latency in a streaming pipeline—it would simply not process unbounded data correctly. Option B is wrong because too many workers would typically improve throughput and reduce latency, not cause high latency, unless there is excessive overhead from worker coordination, but that is less common than underprovisioning. Option D is wrong because an incorrect watermark setting affects event-time processing and windowing accuracy, but it does not directly cause lower throughput or high latency; it may cause late data handling issues or incorrect results.

Full explanation →
845
MCQeasy

A team deployed a model to Vertex AI Endpoint and notices latency spikes during peak hours. What should they first investigate?

A.Switch to batch prediction
B.Reduce number of features
C.Increase machine type
D.Check if autoscaling is enabled and configured correctly
AnswerD

Autoscaling misconfiguration is a common cause of latency spikes during traffic surges.

Why this answer

Latency spikes during peak hours typically indicate that the serving infrastructure is unable to handle the increased request volume. The first step is to check if autoscaling is enabled and configured correctly on the Vertex AI Endpoint, as this determines whether additional compute nodes are automatically provisioned to match demand. Without proper autoscaling, the endpoint will be overwhelmed, leading to queuing delays and latency spikes.

Exam trap

Google Cloud often tests the misconception that latency spikes are always due to model complexity or feature engineering, when in fact the first diagnostic step should always be to verify the serving infrastructure's scaling configuration.

How to eliminate wrong answers

Option A is wrong because switching to batch prediction is for asynchronous, non-real-time inference and does not address the root cause of latency spikes during online serving. Option B is wrong because reducing the number of features may lower model complexity but does not directly resolve infrastructure scaling issues; latency spikes are typically due to insufficient compute resources, not feature count. Option C is wrong because increasing the machine type (e.g., using a larger VM) may improve per-request performance but does not solve the problem of handling concurrent peak traffic; without autoscaling, a single larger machine can still be overwhelmed.

Full explanation →
846
MCQhard

A data team needs to share a BigQuery dataset with another business unit. They want to provide a point-in-time snapshot of the data without incurring additional storage costs for the copy. Which BigQuery feature should they use?

A.BigQuery table snapshots
B.BigQuery table clones
C.BigQuery authorized views
D.BigQuery export to Cloud Storage
AnswerB

Clones are writable and share storage with the base table, so no extra cost for the initial copy. They can be updated independently.

Why this answer

Clones use the same underlying storage as the source table; snapshots also share storage but are immutable. Both are cost-effective. For regular updates, clones are more flexible.

Full explanation →
847
Matchingmedium

Match each Google Cloud data service to its primary use case.

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

Concepts
Matches

Serverless data warehouse for analytics

Object storage for unstructured data

Globally distributed relational database

NoSQL wide-column database for low-latency workloads

Asynchronous messaging service for event-driven systems

Why these pairings

The correct matches are: Cloud SQL for standard relational databases, Cloud Spanner for globally distributed relational data with strong consistency, Bigtable for analytical NoSQL workloads, Firestore for mobile/web apps with real-time sync, and BigQuery for large-scale analytics. Common confusions include mixing up Cloud SQL and Cloud Spanner due to both being relational, or Bigtable and Firestore due to both being NoSQL.

Full explanation →
848
MCQmedium

You train a BigQuery ML linear regression model to predict house prices. The model has high bias during evaluation. Which action BEST reduces bias?

A.Decrease the learning rate in the training options
B.Add more features like number of bedrooms and square footage
C.Remove features that have low correlation with the label
D.Increase L2 regularization
AnswerB

Adding relevant features helps capture patterns, reducing bias.

Why this answer

High bias indicates underfitting, meaning the model is too simple. Adding more relevant features (option B) increases model complexity and reduces bias. Decreasing the learning rate (A) does not address model complexity; it only affects convergence speed.

Removing features with low correlation (C) further reduces complexity, increasing bias. Increasing L2 regularization (D) penalizes large coefficients, which increases bias.

Full explanation →
849
MCQmedium

Refer to the exhibit. A team uses this Cloud Build configuration to deploy a service to Cloud Run. The deployment step fails with a 'Permission denied' error. What is the most likely cause?

A.The Dockerfile is missing from the repository.
B.The Docker image tag is missing or malformed.
C.The region 'us-central1' is incorrect for Cloud Run.
D.The Cloud Build service account does not have the Cloud Run Admin role.
AnswerD

The deploy step requires IAM permissions to create/update Cloud Run services; typically the Cloud Build service account needs roles/run.admin.

Why this answer

The Cloud Build service account (typically the default compute engine service account or a user-specified service account) must have the Cloud Run Admin role (roles/run.admin) to deploy services to Cloud Run. Without this IAM permission, the deployment step fails with a 'Permission denied' error, even if the build itself succeeds. The error occurs because Cloud Build attempts to call the Cloud Run Admin API (run.googleapis.com) to create or update the service, and the service account lacks the required authorization.

Exam trap

Google often tests the distinction between build-time errors (e.g., missing Dockerfile, malformed tags) and deployment-time permission errors, expecting candidates to recognize that a 'Permission denied' error specifically points to IAM misconfiguration rather than build configuration issues.

How to eliminate wrong answers

Option A is wrong because a missing Dockerfile would cause a build failure (e.g., 'unable to prepare context: path not found'), not a deployment-time 'Permission denied' error. Option B is wrong because a missing or malformed image tag would cause a push or pull error (e.g., 'invalid reference format'), not a permission error during deployment. Option C is wrong because 'us-central1' is a valid Cloud Run region; an incorrect region would result in a 'region not found' or 'location not found' error, not a permission error.

Full explanation →
850
MCQhard

A healthcare analytics company runs a nightly Dataproc workflow that reads radiology reports from Cloud Storage (CSV files), transforms them using PySpark, and writes results to BigQuery. The workflow is orchestrated by Cloud Composer. Recently, the job has started failing with 'Disk quota exceeded' errors on the worker nodes. The data volume has grown 5x over the past month. Currently, the cluster uses 5 n1-standard-4 workers (each 10GB persistent disk). The PySpark jobs heavily use intermediate shuffles. You need a cost-effective solution that avoids future failures as data grows. What should you do?

A.Upgrade the worker machine type to n1-standard-8 with local SSDs for shuffle storage.
B.Increase the persistent disk size on each worker node to 100 GB.
C.Add more preemptible workers to the cluster and keep boot disk size at 10GB.
D.Use Cloud Dataflow instead of Dataproc, as it handles disk management transparently.
AnswerB

Increasing the persistent disk size directly addresses the disk quota issue for shuffle data. It is cost-effective and scales with data growth without changing the cluster configuration.

Why this answer

The 'Disk quota exceeded' error occurs because the 10 GB persistent disks on the n1-standard-4 workers are too small to accommodate the intermediate shuffle data, which has grown 5x. Increasing the persistent disk size to 100 GB directly addresses the storage bottleneck without changing the machine type or incurring the cost of local SSDs, making it a cost-effective solution that scales with data growth.

Exam trap

The trap here is that candidates may over-engineer the solution by upgrading machine types or switching to a different service (Dataflow) when the root cause is simply insufficient disk space for shuffle data, which is easily fixed by increasing the persistent disk size.

How to eliminate wrong answers

Option A is wrong because upgrading to n1-standard-8 with local SSDs is overkill and more expensive; the issue is disk space for shuffle data, not CPU or memory, and local SSDs are ephemeral and not cost-effective for persistent storage needs. Option C is wrong because adding more preemptible workers does not increase the persistent disk size per worker; each worker still has only 10 GB, so shuffle data will still exceed the disk quota on those nodes. Option D is wrong because migrating to Cloud Dataflow is a significant architectural change that incurs migration costs and learning curve, and it does not address the immediate disk quota issue in the existing Dataproc workflow; Dataflow also has its own disk management limits.

Full explanation →
851
Multi-Selectmedium

A company uses Cloud Composer to orchestrate data pipelines. They have a DAG that runs hourly and processes files from Cloud Storage. The DAG is triggered by a Pub/Sub message sent from a Cloud Storage bucket notification. Recently, some DAG runs are not starting even though the Pub/Sub messages are published. Which two likely causes should the team investigate? (Choose TWO.)

Select 2 answers
A.The Cloud Storage bucket notification is not sending messages to the correct Pub/Sub topic, or the subscription's ack deadline is too short.
B.The DAG's start_date is set in the past and catchup is set to False, so DAG runs are only triggered on schedule.
C.The total number of DAGs in the environment exceeds the maximum limit of 100, causing DAG processing to stop.
D.The DAG's schedule interval is set too frequently, causing the executor queue to be full and new runs are skipped.
E.The Cloud Composer environment is using a pull subscription instead of a push subscription for the Pub/Sub sensor.
AnswersA, D

Correct: Misconfiguration of the Cloud Storage bucket notification (wrong topic) or a subscription ack deadline that is too short can prevent the Pub/Sub sensor from receiving or processing the trigger message.

Why this answer

If the Cloud Storage bucket notification is misconfigured to send messages to the wrong Pub/Sub topic, the Pub/Sub sensor in the DAG will never receive the trigger message, causing DAG runs to not start. Additionally, if the subscription's ack deadline is too short, the message may be acknowledged before the sensor processes it, leading to message loss and missed triggers. Both issues directly prevent the DAG from being triggered by Pub/Sub messages.

Option D is correct because setting the DAG's schedule interval too frequently can overwhelm the executor queue. When the queue is full, new DAG runs are skipped or delayed, which can cause runs to not start even if the Pub/Sub trigger is received.

Exam trap

Google Cloud often tests the misconception that a push subscription is required for Pub/Sub sensors in Cloud Composer, when in fact the sensor uses a pull subscription and the ack deadline is the critical parameter to manage.

Full explanation →
852
MCQhard

A retail company uses BigQuery to store sales data and wants to forecast weekly demand for the next 8 weeks using historical data from the past 2 years. They need to account for seasonality and holidays. Which BigQuery ML model type and configuration is most appropriate?

A.ARIMA_PLUS with holiday_region parameter
B.Boosted tree classifier
C.Linear regression with engineered time features
D.Time-series DECOMPOSE model
AnswerA

ARIMA_PLUS is designed for time-series forecasting with automatic seasonality detection and holiday support.

Why this answer

BigQuery ML's ARIMA_PLUS model is designed for time-series forecasting, automatically detecting seasonality and handling holiday effects via the holiday_region parameter. Linear regression would require manual feature engineering for time components. Time-series DECOMPOSE is not a model type.

Boosted trees are not natively time-series aware without feature engineering.

Full explanation →
853
Drag & Dropmedium

Drag and drop the steps to set up a BigQuery dataset with a scheduled query 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

Setting up a BigQuery dataset with a scheduled query involves three logical steps in order: first create a dataset to store your data, then write the SQL query that transforms or loads the data, and finally configure the scheduled query to run at specified intervals. The dataset must exist before you can reference it in the query or schedule, and the query must be defined before you can schedule it. Reversing these steps leads to errors because each step depends on the previous one.

Full explanation →
854
MCQmedium

You need to create a Cloud Storage bucket for a data lake that will store raw ingested data. The data must be immutable and cannot be deleted or overwritten for a compliance period of 5 years. Which feature should you enable?

A.Object Versioning
B.Lifecycle rules to delete objects after 5 years
C.Object Lock with governance mode
D.Bucket Lock with a retention policy of 5 years
AnswerD

Correct: Bucket Lock enforces immutability for the specified period.

Why this answer

Bucket Lock with a retention policy enforces a minimum retention period on all objects in the bucket. During the retention period, objects cannot be deleted or overwritten. This is exactly for compliance needs.

Full explanation →
855
MCQmedium

A data team uses Looker Studio to create a report that combines data from two different BigQuery tables: one with sales transactions and another with customer demographics. They need to join these tables in the report without writing SQL. Which feature should they use?

A.Data blending
B.Creating a report with multiple charts
C.Custom query in BigQuery connector
D.Calculated fields
AnswerA

Data blending allows combining data from different sources via a common key without SQL.

Why this answer

Looker Studio's data blending feature allows combining data from multiple sources (including BigQuery tables) using a common key, without writing SQL. It provides a graphical interface to define joins. Creating a custom query requires SQL.

Looker Studio reports support multiple charts, but blending is the specific feature for joining data. Calculated fields transform data within a single source.

Full explanation →
856
MCQeasy

A company uses BigQuery for real-time analytics. They stream data from IoT devices into a BigQuery table. After a few hours, some of the recent data becomes visible in the table although it was streamed less than 10 minutes ago. The data team confirms that no one ran any manual queries. What is the most likely reason for the data visibility?

A.The data was stored in the streaming buffer for more than 24 hours, and BigQuery automatically flushes it to the table.
B.BigQuery time travel allows querying data from the past, including data still in the streaming buffer.
C.The table has an expiration set, and the data is made visible as soon as the table is about to expire.
D.The streaming buffer reached its maximum capacity (default 90 minutes) and automatically flushed the data to the table.
AnswerD

The streaming buffer has a maximum capacity (default 90 minutes) and when reached, BigQuery automatically flushes the data to the table, making it visible.

Why this answer

BigQuery's streaming buffer has a maximum capacity limit, typically around 90 minutes. When the buffer reaches this capacity, BigQuery automatically flushes the buffered data to the table, making it visible. This explains why data streamed less than 10 minutes ago became visible after a few hours.

Exam trap

The trap here is that candidates often assume streaming data is immediately visible or that time travel is responsible for visibility, but BigQuery's streaming buffer has a finite capacity that triggers automatic flushes, making data visible after a delay.

How to eliminate wrong answers

Option A is wrong because the streaming buffer does not have a 24-hour retention; data is flushed automatically within about 90 minutes or when the buffer reaches capacity, not after 24 hours. Option B is wrong because BigQuery time travel allows querying historical data within a 7-day window, but it does not cause data in the streaming buffer to become visible; it only affects how you query already-committed data. Option C is wrong because table expiration settings control when the table is deleted, not when streaming data becomes visible; data visibility is independent of table expiration.

Full explanation →
857
Multi-Selectmedium

A data engineer is planning a time-series forecasting model using BigQuery ML ARIMA+ on a dataset with daily sales data spanning 3 years. Which TWO actions are required to prepare the data for ARIMA+? (Choose 2.)

Select 2 answers
A.Create a partition on the time column to improve performance.
B.Remove any rows with NULL values in the time column.
C.Sort the data by the time column in ascending order.
D.Ensure the time column is of type DATE or TIMESTAMP.
E.Encode the target variable using one-hot encoding.
AnswersC, D

ARIMA+ expects the data to be ordered by time.

Why this answer

ARIMA+ requires a time column and a numeric target column. The time column must be in a date/timestamp format. Additionally, the data should be sorted by time.

Missing values should be handled (e.g., filled with 0 or interpolated) but that's not a requirement of the function itself.

Full explanation →
858
Multi-Selectmedium

Which TWO are best practices for monitoring a deployed machine learning model in production on Vertex AI?

Select 2 answers
A.Set up a weekly retraining pipeline triggered by calendar schedule
B.Enable Vertex AI Model Monitoring to track feature drift and skew
C.Monitor the training job duration to detect anomalies
D.Monitor the distribution of predictions over time to detect concept drift
E.Monitor the model's file size to ensure it hasn't changed
AnswersB, D

Model Monitoring automatically detects drift.

Why this answer

Vertex AI Model Monitoring automatically tracks feature drift and skew by comparing the serving data distribution against the training data distribution using statistical tests like the Kolmogorov-Smirnov test. This is a best practice for detecting data quality issues that can degrade model performance in production.

Exam trap

The trap here is that candidates confuse operational maintenance tasks (like scheduled retraining) with monitoring tasks, or they focus on infrastructure metrics (like job duration or file size) instead of data and prediction distribution monitoring, which directly impact model accuracy in production.

Full explanation →
859
MCQmedium

Your company stores sensitive customer data in Cloud Storage. You need to inspect the data for personally identifiable information (PII) and de-identify it before sharing with a third party. Which Google Cloud service should you use?

A.Security Command Center
B.Dataplex
C.Cloud Data Loss Prevention (DLP)
D.Cloud KMS
AnswerC

DLP is designed for inspecting and de-identifying sensitive data.

Why this answer

Cloud Data Loss Prevention (DLP) is the correct service because it is specifically designed to inspect, classify, and de-identify sensitive data such as PII in Cloud Storage. It provides built-in infoType detectors for over 150 types of PII and supports de-identification techniques like masking, tokenization, and encryption. This directly matches the requirement to inspect and de-identify data before sharing with a third party.

Exam trap

Candidates often confuse Cloud KMS (key management only) with Cloud DLP (inspection and de-identification), leading them to mistakenly choose Cloud KMS because they associate 'de-identify' with encryption, but Cloud KMS only manages keys, not the inspection or transformation of data content.

How to eliminate wrong answers

Option A is wrong because Security Command Center is a security and risk management platform that provides threat detection, vulnerability scanning, and compliance monitoring, but it does not have native capabilities to inspect or de-identify PII in data objects. Option B is wrong because Dataplex is a data governance and management service that helps organize, catalog, and manage data across lakes and warehouses, but it lacks built-in PII inspection and de-identification features. Option D is wrong because Cloud KMS is a key management service for creating, storing, and managing encryption keys, but it does not inspect data for PII or perform de-identification; it only provides encryption/decryption operations.

Full explanation →
860
MCQmedium

Your team is using Vertex AI Pipelines to orchestrate a model retraining workflow. The pipeline includes a data validation step, a training step, and a model evaluation step. You want to ensure that if the evaluation step fails due to low model performance, the pipeline stops and does not deploy the model. Which approach should you use?

A.Run the evaluation step after deployment and roll back if performance is low
B.Configure the evaluation step to retry up to 3 times on failure
C.Use a Conditional in the pipeline to check evaluation metrics and only run the deployment step if metrics pass thresholds
D.Create a separate pipeline for deployment and trigger it manually after review
AnswerC

Conditionals allow pipeline to branch based on results.

Why this answer

Vertex AI Pipelines supports conditional execution via the `Condition` component, which allows you to evaluate model performance metrics (e.g., accuracy, RMSE) and gate subsequent steps. By placing the deployment step inside a conditional branch that only executes when evaluation metrics meet predefined thresholds, the pipeline automatically stops and avoids deploying a poor-performing model. This approach aligns with MLOps best practices for automated gating in production pipelines.

Exam trap

The trap here is that candidates confuse retry logic (Option B) with conditional gating, mistakenly thinking that retrying a failed evaluation step will somehow improve model performance, when in fact retries only handle transient errors, not metric-based failures.

How to eliminate wrong answers

Option A is wrong because running the evaluation step after deployment and then rolling back violates the principle of failing fast; it wastes compute resources and risks serving a bad model to users before rollback. Option B is wrong because retrying the evaluation step on failure does not address the root cause — low model performance — and would simply re-run the same evaluation, potentially masking the failure or delaying the pipeline. Option D is wrong because creating a separate pipeline for manual deployment defeats the purpose of automation and introduces human latency and error, contradicting the goal of an automated orchestrated workflow.

Full explanation →
861
MCQhard

A company runs a batch data processing workload using Dataproc clusters that are auto-scaled based on YARN memory utilization. During peak times, jobs take much longer than expected. Analysis shows the cluster is not scaling up despite high YARN memory utilization. What is the most likely cause?

A.Spark dynamic allocation is disabled, preventing executors from using added workers
B.The cluster autoscaler is misconfigured to scale based on CPU, not memory
C.The autoscaler is set to scale down secondary workers, not up
D.The cluster is using primary workers only; auto-scaling only adds secondary workers
AnswerD

Auto-scaling adds secondary workers, not primary; if only primary workers exist, no scale-up occurs.

Why this answer

Dataproc clusters have two types of workers: primary workers (which run both HDFS and compute) and secondary workers (compute-only). The autoscaler can only add or remove secondary workers; it cannot scale primary workers. If the cluster uses only primary workers, the autoscaler has no secondary workers to add, so it cannot scale up even under high YARN memory utilization.

This explains why the cluster remains static during peak times.

Exam trap

The trap here is that candidates assume autoscaling applies to all worker nodes equally, overlooking the Dataproc-specific distinction between primary and secondary workers and the autoscaler's limitation to secondary workers only.

How to eliminate wrong answers

Option A is wrong because Spark dynamic allocation controls how executors are distributed within existing nodes, not how the cluster adds new nodes; even if disabled, the autoscaler would still attempt to add workers if configured correctly. Option B is wrong because the question explicitly states the autoscaler is based on YARN memory utilization, not CPU; a misconfiguration to CPU would cause scaling based on CPU metrics, but the symptom here is no scaling at all, not scaling on the wrong metric. Option C is wrong because the autoscaler is designed to scale up secondary workers when utilization is high; a misconfiguration to scale down would cause premature removal of workers, not a failure to scale up.

Full explanation →
862
MCQeasy

A company wants to use BigQuery to query data stored in Parquet files in Cloud Storage without loading the data into BigQuery. Which BigQuery feature should they use?

A.BigQuery Omni
B.BigQuery ML
C.BigQuery external tables
D.BigQuery BI Engine
AnswerC

External tables allow querying data directly from GCS without loading into BigQuery storage.

Why this answer

BigQuery external tables allow querying data stored in Cloud Storage (including Parquet files) directly without loading it into BigQuery storage. This feature uses a federated query engine that reads the data on the fly, supporting formats like Parquet, Avro, ORC, CSV, and JSON. Option C is correct because it directly addresses the requirement to query Parquet files in Cloud Storage without ingestion.

Exam trap

Google often tests the distinction between features that query external data (external tables) versus features that process data within BigQuery (like BI Engine) or across clouds (Omni), leading candidates to confuse Omni's multi-cloud capability with external data access in the same cloud.

How to eliminate wrong answers

Option A is wrong because BigQuery Omni is designed to query data across multi-cloud environments (AWS, Azure) using BigQuery's interface, not for querying Parquet files in Cloud Storage without loading. Option B is wrong because BigQuery ML is a machine learning feature that enables creating and executing models using SQL, not for querying external data files. Option D is wrong because BigQuery BI Engine is an in-memory analysis service that accelerates dashboard queries on data already stored in BigQuery, not for querying external Parquet files in Cloud Storage.

Full explanation →
863
MCQhard

A data engineer needs to design a Bigtable row key for a time-series IoT application where each device sends data every second. The query pattern is to retrieve all data for a specific device over a time range. Which row key design minimizes hotspots?

A.device_id#timestamp (e.g., device123#2024-03-15-10:30:00)
B.hash(device_id)#timestamp (e.g., a3f2#2024-03-15-10:30:00)
C.timestamp#device_id (e.g., 2024-03-15-10:30:00#device123)
D.device_type#device_id#timestamp
AnswerB

Hashing the device ID distributes writes across tablets, and appending timestamp allows efficient time-range scans.

Why this answer

To avoid hotspots (where all writes hit a single tablet server), the row key should start with a hash of the device ID to distribute writes across the cluster, then append the timestamp for range scans.

Full explanation →
864
Multi-Selectmedium

A data warehouse team uses Cloud BigQuery for analytics. They want to optimize query performance and reduce costs. Which three actions should they take? (Choose 3)

Select 3 answers
A.Use partitioned tables on time columns
B.Use clustered tables on frequently filtered columns
C.Use automatic reclustering
D.Use materialized views for aggregations
E.Use BI Engine for all queries
AnswersA, B, D

Partitioning allows queries to skip irrelevant partitions, reducing cost and improving speed.

Why this answer

Partitioning tables on time columns (e.g., DATE, TIMESTAMP) in BigQuery allows the query engine to perform partition pruning, scanning only the relevant partitions instead of the entire table. This directly reduces the amount of data read, lowering query costs and improving performance by limiting I/O to the necessary time range.

Exam trap

Google Cloud often tests the distinction between automatic reclustering as a passive maintenance feature versus an active optimization action, leading candidates to mistakenly select it as a cost-saving measure when it is actually a built-in behavior that does not require manual intervention.

Full explanation →
865
Multi-Selectmedium

Which TWO steps are required to deploy a custom scikit-learn model to Vertex AI for online predictions?

Select 2 answers
A.Write a custom prediction routine
B.Containerize the model using Docker
C.Save the model using joblib or pickle
D.Create a Vertex AI Endpoint manually
E.Upload the model to Vertex AI Model Registry
AnswersC, E

Vertex AI expects a saved model artifact.

Why this answer

Scikit-learn models must be serialized using joblib or pickle to be saved as a model artifact that can be uploaded to Vertex AI. Vertex AI's pre-built prediction containers for scikit-learn expect the model file to be in this format (typically model.joblib or model.pkl) to serve online predictions.

Exam trap

Google Cloud often tests the misconception that you must always write a custom prediction routine or containerize your model, when in fact Vertex AI provides pre-built containers for popular frameworks like scikit-learn, making steps A and B unnecessary for standard deployments.

Full explanation →
866
MCQhard

A data pipeline using Cloud Dataflow reads from a Pub/Sub subscription that has a dead letter topic configured. Some messages are being sent to the dead letter topic. Upon investigation, the engineer finds that the messages contain valid data but are malformed according to the schema. What is the most likely reason for the messages being dead-lettered?

A.The Pub/Sub topic has a schema that the messages do not comply with
B.The Pub/Sub topic is not configured with a schema
C.The Dataflow pipeline is using at-least-once delivery guarantee
D.The subscription's ack deadline is too short
AnswerA

Topic schema enforcement causes non-compliant messages to be rejected and sent to dead letter.

Why this answer

The subscription's message schema enforcement validates incoming messages; if the message doesn't conform to the schema, it is forwarded to the dead letter topic.

Full explanation →
867
Multi-Selecthard

A company is migrating their on-premises Hadoop/Spark workloads to Google Cloud. They need a fully managed service that supports existing Spark jobs with minimal code changes, allows autoscaling, and provides integration with Cloud Storage and BigQuery. The team also wants to avoid managing cluster infrastructure and pay only for what they use. Which TWO services meet these requirements? (Choose two.)

Select 2 answers
A.Dataproc Serverless (Spark)
B.Dataproc on GKE
C.Standard Dataproc cluster with preemptible workers
D.Cloud Composer with Spark
E.Dataflow with Spark Runner
AnswersA, B

Dataproc Serverless runs Spark jobs without cluster management, supports autoscaling, and integrates with Cloud Storage and BigQuery.

Why this answer

Dataproc Serverless allows running Spark jobs without managing clusters, with autoscaling and pay-per-use pricing. Dataproc on GKE enables running Spark on Kubernetes with autoscaling and is fully managed. Standard Dataproc requires cluster management and is not serverless.

Dataflow is for Beam, not Spark. Cloud Composer is for orchestration, not data processing.

Full explanation →
868
MCQhard

A company stores sensitive customer data in BigQuery and Cloud Storage. They want to encrypt the data with customer-managed encryption keys (CMEK) and ensure that access to the key material is restricted to only approved networks. Which additional Google Cloud control should they implement to enforce network-based access to the encryption keys?

A.Identity-Aware Proxy (IAP)
B.Private Google Access
C.VPC Service Controls
D.Cloud Armor
AnswerC

VPC Service Controls allow you to define a security perimeter around Google Cloud services, including Cloud KMS, to restrict access based on network origin.

Why this answer

VPC Service Controls (VPC-SC) can create a security perimeter around Cloud KMS and BigQuery/Cloud Storage resources, preventing data exfiltration and restricting access to approved networks. VPC-SC works with CMEK to add an extra layer of network-based access control. Cloud Armor is for HTTP(S) load balancing, IAP is for user identity, and Private Google Access is for on-premises access to public IPs.

Full explanation →
869
MCQeasy

A data scientist wants to automate retraining of a classification model when new labeled data arrives. The model is deployed on AI Platform Prediction. Which Google Cloud service should be used to orchestrate the retraining pipeline?

A.AI Platform Prediction
B.AI Platform Pipelines
C.AI Platform Continuous Evaluation
D.Cloud Dataflow
AnswerB

AI Platform Pipelines provides a way to build and orchestrate ML pipelines.

Why this answer

AI Platform Pipelines (now Vertex AI Pipelines) is the correct service because it provides a fully managed, serverless orchestration engine for building, deploying, and running machine learning pipelines. It integrates with Kubeflow Pipelines and TensorFlow Extended (TFX) to automate the retraining workflow when new labeled data arrives, enabling continuous training and model versioning without manual intervention.

Exam trap

Google Cloud often tests the distinction between services that execute ML tasks (like prediction or evaluation) versus services that orchestrate the workflow; the trap here is that candidates confuse AI Platform Prediction (serving) or Cloud Dataflow (data processing) with pipeline orchestration, missing that AI Platform Pipelines is purpose-built for automating multi-step ML workflows.

How to eliminate wrong answers

Option A is wrong because AI Platform Prediction is a serving endpoint for deploying trained models to make predictions; it does not orchestrate retraining pipelines. Option C is wrong because AI Platform Continuous Evaluation is a service for monitoring model performance and detecting drift, not for orchestrating retraining workflows. Option D is wrong because Cloud Dataflow is a stream and batch data processing service (based on Apache Beam) used for data transformation and ETL, not for orchestrating end-to-end ML pipelines with conditional retraining logic.

Full explanation →
870
MCQhard

A company has a production machine learning model deployed on Vertex AI Endpoint that predicts customer churn. The model is retrained weekly using a Vertex AI Pipeline that pulls new data from BigQuery. Recently, the model's accuracy has been declining. The data science team suspects data drift but is unsure. They have enabled Vertex AI Model Monitoring but have not set up any alerts. The team wants to diagnose and address the issue quickly. The pipeline runs successfully, and no errors are reported. The model endpoint is serving predictions with average latency of 200ms. What should the team do first?

A.Immediately trigger a retraining pipeline with more recent data
B.Increase the number of replicas to reduce latency
C.Examine Cloud Logging for prediction errors
D.Review Vertex AI Model Monitoring drift reports and set up alerts for significant drift
AnswerD

Directly addresses drift detection.

Why this answer

The team has already enabled Vertex AI Model Monitoring, which automatically tracks feature distributions and prediction statistics over time. The first diagnostic step should be to review the drift reports generated by Model Monitoring to confirm whether data drift is occurring, and then set up alerts so the team is proactively notified of significant drift in the future. This directly addresses the suspected root cause without unnecessary operational changes.

Exam trap

Google Cloud often tests the misconception that any model performance decline must be fixed by immediate retraining or infrastructure scaling, when the correct first step is always to diagnose the root cause using the monitoring tools already in place.

How to eliminate wrong answers

Option A is wrong because blindly retraining with more recent data without first confirming data drift may waste resources and could even degrade model performance if the new data is not representative or contains label errors. Option B is wrong because increasing replicas addresses latency, not accuracy decline; the current 200ms latency is well within acceptable bounds and is unrelated to the accuracy problem. Option C is wrong because Cloud Logging captures prediction errors (e.g., runtime exceptions, invalid inputs), but the pipeline runs successfully with no errors, so examining logs for errors will not reveal gradual accuracy degradation caused by data drift.

Full explanation →
871
MCQhard

A financial services company deploys a fraud detection model on Vertex AI using a custom prediction container that runs a PyTorch model. The model requires GPU acceleration. The deployment succeeds but predictions return an error: 'CUDA error: out of memory'. What should the team do to resolve this issue?

A.Change the container to use a CPU-only image to avoid CUDA errors
B.Increase the GPU machine type to one with more memory (e.g., from NVIDIA T4 to A100)
C.Enable Vertex AI Model Monitoring to automatically scale the endpoint
D.Add CPU replicas to distribute the inferencing load
AnswerB

The CUDA out of memory error indicates the current GPU cannot hold the model; a larger GPU or model optimization is needed.

Why this answer

The CUDA out-of-memory error indicates that the GPU's VRAM is insufficient to load the PyTorch model or process the inference batch. Increasing the GPU machine type to one with more memory, such as from an NVIDIA T4 (16 GB) to an A100 (40 or 80 GB), directly resolves the capacity issue. Vertex AI prediction endpoints allow you to select different accelerator types and sizes, and this change ensures the model fits within GPU memory.

Exam trap

The trap here is that candidates may confuse a resource exhaustion error (out of memory) with a scaling or monitoring issue, leading them to choose options like Model Monitoring or adding CPU replicas, rather than recognizing the need for a larger GPU machine type.

How to eliminate wrong answers

Option A is wrong because switching to a CPU-only image would avoid CUDA errors but would likely cause severe performance degradation or timeout, as the model requires GPU acceleration for acceptable inference latency. Option C is wrong because Vertex AI Model Monitoring is designed for detecting data drift and feature skew, not for scaling endpoints or resolving out-of-memory errors; it does not automatically adjust machine resources. Option D is wrong because adding CPU replicas does not address the GPU memory exhaustion; the error occurs on the GPU, and distributing load across CPU replicas would still route requests to GPU-backed instances that lack sufficient VRAM.

Full explanation →
872
MCQeasy

Your company has a machine learning model that predicts customer churn. The model is deployed on Vertex AI Endpoints with autoscaling. After a marketing campaign, traffic to the endpoint increases by 10x. Some predictions start failing with 'HTTP 503 Service Unavailable' errors. What is the most likely cause?

A.The model container has a memory leak.
B.The model's accuracy has degraded due to data drift.
C.The autoscaling configuration has insufficient maximum nodes to handle the traffic.
D.The model is using an older version that is not supported.
AnswerC

Autoscaling with too few max nodes cannot scale up to meet demand, causing overload and 503 errors.

Why this answer

A 503 Service Unavailable error from Vertex AI Endpoints indicates that the endpoint is overwhelmed and cannot handle the incoming request volume. With a 10x traffic spike and autoscaling configured, the most likely cause is that the autoscaling configuration has insufficient maximum nodes, so the endpoint cannot scale out enough to handle the load, causing requests to be rejected.

Exam trap

Google Cloud often tests the distinction between model-level errors (e.g., data drift, accuracy degradation) and infrastructure-level errors (e.g., 503, 429, timeout), so the trap here is that candidates confuse a model performance issue with a scaling/availability issue.

How to eliminate wrong answers

Option A is wrong because a memory leak in the model container would cause gradual performance degradation or OOM kills, not a sudden 503 error under high traffic; Vertex AI would still attempt to serve requests until the container crashes. Option B is wrong because data drift affects prediction accuracy (e.g., wrong predictions), not the availability or HTTP status of the endpoint; 503 errors are infrastructure-level, not model-level. Option D is wrong because using an unsupported older version would cause deployment or startup failures, not transient 503 errors under load; Vertex AI would reject the deployment or return a different error (e.g., 400 or 404) if the version is incompatible.

Full explanation →
873
MCQmedium

A company runs a Dataflow pipeline that reads from Pub/Sub, aggregates events in a 10-minute fixed window, and writes to BigQuery. Recently, the pipeline has been failing with 'high uncommitted bytes' errors during periods of high traffic. What is the most likely cause and recommended action?

A.Reduce the window size from 10 minutes to 1 minute to decrease the amount of data per window.
B.Increase the number of worker machines to handle higher throughput.
C.Use a global window with a trigger that fires early based on element count to reduce the number of open windows.
D.Set a maximum number of workers and use a Pub/Sub flow control setting to limit incoming messages.
AnswerC

A global window with early triggers can reduce the number of panes and mitigate the high uncommitted bytes problem.

Why this answer

The 'high uncommitted bytes' error in Dataflow occurs when the system holds too much data in memory across many open windows, exceeding the default 200 MB limit. Using a global window with an early trigger based on element count reduces the number of simultaneous open windows and allows data to be committed more frequently, preventing memory pressure. This approach is recommended over reducing window size or scaling workers because the root cause is window fan-out, not throughput or parallelism.

Exam trap

Google Cloud often tests the misconception that scaling workers or reducing window size solves memory pressure, when the real issue is the number of open windows in a stateful pipeline.

How to eliminate wrong answers

Option A is wrong because reducing the window size from 10 minutes to 1 minute increases the number of open windows (from 6 per hour to 60 per hour), which would worsen the 'high uncommitted bytes' issue by creating more in-memory state. Option B is wrong because increasing worker machines does not address the fundamental problem of excessive open windows consuming memory; it may temporarily mask the issue but will not reduce the per-worker uncommitted bytes. Option D is wrong because setting a maximum number of workers and Pub/Sub flow control limits incoming messages but does not reduce the number of open windows or the memory used by uncommitted data; it may cause backpressure and data loss without fixing the window state explosion.

Full explanation →
874
MCQmedium

Your company ingests millions of events per second into a Pub/Sub topic. The downstream consumer must process events with minimal latency and high throughput. However, the consumer occasionally falls behind during traffic spikes, and you need to ensure no data loss while minimizing costs. Which subscription type and configuration should you choose?

A.Push subscription with a load balancer
B.Pull subscription with flow control settings
C.Push subscription with endpoint on Cloud Run
D.Pull subscription with exactly-once delivery disabled
AnswerB

Pull subscriptions allow the subscriber to pull messages at its own pace, and flow control helps prevent overwhelming the consumer. This combination handles high throughput efficiently.

Why this answer

Pull subscriptions allow the subscriber to control the throughput by batching messages and setting flow control, which is ideal for high-throughput scenarios. Using a pull subscription with exactly-once delivery (if available) or at-least-once combined with idempotent processing ensures no data loss. Push subscriptions have limitations on throughput and are not suitable for millions of events per second.

Full explanation →
875
MCQmedium

A company is using Dataflow to stream data from Cloud Pub/Sub to BigQuery. The pipeline includes a custom ParDo transformation that enriches the data with external API calls. The pipeline is experiencing high latency and occasional failures due to API timeouts. What strategy should be employed to improve reliability and performance?

A.Remove the enrichment step and store raw data in BigQuery.
B.Use a global window to accumulate all data before enrichment.
C.Use a DoFn with stateful processing and batch API calls using asynchronous HTTP client.
D.Increase the number of workers to parallelize API calls.
AnswerC

Batching and async calls reduce per-element latency and handle timeouts gracefully.

Why this answer

Using a DoFn with stateful processing and an asynchronous HTTP client allows the pipeline to batch API calls and handle timeouts without blocking the main processing thread. This reduces latency by enabling concurrent requests and improves reliability through retry logic and state management, which is essential for external API enrichment in Dataflow.

Exam trap

Google Cloud often tests the misconception that scaling workers (Option D) is a universal fix for performance issues, but the trap here is that API timeouts are often caused by the external service's capacity, not the pipeline's parallelism, and stateful batching with async calls is the correct architectural pattern.

How to eliminate wrong answers

Option A is wrong because removing the enrichment step defeats the purpose of the pipeline and does not address the underlying issue of API call reliability. Option B is wrong because using a global window to accumulate all data before enrichment would introduce unbounded state and memory pressure, and it does not solve API timeout problems; it would also break the streaming nature of the pipeline. Option D is wrong because simply increasing the number of workers does not fix API timeouts; it may even exacerbate the problem by overwhelming the external API with more concurrent requests, leading to more failures.

Full explanation →
876
MCQeasy

A user gets the above error when trying to get online predictions. The model was created and the endpoint exists. What is the most likely reason?

A.The endpoint does not exist.
B.The endpoint is in a different region than the model.
C.No version of the model is deployed to the endpoint.
D.The model does not exist.
AnswerC

A model must be deployed (a model version) to the endpoint to serve predictions.

Why this answer

The error 'No version of the model is deployed to the endpoint' occurs when the endpoint exists but has no active model version assigned to it. In Google Cloud AI Platform (Vertex AI), an endpoint must have at least one deployed model version to serve predictions. Without a deployed version, the endpoint cannot handle inference requests, even though the endpoint resource exists.

Exam trap

Google Cloud exams often test the misconception that creating an endpoint automatically deploys the latest model version, when in fact you must explicitly specify a model version during endpoint creation or update.

How to eliminate wrong answers

Option A is wrong because the user explicitly states 'the endpoint exists,' so the error is not due to a missing endpoint. Option B is wrong because endpoints and models in SageMaker are region-scoped; you cannot create an endpoint in a different region than the model's artifacts, so this scenario would not produce the given error. Option D is wrong because the model exists (the user says 'the model was created'), and the error is specifically about deployment status, not model existence.

Full explanation →
877
Multi-Selecteasy

A data engineer is preparing a dataset for ML training in Vertex AI. The dataset includes a timestamp column, a categorical column with high cardinality (1000 distinct values), and a numerical column with outliers. Which two preprocessing steps should they apply? (Choose TWO)

Select 2 answers
A.Drop the timestamp column
B.Label encode the categorical column
C.Winsorize the numerical column to cap outliers
D.Normalize the numerical column using Z-score
E.One-hot encode the categorical column
AnswersB, C

Label encoding maps categories to integers, reducing dimensionality.

Why this answer

One-hot encoding for high cardinality may be too sparse; label encoding (ordinal encoder) is more common. Winsorizing clips outliers.

Full explanation →
878
MCQhard

Refer to the exhibit. A team is trying to run a custom prediction container on Vertex AI Endpoint. They get this error when the container starts. What is the most likely cause?

A.The container image is too large
B.The entry point is missing or incorrect
C.The container is built for a different CPU architecture
D.The model file is missing from the container
AnswerB

The error message directly states to ensure the container has an entry point.

Why this answer

The error occurs when the container starts, which typically happens during the initial health check or readiness probe. Vertex AI Endpoints require a valid entry point (e.g., CMD or ENTRYPOINT in the Dockerfile) to start the prediction server. If the entry point is missing or incorrect, the container fails to launch, resulting in the observed error.

Exam trap

Google Cloud often tests the distinction between container startup failures (entry point issues) and runtime failures (missing model files or architecture mismatches), leading candidates to confuse a missing model file with a startup error.

How to eliminate wrong answers

Option A is wrong because container image size does not prevent startup; Vertex AI supports images up to 10 GB, and a large image would only affect pull time, not the container's ability to start. Option C is wrong because CPU architecture mismatch would cause a runtime crash or 'exec format error' during execution, not a startup failure, and Vertex AI uses x86_64 architecture by default. Option D is wrong because a missing model file would cause a runtime error during prediction (e.g., 404 or model load failure), not a container startup failure, as the container can still start and listen for requests.

Full explanation →
879
Multi-Selecteasy

Your team is using Cloud Dataprep to clean and transform a dataset. Which TWO features of Cloud Dataprep help you understand data quality issues before running the pipeline? (Choose 2.)

Select 2 answers
A.Scheduling data quality jobs
B.Column histograms
C.Joining datasets
D.Recipe steps
E.Data quality profiling
AnswersB, E

Histograms visually display the distribution of values, helping to spot unexpected patterns.

Why this answer

Data quality profiling provides statistics and distributions to identify anomalies. Column histograms visualize data distribution and outliers. Scheduling and recipe steps are execution features, not exploratory analysis.

Joins are transformations, not profiling.

Full explanation →
880
MCQmedium

A company wants to use Cloud Data Fusion to build ETL pipelines. They need to connect to a legacy on-premises database using JDBC and also want to use prebuilt transforms from the Hub. Which two features should they use?

A.Cloud SQL JDBC driver and Cloud Functions
B.Dataproc Metastore and Cloud Storage sink
C.Wrangler and Dataproc
D.CDAP JDBC plugin and the Hub
AnswerD

CDAP JDBC plugin connects to on-prem DB; Hub provides prebuilt transforms.

Why this answer

Cloud Data Fusion uses CDAP plugins for JDBC connections and the Hub provides prebuilt transforms. Plugins are the mechanism; Hub is where they are sourced. Wrangler is for data preparation, not sink.

Dataproc is not needed as Data Fusion runs on its own infrastructure.

Full explanation →
881
MCQeasy

Which Google Cloud service would you use to create a unified data catalog that automatically captures lineage from BigQuery, Cloud Storage, and other sources?

A.Cloud Composer
B.Dataflow
C.Data Catalog
D.Dataplex
AnswerD

Dataplex includes a unified catalog, lineage, and governance.

Why this answer

Dataplex provides a unified data catalog (Universal Catalog) with automated lineage, discovery, and governance across GCP. Data Catalog is the older standalone service; Dataplex is the recommended unified solution. Cloud Composer and Dataflow are orchestration/processing tools.

Full explanation →
882
MCQhard

A company uses BigQuery flat-rate pricing with 500 slots purchased as a committed use discount. During peak hours, they need additional capacity but do not want to buy more committed slots. They have a secondary project used for ad-hoc queries by analysts. How can they provide burst capacity to the primary project during peak times without increasing committed spend?

A.Create flex slots in the secondary project, create a reservation in the secondary project, and assign the reservation to the primary project.
B.Enable autoscaling slot management in the primary project's reservation, allowing slots to scale up based on demand.
C.Upgrade the primary project's edition to Enterprise Plus to allow bursting.
D.Purchase additional committed use slots in the primary project and apply them to the reservation.
AnswerA

Correct. Flex slots are designed for temporary capacity. Creating them in a secondary project and assigning the reservation to the primary project provides burst capacity without committing to additional long-term slots.

Why this answer

Flex slots provide temporary capacity without long-term commitment. By creating flex slots in a secondary project and assigning the reservation to the primary project, burst capacity is added during peak times without increasing committed spend. Option B is incorrect because autoscaling can be used with committed use reservations, but it does not provide capacity beyond the purchased slots without incurring additional costs; autoscaling on committed use still uses flex pricing.

Option C is incorrect because upgrading to Enterprise Plus does not inherently provide burst capacity without additional slots. Option D is incorrect because purchasing additional committed use slots increases committed spend.

Full explanation →
883
MCQmedium

A data engineer needs to run an existing Spark job on Google Cloud with minimal code changes. The job requires Hive metastore access. Which Dataproc feature should they use to provide a managed Hive metastore?

A.Cloud SQL for MySQL
B.Dataproc Metastore
C.BigQuery as a Hive metastore
D.Dataproc on GKE
AnswerB

Dataproc Metastore is a managed Hive metastore service that works with Dataproc clusters.

Why this answer

Dataproc Metastore provides a fully managed Hive metastore that integrates with Dataproc clusters, allowing existing Spark jobs to use it without code changes.

Full explanation →
884
MCQmedium

You are moving an on-premises Hadoop workload to Google Cloud. The workload uses Hive for metadata and HDFS for storage. Which services should you use to minimise reconfiguration?

A.Dataproc with HDFS and Cloud Bigtable for metadata
B.Dataproc with Cloud Storage and Cloud SQL for Hive metastore
C.Dataflow with Cloud Storage and BigQuery
D.Dataproc with Cloud Storage and Dataproc Metastore
AnswerD

Dataproc Metastore is a fully managed Hive metastore. Cloud Storage replaces HDFS seamlessly.

Why this answer

Dataproc Metastore provides a fully managed Hive metastore service that can be used with Dataproc clusters. Cloud Storage can replace HDFS via the gs:// connector, allowing the same file paths. This minimises code changes.

Full explanation →
885
Multi-Selecteasy

Which TWO options can help reduce costs for a Dataflow batch pipeline that processes 100 GB of data daily from Cloud Storage? (Choose 2)

Select 2 answers
A.Use Dataflow Prime (now Dataflow Runner v2)
B.Use high-memory machine types
C.Use Streaming Engine
D.Use FlexRS (Flexible Resource Scheduling)
E.Use preemptible VMs for Dataflow workers
AnswersD, E

FlexRS offers discounted pricing for batch jobs that are flexible on start time.

Why this answer

FlexRS (Flexible Resource Scheduling) allows you to run batch workloads on a discounted, flexible schedule. It reduces costs by offering lower prices in exchange for the job being able to wait up to 6 hours for resources to become available. This is ideal for a daily 100 GB batch pipeline that can tolerate some scheduling delay.

Exam trap

Google Cloud often tests the distinction between batch and streaming optimizations, so the trap here is that candidates might select Streaming Engine (Option C) thinking it reduces costs in batch pipelines, when it is only relevant for streaming.

Full explanation →
886
Multi-Selectmedium

A data team wants to use Approximate Aggregation Functions in BigQuery to get faster query results. Which two functions can they use? (Choose 2)

Select 2 answers
A.APPROX_SUM
B.APPROX_AVG
C.APPROX_QUANTILES
D.APPROX_COUNT_DISTINCT
E.APPROX_MEDIAN
AnswersC, D

Returns approximate quantiles.

Why this answer

BigQuery provides APPROX_COUNT_DISTINCT for approximate distinct counts and APPROX_QUANTILES for approximate quantiles. Other approximate functions include APPROX_TOP_COUNT and APPROX_TOP_SUM.

Full explanation →
887
MCQmedium

A company uses a custom container image for model serving. The image is large (10 GB). During deployment, they get timeouts. What should they do?

A.Pre-pull the image on all nodes
B.Increase the timeout in the deployment config
C.Switch to a larger machine type
D.Use a smaller base image
AnswerD

Smaller image reduces pull time and deployment time.

Why this answer

Using a smaller base image directly addresses the root cause of the timeout: the 10 GB image takes too long to download from the container registry during pod startup. By reducing the image size (e.g., using a slim or distroless base image), the pull time decreases, avoiding the default kubelet image pull timeout (typically 5 minutes) without requiring infrastructure changes.

Exam trap

Google Cloud often tests the misconception that increasing timeouts or scaling up hardware solves performance bottlenecks, when the correct answer is to optimize the artifact itself (image size) to meet the system's implicit constraints.

How to eliminate wrong answers

Option A is wrong because pre-pulling the image on all nodes is a manual workaround that does not solve the underlying issue of a bloated image; it also adds operational overhead and fails in dynamic clusters where new nodes are added. Option B is wrong because increasing the timeout in the deployment config (e.g., the `imagePullPolicy` or pod-level timeout) only masks the symptom and does not reduce the pull time, potentially leading to other timeouts in the cluster. Option C is wrong because switching to a larger machine type does not affect the network transfer time for pulling the image; it only provides more local resources, which does not address the slow image download.

Full explanation →
888
Multi-Selectmedium

A company is planning to migrate a legacy batch ETL pipeline to Google Cloud. The pipeline involves reading from a relational database, transforming data, and writing to a data warehouse. Which three Google Cloud services can be used as the orchestration layer? (Choose three.)

Select 3 answers
A.Cloud Dataproc
B.Cloud Scheduler
C.Cloud Dataflow
D.Cloud Workflows
E.Cloud Composer
AnswersB, D, E

Cloud Scheduler can trigger jobs on a schedule, acting as a simple orchestrator.

Why this answer

Cloud Scheduler is a fully managed cron job service that can trigger orchestration workflows on a schedule. It is correct because it can initiate batch ETL pipelines by sending HTTP requests to Cloud Run, Cloud Functions, or Pub/Sub, making it a lightweight orchestration trigger for scheduled batch jobs.

Exam trap

Google Cloud often tests the distinction between data processing services (Dataproc, Dataflow) and orchestration services (Workflows, Composer, Scheduler), so candidates mistakenly select Dataproc or Dataflow thinking they can orchestrate, when they are actually execution engines.

Full explanation →
889
Multi-Selectmedium

A data scientist needs to perform feature engineering for a machine learning model using Vertex AI. They want to preprocess data using a pipeline that includes scaling, one-hot encoding, and handling missing values. Which TWO services can they use to define and execute this preprocessing pipeline? (Choose 2.)

Select 2 answers
A.Cloud Dataproc
B.Vertex AI Pipelines
C.BigQuery SQL with ML.TRANSFORM
D.Cloud Dataflow
E.Cloud Functions
AnswersB, C

Allows you to build and run end-to-end ML pipelines, including preprocessing.

Why this answer

Vertex AI Pipelines is the recommended service for building and running ML pipelines, including preprocessing steps. Alternatively, you can use BigQuery SQL for feature engineering directly on the data, then export the processed data for training. Cloud Dataflow is an option for batch/streaming data processing but is not specific to ML pipelines.

Cloud Functions and Dataproc are less suitable for this purpose.

Full explanation →
890
MCQmedium

A company is building a real-time streaming pipeline using Pub/Sub and Dataflow to process clickstream data. The pipeline writes aggregated metrics to BigQuery every 10 seconds using a fixed window. During peak traffic, some windows produce duplicate rows in BigQuery. What is the most likely cause?

A.Dataflow is retrying BigQuery streaming inserts after a timeout, and the retries succeed even though the original insert succeeded.
B.The pipeline uses default triggers instead of after-watermark triggers.
C.The fixed window duration is too short, causing overlapping windows.
D.The pipeline is using too many Dataflow workers, causing load balancing issues.
AnswerA

This is a known scenario: BigQuery streaming inserts are not idempotent, and retries can lead to duplicates.

Why this answer

Dataflow uses at-least-once semantics for streaming inserts into BigQuery. When a streaming insert times out, Dataflow retries the insert, and if the original insert actually succeeded but the acknowledgment was lost, the retry produces a duplicate row. This is a known behavior of BigQuery streaming inserts with retry logic.

Exam trap

The trap here is that candidates often confuse trigger behavior (Option B) with the root cause of duplicates, not realizing that duplicates stem from retry semantics in the sink, not from windowing or parallelism.

How to eliminate wrong answers

Option B is wrong because default triggers in Dataflow (which fire on element arrival and after watermark) do not cause duplicate rows; they affect when results are emitted, not whether duplicates occur. Option C is wrong because fixed windows of 10 seconds do not overlap by design; overlapping windows would require a sliding window, not a fixed window. Option D is wrong because using too many Dataflow workers can cause resource inefficiency or shuffle issues, but it does not directly cause duplicate rows in BigQuery output.

Full explanation →
Page 11

Page 12 of 12

All pages

123456789101112

Practice PDE by domain

Target a specific domain to shore up weak areas.

Designing Data Processing SystemsIngesting and Processing the DataStoring the DataPreparing and Using Data for AnalysisMaintaining and Automating Data Workloads
See all domains with question counts →