Knowledge + Practice

Google Professional Machine Learning Engineer (PMLE) — Questions 451–525

990 questions total · 14pages · All types, answers revealed

Take a mock exam Exam hub

Page 7 of 14

451

MCQeasy

A company wants to monitor the cost of their Vertex AI prediction endpoint. They are charged per hour per replica and per request for GPU instances. Which approach should they use to track these costs?

A.Set up Cloud Billing budget alerts and export billing data to BigQuery for analysis

B.Use Vertex AI Model Monitoring to track cost metrics

C.Enable Cloud Monitoring dashboards for cost metrics

D.Use Vertex AI Pipelines to track cost per job

AnswerA

Budget alerts and exporting billing data are standard practices for cost monitoring.

Why this answer

Vertex AI prediction costs are tracked via Cloud Billing. Budget alerts can be set up to notify when spending exceeds a threshold. Cost breakdown can be viewed in the Billing reports.

Full explanation →

452

MCQhard

A company uses Vertex AI Pipelines to train and deploy models. The pipeline has a step that runs a custom container. The step fails intermittently with a timeout error. Which approach should be taken to robustly handle this?

A.Switch to Kubeflow Pipelines

B.Set up a Cloud Composer DAG to monitor and rerun the pipeline

C.Reduce the size of the training data

D.Increase the timeout for the step in the pipeline definition

E.Use Cloud Functions to retry the step

AnswerD

Directly fixes the timeout issue.

Why this answer

Vertex AI Pipelines (built on Kubeflow Pipelines) allows you to define a `timeout` parameter for each pipeline step. Increasing this timeout directly addresses the intermittent timeout error by giving the custom container more time to complete its work, without changing the pipeline architecture or introducing external monitoring components. This is the most robust and minimal-change solution for a step that occasionally exceeds its current time limit.

Exam trap

The trap here is that candidates may over-engineer the solution by choosing external retry mechanisms (Cloud Functions, Cloud Composer) or changing the pipeline framework, when the simplest and most correct fix is to adjust the step's timeout configuration within the pipeline definition itself.

How to eliminate wrong answers

Option A is wrong because Vertex AI Pipelines is already built on Kubeflow Pipelines; switching does not solve a timeout issue and would require re-architecting the pipeline. Option B is wrong because Cloud Composer (Apache Airflow) is an external orchestrator; adding it to monitor and rerun the pipeline adds complexity and latency, and does not fix the root cause of the step timing out. Option C is wrong because reducing training data size may degrade model quality and does not address the timeout—the step might still fail if the container itself is slow for other reasons.

Option E is wrong because Cloud Functions are stateless and event-driven; they cannot directly retry a step within a Vertex AI Pipeline—retries should be configured natively in the pipeline definition using the `retry_count` or `timeout` parameters.

Full explanation →

453

MCQeasy

A company wants to predict customer churn using a dataset with 10,000 rows and 20 features. They have no ML expertise. Which low-code solution should they use?

A.Kubeflow Pipelines

B.Custom TensorFlow model

C.BigQuery ML

D.Vertex AI AutoML Tables

AnswerD

AutoML Tables provides automated model training and deployment without requiring deep ML knowledge.

Why this answer

Vertex AI AutoML Tables is the correct low-code solution because it allows users with no ML expertise to train high-quality tabular models on structured data (10,000 rows, 20 features) without writing any code. It automates feature engineering, model selection, and hyperparameter tuning, and provides a simple UI to upload data and get predictions. This directly matches the requirement of a low-code, no-expertise solution for a tabular churn prediction problem.

Exam trap

Google Cloud often tests the distinction between low-code/no-code solutions (like AutoML Tables) and platforms that still require coding or infrastructure expertise (like Kubeflow or custom TensorFlow), leading candidates to pick a technically capable but overly complex option.

How to eliminate wrong answers

Option A is wrong because Kubeflow Pipelines is a platform for building and deploying ML pipelines that requires significant coding and Kubernetes expertise, making it unsuitable for users with no ML expertise. Option B is wrong because a custom TensorFlow model requires writing Python code, defining neural network architectures, and tuning hyperparameters, which demands ML expertise. Option C is wrong because BigQuery ML is a low-code option for SQL-based ML, but it requires knowledge of SQL and ML concepts (e.g., creating models with CREATE MODEL statements), and it is less automated than AutoML Tables for users with zero ML background.

Full explanation →

454

MCQmedium

A team is using Vertex AI Experiments to compare different hyperparameters. They want to automatically record the hyperparameters. What is the correct way?

A.Manually log to console

B.Use the `aiplatform.start_run()` context manager

C.Write to a CSV file

D.Use BigQuery

AnswerB

This context manager automatically logs hyperparameters and metrics to Vertex AI Experiments.

Why this answer

Vertex AI Experiments provides a native `aiplatform.start_run()` context manager that automatically captures hyperparameters passed as key-value arguments, logging them to the experiment run metadata without manual intervention. This integrates directly with the Vertex AI SDK, ensuring consistency and traceability across runs.

Exam trap

Google Cloud often tests the misconception that any logging method (console, CSV, BigQuery) is equivalent to native SDK integration, but the key requirement is automatic, structured recording tied to the experiment run, which only the SDK's context manager provides.

How to eliminate wrong answers

Option A is wrong because manually logging to console only outputs data to stdout, which is not persisted in Vertex AI Experiments and cannot be queried or compared programmatically. Option C is wrong because writing to a CSV file requires custom I/O code, lacks integration with Vertex AI's experiment tracking, and does not associate the hyperparameters with a specific experiment run. Option D is wrong because BigQuery is a data warehouse for analytics, not a mechanism for automatically recording hyperparameters during model training; it would require additional infrastructure to capture and store the parameters.

Full explanation →

455

MCQhard

A team monitors features in Vertex AI Feature Store for drift. They want to set up automated alerts when a feature's distribution deviates significantly from the baseline. Which feature monitoring configuration should they use?

A.Enable feature monitoring on the feature group with drift threshold and notification channel.

B.Use Cloud Monitoring custom metrics and log-based alerts manually.

C.Use Vertex AI Experiments to compare distributions.

D.Export features to BigQuery and set up scheduled queries with alerts.

AnswerA

Feature monitoring in Feature Store supports drift detection and alerting.

Why this answer

Feature monitoring in Vertex AI Feature Store allows defining drift thresholds and alerting via Cloud Monitoring.

Full explanation →

456

Multi-Selectmedium

An organization wants to deploy a model on edge devices (e.g., Android phones) for offline inference. They trained a model using TensorFlow. Which THREE steps should they take to prepare and deploy the model?

Select 3 answers

A.Convert the model to TensorFlow Lite format.

B.Deploy the model to a Vertex AI endpoint for online inference.

C.Use Vertex AI Edge Manager to package and deploy the model.

D.Export the model to ONNX format.

E.Deploy the TFLite model to the edge devices.

AnswersA, C, E

TFLite is optimized for mobile and edge devices.

Why this answer

For edge deployment on Android, you need to convert the model to TensorFlow Lite, use Vertex AI Edge Manager to manage the deployment, and then deploy the TFLite model to the devices. Exporting to ONNX is for other platforms, and creating a REST endpoint is for online serving.

Full explanation →

457

MCQeasy

A data scientist wants to use a pre-trained ResNet model from Keras Applications and fine-tune it on a small custom dataset. Which approach should they take to avoid overfitting?

A.Freeze the first few layers and train the rest.

B.Add more convolutional layers to the model.

C.Use a larger learning rate to speed up training.

D.Train the entire model from scratch on the custom dataset.

AnswerA

Freezing earlier layers preserves general features; training only later layers adapts to the new task.

Why this answer

Freezing the earlier layers (which capture general features) and only training the later layers is a common transfer learning approach for small datasets, reducing overfitting.

Full explanation →

458

Multi-Selecthard

Which THREE should be considered when setting up an automated retraining pipeline using Vertex AI Pipelines and Cloud Composer? (Choose THREE.)

Select 3 answers

A.Setting performance thresholds for new models to decide deployment

B.Including hyperparameter tuning in every retraining run

C.Optimizing resource allocation to control costs

D.Frequency of code commits to the repository

E.Monitoring for data drift to trigger retraining

AnswersA, C, E

Ensure new model is better than current.

Why this answer

In an automated retraining pipeline, you must set performance thresholds (e.g., accuracy, precision, recall) for new models to decide whether to deploy them. Vertex AI Pipelines can evaluate model metrics against these thresholds and conditionally deploy only if the new model meets or exceeds the current production model's performance, preventing regressions.

Exam trap

Google Cloud often tests the misconception that hyperparameter tuning must be part of every retraining run, but in practice it is a separate, infrequent optimization step to avoid excessive compute costs and pipeline latency.

Full explanation →

459

MCQeasy

You deploy a new version of a model to a Vertex AI endpoint and want to gradually shift traffic from the old version to the new version over 24 hours. The endpoint currently serves 100% traffic to the old version. What should you do?

A.Use Vertex AI Experiments to run an A/B test between the two versions.

B.Deploy the new version to a separate endpoint and update your client to use the new endpoint for a percentage of requests.

C.Update the endpoint to split traffic between the two model versions using the traffic split configuration.

D.Delete the old version and redeploy the new version with a different endpoint name, then update DNS.

AnswerC

Vertex AI traffic split allows gradual shifting of traffic between model versions on the same endpoint.

Why this answer

Vertex AI endpoints support a built-in traffic split configuration that allows you to gradually shift traffic between model versions deployed to the same endpoint. By updating the endpoint's traffic split percentages (e.g., from 100% old / 0% new to 0% old / 100% new over 24 hours), you can achieve a smooth, controlled rollout without changing client code or managing multiple endpoints.

Exam trap

Google often tests the misconception that traffic splitting requires separate endpoints or client-side logic, when in fact Vertex AI provides a native traffic split configuration on a single endpoint.

How to eliminate wrong answers

Option A is wrong because Vertex AI Experiments is designed for tracking and comparing model training runs, not for managing production traffic splits or A/B testing at the serving layer. Option B is wrong because deploying to a separate endpoint and updating the client to split requests manually introduces unnecessary complexity, client-side changes, and potential inconsistency; Vertex AI's traffic split feature handles this natively at the server side. Option D is wrong because deleting the old version and redeploying with a different endpoint name, then updating DNS, would cause a complete traffic cutover (not gradual) and disrupt service during the DNS propagation period, which can take minutes to hours.

Full explanation →

460

MCQeasy

A company deploys a model on Vertex AI Endpoints for real-time inference. They notice latency spikes during peak hours. Which action is most effective to reduce latency without sacrificing accuracy?

A.Enable autoscaling based on CPU utilization

B.Use a larger machine type

C.Reduce model size by pruning

D.Implement client-side caching

AnswerA

Autoscaling adds instances during load spikes, maintaining low latency without sacrificing accuracy.

Why this answer

Enabling autoscaling based on CPU utilization dynamically adjusts the number of instances to handle traffic spikes, reducing latency without sacrificing accuracy. Option B increases cost without addressing scaling elasticity. Option C may reduce accuracy.

Option D does not address latency spikes at the serving layer.

Full explanation →

461

MCQmedium

A company uses Vertex AI Vector Search for similarity search. They have a dataset of 10 million 512-dimensional vectors. Which index type should they choose for lowest latency at high recall?

A.Brute-force (flat) index

B.Approximate nearest neighbor (ANN) index with Scann

C.Tree-based index

D.Hashing-based index

AnswerB

ANN is designed for large-scale, low-latency search with high recall.

Why this answer

For a dataset of 10 million 512-dimensional vectors, a brute-force (flat) index would be far too slow for low-latency queries. Approximate Nearest Neighbor (ANN) with ScaNN (Scalable Nearest Neighbors) is specifically designed by Google for high-dimensional vector search, offering sub-linear query time while maintaining high recall through techniques like anisotropic quantization and tree-based partitioning. This makes it the optimal choice for balancing latency and recall at this scale.

Exam trap

The trap here is that candidates often assume brute-force is the only way to guarantee high recall, but the question explicitly asks for lowest latency at high recall, which is the exact trade-off that ANN indexes like ScaNN are designed to optimize.

How to eliminate wrong answers

Option A is wrong because a brute-force (flat) index computes exact distances to every vector, resulting in O(N) complexity per query, which is prohibitively slow for 10 million vectors and cannot achieve low latency. Option C is wrong because tree-based indexes (e.g., KD-trees, R-trees) suffer from the curse of dimensionality in high-dimensional spaces (512-D), where their performance degrades to near brute-force due to the sparsity of data. Option D is wrong because hashing-based indexes (e.g., LSH) typically require multiple hash tables to achieve high recall, leading to high memory usage and often lower recall compared to optimized ANN methods like ScaNN, especially for 512-dimensional vectors.

Full explanation →

462

MCQmedium

An engineer is using TensorFlow Transform (tf.Transform) to preprocess training data. They want to ensure that the same preprocessing logic is applied during inference without code duplication. Which approach should they take?

A.Use tf.Transform at prediction time by running a separate Beam pipeline

B.Use Dataflow to preprocess data for both training and serving

C.Use tf.Transform to generate a transform_fn and save it as a SavedModel; then use tf.saved_model.load to apply it in the serving pipeline

D.Write separate preprocessing code for training and serving in Python

AnswerC

The transform_fn SavedModel ensures consistency.

Why this answer

TensorFlow Transform outputs a SavedModel that contains the preprocessing graph. This can be exported as a transform_fn and embedded in the serving model, ensuring consistency between training and serving.

Full explanation →

463

Multi-Selectmedium

You need to orchestrate a complex ML workflow that involves multiple Vertex AI pipelines, BigQuery jobs, and Dataflow pipelines. The workflow must handle dependencies, retries, and monitoring. Which two services are best suited for this orchestration?

Select 2 answers

A.Cloud Composer

B.Vertex AI Pipelines

C.Cloud Scheduler

D.BigQuery scheduled queries

E.Cloud Functions

AnswersA, B

Airflow can orchestrate Vertex AI pipelines, BigQuery jobs, and Dataflow pipelines with dependencies.

Why this answer

Cloud Composer (based on Apache Airflow) is the correct choice because it provides a managed environment for orchestrating complex workflows with dependencies, retries, and monitoring across heterogeneous services like Vertex AI pipelines, BigQuery, and Dataflow. Airflow's DAGs allow you to define task dependencies, set retry policies, and integrate with Cloud Monitoring for observability, making it ideal for multi-service ML workflows.

Exam trap

The trap here is that candidates often confuse Cloud Scheduler or Cloud Functions as sufficient for orchestration, but they lack the dependency management, retry logic, and cross-service monitoring that Cloud Composer provides for complex ML workflows.

Full explanation →

464

MCQeasy

A machine learning engineer needs to pass a large dataset between two components in a Vertex AI pipeline. What is the recommended way to pass this data?

A.Store the dataset as a Dataset artifact and pass the artifact between components.

B.Write the dataset to a temporary BigQuery table and pass the table name.

C.Serialize the dataset to a string and pass it as a pipeline parameter.

D.Use a Cloud Storage bucket and pass the bucket name as a parameter.

AnswerA

Correct: Using Dataset artifacts ensures efficient storage and versioning via Cloud Storage.

Why this answer

In Vertex AI Pipelines, the recommended way to pass large datasets between components is to use a `Dataset` artifact. Artifacts are metadata references that point to the underlying data stored in Cloud Storage, enabling efficient, scalable, and type-safe data passing without serialization overhead or size limits. This approach leverages the Kubeflow Pipelines SDK's artifact tracking, which automatically handles lineage and versioning.

Exam trap

The trap here is that candidates often assume passing a Cloud Storage bucket name (Option D) is sufficient, but they miss that artifacts provide automatic metadata tracking, type safety, and integration with Vertex AI's lineage system, which is required for production ML pipelines.

How to eliminate wrong answers

Option B is wrong because writing a large dataset to a temporary BigQuery table introduces unnecessary latency, cost, and complexity; BigQuery is designed for analytical queries, not as an intermediate data transfer mechanism for pipeline components. Option C is wrong because serializing a large dataset to a string and passing it as a pipeline parameter violates the parameter size limit (typically 64KB in Kubeflow Pipelines) and would cause out-of-memory errors or pipeline failures. Option D is wrong because passing only the bucket name as a parameter lacks the structured metadata and type safety that artifacts provide; it forces components to independently resolve file paths and does not automatically track lineage or versioning.

Full explanation →

465

MCQmedium

An ML engineer needs to update a model deployed on a Vertex AI endpoint without downtime. They want to gradually shift traffic to the new version while monitoring for errors. What is the correct procedure?

A.Use a canary deployment by deploying to a separate endpoint and using a load balancer with weighted routing.

B.Deploy the new model to a new endpoint, then update DNS to point to the new endpoint.

C.Delete the old model and deploy the new one with the same endpoint.

D.Deploy the new model to the same endpoint with 0% traffic initially, then gradually increase traffic while monitoring.

AnswerD

This ensures no downtime and allows controlled rollout.

Why this answer

The correct procedure is to deploy the new model version to the same endpoint, initially with 0% traffic, then gradually increase its traffic allocation while monitoring.

Full explanation →

466

MCQhard

You need to deploy a TensorFlow model to edge devices for real-time inference with minimal latency. The model is currently trained on Vertex AI. Which approach should you use?

A.Convert the model to TensorFlow Lite using the TF Lite converter, then deploy to edge devices via Vertex AI Edge Manager.

B.Export the model as a SavedModel and deploy it to Vertex AI Edge Manager using the Edge Manager API.

C.Deploy the model to Vertex AI endpoint and use Cloud IoT Core to stream data to the cloud for inference.

D.Use Vertex AI Model Optimization to quantize the model to INT8 and then deploy as a web service on a Raspberry Pi.

AnswerA

TFLite is optimized for on-device inference; Edge Manager can deploy it to edge devices.

Why this answer

TensorFlow Lite is specifically designed for on-device inference on edge devices, offering reduced model size and optimized performance for low-latency, real-time scenarios. Vertex AI Edge Manager provides a managed service to deploy, monitor, and update models on edge devices, making it the ideal combination for this use case.

Exam trap

This scenario tests the distinction between cloud-based serving (SavedModel, Vertex AI endpoints) and edge-optimized deployment (TF Lite, Edge Manager), and the trap here is assuming that any Vertex AI deployment method works for edge devices without considering the need for model optimization and offline inference capability.

How to eliminate wrong answers

Option B is wrong because exporting as a SavedModel alone does not optimize the model for edge devices; SavedModel is a full TensorFlow format intended for serving on cloud or server infrastructure, not for resource-constrained edge hardware. Option C is wrong because streaming data to the cloud for inference introduces network latency and dependency on connectivity, which contradicts the requirement for minimal latency and real-time inference on edge devices. Option D is wrong because deploying as a web service on a Raspberry Pi does not leverage Vertex AI Edge Manager for lifecycle management, and while INT8 quantization helps, the approach lacks the managed deployment and monitoring capabilities needed for production edge deployments.

Full explanation →

467

MCQhard

A team uses Vertex AI Experiments to track ML training runs. They want to automatically trigger a retraining pipeline when new labeled data arrives in BigQuery, and ensure the pipeline uses only approved libraries from a central artifact registry. Which combination of services should they use?

A.Cloud Composer to orchestrate, with Cloud Storage for libraries.

B.Vertex AI Pipelines with a scheduled trigger, and use Cloud Build to pull libraries from Artifact Registry.

C.Cloud Functions triggered by BigQuery, Cloud Build to run training, and Artifact Registry for libraries.

D.Vertex AI Experiments with continuous evaluation, and a Cloud Run job for training.

E.Dataflow to preprocess, then trigger a Cloud Run job.

AnswerB

Scheduled pipeline can query BigQuery for new data, and Cloud Build ensures consistent library versions.

Why this answer

Vertex AI Pipelines provides a managed orchestration service for ML workflows, and a scheduled trigger can be set to run the pipeline when new labeled data arrives in BigQuery (e.g., via a Cloud Scheduler or Eventarc trigger). Cloud Build is used to pull approved libraries from Artifact Registry, ensuring only vetted dependencies are used during pipeline execution, which meets the security and compliance requirement.

Exam trap

The trap here is that candidates may confuse Cloud Build (a CI/CD service) with Vertex AI Training (a managed ML training service), or think that Cloud Composer is the only orchestration option for ML pipelines, when Vertex AI Pipelines is the native, more integrated choice for ML workflows on Vertex AI.

How to eliminate wrong answers

Option A is wrong because Cloud Composer (based on Apache Airflow) is a general-purpose workflow orchestrator, not specifically designed for Vertex AI Pipelines, and using Cloud Storage for libraries does not enforce the use of a central artifact registry with version control and access policies. Option C is wrong because Cloud Functions triggered by BigQuery can initiate a retraining pipeline, but Cloud Build is a CI/CD tool, not a managed ML training service; Vertex AI Training or Pipelines should be used for the actual training run, not Cloud Build. Option D is wrong because Vertex AI Experiments tracks runs but does not orchestrate retraining pipelines; continuous evaluation is a monitoring feature, not a trigger mechanism, and Cloud Run is a serverless compute service for containers, not a managed ML training service.

Option E is wrong because Dataflow is a stream/batch data processing service, not a trigger mechanism for retraining, and Cloud Run is not designed for long-running ML training jobs; it lacks GPU support and has request timeout limits.

Full explanation →

468

MCQmedium

A team wants to implement CI/CD for their ML models using Cloud Build. They have a pipeline that trains a model and deploys it. What is the best practice for triggering the pipeline when a new commit is pushed to the source repository?

A.Set up a Cloud Scheduler job to poll the repository periodically

B.Deploy a custom web service on App Engine to call Cloud Build API

C.Use Pub/Sub to notify Cloud Build of new commits

D.Configure a Cloud Build trigger on the source repository (e.g., Cloud Source Repositories, GitHub)

AnswerD

Cloud Build supports triggers that automatically start a build upon a push to the repository.

Why this answer

Cloud Build natively supports triggers that automatically start a pipeline when a new commit is pushed to a connected source repository (e.g., Cloud Source Repositories, GitHub, Bitbucket). This is the simplest, most event-driven approach, requiring no polling, custom services, or additional messaging infrastructure. It directly maps the git push event to a build invocation, ensuring near-instantaneous pipeline execution.

Exam trap

The trap here is that candidates may overthink the solution and choose Pub/Sub (Option C) because they know Pub/Sub is used for event-driven architectures, but they miss that Cloud Build triggers already abstract this complexity away, making direct trigger configuration the best practice.

How to eliminate wrong answers

Option A is wrong because Cloud Scheduler polling is inefficient, introduces latency (minimum 1-minute intervals), and is not event-driven; it would waste resources and delay pipeline starts. Option B is wrong because deploying a custom web service on App Engine to call the Cloud Build API adds unnecessary complexity, cost, and maintenance overhead, and is not a best practice when native triggers exist. Option C is wrong because while Pub/Sub can be used to trigger builds, it requires an intermediary (e.g., a Cloud Function) to receive the commit notification and call the Cloud Build API, adding latency and complexity compared to a direct Cloud Build trigger.

Full explanation →

469

MCQhard

A company uses a Cloud Composer DAG to run a daily ML pipeline that includes Dataflow jobs and model training on Vertex AI. The pipeline frequently fails due to insufficient permissions when the Dataflow worker accesses data in Cloud Storage. What is the most efficient way to resolve this issue?

A.Create a custom service account with required permissions and assign it to the Dataflow job.

B.Grant the 'roles/storage.objectViewer' role to 'allUsers' on the Cloud Storage bucket.

C.Use the Composer environment's service account for all pipeline components.

D.Move the Dataflow job to run after the pipeline so that data is already processed.

AnswerA

Lets the Dataflow worker access the data securely.

Why this answer

The most efficient way to resolve insufficient permissions for Dataflow workers accessing Cloud Storage is to create a custom service account with the required roles (e.g., roles/storage.objectViewer) and assign it to the Dataflow job via the --serviceAccount option. This follows the principle of least privilege and ensures that only the Dataflow workers have the necessary permissions, without affecting other pipeline components or exposing the bucket publicly.

Exam trap

Google Cloud often tests the misconception that using a single service account for all components (like the Composer environment's service account) is simpler and sufficient, but this ignores the principle of least privilege and can cause security vulnerabilities or permission conflicts in distributed pipelines.

How to eliminate wrong answers

Option B is wrong because granting roles/storage.objectViewer to 'allUsers' makes the Cloud Storage bucket publicly readable, which is a severe security risk and violates least privilege principles. Option C is wrong because the Composer environment's service account typically has broader permissions than needed for Dataflow workers, and using it for all components can lead to over-privileging and potential security issues; moreover, Dataflow workers require a separate identity to access resources independently. Option D is wrong because moving the Dataflow job to run after the pipeline does not address the root cause of insufficient permissions; the Dataflow job will still fail when it tries to access Cloud Storage data, regardless of when it runs.

Full explanation →

470

MCQmedium

You need to serve a large embedding model for similarity search with low latency. The model was trained to generate 256-dimensional embeddings. You plan to use Vertex AI Vector Search. Which index type should you choose to balance accuracy and performance for a dataset with 10 million vectors?

A.Tree-based index

B.Approximate nearest neighbor (ANN) index using ScaNN

C.Brute-force index

D.Hash-based index

AnswerB

ScaNN is designed for efficient large-scale similarity search with configurable accuracy.

Why this answer

Vertex AI Vector Search uses ScaNN (Scalable Nearest Neighbors) as its underlying ANN algorithm, which is specifically designed for high-dimensional embeddings (like 256-d) and large-scale datasets (10M vectors). ScaNN balances accuracy and performance by employing anisotropic quantization and tree-based partitioning, making it the optimal choice for low-latency similarity search without requiring exhaustive comparison.

Exam trap

Candidates often mistakenly choose Tree-based index (Option A) because ScaNN uses tree-based partitioning internally, but a standalone tree index fails in high dimensions. Vertex AI Vector Search’s ScaNN combines tree partitioning with quantization to overcome the curse of dimensionality and balance accuracy and performance for 10 million 256-d vectors.

How to eliminate wrong answers

Option A is wrong because a pure tree-based index (e.g., KD-tree) suffers from the 'curse of dimensionality' at 256 dimensions, where performance degrades to near brute-force levels. Option C is wrong because a brute-force index computes exact distances for all 10M vectors, resulting in O(n) latency that is unacceptable for real-time serving. Option D is wrong because hash-based indexes (e.g., LSH) are typically used for approximate nearest neighbor search in lower dimensions or for specific distance metrics, but they are not natively supported as a primary index type in Vertex AI Vector Search, and they often require extensive tuning to match ScaNN's accuracy-latency trade-off.

Full explanation →

471

MCQmedium

What is the most likely cause of the error?

A.The data split column contains only NULL values, so no rows are assigned to the training set

B.The model type 'linear_reg' is incompatible with the column 'price' because of missing values

C.The model creation does not have permission to read the dataset in BigQuery

D.The model creation did not specify a training budget, so default is insufficient

AnswerA

Custom split requires non-NULL values 0,1,2.

Why this answer

When the data split column contains only NULL values, BigQuery ML cannot assign any rows to the training set. The `DATA_SPLIT_METHOD` using a custom column requires non-NULL values in that column to partition data into training and evaluation sets; if all values are NULL, the training set receives zero rows, causing the model creation to fail with an error about insufficient training data.

Exam trap

Google Cloud often tests the subtle distinction between missing values in the label column (which are handled gracefully) versus missing values in the data split column (which can cause a complete failure), leading candidates to incorrectly blame missing values in the target column.

How to eliminate wrong answers

Option B is wrong because the `linear_reg` model type is fully compatible with the `price` column even if it has missing values; BigQuery ML handles NULLs in the label column by excluding those rows during training, but the error here is about no training rows, not missing values. Option C is wrong because if the user lacked permission to read the dataset, the error would be a permissions-related message (e.g., 'Access Denied'), not a training set size error. Option D is wrong because BigQuery ML does not require a training budget for linear regression models; the default settings are sufficient, and the error is not budget-related.

Full explanation →

472

Multi-Selecteasy

Which TWO of the following are benefits of using Vertex AI Matching Engine (Vector Search) over a brute-force nearest neighbor search? (Choose 2)

Select 2 answers

A.Simpler to implement than brute-force

B.Supports real-time updates without index rebuild

C.Lower query latency for large datasets

D.Reduced memory footprint compared to brute-force

E.Guaranteed exact nearest neighbor results

AnswersC, D

ANN trades off some accuracy for much faster search.

Why this answer

Vertex AI Matching Engine uses approximate nearest neighbor (ANN) algorithms like ScaNN (Scalable Nearest Neighbors) to index high-dimensional vectors. For large datasets, ANN dramatically reduces query latency by avoiding a full scan of all vectors, unlike brute-force search which must compute distances against every vector. This makes option C correct because ANN trades a negligible accuracy loss for orders-of-magnitude faster retrieval.

Exam trap

Google often tests the misconception that approximate nearest neighbor search provides exact results, but the trap here is that candidates confuse 'nearest neighbor' with 'exact nearest neighbor,' forgetting that ANN algorithms like ScaNN are inherently approximate.

Full explanation →

473

MCQmedium

Your organization has a large production system that uses Vertex AI Prediction for an NLP model with a 2 GB memory footprint. The endpoint is configured with 5 replicas, each using an n1-standard-4 with a single T4 GPU. Recently, you observed an increase in 503 errors during peak hours. Cloud Monitoring shows that GPU utilization is consistently above 90% across all replicas, while CPU and memory are below 50%. You have already increased the max replicas to 10, but the errors persist because the increased replicas also become saturated. What should you do to resolve the issue?

A.Switch to a larger GPU such as V100 or A100 to increase per-replica throughput.

B.Implement request batching in the custom container to improve GPU utilization efficiency.

C.Enable model parallelism across multiple GPUs within each replica.

D.Use a high-memory machine type like n1-highmem-16 to reduce memory pressure.

AnswerA

Switching to a larger GPU (e.g., V100 or A100) increases per-replica compute capacity, directly addressing the GPU saturation and reducing 503 errors. This is the most effective fix.

Why this answer

GPU utilization is above 90% across all replicas, indicating the GPU is the bottleneck. Increasing replicas does not help because each new replica also saturates its GPU. The most direct solution is to increase per-replica throughput by using a more powerful GPU (e.g., V100 or A100), which can process more work per unit time.

Option A addresses the root cause—GPU capacity. Option D (high-memory machine) does not help because memory is not the constraint (CPU/memory < 50%). Batching (B) is likely already in use but limited by GPU compute capacity.

Model parallelism (C) is unnecessary for a 2 GB model.

Exam trap

Candidates may assume that adding more replicas or memory will solve throughput issues, but when the GPU is the bottleneck, the only effective remedy is to upgrade the GPU itself.

Full explanation →

474

MCQmedium

You are deploying a scikit-learn model for online predictions. The model size is 200 MB. You want to minimize latency and cost. Which serving option should you choose?

A.Deploy to Vertex AI online prediction using a prebuilt container for scikit-learn.

B.Use Cloud Run with a custom container.

C.Create a Kubernetes cluster on GKE and deploy the model there.

D.Export the model as a Cloud Function.

AnswerA

Vertex AI provides optimized containers and autoscaling for online prediction.

Why this answer

Vertex AI online prediction with custom containers is suitable for scikit-learn models. Vertex AI will host the container and scale. Using AI Platform or Cloud Functions with a 200 MB model might hit limits.

Full explanation →

475

MCQeasy

A team uses Vertex AI Feature Store for storing features. They want to share feature definitions with other teams in a collaborative manner. What is the best way to collaborate on feature definitions?

A.Use a shared repository with feature definition files and CI/CD to update the feature store.

B.Grant all teams write access to the same feature store so they can modify definitions directly.

C.Export the feature definitions as CSV and email them to the other teams.

D.Use a wiki page to document feature definitions and update it manually.

AnswerA

Using a shared repo with CI/CD provides version control and automated updates, ensuring consistency and traceability.

Why this answer

Using a shared repository with feature definition files and CI/CD pipelines enables version control, peer review, and automated deployment to Vertex AI Feature Store. This approach ensures consistency, traceability, and collaboration without risking direct, uncoordinated changes to the production feature store.

Exam trap

The trap here is that candidates may assume direct write access (Option B) is efficient for collaboration, but the exam tests understanding that feature stores require controlled, versioned updates to maintain data integrity and avoid breaking downstream models.

How to eliminate wrong answers

Option B is wrong because granting all teams write access to the same feature store allows uncoordinated, direct modifications to feature definitions, which can lead to conflicts, data corruption, and lack of version control. Option C is wrong because exporting feature definitions as CSV and emailing them is error-prone, lacks versioning, and does not provide a single source of truth for collaboration. Option D is wrong because using a wiki page for manual documentation is static, easily outdated, and does not integrate with the feature store's actual schema or deployment process.

Full explanation →

476

MCQmedium

A team deploys a PyTorch model on Vertex AI for online predictions. They notice that after deployment, the latency increases over time, especially during peak hours. The model is served using a custom container. What is the most likely cause?

A.The custom container does not have a health check, causing instances to be prematurely terminated.

B.The model is not using GPU even though a GPU machine is selected.

C.The model is too large for the machine's memory, causing swapping.

D.The prediction requests are not being batched, and the model inference code is not optimized for concurrency.

AnswerD

Without batching and concurrency, requests queue up, increasing latency under load.

Why this answer

The latency increase over time, especially during peak hours, indicates that the model inference code is not handling concurrent requests efficiently. Without batching or optimized concurrency, each request is processed sequentially, causing a queue buildup under load. This is a common issue with custom containers on Vertex AI when the prediction handler is single-threaded or lacks async processing.

Exam trap

Google Cloud often tests the misconception that latency increases are always due to resource exhaustion (memory/CPU) rather than concurrency or request handling inefficiencies, leading candidates to pick Option C.

How to eliminate wrong answers

Option A is wrong because a missing health check would cause instances to be terminated and recreated, leading to intermittent failures or startup latency, not a gradual latency increase over time. Option B is wrong because selecting a GPU machine without using the GPU would result in underutilization but not necessarily increasing latency; the model would still run on CPU, and latency would be constant or high from the start. Option C is wrong because if the model were too large for memory, swapping would cause consistently high latency from the outset, not a gradual increase during peak hours.

Full explanation →

477

MCQhard

A company uses BigQuery as their data warehouse. They want to version datasets for ML experiments and be able to query snapshots at specific points in time. Which approach is most cost-effective and requires minimal operational overhead?

A.Use BigQuery table clones to create copies of the data.

B.Export the table to Cloud Storage as Parquet and use DVC to version the files.

C.Use BigQuery time-travel (7-day window) to query historical data without snapshots.

D.Create BigQuery table snapshots at key milestones.

AnswerD

Snapshots are incremental and cost-effective.

Why this answer

BigQuery table snapshots are a built-in feature for point-in-time recovery and versioning at low cost (only storage changes).

Full explanation →

478

MCQeasy

A data scientist wants to track the lineage of a dataset used in a training run. Which Vertex AI feature should they use?

A.Vertex ML Metadata

B.Vertex AI Feature Store

C.Vertex AI Experiments

D.Vertex AI Model Registry

AnswerA

ML Metadata tracks data lineage and artifact relationships.

Why this answer

Vertex ML Metadata is the correct choice because it is specifically designed to track the lineage of datasets, models, and other artifacts throughout the ML lifecycle. It records metadata about each step in a pipeline, including the source dataset used for a training run, enabling full provenance tracking. This allows data scientists to trace back which data was used, how it was transformed, and which model version it produced.

Exam trap

The trap here is that candidates often confuse Vertex AI Experiments (which tracks run metrics and parameters) with lineage tracking, but Experiments does not capture the full artifact-to-execution graph that ML Metadata provides for dataset provenance.

How to eliminate wrong answers

Option B is wrong because Vertex AI Feature Store is a centralized repository for storing, serving, and sharing feature values for ML models, not for tracking dataset lineage. Option C is wrong because Vertex AI Experiments is used to track and compare model training runs, hyperparameters, and metrics, but it does not natively capture the lineage of the dataset itself beyond run-level parameters. Option D is wrong because Vertex AI Model Registry is a version control system for trained models, managing model deployments and versions, but it does not track the provenance of the training data used to create those models.

Full explanation →

479

MCQhard

A company has multiple teams working on different models. They want to enforce consistent data preprocessing steps across all teams. Which approach should they take?

A.Use Cloud Composer to orchestrate preprocessing

B.Write shared Python packages in Artifact Registry

C.Use Cloud Dataflow templates

D.Create shared Vertex AI Pipelines components

AnswerD

Shared components can be reused across pipelines, enforcing consistent preprocessing.

Why this answer

Vertex AI Pipelines components allow teams to define reusable, versioned, and parameterized preprocessing steps that can be shared across models and pipelines. This ensures consistent execution of data transformations because each component encapsulates the exact code and environment, and pipelines enforce the same DAG of steps regardless of which team triggers them.

Exam trap

Google Cloud often tests the distinction between 'sharing code' (e.g., packages) and 'sharing executable, environment-encapsulated pipeline steps' (e.g., components), leading candidates to choose a code-sharing option like Artifact Registry instead of the pipeline component approach that enforces consistency.

How to eliminate wrong answers

Option A is wrong because Cloud Composer is an orchestration service for workflows (based on Apache Airflow) and does not inherently enforce consistent preprocessing logic across teams; it only schedules and monitors tasks, leaving the actual preprocessing code to be defined separately and potentially inconsistently. Option B is wrong because writing shared Python packages in Artifact Registry provides a way to distribute code, but it does not enforce a standardized execution environment or pipeline structure; teams could still call the packages with different parameters or in different orders, leading to inconsistency. Option C is wrong because Cloud Dataflow templates are used for batch and stream data processing jobs (based on Apache Beam), but they are not designed to be shared as reusable, composable steps across multiple ML pipelines; they lack the pipeline-level DAG enforcement and versioning that Vertex AI Pipelines components provide.

Full explanation →

480

MCQhard

A company has deployed a model for image classification and wants to monitor for feature drift using XRAI attributions. However, they notice that the XRAI attribution maps are too large and are causing high latency in the monitoring pipeline. What is the most effective way to reduce the overhead of explainability monitoring for image models?

A.Disable XRAI and use integrated gradients instead

B.Reduce the sampling rate for the explainability feature

C.Use a smaller image size for the model

D.Increase the number of replicas on the endpoint

AnswerB

Sampling rate controls the fraction of predictions for which explanations are generated, directly reducing overhead.

Why this answer

Vertex AI Explainable AI supports XRAI for image models, but generating XRAI attributions can be computationally expensive. Sampling a subset of predictions reduces the number of explanations generated, lowering latency and cost.

Full explanation →

481

Multi-Selecthard

A team uses Vertex AI Feature Store with an online store for real-time predictions. They notice that the online store queries are taking longer than expected. Which TWO actions could improve online store performance? (Choose 2)

Select 2 answers

A.Use the offline store for serving predictions.

B.Reduce the number of features served by the online store.

C.Switch from Bigtable to Firestore online store.

D.Enable caching on the online store.

E.Increase the number of Bigtable nodes if using Bigtable online store.

AnswersB, E

Fewer features reduce data volume and improve latency.

Why this answer

For Bigtable online store, increasing nodes improves throughput; for optimized online store, decreasing number of features reduces load. Caching is not a built-in feature.

Full explanation →

482

MCQeasy

An organization wants to use Cloud Composer (Airflow) to orchestrate a machine learning workflow that includes running a Vertex AI Pipeline, followed by a BigQuery job, and then a Dataflow pipeline. What is the primary advantage of using Cloud Composer for this orchestration?

A.It allows orchestrating heterogeneous workflows across multiple GCP services with dependencies and retries.

B.It automatically caches the outputs of each step to avoid recomputation.

C.It integrates natively with the Vertex AI Model Registry for model versioning.

D.It provides a serverless execution environment for ML pipelines.

AnswerA

Cloud Composer excels at orchestrating complex DAGs that span multiple services like Vertex AI, BigQuery, and Dataflow.

Why this answer

Cloud Composer (Apache Airflow) is designed to orchestrate heterogeneous workflows across multiple GCP services. In this scenario, it can define a Directed Acyclic Graph (DAG) that runs a Vertex AI Pipeline, then a BigQuery job, and finally a Dataflow pipeline, with built-in support for dependency management, retries, and failure handling. This is the primary advantage because it allows you to coordinate disparate services in a single, reliable workflow.

Exam trap

The trap here is that candidates may confuse Cloud Composer's orchestration capabilities with features specific to individual GCP services (like caching, model registry, or serverless execution), leading them to pick options that describe those services' features rather than the primary advantage of using an orchestrator.

How to eliminate wrong answers

Option B is wrong because Cloud Composer does not automatically cache outputs of each step; caching is a feature of specific services like Vertex AI Pipelines or Dataflow, not Airflow itself. Option C is wrong because Cloud Composer does not natively integrate with the Vertex AI Model Registry; that integration is handled by Vertex AI Pipelines or custom operators, not by Airflow's core orchestration. Option D is wrong because Cloud Composer is not serverless; it runs on a managed GKE cluster, and serverless ML pipeline execution is provided by Vertex AI Pipelines, not Cloud Composer.

Full explanation →

483

MCQhard

A financial institution wants to use Natural Language API for sentiment analysis on customer feedback, but the domain-specific language (e.g., 'bullish', 'bearish') is not correctly classified. They have 200 labeled examples. Which approach minimizes coding effort while improving accuracy?

A.Submit a feature request to Google for domain-specific terms

B.Create a custom sentiment dictionary and pass it to the Natural Language API

C.Build a custom TensorFlow model for sentiment

D.Use AutoML Natural Language to train a custom model

AnswerD

No-code training on labeled data for improved accuracy.

Why this answer

AutoML Natural Language enables you to train a custom model on your 200 labeled examples without writing code, directly improving accuracy for domain-specific terms like 'bullish' and 'bearish'. This approach leverages transfer learning from Google's pre-trained models, minimizing coding effort while adapting to your unique vocabulary and sentiment patterns.

Exam trap

Google Cloud often tests the misconception that the Natural Language API supports custom dictionaries or rule-based overrides, when in fact it only offers a fixed pre-trained model, making AutoML the correct low-code path for domain adaptation.

How to eliminate wrong answers

Option A is wrong because submitting a feature request to Google for domain-specific terms is not a practical solution—Google does not provide custom term updates for individual customers, and the turnaround time is indefinite. Option B is wrong because the Natural Language API does not accept a custom sentiment dictionary; it only supports a static, built-in sentiment model, and passing a dictionary is not a supported feature. Option C is wrong because building a custom TensorFlow model requires significant coding effort, including data preprocessing, model architecture design, training, and deployment, which contradicts the goal of minimizing coding effort.

Full explanation →

484

MCQhard

A machine learning engineer is deploying a TensorFlow model on an edge device with limited memory and compute. The model needs to perform inference with low latency. The engineer has a trained float32 model. Which model compression technique should be applied first to reduce the model size and improve inference speed without significant accuracy loss?

A.Post-training quantization to INT8

B.Knowledge distillation

C.Quantization-aware training

D.Weight pruning

AnswerA

This is the recommended first step for edge deployment.

Why this answer

Post-training quantization to INT8 is the correct first step because it directly reduces the model size by approximately 4x (from 32-bit floats to 8-bit integers) and speeds up inference on edge devices by leveraging integer-optimized hardware (e.g., ARM NEON or Qualcomm Hexagon). This technique requires no retraining and typically yields minimal accuracy loss for most TensorFlow models, making it the fastest path to deploy on resource-constrained devices.

Exam trap

Google Cloud often tests the misconception that quantization-aware training is always required for INT8 deployment, but the trap here is that post-training quantization is the simplest and most effective first step for reducing model size and latency on edge devices, with quantization-aware training reserved only for cases where accuracy drops below acceptable thresholds.

How to eliminate wrong answers

Option B (Knowledge distillation) is wrong because it requires training a smaller student model from scratch using the teacher model's outputs, which is computationally expensive and not a quick compression technique for an already trained model. Option C (Quantization-aware training) is wrong because it simulates quantization effects during training to preserve accuracy, but it requires retraining the model, making it a second step after post-training quantization if accuracy loss is unacceptable. Option D (Weight pruning) is wrong because it removes individual weights (often via magnitude-based pruning), which can reduce model size but typically requires retraining to recover accuracy and does not directly improve inference speed on standard edge hardware without sparse matrix support.

Full explanation →

485

MCQmedium

An organization uses Vertex AI Workbench user-managed notebooks and wants to enable collaboration where multiple data scientists can edit the same notebook simultaneously. Which configuration should they use?

A.Use Git to branch and merge notebooks, with a CI/CD pipeline to resolve conflicts.

B.Share the user-managed notebook instance by giving multiple users IAM roles to access the same JupyterLab instance.

C.Store the notebook in Cloud Storage and ask users to edit sequentially using gsutil cp.

D.Use a managed notebook instance (Colab Enterprise) and share the notebook via a link.

AnswerD

Managed notebooks support real-time collaboration.

Why this answer

Vertex AI Workbench user-managed notebooks do not support real-time collaboration. Managed notebooks (now upgraded to Colab Enterprise) support simultaneous editing via integration with Colab.

Full explanation →

486

MCQeasy

A team wants to share a trained model with another team who will deploy it to a different Google Cloud project. Which is the recommended way to transfer the model?

A.Copy the model artifact from one project's Cloud Storage to another using gsutil.

B.Export the model as a SavedModel, store in a shared Cloud Storage bucket, and import into the second project.

C.Package the model in a Docker container and push to a cross-project Container Registry.

D.Use Cloud Marketplace to publish the model.

E.Use Vertex AI Model Registry with cross-project IAM permissions to allow the second project to access the model.

AnswerE

Model Registry maintains version history and metadata while enabling cross-project sharing.

Why this answer

Vertex AI Model Registry supports cross-project access via IAM permissions, allowing the second project to directly deploy the model without copying artifacts. This approach maintains a single source of truth, avoids data duplication, and leverages Vertex AI's built-in versioning and lineage tracking. It is the recommended pattern for sharing models across projects in Google Cloud.

Exam trap

Google Cloud often tests the misconception that copying artifacts (gsutil) or using shared storage is the simplest approach, but the exam expects candidates to recognize that Vertex AI Model Registry with cross-project IAM is the recommended, managed solution for model sharing across projects.

How to eliminate wrong answers

Option A is wrong because copying model artifacts via gsutil bypasses Vertex AI's model management, losing metadata, versioning, and deployment history, and is not a recommended practice for production model sharing. Option B is wrong because exporting a SavedModel to a shared Cloud Storage bucket still requires manual import and does not leverage Vertex AI's model registry, leading to potential versioning and access control issues. Option C is wrong because packaging the model in a Docker container and pushing to a cross-project Container Registry is more appropriate for containerized inference services, not for sharing a trained model artifact itself, and adds unnecessary complexity.

Option D is wrong because Cloud Marketplace is designed for publishing commercial solutions, not for internal team-to-team model sharing within an organization.

Full explanation →

487

MCQmedium

You are A/B testing a new model version (challenger) against the current version (champion) on Vertex AI. You want to gradually shift traffic from champion to challenger while measuring business metrics. Which approach should you use?

A.Deploy the challenger to a separate endpoint and use a load balancer to route a percentage of requests.

B.Use Cloud Armor to route traffic based on headers.

C.Deploy both models to the same endpoint and use the traffic split feature to allocate percentages.

D.Create a new endpoint for the challenger and gradually shift DNS records.

AnswerC

Vertex AI allows multiple models on one endpoint with traffic allocation.

Why this answer

Vertex AI endpoints support traffic splitting between deployed models. By updating the traffic percentage, you can gradually shift traffic and monitor performance.

Full explanation →

488

MCQmedium

A data scientist notices that the prediction distribution of a deployed model has changed significantly over the past week. They want to identify which features are contributing most to the drift. Which approach should they use?

A.Use Vertex AI Explainability to get feature importance and identify which features have high importance and significant drift

B.Compute Pearson correlation between each feature's drift score and the model's prediction drift

C.Use Vertex AI Model Monitoring to compare training and serving distributions for each feature

D.Enable request/response logging to BigQuery and manually analyze feature distributions

AnswerA

Combining drift detection with feature importance pinpoints root cause features.

Why this answer

Vertex AI Explainability provides feature attributions (e.g., SHAP values) that can be used to correlate feature drift with model prediction changes.

Full explanation →

489

Multi-Selecthard

Your team has deployed a model on Vertex AI endpoints and you are planning an A/B test to compare a new challenger model (v2) against the current champion (v1). The test should measure business metrics such as click-through rate. Which THREE steps should you take to set up the A/B test correctly? (Choose 3 correct answers)

Select 3 answers

A.Deploy the challenger model (v2) to the same endpoint as the champion (v1).

B.Modify your application to log which model version served each prediction.

C.Create a new endpoint for v2 and gradually shift DNS traffic.

D.Use Vertex AI Experiments to compare model performance.

E.Set up a traffic split between v1 and v2, e.g., 90% v1 and 10% v2.

AnswersA, B, E

Both models must be on the same endpoint to use traffic splitting.

Why this answer

Deploying both v1 and v2 to the same Vertex AI endpoint allows you to use the built-in traffic splitting feature. This enables you to route a percentage of requests to each model version without managing separate endpoints or DNS changes, which is the standard approach for A/B testing on Vertex AI.

Exam trap

The trap here is that candidates confuse Vertex AI Experiments (for training) with endpoint traffic splitting (for serving), and they incorrectly think creating separate endpoints with DNS shifting is a valid A/B testing method, when Vertex AI's native traffic splitting is the correct and simpler approach.

Full explanation →

490

MCQhard

A machine learning engineer is scaling a prototype natural language processing model that uses a transformer encoder. The prototype was trained on a small corpus on a single GPU. For production, they need to train on a much larger corpus using TPUs on Vertex AI. They convert the TensorFlow code to work with TPUStrategy. The training starts but after a few steps, the loss becomes NaN and training diverges. The learning rate scheduler uses a warm-up and then linear decay. The initial learning rate is 1e-4. The batch size per TPU core is 32, with 8 cores total (batch size 256). What is the most likely cause?

A.The batch size is too small for TPU.

B.The learning rate is too high for the batch size.

C.The learning rate schedule should be cosine instead of linear.

D.The warm-up steps are insufficient.

AnswerB

Larger batch size requires lower learning rate to maintain stability.

Why this answer

When scaling from a single GPU to 8 TPU cores, the global batch size increases from 32 to 256. The learning rate of 1e-4, which was appropriate for batch size 32, becomes too high for the larger batch size. This violates the linear scaling rule (learning rate should be scaled proportionally to batch size), causing gradient updates to overshoot minima and leading to NaN loss and divergence.

Exam trap

Google Cloud often tests the misconception that TPU-specific issues (like batch size or hardware compatibility) are the root cause, when in fact the problem is a fundamental hyperparameter scaling error that applies to any distributed training setup.

How to eliminate wrong answers

Option A is wrong because TPUs are designed to handle large batch sizes efficiently; a batch size of 256 is well within typical TPU capabilities and is not the cause of NaN loss. Option C is wrong because the learning rate schedule (linear vs. cosine) is not the primary issue; the fundamental problem is the learning rate magnitude relative to the batch size, not the decay shape. Option D is wrong because insufficient warm-up steps might cause early instability but would not typically lead to persistent NaN loss after several steps; the core issue is the learning rate being too high for the increased batch size.

Full explanation →

491

MCQhard

You need to create a reproducible snapshot of a BigQuery table as of a specific timestamp for ML model training. The snapshot should be queryable without copying the entire dataset. Which BigQuery feature should you use?

A.BigQuery export to Cloud Storage as Parquet

B.BigQuery time travel (FOR SYSTEM_TIME AS OF)

C.CREATE TABLE AS SELECT with WHERE clause

D.BigQuery table snapshots

AnswerD

Snapshots provide a point-in-time, queryable copy that persists beyond 7 days.

Why this answer

BigQuery table snapshots create a read-only copy of a table at a specific point in time, queryable without additional storage costs for the data. Time travel queries access historical data but are limited to 7 days, and copying to a new table duplicates storage.

Full explanation →

492

MCQeasy

A data science team deploys a regression model to predict house prices. After one month, the mean absolute error (MAE) on the serving data increases by 20% compared to the test set. Which monitoring strategy should the team implement first to diagnose the issue?

A.Retrain the model daily with the latest data to adapt to changing patterns.

B.Monitor prediction residuals and compute serving-time MAE over sliding windows.

C.Compare the distribution of training labels with serving labels using a two-sample t-test.

D.Monitor input feature distributions for drift using the Kolmogorov-Smirnov test.

AnswerB

Directly tracking MAE on serving data over time is the most straightforward diagnostic for performance degradation.

Why this answer

The first step in diagnosing a 20% MAE increase on serving data is to monitor prediction residuals over sliding windows. This directly tracks how model errors evolve in production, allowing the team to detect whether performance degradation is sudden or gradual, and to correlate it with specific time windows or data slices. Computing serving-time MAE on sliding windows provides an immediate, interpretable signal of model health without assuming the root cause.

Exam trap

Google Cloud often tests the misconception that the first step in diagnosing model degradation is to check for data drift (Option D), when in fact the correct first step is to confirm and quantify the performance drop itself using serving-time metrics like sliding-window MAE.

How to eliminate wrong answers

Option A is wrong because retraining daily without first diagnosing the cause of the MAE increase is a reactive, resource-intensive approach that may mask underlying issues like data drift or concept drift, and does not help identify whether retraining is even necessary. Option C is wrong because comparing training labels with serving labels using a two-sample t-test checks for label distribution shift, but the MAE increase could be due to feature drift, concept drift, or data quality issues unrelated to label distribution; this test is too narrow and may miss the actual cause. Option D is wrong because monitoring input feature distributions for drift using the Kolmogorov-Smirnov test is a valid technique, but it is a secondary diagnostic step; the first priority should be to confirm and characterize the performance degradation itself via residual monitoring before investigating potential causes.

Full explanation →

493

MCQmedium

You are setting up feature monitoring in Vertex AI Feature Store to detect drift in a numerical feature. The monitoring job should run daily and alert if the Jensen-Shannon divergence exceeds 0.1. Which configuration should you use?

A.Configure feature monitoring in the feature view with a drift threshold of 0.1 using Jensen-Shannon divergence

B.Use BigQuery scheduled queries to compare distributions and send alerts

C.Set up a Cloud Composer DAG to compute drift and publish to Cloud Monitoring

D.Enable model monitoring on the Vertex AI endpoint to detect drift

AnswerA

Vertex AI Feature Store allows setting drift thresholds per feature view, using methods like JS divergence.

Why this answer

Feature monitoring in Vertex AI Feature Store uses monitoring_config with drift detection via statistical tests like Jensen-Shannon divergence. The correct approach is to set the drift threshold in the feature view's monitoring configuration.

Full explanation →

494

MCQhard

An ML team uses Vertex AI Pipelines to automate model retraining. The pipeline includes a step that queries BigQuery to create a training dataset. The team notices that the pipeline fails intermittently with a '403 Exceeded rate limits' error. What is the most likely cause and solution?

A.The pipeline is issuing too many concurrent queries; use a BigQuery reservation to guarantee slot capacity

B.The training dataset is too large; partition the table and query only the latest partition

C.The pipeline step timeout is too short; increase the timeout to 30 minutes

D.The SQL query is inefficient; rewrite it using materialized views

AnswerA

Reservations provide dedicated slots, avoiding API rate limits.

Why this answer

The 403 'Exceeded rate limits' error in BigQuery indicates that the project is hitting the concurrent query rate limit or the rate of bytes read per second. Using a BigQuery reservation guarantees dedicated slot capacity, which prevents rate-limit errors by ensuring the pipeline has consistent compute resources regardless of other workloads in the project. This is the most direct solution because rate limits are enforced at the project level based on available slots, and a reservation provides a fixed number of slots that bypass those limits.

Exam trap

The trap here is that candidates confuse rate-limit errors with performance or timeout issues, and they choose options that optimize query cost or size (B, D) or adjust timeouts (C), instead of recognizing that a 403 error specifically points to a quota or rate-limit violation that requires resource allocation like a reservation.

How to eliminate wrong answers

Option B is wrong because a large dataset does not cause a 403 rate-limit error; it would cause a 'resources exceeded' or timeout error, not a rate-limit error. Partitioning and querying only the latest partition could reduce bytes processed but does not address the rate limit on concurrent queries or slot usage. Option C is wrong because a timeout error would manifest as a deadline exceeded or 504 error, not a 403 rate-limit error; increasing the timeout does not resolve rate-limiting.

Option D is wrong because an inefficient SQL query would cause high slot consumption or slow performance, but the error is specifically about rate limits, not query efficiency; materialized views could reduce query cost but do not change the project-level rate limit enforcement.

Full explanation →

495

MCQmedium

A data scientist uses Vertex AI Workbench to train a model and then deploys it to an endpoint. They want to automate the retraining and redeployment pipeline when new data arrives. Which service should they use?

A.Cloud Composer

B.Vertex AI Pipelines

C.Cloud Scheduler

D.Cloud Functions

AnswerB

Vertex AI Pipelines is purpose-built for ML workflows, allowing easy automation of retraining and redeployment.

Why this answer

(Vertex AI Pipelines) is correct because Vertex AI Pipelines is a serverless, managed pipeline orchestration service that can automate retraining and redeployment pipelines when new data arrives. Option A (Cloud Composer) is a workflow orchestration service but is more complex and not as integrated with Vertex AI. Option C (Cloud Scheduler) is for scheduled jobs, not event-driven retraining.

Option D (Cloud Functions) is event-driven but lacks the pipeline capabilities needed for a full retraining and redeployment workflow.

Full explanation →

496

MCQmedium

A company needs to run batch predictions on 10 TB of data stored in Cloud Storage. The predictions should be written to BigQuery. Which approach should they use?

A.Export the model to Cloud Functions and trigger on file upload

B.Create a Vertex AI Batch Prediction job with GCS input and BigQuery output

C.Use Vertex AI Online Prediction with a batch job

D.Use Dataflow to read from GCS and write to BigQuery, calling the model for each record

AnswerB

Batch Prediction directly supports this configuration.

Why this answer

Vertex AI Batch Prediction natively supports reading input from Cloud Storage and writing predictions directly to BigQuery, making it the most efficient and fully managed solution for large-scale batch inference on 10 TB of data. This approach avoids the complexity of custom infrastructure or per-record model calls, leveraging Vertex AI's optimized batch processing pipeline.

Exam trap

This question tests the distinction between batch and online prediction modes in Vertex AI. The trap is that candidates may confuse Vertex AI's batch prediction with using Dataflow or Cloud Functions, not realizing that Vertex AI natively supports BigQuery as a direct output destination for batch jobs.

How to eliminate wrong answers

Option A is wrong because Cloud Functions are designed for event-driven, lightweight processing and cannot handle 10 TB of data efficiently; exporting a model to Cloud Functions also lacks native batch prediction orchestration and BigQuery output support. Option C is wrong because Vertex AI Online Prediction is intended for real-time, low-latency inference on individual requests, not for batch jobs; there is no 'batch job' mode within online prediction. Option D is wrong because while Dataflow can read from GCS and write to BigQuery, calling the model for each record would require custom code and per-record inference, which is less efficient and more complex than using Vertex AI's built-in batch prediction with direct BigQuery output.

Full explanation →

497

Multi-Selecteasy

A company uses Vertex AI Pipelines for ML training. They want to implement continuous training triggered by new data arrival. Which two Google Cloud services should they use to achieve this? (Choose two.)

Select 2 answers

A.Cloud Functions

B.Cloud Scheduler

C.Cloud Storage

D.Vertex AI Experiments

E.Cloud Composer

AnswersA, C

Cloud Functions can be triggered by GCS events and start a Vertex AI pipeline.

Why this answer

Cloud Functions is correct because it can be triggered directly by Cloud Storage events (e.g., object finalize/create) to start a Vertex AI Pipeline run when new data arrives, enabling event-driven continuous training without manual intervention. Cloud Storage is correct because it serves as the source of new data and its event notifications (via Pub/Sub) are the trigger mechanism that Cloud Functions subscribes to, forming the core event-driven architecture.

Exam trap

Google often tests the distinction between event-driven triggers (Cloud Functions + Cloud Storage) and time-based schedulers (Cloud Scheduler), leading candidates to incorrectly select Cloud Scheduler when the requirement is 'triggered by new data arrival' rather than 'run at a specific time'.

Full explanation →

498

MCQhard

A media company wants to build a real-time recommendation system for articles. They have a large user base (10M+) and frequent updates to user interactions. They need to handle cold-start users and new articles. Which architecture on Vertex AI is most suitable?

A.Deploy a Deep Learning Recommendation Model (DLRM) for prediction

B.Use a contextual bandit algorithm for exploration only

C.Use matrix factorization with collaborative filtering

D.Implement a two-tower model (user and item towers) with embeddings and nearest neighbor search

AnswerD

Two-tower models can incorporate side features and enable fast retrieval.

Why this answer

The two-tower model (user and item towers) with embeddings and nearest neighbor search is the most suitable because it handles cold-start users and new articles by learning separate embeddings for users and items, enabling efficient retrieval via approximate nearest neighbor (ANN) search. This architecture supports real-time updates and scales to 10M+ users by decoupling user and item representations, allowing incremental training on new interactions without full retraining.

Exam trap

Google Cloud often tests the misconception that matrix factorization (Option C) is sufficient for cold-start scenarios, but candidates miss that it requires retraining on new data and cannot generate embeddings for unseen users or items without side features.

How to eliminate wrong answers

Option A is wrong because DLRM is a deep learning model for click-through rate prediction that requires retraining on new data and does not natively handle cold-start items or users without additional feature engineering, making it less suitable for frequent updates and real-time recommendation. Option B is wrong because a contextual bandit algorithm for exploration only lacks exploitation of known user preferences, leading to suboptimal recommendations over time, and does not provide a full recommendation system. Option C is wrong because matrix factorization with collaborative filtering cannot handle cold-start users or new articles without retraining the entire model, as it relies on existing interaction matrices and lacks a mechanism for incorporating new entities in real time.

Full explanation →

499

MCQmedium

A team uses Vertex AI Feature Store for online serving. They notice high latency during peak hours. They have configured the feature store with Bigtable as the online serving store. What is the most likely cause of the high latency?

A.The Bigtable cluster has too many nodes.

B.Feature data is stored as Avro files.

C.The online serving node count is insufficient for the QPS.

D.Feature values are not pre-cached.

AnswerC

Insufficient nodes cause queuing and higher latency under load.

Why this answer

Vertex AI Feature Store uses Bigtable as the online serving store, and during peak hours, high query-per-second (QPS) loads can overwhelm the serving nodes if they are under-provisioned. Insufficient node count leads to queuing and increased latency, as Bigtable's performance scales linearly with the number of nodes for read throughput. The most direct remedy is to increase the number of Bigtable nodes to match the QPS demand.

Exam trap

The trap here is that candidates may confuse Bigtable's scaling model with caching solutions (like Redis or Memorystore) and incorrectly assume that pre-caching (Option D) is the fix, when in fact the root cause is insufficient node count for the QPS load.

How to eliminate wrong answers

Option A is wrong because having too many Bigtable nodes would reduce latency, not increase it, as more nodes provide higher read throughput and lower queue depth. Option B is wrong because Avro files are used for offline batch storage or export, not for the online serving store, which uses Bigtable's native storage format; Avro files do not affect online latency. Option D is wrong because Bigtable does not support pre-caching of feature values in the same way as an in-memory cache; the latency issue is due to insufficient node count, not a missing caching mechanism.

Full explanation →

500

MCQeasy

What does the `ML.PREDICT` command do in BigQuery ML?

A.Trains a new BigQuery ML model

B.Exports the model to Cloud Storage

C.Evaluates the model's performance

D.Makes predictions using the model

AnswerD

ML.PREDICT generates predictions.

Why this answer

The command is likely a BigQuery ML prediction query (e.g., using `ML.PREDICT`) that uses a trained model to generate predictions on new input data, making option D correct. It does not train, export, or evaluate the model.

Exam trap

Google Cloud often tests the distinction between the four key BigQuery ML commands (`CREATE MODEL`, `ML.EVALUATE`, `ML.PREDICT`, `EXPORT MODEL`), and the trap here is confusing the prediction function with the evaluation function, especially when the exhibit shows a query that looks like it might be evaluating performance due to the presence of a model name and input data.

How to eliminate wrong answers

Option A is wrong because training a new BigQuery ML model uses the `CREATE MODEL` statement, not the `ML.PREDICT` function. Option B is wrong because exporting a model to Cloud Storage uses the `EXPORT MODEL` statement, not a prediction query. Option C is wrong because evaluating model performance uses the `ML.EVALUATE` function, which returns metrics like loss and accuracy, not predictions.

Full explanation →

501

Multi-Selectmedium

Which TWO tools can be used to collaborate on feature definitions across teams?

Select 2 answers

A.Cloud Storage

B.Vertex AI Feature Store

C.Cloud Logging

D.Cloud Build

E.Data Catalog

AnswersB, E

Feature Store provides a central repository for features that teams can share.

Why this answer

The correct options are B (Vertex AI Feature Store) and E (Data Catalog). Vertex AI Feature Store allows teams to share and reuse feature definitions across projects. Data Catalog provides metadata management and can catalog feature definitions, making them discoverable and understandable across teams.

Cloud Storage (A) is a blob storage service, not a feature collaboration tool. Cloud Build (D) is for CI/CD pipelines. Cloud Logging (C) is for log management.

Full explanation →

502

Multi-Selectmedium

Which TWO of the following are recommended methods to ensure data privacy when collaborating with external partners on ML projects?

Select 2 answers

A.Use Vertex AI Feature Store with access controls.

B.Use Cloud DLP to de-identify data before sharing.

C.Grant the partner project's service account direct access to the raw data in BigQuery.

D.Use Confidential VMs for training with sensitive data.

E.Share data via email.

AnswersB, D

DLP can redact, tokenize, or mask sensitive data.

Why this answer

Cloud DLP (Data Loss Prevention) is a recommended method to de-identify sensitive data before sharing it with external partners. It can automatically detect and mask, tokenize, or redact PII, PCI, or other sensitive elements, ensuring that only anonymized data leaves your environment. This aligns with the principle of least privilege and data minimization for external collaboration.

Exam trap

Google Cloud often tests the misconception that access controls alone (like IAM or Feature Store ACLs) are sufficient for data privacy with external partners, but the key requirement is de-identification or encryption in use, not just authorization.

Full explanation →

503

MCQmedium

You need to deploy a PyTorch model for online inference on Vertex AI but the model was trained using custom ops that are not natively supported. You want to use NVIDIA Triton Inference Server for optimisation. How should you proceed?

A.Convert the model to TFLite and deploy on an edge device.

B.Build a custom container with NVIDIA Triton Inference Server and deploy it to Vertex AI.

C.Export the model to ONNX and deploy using Vertex AI's built-in TensorFlow serving.

D.Use Vertex AI Model Optimisation to automatically quantise the model.

AnswerB

Correct. Custom containers allow using Triton with arbitrary models.

Why this answer

Vertex AI supports deploying models with NVIDIA Triton Inference Server. You can build a custom container with Triton and the model, then deploy it to a Vertex AI endpoint. This allows using Triton's optimisations.

Full explanation →

504

MCQeasy

A data engineer wants to orchestrate a complex workflow that includes running a Vertex AI pipeline, then a BigQuery job, and finally a Dataflow pipeline. The workflow must handle dependencies, retries, and monitoring. Which Google Cloud service is most suitable for this orchestration?

A.Cloud Tasks

B.Cloud Composer

C.Cloud Scheduler

D.Workflows

AnswerB

Correct: Cloud Composer (Airflow) provides DAG-based orchestration with operators for all mentioned services.

Why this answer

Cloud Composer (based on Apache Airflow) is the most suitable service for orchestrating a complex workflow with dependencies, retries, and monitoring across Vertex AI, BigQuery, and Dataflow. It provides a managed Airflow environment that natively supports DAG-based orchestration, built-in retry logic, and integration with Google Cloud services via operators like VertexAIPipelineOperator, BigQueryOperator, and DataflowTemplatedJobStartOperator.

Exam trap

A common misconception is that Workflows is sufficient for complex ML orchestration, but it lacks the built-in operator integrations and retry semantics that Cloud Composer provides for multi-service pipelines.

How to eliminate wrong answers

Option A is wrong because Cloud Tasks is a distributed task queue for executing discrete, short-lived tasks with HTTP endpoints, not for orchestrating multi-step workflows with complex dependencies and retries across different services. Option C is wrong because Cloud Scheduler is a cron-based job scheduler that triggers single events at specified times, lacking the ability to manage dependencies between multiple pipeline stages or handle retries. Option D is wrong because Workflows is a low-code orchestration service for sequential or parallel steps, but it does not natively support the rich operator ecosystem, retry policies, or monitoring capabilities that Cloud Composer provides for ML pipelines involving Vertex AI, BigQuery, and Dataflow.

Full explanation →

505

MCQmedium

An ML engineer needs to run batch predictions on 10 TB of data stored in BigQuery using a TensorFlow model. The predictions must be written to BigQuery. Which service should they use?

A.Create a Dataflow pipeline to read from BigQuery, run the model using Python, and write results to BigQuery.

B.Export BigQuery data to GCS, run batch prediction on GCS, then load results back to BigQuery.

C.Use Vertex AI online prediction with batch requests.

D.Use Vertex AI Batch Prediction with BigQuery source and sink.

AnswerD

Correct: Vertex AI Batch Prediction supports BigQuery directly for both input and output.

Why this answer

Vertex AI Batch Prediction supports BigQuery as both source and sink, enabling direct batch prediction without additional infrastructure.

Full explanation →

506

MCQeasy

A data science team uses Vertex AI Pipelines to build a training pipeline. They notice that when the pipeline fails due to a transient error in a component, the entire pipeline restarts from the beginning, taking a long time. What is the best practice to handle transient errors efficiently?

A.Use Vertex AI Experiment to track runs and manually restart failed components.

B.Configure Vertex AI Pipelines to automatically restart from the last successful state by enabling checkpointing.

C.Wrap the component code in a try-except block and retry indefinitely.

D.Set the component's retry count to 3 in the pipeline definition.

AnswerB

Checkpointing allows the pipeline to resume from the last successful state, minimizing rerun time.

Why this answer

Vertex AI Pipelines supports checkpointing, which allows a pipeline to resume from the last successful state after a transient failure, avoiding a full restart. This is the most efficient approach for handling transient errors in a managed pipeline service, as it minimizes wasted compute time and resources.

Exam trap

The trap here is that candidates often confuse simple retry logic (Option D) with stateful checkpointing, assuming that retrying a component a few times is sufficient, but they miss that checkpointing preserves the pipeline's progress across failures, which is critical for long-running pipelines.

How to eliminate wrong answers

Option A is wrong because Vertex AI Experiment is designed for tracking and comparing runs, not for automating recovery from transient errors; manually restarting failed components defeats the purpose of automation and is inefficient. Option C is wrong because wrapping component code in a try-except block with indefinite retries can lead to infinite loops, resource exhaustion, and does not leverage the pipeline's orchestration capabilities for stateful recovery. Option D is wrong because setting a retry count of 3 in the pipeline definition only retries the failed component from scratch, not from the last successful state, which still wastes time if the component has long-running steps.

Full explanation →

507

MCQmedium

A company deploys a batch prediction job on Vertex AI using a custom container. The job completes successfully, but the predictions are later found to be inaccurate. The ML engineer wants to set up monitoring to detect similar issues proactively. Which approach should the engineer take?

A.Use Cloud Monitoring to create a custom metric for prediction confidence and set an alert when confidence drops below 0.8.

B.Use Cloud Logging to export prediction requests and responses, then create a metric based on prediction count.

C.Export batch predictions to BigQuery, and use Vertex AI Model Monitoring to compare prediction distributions against a baseline.

D.Enable Cloud Audit Logs to track when the batch prediction job runs and analyze the logs for anomalies.

AnswerC

Model Monitoring detects drift by comparing predictions to a baseline.

Why this answer

Vertex AI Model Monitoring can compare the distribution of batch prediction outputs (stored in BigQuery) against a baseline distribution to detect data drift or skew, which is the most direct way to proactively identify prediction inaccuracies. This approach monitors the statistical properties of predictions over time, catching shifts that could cause accuracy degradation even when the job runs successfully.

Exam trap

The trap here is that candidates assume monitoring prediction confidence or logging request counts is sufficient for detecting inaccuracies, but the PMLE exam specifically tests the concept of distribution drift monitoring as the correct proactive approach for batch prediction quality.

How to eliminate wrong answers

Option A is wrong because prediction confidence is a model-specific output (e.g., softmax probabilities) that may not exist for all models (e.g., regression models), and a fixed threshold of 0.8 is arbitrary; the question requires detecting inaccuracies proactively, not monitoring a single confidence score. Option B is wrong because exporting prediction requests/responses to Cloud Logging and creating a metric based on prediction count only tracks volume, not prediction quality or drift; count metrics cannot detect inaccuracies. Option D is wrong because Cloud Audit Logs track administrative actions (e.g., who ran the job), not the prediction data itself; analyzing audit logs for anomalies would not reveal prediction inaccuracies.

Full explanation →

508

MCQmedium

A team uses Vertex AI Workbench managed notebooks. They want to version control their notebook files and collaborate using Git. What is the best way to integrate Git?

A.Use Cloud Source Repositories only

B.Use the built-in Git integration in Vertex AI Workbench managed notebooks

C.Use gcloud source repos clone inside the terminal

D.Manually download notebooks and upload to GitHub via browser

AnswerB

Direct integration simplifies version control.

Why this answer

Vertex AI Workbench managed notebooks support direct Git integration via the user interface, allowing clone, commit, and push operations.

Full explanation →

509

MCQmedium

A company has a TensorFlow model for image classification that must run on edge devices with limited memory. They need to reduce the model size without significant accuracy loss. Which technique should they use?

A.Post-training quantization using TensorFlow Lite.

B.Knowledge distillation to train a smaller student model.

C.Pruning the model weights to zero out unimportant connections.

D.Use a larger VM for training.

AnswerA

TFLite quantization reduces size and latency, suitable for edge devices.

Why this answer

Post-training quantization (e.g., INT8) reduces model size and speeds up inference with minimal accuracy loss. It is the simplest method for deployment on edge devices.

Full explanation →

510

MCQeasy

You want to use Vertex AI JumpStart to quickly deploy a pre-built foundation model for text summarization. Which action is required?

A.Select the model from Model Garden and deploy it to a Vertex AI endpoint

B.Train the model from scratch using Vertex AI Training

C.Export the model to a Cloud Storage bucket and use batch prediction

D.Build a custom Docker container with the model and deploy to Vertex AI

AnswerA

JumpStart allows selecting and deploying foundation models directly.

Why this answer

JumpStart provides one-click deployment of foundation models from Model Garden. You select a model and deploy it to an endpoint. No custom training or container building is needed.

Full explanation →

511

MCQhard

You are troubleshooting a Vertex AI endpoint for a customer. The exhibit shows the endpoint configuration. The customer reports that Model A is experiencing high latency during peaks. Model B runs fine. What is the most likely cause?

A.Model A is not autoscaling properly due to minReplicaCount=1.

B.Model A's machine type has insufficient CPU and GPU for the load.

C.Dedicated endpoint is disabled, causing resource sharing between models.

D.The traffic split is unevenly balanced, causing Model A to receive more requests.

AnswerB

Model A uses n1-standard-4 with 1 GPU, while Model B uses n1-standard-8 with 2 GPUs.

Why this answer

Model A has only one GPU and fewer CPU cores compared to Model B. During high traffic, Model A's resources become a bottleneck. The traffic split is equal, so both get similar load, but Model A's hardware is weaker.

Full explanation →

512

MCQhard

A financial services company uses Vertex AI to build credit risk models. They have a team of 10 data scientists and 3 ML engineers. They use multiple notebooks in Vertex AI Workbench, storing data in Cloud Storage and BigQuery. The team reports that training jobs sometimes fail with 'Permission denied' errors when reading from certain Cloud Storage buckets. The error occurs intermittently and only for some users. The team uses custom service accounts for each user's notebook instance, but the permissions seem inconsistent. The IT security team has enforced that all service accounts must have least privilege. What is the most effective course of action to resolve the permission issues while maintaining security?

A.Create a single service account with broad permissions for all notebook instances and have users impersonate it.

B.Implement resource-level IAM policies on the specific Cloud Storage buckets used, and audit the existing service account permissions.

C.Grant all data scientists the 'Storage Admin' role on the project to ensure they can access any bucket.

D.Move all training data to BigQuery to avoid Cloud Storage permission issues.

AnswerB

Resource-level policies allow fine-grained control while maintaining least privilege.

Why this answer

Implementing resource-level IAM policies on the specific Cloud Storage buckets ensures that only the necessary permissions are granted, adhering to least privilege. Auditing existing service account permissions helps identify inconsistencies and ensure proper configuration. Option A is incorrect because a single service account with broad permissions violates least privilege and centralizes risk.

Option C is incorrect because granting Storage Admin is an overly permissive role. Option D is incorrect because moving data to BigQuery does not address the core permission issue and may introduce architectural complexity.

Full explanation →

513

MCQmedium

A company needs to perform sentiment analysis on streaming social media data. Which architecture should they use?

A.Dataflow → Pub/Sub → Natural Language API → BigQuery

B.Pub/Sub → Cloud Functions → Natural Language API → Cloud Storage

C.Cloud Functions → Pub/Sub → Natural Language API → BigQuery

D.Pub/Sub → Dataflow → Natural Language API → BigQuery

AnswerD

This is the recommended architecture for streaming analytics.

Why this answer

Streaming social media data requires a scalable, ordered ingestion pipeline. Pub/Sub ingests the stream, Dataflow processes it in real-time (e.g., windowing, deduplication), the Natural Language API performs sentiment analysis, and BigQuery stores results for querying. This decouples ingestion from processing and storage, enabling exactly-once semantics and auto-scaling.

Exam trap

Google Cloud often tests the misconception that Cloud Functions can replace Dataflow for streaming pipelines, but Cloud Functions lacks stream processing primitives (e.g., windowing, state management) and has a 9-minute timeout, making it unsuitable for continuous sentiment analysis.

How to eliminate wrong answers

Option A is wrong because Dataflow cannot directly read from a streaming source without a buffer like Pub/Sub; placing Dataflow before Pub/Sub reverses the pipeline order and breaks stream ingestion. Option B is wrong because Cloud Functions is not designed for high-throughput streaming; it has a 9-minute timeout and no built-in stream processing (e.g., windowing), making it unsuitable for continuous social media data. Option C is wrong because Cloud Functions should not be the entry point for streaming data; it lacks Pub/Sub's durability and ordering guarantees, and placing Pub/Sub after Cloud Functions would lose the stream before processing.

Full explanation →

514

MCQeasy

When distributing training across multiple workers using Vertex AI Training, how should the team share the training dataset?

A.Copy the dataset to each worker's local disk

B.Use NFS

C.Use Cloud Storage

D.Use Google Drive

AnswerC

Cloud Storage provides scalable, shared access to training data.

Why this answer

Vertex AI Training workers need shared, concurrent read access to the training dataset without manual replication. Cloud Storage (GCS) is the recommended and fully integrated solution because it provides a distributed, highly available object store that all workers can read from in parallel via the `tf.io.gfile` API or GCS connector, eliminating data duplication and ensuring consistency across the cluster.

Exam trap

The trap here is that candidates confuse 'shared storage' with 'local copies' or 'user-friendly sync tools,' assuming NFS or Drive are viable for distributed ML, when Vertex AI explicitly requires a cloud-native object store like GCS for scalability and fault tolerance.

How to eliminate wrong answers

Option A is wrong because copying the dataset to each worker's local disk introduces data duplication, increases startup latency, and risks inconsistency if workers are preempted or auto-scaled; Vertex AI does not manage local disk replication. Option B is wrong because NFS (Network File System) is not natively supported in Vertex AI Training; it would require manual setup of an NFS server, introduces a single point of failure, and adds network latency that GCS avoids with its native parallel read capabilities. Option D is wrong because Google Drive is a user-facing file sync service, not designed for high-throughput, concurrent access by distributed training jobs; it lacks the necessary IAM integration, access controls, and performance guarantees for ML workloads.

Full explanation →

515

MCQmedium

A team uses Cloud Build to automatically trigger a Vertex AI pipeline when changes are pushed to the model code repository. They have a cloudbuild.yaml file that builds a container image and submits the pipeline. However, they want to run the pipeline only if the commit includes changes to the 'training/' directory. Which Cloud Build configuration option should be used to filter the trigger?

A.Add a 'ignoreFiles' field with 'training/**' to the trigger.

B.Use a 'substitutions' field with a regex pattern to filter commits.

C.Configure a Cloud Function to check the commit diff and call Cloud Build API conditionally.

D.Set the 'includedFiles' field to 'training/**' in the trigger configuration.

AnswerD

Correct: includedFiles filters to only trigger when files under training/ are changed.

Why this answer

Cloud Build triggers support an `includedFiles` field that specifies a glob pattern. When set to `training/**`, the trigger will only fire if the commit includes changes to files under the `training/` directory. This is the native, declarative way to filter triggers based on changed file paths without additional infrastructure.

Exam trap

The trap here is that candidates confuse `ignoreFiles` with `includedFiles`, or assume that a custom solution like Cloud Functions is required when Cloud Build already provides a native, simpler mechanism for path-based filtering.

How to eliminate wrong answers

Option A is wrong because `ignoreFiles` excludes commits that match the pattern, but the requirement is to run the pipeline only when changes occur in `training/`, not to ignore them. Option B is wrong because `substitutions` are used for variable replacement in build configuration, not for filtering trigger conditions based on file changes. Option C is wrong because while a Cloud Function could achieve this, it introduces unnecessary complexity and cost; Cloud Build triggers natively support file path filtering via `includedFiles`, making a separate function an anti-pattern.

Full explanation →

516

MCQhard

A financial services company uses Vertex AI to deploy multiple models for fraud detection. The ML team has set up a CI/CD pipeline using Cloud Build and Cloud Deploy. The pipeline builds a custom container with the trained model, pushes it to Artifact Registry, and deploys it to a Vertex AI Endpoint. Recently, a new regulation requires that all model deployments be audited and approved by the compliance team before going live. The compliance team wants to review the model's evaluation metrics and approve the deployment via a ticketing system. Currently, the CI/CD pipeline automatically deploys after the container is built. The team needs to implement a gating process without slowing down the development cycle. What should they do?

A.Use Cloud Composer to orchestrate the deployment and add a sensor that waits for approval from the ticketing system via a custom operator.

B.Use Cloud Build's built-in approval gate feature to require compliance team sign-off before deployment.

C.Modify the CI/CD pipeline to use Cloud Deploy's approval gate feature, requiring a manual approval from the compliance team before the deployment step.

D.Store the model artifacts in Cloud Storage and have the compliance team deploy manually using the gcloud command.

AnswerC

Cloud Deploy supports manual approval gates integrated with the pipeline.

Why this answer

Cloud Deploy provides a native approval gate feature that can be inserted into a delivery pipeline to require manual sign-off before a deployment proceeds. This allows the compliance team to review model evaluation metrics and approve via a ticketing system without modifying the CI/CD pipeline's build process, thus maintaining development velocity. The approval gate pauses the deployment at a specific stage, waiting for an external approval signal, which integrates seamlessly with Cloud Deploy's rollout management.

Exam trap

The trap here is confusing Cloud Build's approval gates (which operate at the build stage) with Cloud Deploy's approval gates (which operate at the deployment stage), leading candidates to incorrectly select Option B despite it not addressing the deployment gating requirement.

How to eliminate wrong answers

Option A is wrong because Cloud Composer (based on Apache Airflow) is an orchestration tool for workflows, but adding a sensor for ticketing approval introduces unnecessary complexity and overhead, slowing down the development cycle compared to a native approval gate. Option B is wrong because Cloud Build's built-in approval gate feature is designed for build-level approvals (e.g., before pushing an image), not for deployment-stage gating; it would require restructuring the pipeline to pause the build process, which is not aligned with the requirement to gate deployment after the container is built. Option D is wrong because manual deployment via gcloud commands bypasses automation entirely, reintroducing delays and human error, contradicting the goal of not slowing down the development cycle.

Full explanation →

517

MCQmedium

A data engineer wants to use BigQuery ML to train a model for predicting customer churn (binary classification) using a large dataset. They want the model to be automatically tuned. Which model type should they choose?

A.LOGISTIC_REG

B.BOOSTED_TREE_CLASSIFIER

C.DNN_CLASSIFIER

D.AUTOML_CLASSIFIER

AnswerD

Why this answer

(AUTOML_CLASSIFIER) is correct because it automatically performs architecture search and hyperparameter tuning to find the best model for binary classification tasks, such as customer churn prediction. This is ideal when the data engineer wants the model to be automatically tuned without manual intervention, as AutoML handles feature engineering, model selection, and tuning under the hood.

Exam trap

The trap here is that candidates often confuse 'automatically tuned' with models that have default hyperparameters (like LOGISTIC_REG or BOOSTED_TREE_CLASSIFIER), but only AUTOML_CLASSIFIER performs automated hyperparameter tuning and architecture search without requiring manual specification.

How to eliminate wrong answers

Option A (LOGISTIC_REG) is wrong because logistic regression does not support automatic tuning; it requires manual specification of hyperparameters like learning rate or regularization, and it is a simpler linear model that may not capture complex patterns in large datasets. Option B (BOOSTED_TREE_CLASSIFIER) is wrong because while it can be tuned, it does not offer fully automatic tuning; the user must manually set parameters such as tree depth, learning rate, and number of iterations. Option C (DNN_CLASSIFIER) is wrong because deep neural network classifiers require manual tuning of architecture (e.g., number of layers, neurons) and hyperparameters (e.g., learning rate, batch size), and they do not automatically search for the optimal configuration.

Full explanation →

518

MCQhard

A financial institution needs to deploy a fraud detection model with strict latency <100ms per prediction and high throughput (1000 predictions/sec). The model is a deep neural network. Which architecture on Google Cloud meets these requirements?

A.Deploy the model on AI Platform Training with a single large VM

B.Deploy the model as a Cloud Function triggered by Cloud Pub/Sub

C.Use Vertex AI Batch Prediction with a fixed number of machines

D.Use Vertex AI Prediction with autoscaling enabled and GPU machine types

AnswerD

Vertex AI Prediction provides real-time endpoints with autoscaling and GPU support for low latency and high throughput.

Why this answer

Vertex AI Prediction with autoscaling and GPU machine types is correct because it provides low-latency online serving with autoscaling to handle high throughput (1000 predictions/sec) while keeping latency under 100ms. GPUs accelerate deep neural network inference, and autoscaling ensures resources match demand without over-provisioning.

Exam trap

Google Cloud often tests the distinction between batch and online prediction services, where candidates mistakenly choose batch prediction for real-time requirements because they focus on throughput without considering latency constraints.

How to eliminate wrong answers

Option A is wrong because AI Platform Training is designed for model training, not real-time serving, and a single large VM cannot guarantee sub-100ms latency under high throughput due to resource contention and lack of autoscaling. Option B is wrong because Cloud Functions have a maximum timeout of 9 minutes (540 seconds) and are not optimized for high-throughput, low-latency ML inference; they also lack GPU support, making deep neural network inference too slow. Option C is wrong because Vertex AI Batch Prediction is for asynchronous, offline predictions on large datasets, not real-time serving with strict latency requirements; it processes jobs in batches and cannot meet sub-100ms per prediction.

Full explanation →

519

MCQeasy

A data analyst wants to train a binary classification model on a BigQuery table without moving data out of BigQuery. They have limited ML expertise. Which approach should they take?

A.Use BigQuery ML with CREATE MODEL and LOGISTIC_REG model type.

B.Use Cloud Datalab to train an XGBoost model on BigQuery data.

C.Train a model using Vertex AI Workbench with a custom container.

D.Export the data to Cloud Storage and use Vertex AI AutoML Tables.

AnswerA

Why this answer

BigQuery ML allows users to create and train binary classification models directly on data in BigQuery using SQL, with no need to move data or have deep ML expertise. The LOGISTIC_REG model type implements logistic regression, a standard algorithm for binary classification, and the CREATE MODEL statement handles all the underlying training infrastructure, making it ideal for a data analyst with limited ML skills.

Exam trap

Google often tests the distinction between low-code/no-code solutions (like BigQuery ML) and more advanced, infrastructure-heavy approaches (like custom containers or AutoML with data export), expecting candidates to recognize that the simplest, most integrated option is correct when the user has limited ML expertise and wants to avoid data movement.

How to eliminate wrong answers

Option B is wrong because Cloud Datalab is a deprecated interactive notebook service that requires users to write custom code and manage infrastructure, which is not suitable for someone with limited ML expertise and does not leverage BigQuery's native ML capabilities. Option C is wrong because Vertex AI Workbench with a custom container demands advanced knowledge of containerization, model training pipelines, and infrastructure management, far beyond the scope of a low-code solution for a data analyst. Option D is wrong because exporting data to Cloud Storage and using Vertex AI AutoML Tables, while low-code, introduces unnecessary data movement and additional complexity compared to the simpler, fully integrated BigQuery ML approach that keeps data in place.

Full explanation →

520

Multi-Selecteasy

Which TWO of the following are low-code machine learning solutions on Google Cloud?

Select 2 answers

A.TensorFlow

B.scikit-learn

C.PyTorch

D.BigQuery ML

E.Vertex AI AutoML

AnswersD, E

BigQuery ML allows creating models using SQL.

Why this answer

BigQuery ML (D) is a low-code ML solution because it allows users to create, train, and deploy machine learning models using standard SQL queries directly within BigQuery, eliminating the need for custom coding in Python or other programming languages. Vertex AI AutoML (E) is also low-code as it provides a graphical interface and automated pipeline to train high-quality models with minimal manual intervention, handling feature engineering, model selection, and hyperparameter tuning automatically.

Exam trap

Google Cloud often tests the distinction between general-purpose ML frameworks (like TensorFlow, scikit-learn, PyTorch) that require significant coding versus managed services (BigQuery ML, AutoML) that provide low-code or no-code interfaces, leading candidates to mistakenly classify any ML tool on Google Cloud as low-code.

Full explanation →

521

Multi-Selectmedium

Which TWO actions are recommended for collaborating on machine learning models using Vertex AI Model Registry?

Select 2 answers

A.Use Cloud Storage object labels to store model descriptions.

B.Use version aliases such as 'champion' and 'challenger' to manage model lifecycle.

C.Deploy all model versions to a single endpoint for comparison.

D.Attach custom metadata (e.g., training dataset, hyperparameters) to each model version.

E.Create a separate model entry for each training run.

AnswersB, D

Aliases enable controlled promotion of models.

Why this answer

Vertex AI Model Registry supports version aliases like 'champion' and 'challenger' to designate which model version should serve as the production candidate and which is under evaluation, enabling controlled lifecycle management and A/B testing without manual version tracking.

Exam trap

Google Cloud often tests the distinction between a single model entry with multiple versions versus separate model entries per run, and candidates mistakenly think separate entries provide better traceability, but the registry's versioning and alias system is specifically designed to avoid that fragmentation.

Full explanation →

522

MCQmedium

A company wants to implement continuous delivery (CD) for ML models, where a model is automatically deployed to a staging environment and only promoted to production after passing an evaluation gate. Which combination of GCP services is BEST suited for orchestrating this CD pipeline?

A.Cloud Scheduler and Pub/Sub

B.Cloud Composer (Airflow) with Cloud Functions

C.Cloud Build with Vertex AI Pipelines and Cloud Deploy

D.Vertex AI Pipelines with Cloud Run

AnswerC

Cloud Build triggers the pipeline, Vertex AI Pipelines runs training/evaluation, and Cloud Deploy manages promotion to production.

Why this answer

Cloud Build can trigger on code/model changes and run a pipeline that deploys to staging. After evaluation, if successful, it can promote to production using Cloud Deploy or directly update Vertex AI endpoints. Cloud Composer (Airflow) is also a good option for complex orchestration, but for CI/CD, Cloud Build is a natural fit.

The combination of Cloud Build, Cloud Deploy, and Vertex AI provides a robust CD pipeline.

Full explanation →

523

MCQeasy

A company wants to classify support ticket text into categories. They have labeled historical tickets. Which Google Cloud service allows them to train a custom classification model with no code?

A.Vertex AI Matching Engine

B.AutoML Natural Language

C.Cloud Natural Language API

D.Document AI

AnswerB

Correct: No-code custom text classification.

Why this answer

AutoML Natural Language (now part of Vertex AI) is the correct service because it enables users to train custom text classification models using labeled data without writing any code. It provides a no-code interface for uploading datasets, training models, and evaluating performance, making it ideal for classifying support ticket text into custom categories.

Exam trap

The trap here is that candidates confuse the pre-trained Cloud Natural Language API (which requires no training but cannot be customized) with AutoML Natural Language (which requires labeled data but allows custom categories), leading them to select Option C incorrectly.

How to eliminate wrong answers

Option A is wrong because Vertex AI Matching Engine is designed for vector similarity search and embeddings, not for training custom classification models with labeled text data. Option C is wrong because Cloud Natural Language API is a pre-trained API that offers sentiment analysis, entity extraction, and syntax analysis, but it cannot be trained on custom labeled data for custom categories. Option D is wrong because Document AI is specialized for document processing (e.g., OCR, form parsing, invoice extraction) and is not intended for general text classification from labeled ticket data.

Full explanation →

524

MCQhard

Refer to the exhibit. An alert policy is configured to trigger when prediction latency exceeds 500 ms for 5 consecutive minutes. The team is experiencing many false positive alerts during brief latency spikes. Which adjustment would most effectively reduce false positives while still detecting prolonged latency issues?

A.Change the comparison to less than

B.Add a condition that CPU utilization is also high

C.Increase the duration to 30 minutes

D.Increase the threshold to 1000 ms

AnswerC

A longer duration means the condition must persist for 30 minutes, filtering out brief spikes while still catching sustained high latency.

Why this answer

Increasing the duration from 5 to 30 minutes (Option C) directly addresses the problem of false positives from brief latency spikes by requiring the latency to exceed 500 ms for a longer continuous period before triggering an alert. This ensures that only sustained, prolonged latency issues—not transient spikes—activate the policy, aligning with the goal of detecting genuine degradation while ignoring noise.

Exam trap

Google Cloud often tests the distinction between threshold and duration adjustments, trapping candidates who think raising the threshold (Option D) is the only way to reduce false positives, when in fact increasing the evaluation window is more precise for filtering out transient spikes without compromising detection of sustained issues.

How to eliminate wrong answers

Option A is wrong because changing the comparison to 'less than' would invert the logic, triggering alerts when latency is below 500 ms, which is the opposite of detecting high latency and would generate false positives for normal or low-latency conditions. Option B is wrong because adding a condition that CPU utilization is also high introduces an unnecessary dependency that may miss prolonged latency issues caused by other factors (e.g., network bottlenecks, memory pressure, or I/O wait), and it does not address the core problem of brief latency spikes. Option D is wrong because increasing the threshold to 1000 ms would allow sustained latency between 500 ms and 1000 ms to go undetected, failing to capture prolonged issues that still violate the original 500 ms requirement, and it does not filter out brief spikes.

Full explanation →

525

MCQeasy

A company needs to serve a model for real-time predictions with a strict latency SLA of 100ms at the 99th percentile. The model is lightweight and traffic patterns are highly variable with occasional spikes. Which deployment strategy best meets the SLA while controlling cost?

A.Deploy the model as a Cloud Run service with autoscaling to zero.

B.Deploy to Vertex AI Endpoint with manual scaling and a fixed number of replicas.

C.Use Vertex AI Batch Prediction.

D.Deploy to Vertex AI Endpoint with min_replica_count=3 and autoscaling enabled.

AnswerD

Min replicas provide baseline capacity to absorb spikes, and autoscaling adds replicas as needed.

Why this answer

Setting a minimum number of replicas ensures baseline capacity to handle initial spikes without cold start delays, while autoscaling handles larger spikes. Option A is wrong because Cloud Run with autoscaling to zero may cause cold start delays, which could violate the strict latency SLA. Option B is wrong because manual scaling with a fixed number of replicas may lead to over-provisioning or under-provisioning.

Option C is wrong because batch prediction is not real-time.

Full explanation →

Page 7 of 14

All pages

1 2 3 4 5 6 7 8 9 10 11 12 13 14

Practice PMLE by domain

Target a specific domain to shore up weak areas.

Automating and Orchestrating ML Pipelines Collaborating Within and Across Teams to Manage Data and Models Serving and Scaling Models Monitoring ML Solutions Architecting Low-Code ML Solutions Scaling Prototypes into ML Models Collaborating to manage data and models

See all domains with question counts →