Courseiva

Google Professional Machine Learning Engineer (PMLE) — Questions 1–75

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

Take a mock examExam hub

Page 1 of 14

Page 2
1
MCQmedium

A company needs to extract key fields from scanned invoices, such as invoice number and total amount, with high accuracy. They want a managed service and plan to use human review for low-confidence results. Which combination of services should they use?

A.Vision API and Natural Language API
B.Document AI and Human-in-the-Loop
C.Translation API and AutoML Vision
D.BigQuery ML and Vertex AI Prediction
AnswerB

Why this answer

Document AI provides specialized processors like invoice parser, and Human-in-the-Loop (HITL) can be integrated for low-confidence predictions. Vision API is generic OCR, Natural Language API is for text analysis, and Translation API is for language translation.

Full explanation →
2
Multi-Selectmedium

A company wants to analyze videos to detect objects and track their movement over time. Which TWO Google Cloud services are suitable for this task?

Select 2 answers
A.AutoML Vision
B.Speech-to-Text
C.AutoML Video
D.Video Intelligence API
E.Natural Language API
AnswersC, D

Why this answer

AutoML Video supports object tracking, and Video Intelligence API provides both object detection and tracking. AutoML Vision is for images only, Natural Language for text, and Speech-to-Text for audio.

Full explanation →
3
MCQeasy

Your team has deployed a scikit-learn model using a custom container on Vertex AI Prediction. The model receives about 100 requests per second, and the endpoint is configured with a single n1-standard-4 machine. You notice that response times are around 200 ms on average, but occasionally spike to over 10 seconds during traffic bursts. You have set the min replicas to 1 and max replicas to 10. Despite this, spikes still occur. What is the most likely cause and the best course of action?

A.The autoscaling is too slow to react; you should increase the max replicas to 20 and reduce the cooldown period.
B.The model is not optimized for parallel inference; you should enable batching in the custom container.
C.The machine type is insufficient for the model size; you should switch to a n1-highmem-8.
D.The container has a memory leak; you should restart the container periodically.
AnswerA

Reducing cooldown and increasing max replicas helps autoscaling respond faster to bursts.

Why this answer

The occasional spikes during traffic bursts indicate that the autoscaling is not reacting quickly enough. Increasing max replicas to 20 allows more room to scale, and reducing the cooldown period makes the autoscaler add replicas faster when load increases. This addresses the immediate spikes.

Full explanation →
4
MCQhard

A company uses BigQuery ML with a remote model calling Vertex AI's pre-trained image classification model. They need to classify images stored in Cloud Storage buckets. What is the correct approach?

A.Create a remote model with model_type='VERTEX_AI' and use ML.PREDICT with image URIs.
B.Train a custom model in BigQuery ML with image data.
C.Export images to BigQuery as base64 and then use ML.PREDICT.
D.Use ML.PREDICT with IMAGE data type directly.
AnswerA

Why this answer

BigQuery ML remote models allow you to invoke Vertex AI pre-trained models via the `model_type='VERTEX_AI'` setting. You can then use `ML.PREDICT` directly on Cloud Storage image URIs without needing to export or transform the image data, as BigQuery ML handles the URI resolution and passes the image to Vertex AI for classification.

Exam trap

Google often tests the misconception that BigQuery ML can handle unstructured data like images natively, leading candidates to choose options that involve base64 encoding or direct IMAGE data types, when the correct approach is to use remote models with URI references.

How to eliminate wrong answers

Option B is wrong because BigQuery ML does not support training custom image classification models natively; it is designed for tabular and structured data, not raw image pixel data. Option C is wrong because exporting images as base64 is unnecessary and inefficient; BigQuery ML remote models accept Cloud Storage URIs directly, and base64 encoding adds overhead without benefit. Option D is wrong because BigQuery ML does not have an IMAGE data type; image data is referenced via URIs, not stored as a native column type.

Full explanation →
5
MCQhard

A team uses Vertex AI Explainable AI with integrated gradients for a deep learning model. They want to reduce the computational cost of explanations without significantly reducing explanation quality. Which configuration change should they make?

A.Switch from integrated gradients to XRAI.
B.Reduce the number of integral approximation steps.
C.Apply feature attribution to only a random subset of predictions.
D.Use sampled Shapley instead, as it is always cheaper.
AnswerB

Fewer steps lower computation; optimal steps can be tuned.

Why this answer

Integrated gradients approximates Shapley values by integrating gradients along a path. Reducing the number of steps (integral approximation steps) reduces computation, but may reduce quality. A moderate reduction balances cost and quality.

Full explanation →
6
Drag & Dropmedium

Drag and drop the steps to implement a CI/CD pipeline for ML models using Cloud Build and Vertex AI in the correct order.

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

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

Why this order

In a CI/CD pipeline for ML models using Cloud Build and Vertex AI, the correct order is: first, configure the trigger (e.g., a Cloud Build trigger linked to a source repository), then define the pipeline (e.g., using Cloud Build configuration file or Vertex AI Pipelines), and finally commit code changes to trigger the automated training and deployment. This ensures that the trigger is set up to detect changes and the pipeline is defined before execution.

Exam trap

A common trap is to think that committing code should come first, but the pipeline and trigger must be defined beforehand.

Full explanation →
7
MCQmedium

You are configuring a Vertex AI Feature Store online store for a real-time recommendation system that requires single-digit millisecond latency and high throughput. The feature values are updated frequently. Which online store type should you use?

A.Spanner online store
B.Bigtable online store
C.Firestore online store
D.Optimized online store
AnswerD

Optimized online store uses Cloud Bigtable with automatic scaling and lower cost, ideal for high-throughput real-time systems.

Why this answer

The optimized online store (backed by Cloud Bigtable) is designed for high throughput, low latency, and frequent updates, making it suitable for real-time systems. Bigtable online store is the legacy option with similar performance but higher cost and manual scaling.

Full explanation →
8
Multi-Selecthard

You are tasked with building a robust ML pipeline that must be idempotent and handle data skew between training and serving. Which three practices should you implement?

Select 3 answers
A.Store intermediate data in Cloud Storage with unique run IDs.
B.Pass large datasets between components as serialized in-memory objects.
C.Monitor feature distributions in training data vs. serving data to detect skew.
D.Use the same random seed for every run to ensure reproducibility.
E.Ensure each component produces deterministic outputs given the same inputs.
AnswersA, C, E

Unique paths prevent collisions and support idempotency.

Why this answer

Idempotent components ensure the same inputs produce the same outputs. Passing data via GCS URIs is a best practice. Skew detection should compare training data distribution with serving data.

Using unique run IDs for outputs ensures idempotency. Avoiding in-memory data passing is important for large datasets.

Full explanation →
9
MCQmedium

You are deploying a PyTorch model for online predictions on Vertex AI. The model expects input tensors and performs GPU-accelerated inference. You want to minimize prediction latency and maximize throughput. Which approach should you use?

A.Package the model in a custom container without any inference server.
B.Deploy using a prebuilt PyTorch serving container with NVIDIA Triton Inference Server.
C.Use Vertex AI Model Optimization to quantize the model to FP16 and deploy using the optimized model.
D.Use batch prediction instead of online prediction to reduce latency.
AnswerB

Triton is optimized for GPU inference and can reduce latency and increase throughput.

Why this answer

NVIDIA Triton Inference Server provides advanced features like dynamic batching, concurrent model execution, and GPU scheduling that maximize throughput and minimize latency for GPU-accelerated inference. Vertex AI's prebuilt PyTorch serving container with Triton is specifically designed to handle online prediction workloads efficiently, outperforming a plain custom container without an inference server.

Exam trap

A common pitfall is assuming that model optimization alone (e.g., quantization) is sufficient for low-latency serving, when in fact the inference server's request handling and batching capabilities are critical for minimizing latency and maximizing throughput in online predictions on Vertex AI.

How to eliminate wrong answers

Option A is wrong because a custom container without any inference server lacks request batching, model queuing, and GPU utilization optimizations, leading to higher latency and lower throughput under concurrent requests. Option C is wrong because Vertex AI Model Optimization for FP16 quantization reduces model size and can improve throughput, but it does not address the serving infrastructure needed for low-latency online predictions; the deployment still requires an inference server like Triton to handle request management and GPU scheduling. Option D is wrong because batch prediction is designed for high-throughput, offline processing of large datasets and typically has higher latency per request due to job queuing and resource provisioning, making it unsuitable for minimizing prediction latency in online scenarios.

Full explanation →
10
Multi-Selectmedium

A company has a TensorFlow model that requires GPU for inference. They are deploying on Vertex AI. Which TWO configurations are necessary to ensure GPU is used?

Select 2 answers
A.Set the environment variable TF_GPU_ALLOCATOR=cuda_malloc_async.
B.Use the pre-built TensorFlow serving container, which automatically uses GPU if available.
C.Build a custom container with GPU drivers.
D.Select a machine type that includes a GPU (e.g., NVIDIA Tesla T4).
E.Set the accelerator type and count in the model deployment configuration.
AnswersD, E

Necessary to have GPU hardware available.

Why this answer

Vertex AI requires you to explicitly select a machine type that includes a GPU (e.g., n1-standard-4 with an attached NVIDIA Tesla T4) to provide the physical hardware for GPU acceleration. Without selecting a GPU machine type, the inference will run on CPU only, regardless of any other configuration.

Exam trap

Google Cloud often tests the misconception that simply using a pre-built container or setting environment variables is sufficient to enable GPU acceleration, when in fact you must both select a GPU-capable machine type and explicitly configure the accelerator in the deployment settings.

Full explanation →
11
MCQeasy

A data scientist has deployed a model on Vertex AI Endpoints and wants to monitor the model's predictions for any drift over time. Which Vertex AI service should they use?

A.Vertex AI Feature Store
B.Vertex AI Predictions
C.Vertex AI Explainable AI
D.Vertex AI Model Monitoring
AnswerD

Vertex AI Model Monitoring is designed for monitoring drift and skew in deployed models.

Why this answer

Vertex AI Model Monitoring is specifically designed to monitor deployed models for feature drift, feature skew, and prediction drift. It uses statistical methods to compare serving distributions over time or against training data.

Full explanation →
12
MCQmedium

A data engineer wants to use BigQuery ML to train a model that predicts customer churn using a table with customer features and a label column. They want to use a deep neural network. Which model type should they specify?

A.BOOSTED_TREE_CLASSIFIER
B.LOGISTIC_REG
C.DNN_CLASSIFIER
D.DNN_REGRESSOR
AnswerC

Why this answer

The DNN_CLASSIFIER model type in BigQuery ML is specifically designed for classification tasks using a deep neural network architecture. Since the problem is predicting customer churn (a binary classification problem) and the data engineer explicitly wants to use a deep neural network, DNN_CLASSIFIER is the appropriate choice.

Exam trap

The trap is that candidates may confuse DNN_REGRESSOR with DNN_CLASSIFIER, but BigQuery ML uses different model types for regression vs. classification. DNN_CLASSIFIER is used for classification tasks like churn prediction, while DNN_REGRESSOR is for continuous values.

How to eliminate wrong answers

Option A is wrong because BOOSTED_TREE_CLASSIFIER uses gradient-boosted decision trees, not a deep neural network, so it does not meet the requirement for a DNN model. Option B is wrong because LOGISTIC_REG is a logistic regression model, which is a linear classifier and not a deep neural network. Option D is wrong because DNN_REGRESSOR is used for regression tasks (predicting continuous values), not for classification tasks like churn prediction.

Full explanation →
13
MCQmedium

You are responsible for monitoring a batch prediction pipeline that runs daily. Recently, the pipeline started failing intermittently with out-of-memory errors. The input data volume has not changed. What is the most likely cause?

A.A recent code change that loads the entire dataset into memory before processing
B.Increase in model size due to retraining
C.Decrease in the number of worker machines
D.Increase in input data size
AnswerA

This could cause OOM for large datasets.

Why this answer

A code change that loads the entire dataset into memory before processing would directly cause out-of-memory (OOM) errors, even if the input data volume remains unchanged. In batch prediction pipelines, data is typically streamed or processed in chunks to manage memory efficiently. A change that bypasses this pattern and loads all data at once can exceed the available heap or container memory, leading to intermittent failures depending on data characteristics or concurrent loads.

Exam trap

The trap here is that candidates may assume OOM errors are always caused by increased data volume or resource scaling issues, but the question explicitly states data volume is unchanged, forcing you to consider code-level changes that alter memory access patterns.

How to eliminate wrong answers

Option B is wrong because an increase in model size due to retraining would affect memory usage during model loading or inference, but it would not cause intermittent OOM errors if the input data volume is unchanged; model size changes are typically gradual and would cause consistent failures, not intermittent ones. Option C is wrong because a decrease in the number of worker machines would reduce total available memory, but the question states the input data volume has not changed, so this would cause consistent OOM errors on every run, not intermittent ones. Option D is wrong because the question explicitly states that input data volume has not changed, so an increase in data size cannot be the cause.

Full explanation →
14
MCQmedium

A company trains models using Vertex AI Training and wants to share the resulting model artifacts with a different team in another Google Cloud project. What is the most secure way to grant access?

A.Use BigQuery to copy the model artifacts and share the BigQuery dataset.
B.Share the Vertex AI model resource directly by adding the other project's members to the IAM policy on the model.
C.Set the Cloud Storage bucket containing the artifacts to 'public' access.
D.Create a new service account in the other project, then grant it the 'roles/storage.objectViewer' role on the bucket.
AnswerD

Least privilege, secure cross-project access.

Why this answer

It follows the principle of least privilege and cross-project access best practices. By creating a dedicated service account in the target project and granting it the 'roles/storage.objectViewer' role on the specific Cloud Storage bucket, you avoid exposing the bucket publicly and avoid sharing the Vertex AI model resource directly, which would grant broader permissions than necessary. This approach ensures that only the service account can read the model artifacts, and the other team can use that service account to access the bucket securely.

Exam trap

The trap here is that candidates often confuse sharing the Vertex AI model resource (which controls access to the model metadata and endpoint) with sharing the underlying artifacts in Cloud Storage, leading them to choose option B, which does not grant the necessary read access to the actual model files.

How to eliminate wrong answers

Option A is wrong because BigQuery is a data warehouse service, not a mechanism for copying or sharing model artifacts; model artifacts are stored in Cloud Storage, and BigQuery cannot be used to copy or grant access to those files. Option B is wrong because sharing the Vertex AI model resource directly via IAM grants access to the model metadata and endpoints, but does not grant access to the underlying model artifacts stored in Cloud Storage; the other team would still need separate permissions on the bucket. Option C is wrong because setting the Cloud Storage bucket to 'public' access would allow anyone on the internet to read the artifacts, violating security best practices and potentially exposing proprietary or sensitive model data.

Full explanation →
15
MCQmedium

Refer to the exhibit. A team runs this Vertex AI Pipeline definition but the deploy component never executes, even though the evaluate step outputs a metric of 0.9. What is the most likely cause?

A.The deploy component depends on the gate component, but the gate is not producing an output.
B.The deploy container image does not exist.
C.The evaluate component must be run before train, but the pipeline order is incorrect.
D.The condition should reference the evaluate component's output directly instead of using an input variable.
E.The pipeline should use a custom component for the condition instead of the built-in type.
AnswerD

The `condition` expression must directly use the output reference, not a local input.

Why this answer

In Vertex AI Pipelines, the `condition` block evaluates a boolean expression at pipeline compile time, not runtime. If the condition references an input variable rather than the actual output of the `evaluate` component, the pipeline will use the default or placeholder value (often `False`), causing the deploy step to be skipped even when the runtime metric is 0.9. The condition must directly reference the `evaluate` component's output (e.g., `evaluate.outputs['metric']`) to be evaluated correctly at runtime.

Exam trap

Google Cloud often tests the distinction between compile-time and runtime evaluation in pipeline orchestration, trapping candidates who assume that pipeline input parameters are dynamically resolved at the same point as component outputs.

How to eliminate wrong answers

Option A is wrong because the gate component is not required for the deploy step; the condition is evaluated based on the evaluate component's output, not a gate output. Option B is wrong because if the deploy container image did not exist, the pipeline would fail with an image pull error, not silently skip execution. Option C is wrong because the pipeline order (train → evaluate → deploy) is correct; the evaluate step must run after train, and the condition is on evaluate's output, not on train.

Option E is wrong because the built-in `condition` component in Vertex AI Pipelines is fully capable of evaluating boolean expressions; a custom component is not needed and would not fix the issue of referencing an input variable instead of a component output.

Full explanation →
16
MCQeasy

A data science team has trained a TensorFlow model and wants to serve it online with minimal latency. Which Vertex AI deployment option should they use to ensure the model can handle traffic spikes without manual scaling?

A.Use Vertex AI Model Garden.
B.Deploy the model to a Vertex AI Endpoint with automatic scaling.
C.Use Vertex AI Batch Prediction for offline inference.
D.Deploy the model to a Compute Engine VM with a load balancer.
AnswerB

Autoscaling handles traffic spikes with low latency.

Why this answer

Vertex AI Endpoints with automatic scaling (option B) are designed for online serving with minimal latency and can automatically adjust the number of replicas based on traffic load, handling spikes without manual intervention. This is the correct choice for a TensorFlow model requiring real-time inference and elastic scaling.

Exam trap

Google Cloud often tests the misconception that any cloud deployment with a load balancer (like Compute Engine) provides automatic scaling, but the trap here is that Vertex AI Endpoints offer managed autoscaling natively, whereas Compute Engine VMs require additional infrastructure setup and do not automatically scale without configuring managed instance groups.

How to eliminate wrong answers

Option A is wrong because Vertex AI Model Garden is a repository of pre-built models and foundation models, not a deployment option for serving custom trained models with automatic scaling. Option C is wrong because Vertex AI Batch Prediction is for offline, asynchronous inference on large datasets, not for real-time online serving with low latency. Option D is wrong because deploying to a Compute Engine VM with a load balancer requires manual scaling configuration (e.g., managed instance groups) and lacks the integrated autoscaling, monitoring, and model versioning capabilities of Vertex AI Endpoints.

Full explanation →
17
Multi-Selectmedium

A pipeline uses the Google Cloud Pipeline Components to perform AutoML training and batch prediction. Which two components from the GCPC library should they use? (Choose two.)

Select 2 answers
A.CustomJobRunOp
B.DataflowPythonOp
C.AutoMLTabularTrainingJobRunOp
D.BatchPredictOp
E.EndpointPredictOp
AnswersC, D

This component runs an AutoML training job for tabular data.

Why this answer

AutoMLTabularTrainingJobRunOp is for AutoML training on tabular data, and BatchPredictOp is for batch predictions. Other options are for custom training or online prediction.

Full explanation →
18
Multi-Selectmedium

A company is deploying a model on Vertex AI for online predictions with strict latency SLOs. The model requires GPU acceleration. Which TWO configurations should they consider to meet the SLOs while optimizing cost?

Select 2 answers
A.Use n1-highmem-32 machine types without GPU
B.Set min_replica_count to handle base traffic and max_replica_count to handle spikes
C.Use GPU-enabled machine types such as n1-standard-4 with T4
D.Enable autoscaling with min_replica_count=0 and max_replica_count=10
E.Disable autoscaling and set a fixed number of replicas equal to peak load
AnswersB, C

Ensures always-on capacity for base load and ability to scale up.

Why this answer

Enabling autoscaling with min_replica_count to handle base load and max_replica_count for spikes, and using scale-to-zero for non-production (but for production, scale-to-zero may not meet SLOs due to cold starts; however, the question says 'optimizing cost', so scale-to-zero is not appropriate for low latency. The correct answers are: set appropriate min and max replicas, and use GPU-enabled machine types. The other options are either irrelevant or counterproductive.

Full explanation →
19
Multi-Selectmedium

Which TWO actions can help reduce prediction latency for a model deployed on Vertex AI Endpoint without changing the model architecture?

Select 2 answers
A.Increase the batch size of prediction requests.
B.Attach a GPU accelerator to the endpoint's machine type.
C.Quantize the model from FP32 to INT8.
D.Deploy the model in multiple regions and use global load balancing.
E.Use a smaller machine type to reduce complexity.
AnswersB, C

GPU reduces computation time for neural networks.

Why this answer

Options B and C are correct. Option B (GPU accelerator) can significantly speed up inference for deep learning models. Option C (model quantization) reduces model size and inference time.

Option A (increasing batch size) increases latency per request. Option D (multiregion deployment) reduces network latency but not prediction latency. Option E (smaller machine type) may increase latency.

Full explanation →
20
MCQhard

A company uses Vertex AI Pipelines with prebuilt components for data processing, training, and deployment. They need to integrate a custom validation step written in Python. What is the correct way to include this as a component?

A.Package the code in a Docker container and reference it as a custom job
B.Define the step in the YAML pipeline definition using arbitrary Python commands
C.Create a custom component using the Vertex AI Pipelines SDK @component decorator
D.Use a Cloud Function as a pipeline step
E.Write a standalone Python script and call it using a Cloud Shell step
AnswerC

Standard method for custom components.

Why this answer

The Vertex AI Pipelines SDK provides a `@component` decorator that allows you to define a custom Python function as a pipeline component. This decorator automatically handles packaging the Python code into a container image, generating the component specification, and integrating it seamlessly with the pipeline orchestration engine. It is the idiomatic and recommended way to add custom validation logic without manually managing Docker or infrastructure.

Exam trap

The trap here is that candidates often confuse the `@component` decorator with a simple function wrapper and assume they can just write inline Python code in the pipeline YAML (Option B), not realizing that Vertex AI Pipelines requires each step to be a containerized component with explicit input/output definitions.

How to eliminate wrong answers

Option A is wrong because packaging code in a Docker container and referencing it as a custom job would create an independent job outside the pipeline DAG, losing the ability to pass inputs/outputs between pipeline steps and breaking the orchestration flow. Option B is wrong because Vertex AI Pipelines YAML definitions do not support arbitrary Python commands; they require prebuilt or custom component definitions with proper container specifications. Option D is wrong because Cloud Functions are event-driven serverless functions not designed for pipeline step integration; they lack native support for pipeline I/O, artifact tracking, and retry logic within Vertex AI Pipelines.

Option E is wrong because Cloud Shell is an interactive environment for ad-hoc commands, not a pipeline execution step; it cannot be used as a component in a Vertex AI Pipeline and would not support parameter passing or artifact management.

Full explanation →
21
MCQhard

A team uses Cloud Composer to orchestrate a complex ML pipeline with many tasks. They notice that the DAG parsing time is very high, causing delays in task scheduling. Which action would most effectively reduce DAG parsing time?

A.Remove all DAG files that are not currently needed from the bucket
B.Increase the parallelism of the Airflow scheduler
C.Optimize DAG files to avoid heavy top-level imports and database queries
D.Combine all DAGs into a single file
AnswerC

Top-level imports/queries are executed on every parse, so reducing them speeds up parsing.

Why this answer

Heavy top-level imports and database queries in DAG files are executed every time the scheduler parses the DAG, which happens frequently (default every 30 seconds). By moving imports inside Python callables or using lazy loading, the parsing time is drastically reduced, allowing the scheduler to process DAGs faster and trigger tasks without delay.

Exam trap

Google Cloud often tests the misconception that reducing the number of DAG files or increasing scheduler resources will fix parsing delays, when the real bottleneck is the top-level code execution inside each DAG file.

How to eliminate wrong answers

Option A is wrong because removing unused DAG files reduces clutter but does not address the root cause of high parsing time; the scheduler still parses all present DAG files, and if they contain heavy top-level code, parsing remains slow. Option B is wrong because increasing scheduler parallelism (e.g., `scheduler_parallelism` or `max_threads`) only affects how many tasks the scheduler can process concurrently, not how fast it parses DAG files; parsing is a sequential, per-file operation. Option D is wrong because combining all DAGs into a single file actually increases parsing time, as the scheduler must parse one very large file with all dependencies loaded at once, and it also breaks Airflow's ability to detect changes per DAG.

Full explanation →
22
MCQhard

An organization uses Cloud Dataflow to preprocess training data. Dataflow jobs are often failing because of insufficient quota for certain resources. The team has requested a quota increase, but the jobs still fail with 'quota exceeded' errors for a different resource. They want to proactively monitor and manage quotas to avoid failures. What is the best approach?

A.Set up Cloud Monitoring alerts for quota usage and automate quota increase requests.
B.Configure Dataflow to use a different pipeline type that avoids the quota.
C.Use Dataflow's autoscaling feature to reduce resource usage.
D.Increase the maximum number of workers in the Dataflow job.
AnswerA

Proactive monitoring and automation allow scaling quotas as needed.

Why this answer

Setting up Cloud Monitoring alerts for quota usage and automating quota increase requests helps catch issues before failures occur. Option B might reduce resource consumption but does not address the root cause of quota limits. Option C is not feasible.

Option D could worsen the problem by requiring more resources.

Full explanation →
23
MCQeasy

A data analyst wants to build a binary classification model to predict customer churn using SQL queries in BigQuery. Which BigQuery ML model type should they use?

A.MATRIX_FACTORIZATION
B.LINEAR_REG
C.LOGISTIC_REG
D.K_MEANS
AnswerC

Why this answer

BigQuery ML supports LOGISTIC_REG for binary classification via SQL. LINEAR_REG is for regression, K_MEANS for clustering, and MATRIX_FACTORIZATION for recommendations.

Full explanation →
24
MCQeasy

Which of the following is a benefit of using Vertex AI Endpoints with autoscaling and scale-to-zero?

A.It eliminates the need for a load balancer.
B.It reduces costs by scaling down to zero replicas when no requests are received.
C.It reduces model training time.
D.It automatically upgrades the model version.
AnswerB

Scale-to-zero minimizes cost for low-traffic endpoints.

Why this answer

Vertex AI Endpoints with autoscaling and scale-to-zero allow the number of serving replicas to dynamically adjust based on incoming traffic. When no requests are received, the endpoint can scale down to zero replicas, meaning you are not charged for idle compute resources. This directly reduces operational costs compared to maintaining a minimum number of always-on instances.

Exam trap

A common misconception is that autoscaling eliminates the need for a load balancer, but in Vertex AI Endpoints, the load balancer is a separate component that remains essential for request distribution even when scaling to zero.

How to eliminate wrong answers

Option A is wrong because Vertex AI Endpoints still require a load balancer (the built-in Google Cloud Load Balancer) to distribute incoming requests across replicas; autoscaling does not eliminate this need. Option C is wrong because model training time is a function of training infrastructure and algorithm, not of serving endpoint configuration like autoscaling. Option D is wrong because Vertex AI Endpoints do not automatically upgrade model versions; you must explicitly deploy a new model version or use a traffic split to route requests to a different version.

Full explanation →
25
MCQmedium

Your Vertex AI custom training job is failing with an out-of-memory error on a single GPU. You need to reduce memory usage without changing the model architecture. Which approach should you try first?

A.Decrease the batch size
B.Implement model parallelism across GPUs
C.Use gradient accumulation
D.Enable mixed precision training (FP16)
AnswerA

Decreasing batch size directly reduces the memory footprint of activations and gradients, easily lowering GPU memory usage.

Why this answer

Decreasing the batch size is the simplest and most direct approach to reduce GPU memory usage for a custom training job. It linearly reduces the memory needed for activations and gradients. While mixed precision can also reduce memory, it may introduce numerical precision issues and only works on compatible hardware, so decreasing batch size should be attempted first.

Full explanation →
26
MCQeasy

A company stores training data in Cloud Storage and uses Vertex AI Training for model training. They want to implement a data validation pipeline to detect data drift before retraining. Which service should they use?

A.Vertex AI Model Monitoring
B.BigQuery ML
C.Cloud Data Loss Prevention
D.Dataflow
AnswerA

Vertex AI Model Monitoring can detect data drift by comparing distributions.

Why this answer

Vertex AI Model Monitoring is designed specifically to detect data drift and feature skew in production ML models by continuously comparing prediction requests against a baseline training dataset. It provides automated alerts when statistical distributions shift beyond a defined threshold, making it the correct choice for a data validation pipeline before retraining.

Exam trap

Google Cloud often tests the distinction between a general-purpose data processing tool (Dataflow) and a specialized managed service (Vertex AI Model Monitoring), leading candidates to choose Dataflow because they think they need to build a custom pipeline, while the question asks for the service that should be used, implying the most appropriate managed solution.

How to eliminate wrong answers

Option B is wrong because BigQuery ML is used for creating and executing ML models directly in BigQuery using SQL, not for monitoring data drift in existing models. Option C is wrong because Cloud Data Loss Prevention (DLP) is focused on inspecting and classifying sensitive data (e.g., PII) for security and compliance, not for statistical drift detection. Option D is wrong because Dataflow is a stream and batch data processing service (based on Apache Beam) that could be used to build a custom drift detection pipeline, but it is not a managed service purpose-built for model monitoring like Vertex AI Model Monitoring.

Full explanation →
27
Multi-Selectmedium

An ML engineer wants to monitor a deployed model for fairness across different age groups and genders. Which TWO Vertex AI services should they use together to achieve this? (Choose two.)

Select 2 answers
A.Vertex AI Feature Store
B.Vertex AI Explainable AI
C.BigQuery
D.Cloud Monitoring
E.Vertex AI Model Evaluation
AnswersC, E

BigQuery stores the ground truth labels and can be used as the source for sliced evaluation.

Why this answer

Vertex AI Model Evaluation provides sliced evaluation when ground truth is available in BigQuery. Vertex AI Explainable AI can help understand feature importance but is not required for fairness monitoring.

Full explanation →
28
MCQmedium

You are using Vertex AI batch prediction and your model requires preprocessing that involves joining two BigQuery tables. The preprocessing logic is complex and must be done before inference. How should you design the pipeline?

A.Write a Cloud Composer workflow that runs the preprocessing and then triggers the batch prediction job.
B.Use Dataflow to read from both BigQuery tables, perform the join and preprocessing, write the results to GCS, then run Vertex AI batch prediction with GCS source.
C.Use Vertex AI batch prediction with a custom container that includes logic to read and join tables on the fly.
D.Use BigQuery to create a materialized view that joins the tables and directly use that as the batch prediction source.
AnswerB

Dataflow handles the complex join and scales; batch prediction can read from GCS.

Why this answer

Dataflow (Apache Beam) is designed for complex, stateful data processing like joining two BigQuery tables and performing custom preprocessing. It can read from BigQuery, execute the join logic, and write the preprocessed results to Cloud Storage (GCS). Vertex AI batch prediction then reads the preprocessed data from GCS, which is the recommended pattern for non-trivial transformations before inference, as it decouples preprocessing from prediction and avoids resource contention.

Exam trap

Google often tests the misconception that batch prediction can handle live data transformations within the prediction container, but the correct design is to preprocess data in a separate, scalable data processing service like Dataflow before feeding it to batch prediction.

How to eliminate wrong answers

Option A is wrong because Cloud Composer (Apache Airflow) is an orchestration tool, not a data processing engine; using it to run the preprocessing itself would be inefficient and error-prone, as it lacks native support for large-scale data joins and transformations. Option C is wrong because Vertex AI batch prediction with a custom container that reads and joins tables on the fly violates the principle of separation of concerns, leading to longer inference latency, higher memory usage, and potential timeouts during prediction, as batch prediction expects preprocessed input, not live database joins. Option D is wrong because BigQuery materialized views are precomputed, read-only snapshots that cannot be used directly as a batch prediction source; batch prediction requires input data in GCS (JSON/CSV) or BigQuery tables, but a materialized view is not a table and cannot be referenced as a source URI.

Full explanation →
29
Multi-Selecthard

A financial services company has deployed a classification model on Vertex AI to detect fraudulent transactions. The model is monitored using Vertex AI Model Monitoring for skew and drift detection, and also logs predictions to BigQuery for analysis. After a month, the monitoring alerts show a significant drift in one feature (transaction_amount). Which TWO actions should the team take to diagnose and address this issue?

Select 2 answers
A.Compare the feature distribution in the training data with the recent serving data using statistical tests.
B.Retrain the model on the most recent data to incorporate the new distribution.
C.Increase the frequency of model monitoring checks to every hour.
D.Increase the sampling rate for prediction logging to ensure full data capture.
E.Reduce the alert threshold to minimize false positives.
AnswersA, B

This diagnostic step helps understand the nature and extent of the drift.

Why this answer

Comparing the feature distribution of the training data with recent serving data using statistical tests (e.g., Kolmogorov-Smirnov or Jensen-Shannon divergence) is the standard first step to quantify the drift and confirm it is statistically significant. This diagnostic action helps the team understand the nature and magnitude of the drift before deciding on remediation steps. Vertex AI Model Monitoring already performs such comparisons, but the team should independently verify the results in BigQuery to ensure accuracy.

Exam trap

The trap here is that candidates often confuse 'detecting drift' with 'fixing drift' and immediately choose retraining (Option B) without first performing a diagnostic comparison, which is a critical step in the ML lifecycle per the PMLE exam's emphasis on systematic troubleshooting.

Full explanation →
30
MCQeasy

What is the primary purpose of Vertex AI Model Optimization (formerly Model Garden)?

A.To monitor model performance in production
B.To search for optimal hyperparameters
C.To optimize models for deployment by quantizing and compiling them
D.To train models faster using distributed training
AnswerC

Model Optimization reduces model size and improves inference speed.

Why this answer

Vertex AI Model Optimization automatically quantizes and compiles models to reduce latency and memory footprint for serving.

Full explanation →
31
MCQmedium

A company wants to analyze customer reviews for sentiment (positive, negative, neutral) using a pre-trained model with no training. They have text data stored in BigQuery. Which Google Cloud service should they use?

A.Translation API
B.Speech-to-Text API
C.Natural Language API
D.AutoML NLP
AnswerC

Why this answer

Natural Language API provides pre-trained sentiment analysis. AutoML NLP is for custom models. Speech-to-Text is for audio transcription.

Translation API is for language translation.

Full explanation →
32
MCQeasy

An MLOps team has deployed a model on Vertex AI Endpoints and wants to monitor for skew between training and serving data distributions. Which Vertex AI service should they use?

A.Vertex AI Explainability
B.Vertex AI Model Monitoring
C.Vertex AI Model Registry
D.Vertex AI Continuous Training
AnswerB

Correct service for monitoring feature skew and drift.

Why this answer

Vertex AI Model Monitoring is specifically designed for monitoring feature skew (training vs serving) and drift (serving over time) on deployed models.

Full explanation →
33
MCQhard

A company is using AutoML Tables to build a fraud detection model. The dataset has 10 million rows with 100 features, heavily imbalanced (fraud cases 0.1%). They used AutoML Tables with default settings and achieved high precision but very low recall. They need to deploy the model for real-time scoring on a Vertex AI Endpoint. The model will be used by a transaction processing system that requires low latency (<100 ms per prediction) and high throughput. The team is concerned about cost as the endpoint will receive up to 5,000 predictions per second. After deploying the model, they notice that the endpoint's latency occasionally spikes to over 1 second during peak hours. The team wants to optimize both model performance (recall) and serving performance. Which course of action should they take?

A.Retrain the model with adjusted class weights in AutoML Tables to increase recall, then deploy using Vertex AI Prediction with autoscaling enabled.
B.Use BigQuery ML to create a logistic regression model with class weights, then deploy it on Cloud Run with maximum concurrency.
C.Export the AutoML Tables model as a TensorFlow SavedModel and deploy it on Vertex AI Prediction with a larger machine type and increased min replicas.
D.Use Vertex AI Workbench to manually tune a deep neural network with class imbalance techniques, then deploy as a custom container on App Engine.
AnswerA

AutoML Tables supports class weights to handle imbalance, improving recall. Vertex AI Prediction with autoscaling dynamically adjusts resources to maintain latency during spikes and control costs.

Why this answer

AutoML Tables allows adjusting class weights to handle imbalanced datasets, which directly addresses the low recall issue by penalizing misclassifications of the minority class more heavily. Deploying on Vertex AI Prediction with autoscaling ensures the endpoint can handle up to 5,000 predictions per second while maintaining low latency, as autoscaling dynamically adjusts resources based on traffic, preventing spikes during peak hours.

Exam trap

Google Cloud often tests the misconception that exporting a managed model to a custom format (like TensorFlow SavedModel) and deploying on a larger machine type is the best way to optimize serving performance, when in fact autoscaling and class weight adjustments within the managed service are the correct low-code approach.

How to eliminate wrong answers

Option B is wrong because BigQuery ML's logistic regression is a simpler model that may not capture complex patterns in 100 features, and Cloud Run's maximum concurrency can lead to increased latency under high throughput (5,000 QPS) without dedicated GPU/TPU support for real-time scoring. Option C is wrong because exporting an AutoML Tables model as a TensorFlow SavedModel loses the optimized serving infrastructure of AutoML, and simply using a larger machine type with increased min replicas does not guarantee sub-100ms latency during traffic spikes without autoscaling. Option D is wrong because using Vertex AI Workbench to manually tune a deep neural network is not a low-code solution, and deploying on App Engine introduces cold start issues and lacks the low-latency, high-throughput capabilities of Vertex AI Prediction for real-time scoring.

Full explanation →
34
MCQmedium

Refer to the exhibit. This IAM policy is applied at the project level. What is the effect of the condition?

A.The service account can only access AI Platform resources that start with 'projects/ml-'
B.The service account can only be used in projects whose ID starts with 'ml-'
C.The role is granted only if the project's name contains 'ml-'
D.The condition is ignored because conditions are not supported for service accounts
AnswerA

Condition on resource name limits access to resources with that prefix.

Why this answer

The condition block uses the `resource.name.startsWith` condition key to restrict access to AI Platform resources whose names begin with `projects/ml-`. This means the service account can only interact with AI Platform resources (such as models, jobs, or endpoints) that have a resource name starting with that prefix, effectively scoping the permission to a specific set of projects or resources.

Exam trap

Google Cloud often tests the distinction between resource-level conditions (like `resource.name`) and identity-level conditions (like `principal` or `request.auth`), and candidates mistakenly apply the condition to the service account's project ID instead of the target resource's name.

How to eliminate wrong answers

Option B is wrong because the condition checks the resource name (the AI Platform resource path), not the project ID of the service account itself; the service account can be from any project, but the resources it can access must have names starting with `projects/ml-`. Option C is wrong because the condition uses `resource.name.startsWith`, which operates on the resource name, not the project's display name or label; the project name is irrelevant. Option D is wrong because IAM conditions are fully supported for service accounts; the condition is evaluated at access time and can restrict permissions based on resource attributes.

Full explanation →
35
MCQeasy

Which Vertex AI service is best suited for finding similar items in a large dataset based on embedding vectors, such as product recommendations or image similarity search?

A.Vertex AI Prediction Endpoint
B.Vertex AI Model Monitoring
C.Vertex AI Feature Store
D.Vertex AI Matching Engine
AnswerD

Correct: Matching Engine (Vector Search) is for ANN-based similarity search on embeddings.

Why this answer

Vertex AI Matching Engine is specifically designed for high-performance vector similarity search (also known as approximate nearest neighbor search) using embedding vectors. It scales to billions of vectors and is ideal for use cases like product recommendations and image similarity search, where you need to find the most similar items based on dense vector representations.

Exam trap

Candidates often confuse Vertex AI Prediction (model serving) with Vertex AI Matching Engine (vector similarity search). The key distinction is that Prediction serves model inference on input data, while Matching Engine retrieves similar items based on embedding vectors.

How to eliminate wrong answers

Option A is wrong because Vertex AI Prediction Endpoint serves model predictions via HTTP requests but does not provide built-in vector similarity search or indexing capabilities. Option B is wrong because Vertex AI Model Monitoring tracks prediction quality and data drift over time, not similarity search. Option C is wrong because Vertex AI Feature Store is a centralized repository for storing, serving, and sharing feature data, but it does not perform nearest neighbor search on embedding vectors.

Full explanation →
36
MCQmedium

Your Vertex AI endpoint is experiencing high latency during traffic spikes. You have set maxReplicas=10 and minReplicas=2. The CPU utilisation target is 60%. During spikes, the endpoint never scales beyond 4 replicas. What is the most likely reason?

A.The maxReplicas limit is set to 10, but the cooldown period is preventing rapid scaling.
B.You need to enable GPU acceleration.
C.The endpoint is using a legacy model framework.
D.The machine type is too small.
AnswerA

Correct. Cooldown periods can delay scaling decisions, especially for short spikes.

Why this answer

The default cooldown period (usually 120 seconds) prevents rapid scaling. If traffic spikes are very short, the endpoint may not trigger a scale-up because the utilisation spike doesn't persist long enough.

Full explanation →
37
Multi-Selectmedium

Which THREE factors should be considered when choosing between using Vertex AI Endpoints and Cloud Run for model serving? (Choose three.)

Select 3 answers
A.Built-in model monitoring
B.Complexity of model containerization
C.Cost per request
D.GPU support
E.Automatic scaling to zero
AnswersA, D, E

Vertex AI Endpoints integrates with Model Monitoring; Cloud Run requires custom implementation.

Why this answer

The key differentiators between Vertex AI Endpoints and Cloud Run for model serving are built-in model monitoring, GPU support, and automatic scaling to zero. Vertex AI Endpoints provides built-in model monitoring, while Cloud Run does not offer this natively. GPU support is a strong differentiator: Vertex AI Endpoints natively supports GPUs, whereas Cloud Run has very limited GPU support, often making it unsuitable for GPU-dependent models.

Automatic scaling to zero is a feature of Cloud Run, which can scale down to zero instances when not in use, reducing costs; Vertex AI Endpoints typically requires at least one instance, so it does not scale to zero as easily. In contrast, the complexity of model containerization and cost per request are less differentiating: both services require similar containerization effort and have comparable per-request pricing models, though cost specifics depend on usage patterns.

Full explanation →
38
Multi-Selecthard

Which TWO strategies can help reduce the cost of running ML pipelines on Vertex AI?

Select 2 answers
A.Run hyperparameter tuning jobs with a large search space
B.Use Vertex AI managed datasets to reduce storage costs
C.Manually scale up resources during peak times and scale down during off-peak
D.Use preemptible VMs for training steps where possible
E.Use a larger machine type for training to complete faster
AnswersB, D

Managed datasets avoid duplication and reduce storage costs.

Why this answer

Options B and D are correct. Option B is correct because using Vertex AI managed datasets can reduce storage costs by eliminating duplicate copies and providing efficient storage. Option D is correct because preemptible VMs are significantly cheaper than regular VMs, making them cost-effective for fault-tolerant training tasks.

Option A is incorrect because hyperparameter tuning with a large search space can increase cost due to many trials. Option C is incorrect because manual scaling is less efficient and can lead to higher costs compared to automated scaling. Option E is incorrect because using a larger machine type for training usually increases cost, even if it reduces training time.

Full explanation →
39
MCQeasy

A team wants to track the lineage of ML pipeline runs, including which datasets, parameters, and models were used in each execution. Which Vertex AI service should they use?

A.Vertex AI Metadata
B.Vertex AI Feature Store
C.Vertex AI Model Registry
D.Vertex AI Experiments
AnswerA

Metadata store is designed for lineage tracking.

Why this answer

Vertex AI Metadata (part of Vertex ML Metadata) tracks artifacts, executions, and lineage.

Full explanation →
40
MCQmedium

The exhibit shows a Cloud Build configuration. An ML engineer wants to automate the deployment of a model to Vertex AI after training. What is missing in this config to successfully deploy the model?

A.A step to upload the training image to Artifact Registry
B.A step to build the serving container image
C.A step to run unit tests
D.A step to create the Vertex AI Endpoint
AnswerB

The config only builds the training image; it needs a separate step to build and push the serving image.

Why this answer

The Cloud Build configuration shown is for training a model, but to deploy it to Vertex AI, a serving container image must be built and pushed to Artifact Registry. Vertex AI requires a custom serving container (or a prebuilt one) to host the model for predictions. Without a step to build the serving container image (e.g., using a Dockerfile that includes the model and serving dependencies), the deployment will fail because there is no runnable image to deploy to the endpoint.

Exam trap

Google Cloud often tests the distinction between training and serving containers, leading candidates to mistakenly think that the training image (or any image) is sufficient for deployment, when in fact a separate serving container is required.

How to eliminate wrong answers

Option A is wrong because uploading the training image to Artifact Registry is already implied or handled by the training step; the missing piece is the serving container image, not the training image. Option C is wrong because running unit tests, while good practice, is not a prerequisite for deploying a model to Vertex AI; the deployment process specifically requires a serving container image. Option D is wrong because creating the Vertex AI Endpoint can be done as part of the deployment step (e.g., via `gcloud ai endpoints create` or the Vertex AI SDK) and is not the missing piece; the fundamental gap is the absence of a serving container image build step.

Full explanation →
41
MCQeasy

A team needs to quickly create a visual interface for data exploration and model building without writing code. They want to run AutoML jobs and visualize results. Which Google Cloud tool should they use?

A.Vertex AI Workbench
B.Cloud Datalab
C.Cloud Composer
D.Google Colab
AnswerA

Provides a managed notebook environment with visual data exploration and one-click AutoML integration.

Why this answer

Vertex AI Workbench provides a managed JupyterLab environment with a low-code interface for data exploration, AutoML model training, and result visualization without writing code. It integrates directly with Vertex AI's AutoML and custom training services, allowing users to run AutoML jobs and view evaluation metrics, feature importance, and predictions through its UI.

Exam trap

Google Cloud often tests the distinction between code-based notebook tools (Colab, Datalab) and managed low-code platforms (Vertex AI Workbench), expecting candidates to recognize that AutoML job execution and visual result exploration require the latter's integrated UI and API access.

How to eliminate wrong answers

Option B (Cloud Datalab) is wrong because it is a deprecated tool that required code-based notebooks and does not support AutoML job execution or low-code visual interfaces. Option C (Cloud Composer) is wrong because it is a workflow orchestration service based on Apache Airflow, designed for scheduling and monitoring pipelines, not for interactive data exploration or AutoML. Option D (Google Colab) is wrong because it is a free, code-centric notebook environment that lacks native integration with Vertex AI AutoML and does not provide a low-code visual interface for model building.

Full explanation →
42
Multi-Selecteasy

A data scientist is creating a Vertex AI pipeline using the Kubeflow Pipelines SDK v2. Which TWO statements about pipeline parameters are correct? (Choose two.)

Select 2 answers
A.Pipeline parameters are defined as inputs to the pipeline function decorated with @dsl.pipeline.
B.Pipeline parameters must be serialized to JSON before use.
C.Pipeline parameters can only be of type str.
D.Pipeline parameters can be overridden at pipeline run time.
E.Pipeline parameters can be used to pass large datasets between components.
AnswersA, D

Correct: Parameters are function arguments of the pipeline function.

Why this answer

In the Kubeflow Pipelines SDK v2, pipeline parameters are explicitly defined as input arguments to the pipeline function that is decorated with @dsl.pipeline. These parameters serve as the primary mechanism for passing configuration values (e.g., model name, learning rate, number of epochs) into the pipeline at creation time and can be consumed by downstream components.

Exam trap

The trap is that candidates often assume pipeline parameters must be JSON-serialized or limited to strings due to older Kubeflow v1 conventions, but Vertex AI's Kubeflow Pipelines SDK v2 natively supports multiple Python types and automatic serialization.

Full explanation →
43
MCQhard

A data scientist runs a batch prediction job on Vertex AI using a custom container. The job processes a large JSONL file (10 GB) and fails with an out-of-memory error. The machine type is n1-standard-4 (15 GB memory). Which action should be taken to resolve the error while minimizing cost?

A.Reduce the batch size in the prediction request.
B.Split the input data into smaller files and run multiple batch jobs.
C.Add a GPU accelerator to offload computation.
D.Use a machine type with more memory, such as n1-highmem-8 (52 GB).
AnswerD

Increasing memory directly solves out-of-memory errors.

Why this answer

The out-of-memory (OOM) error indicates the machine's memory is insufficient for the model or data processing. Upgrading to n1-highmem-8 (52 GB) directly addresses the memory shortage while minimizing cost, as high-memory machines provide more RAM without unnecessary extras like GPUs. Option A (reducing batch size) might help but is not the primary fix if the model itself is large, and cost efficiency is not improved.

Option B (splitting input data into smaller files) does not reduce per-instance memory pressure and could increase latency and cost due to multiple jobs. Option C (adding a GPU) increases compute but not memory, so it does not resolve the OOM error.

Full explanation →
44
MCQmedium

Your team is developing a machine learning model for real-time fraud detection. The training pipeline runs on Vertex AI and uses BigQuery for feature engineering. Recently, the pipeline has been taking significantly longer to execute. Upon investigation, you find that the BigQuery query for feature extraction is being rerun every time the pipeline runs, even though the underlying data hasn't changed. The pipeline is scheduled to run every hour. You want to reduce cost and execution time without losing the ability to detect data drifts. Which approach should you take?

A.Implement a caching mechanism in the pipeline that stores the results of the BigQuery query and reuses them if the data hasn't changed.
B.Move the feature extraction to a separate scheduled query in BigQuery and load the results into a table that the pipeline reads from.
C.Reduce the pipeline frequency to once a day to minimize the number of runs.
D.Use a conditional pipeline that checks if the data has changed before running the feature extraction step.
AnswerB

This separates concerns and avoids redundant execution, while still allowing data drift detection via the pipeline.

Why this answer

It decouples the feature extraction from the training pipeline by using a separate scheduled BigQuery query that writes results to a table. This eliminates redundant query execution on every pipeline run, reducing cost and execution time, while the scheduled query can be set to run at a frequency that still detects data drifts (e.g., hourly). The pipeline then reads from the precomputed table, avoiding repeated full scans of the source data.

Exam trap

Google Cloud often tests the misconception that caching or conditional checks are sufficient to reduce cost, when in fact the most efficient solution is to offload the repetitive computation to a separate scheduled job that writes to a table, avoiding any pipeline-level overhead.

How to eliminate wrong answers

Option A is wrong because implementing a caching mechanism that checks if data hasn't changed still requires an initial query or metadata check each run, and caching in the pipeline itself does not leverage BigQuery's native scheduled query capabilities, potentially missing data drift detection if the cache is stale. Option C is wrong because reducing pipeline frequency to once a day would significantly delay fraud detection, violating the real-time requirement and increasing the risk of missing drifts between runs. Option D is wrong because a conditional pipeline that checks for data changes before running the feature extraction step still incurs the overhead of a check query every hour, and if the check is lightweight, it may not accurately detect all data drifts (e.g., schema changes or new partitions), while still adding complexity without the cost savings of a scheduled query.

Full explanation →
45
Multi-Selectmedium

An ML team uses Delta Lake on Dataproc for data versioning. Which THREE benefits does Delta Lake provide?

Select 3 answers
A.Automatic data encryption at rest
B.Time travel for accessing previous versions
C.Schema enforcement and evolution
D.ACID transactions on data lakes
E.Built-in real-time streaming
AnswersB, C, D

Enables reproducibility.

Why this answer

Delta Lake provides ACID transactions, schema enforcement, and time travel.

Full explanation →
46
MCQmedium

A company needs to serve a model for low-frequency inference requests (a few hundred per month) from multiple regions. The priority is simplicity and minimal cost without maintaining infrastructure. Which serving option should they choose?

A.Deploy a real-time Vertex AI Endpoint with min replicas set to 1.
B.Set up a Dataflow streaming pipeline to process requests.
C.Use Vertex AI Batch Prediction triggered as needed.
D.Use Cloud Run with serving container and scale to zero.
AnswerC

Batch prediction is serverless, pay-per-query, and ideal for infrequent large predictions.

Why this answer

Vertex AI Batch Prediction runs on-demand jobs without any idle infrastructure cost, making it ideal for low-frequency inference requests (a few hundred per month) from multiple regions. Option A is wrong because a real-time endpoint with min replicas=1 incurs per-hour cost even when idle. Option B is wrong because Dataflow streaming pipelines are designed for continuous, real-time data processing, which adds complexity and cost for infrequent requests.

Option D is wrong because Cloud Run scales to zero but is still a real-time serving option designed for online inference, not batch; it also requires containerized application and is not optimized for batch workloads.

Full explanation →
47
MCQhard

A company needs to perform real-time similarity search on a dataset of 10 million embedding vectors. They expect low latency (under 10ms) and high throughput. Which index type should they use in Vertex AI Vector Search?

A.Brute-force index
B.Hash-based index
C.Tree-based index
D.Approximate nearest neighbor (ANN) index with ScaNN
AnswerD

ANN with ScaNN provides fast approximate search, suitable for large-scale real-time search.

Why this answer

For large datasets requiring low latency, an approximate nearest neighbor (ANN) index is appropriate. The Scann algorithm (ScaNN) is used by Vertex AI Vector Search for ANN.

Full explanation →
48
MCQeasy

Which algorithm does Vertex AI Model Monitoring use by default to detect feature drift in a categorical feature?

A.Population Stability Index (PSI)
B.Wasserstein distance
C.Jensen-Shannon divergence
D.Kullback-Leibler divergence
AnswerC

Default algorithm for drift detection on categorical features.

Why this answer

Vertex AI Model Monitoring uses Jensen-Shannon divergence (JS divergence) as the default metric for drift detection on categorical features.

Full explanation →
49
MCQhard

A company needs to serve a large Transformer model (5 GB) with strict latency requirements (< 50 ms) and throughput of 1000 requests per second. The model is in SavedModel format. They are considering deployment options on Google Cloud. Which approach best meets these requirements?

A.Deploy on Vertex AI Prediction using a single high-memory VM with a GPU (e.g., n1-highmem-32 with A100).
B.Deploy on Cloud Run with a GPU-enabled instance and increase concurrency.
C.Deploy on Vertex AI Prediction using model parallelism across multiple GPUs on a single VM.
D.Deploy on Vertex AI Prediction using distributed serving with TensorFlow Serving and model sharding across multiple VMs.
AnswerA

A single high-memory VM with a powerful GPU (e.g., A100) can handle the model size and throughput with low latency, avoiding network overhead.

Why this answer

A single high-memory VM with a powerful GPU (e.g., A100) can handle the model size and throughput with low latency, avoiding network overhead. Option B is wrong because Cloud Run does not currently support GPU instances effectively, and even with GPU, concurrency may not meet strict latency requirements. Option C is wrong because model parallelism across multiple GPUs on a single VM adds complexity and overhead that is unnecessary for a 5GB model that fits on a single high-end GPU.

Option D is wrong because distributed serving across multiple VMs introduces network latency that would make it difficult to meet the 50 ms requirement.

Full explanation →
50
MCQmedium

A data science team is using AI Platform for training. They want to track hyperparameters and metrics across multiple experiments. What should they use?

A.Cloud Logging with custom metrics
B.Vertex AI Experiments
C.Store metrics in Cloud Storage and compare manually
D.Cloud Monitoring dashboards
AnswerB

Provides experiment tracking, comparison, and analysis.

Why this answer

Vertex AI Experiments is the correct choice because it is the native service within Vertex AI designed specifically for tracking, comparing, and analyzing hyperparameters and metrics across multiple training runs. It provides a centralized UI and SDK to log parameters, metrics, and artifacts, enabling systematic experiment management without manual effort or external tools.

Exam trap

Google Cloud often tests the distinction between logging/monitoring services (Cloud Logging, Cloud Monitoring) and ML-specific experiment tracking (Vertex AI Experiments), leading candidates to pick a generic monitoring tool instead of the purpose-built ML service.

How to eliminate wrong answers

Option A is wrong because Cloud Logging is intended for collecting and querying log data (e.g., application logs, error messages), not for structured tracking of hyperparameters and metrics across experiments; it lacks built-in experiment comparison features. Option C is wrong because storing metrics in Cloud Storage and comparing manually is inefficient, error-prone, and does not provide automated tracking, visualization, or versioning of experiments, which is the core requirement. Option D is wrong because Cloud Monitoring dashboards are designed for monitoring infrastructure and application performance metrics (e.g., CPU usage, latency), not for tracking ML experiment hyperparameters and metrics across multiple runs.

Full explanation →
51
MCQeasy

A startup wants to build a product recommendation engine without writing custom training code. They have user-item interaction data stored in BigQuery. Which Google Cloud service should they use?

A.Cloud Dataflow with ML APIs
B.BigQuery ML matrix factorization
C.Vertex AI AutoML Tables
D.Vertex AI Matching Engine
AnswerB

Train a recommendation model using SQL with no code.

Why this answer

BigQuery ML matrix factorization is the correct choice because it allows building a recommendation engine directly in BigQuery using SQL, without writing custom training code. It supports implicit and explicit user-item interaction data and provides built-in evaluation metrics, making it ideal for low-code ML solutions on existing BigQuery data.

Exam trap

Google Cloud often tests the distinction between services that require custom code (Dataflow) versus those that offer SQL-based low-code ML (BigQuery ML), and the trap here is assuming any ML service like AutoML or Matching Engine is suitable for recommendation without recognizing the specific need for matrix factorization on interaction data.

How to eliminate wrong answers

Option A is wrong because Cloud Dataflow is a data processing pipeline service, not a low-code ML training service; using ML APIs would require custom code to orchestrate and train models. Option C is wrong because Vertex AI AutoML Tables is designed for tabular data with structured features, not specifically for user-item interaction matrices, and requires exporting data from BigQuery. Option D is wrong because Vertex AI Matching Engine is for vector similarity search and nearest neighbor retrieval, not for training matrix factorization models from interaction data.

Full explanation →
52
MCQmedium

An ML engineer is using Vertex AI Vizier to tune hyperparameters for a custom training job. The training job takes 2 hours per trial. To speed up the process, the engineer wants to run 10 trials in parallel. What is the correct way to configure parallel trial execution?

A.Use the '--parallel-trials' flag in the gcloud ai hp-tuning-jobs create command
B.Set the 'parallelTrialCount' parameter in the study configuration to 10
C.Set the 'maxParallelTrials' attribute in the HyperparameterSpec
D.Create a CustomJob with 'numTrials' set to 10 and 'parallel' flag
AnswerB

This is the correct parameter to specify the number of parallel trials.

Why this answer

In Vertex AI Vizier, parallel trial execution is configured by setting the 'parallelTrialCount' field in the study configuration. The maxParallelTrials is not a direct field; instead, the StudySpec contains a StudyJobConfig with parallelTrialCount. Setting parallelTrialCount to 10 allows up to 10 trials to run concurrently.

Full explanation →
53
MCQmedium

An ML engineer is using Cloud Build to trigger a Vertex AI Pipeline on every commit to a repository. The pipeline takes 2 hours. The engineer wants to only run the pipeline when changes are made to specific directories. How can this be achieved?

A.Use Cloud Composer to poll the repository periodically
B.Configure Cloud Build trigger with included file globs
C.Use a Cloud Function to evaluate changes and invoke the pipeline
D.Modify the pipeline to ignore unrelated changes
E.Add a conditional step in the pipeline to abort if no relevant changes
AnswerB

Native feature of Cloud Build triggers.

Why this answer

Cloud Build triggers support 'included file globs' and 'ignored file globs' to filter which file changes should invoke the trigger. By specifying glob patterns for the directories of interest, the trigger will only fire when commits modify files matching those patterns, avoiding unnecessary pipeline runs for unrelated changes.

Exam trap

The trap here is that candidates may think a pipeline-level conditional check (Option E) is sufficient, but they overlook that Cloud Build triggers can filter at the trigger level, avoiding any pipeline startup cost for irrelevant changes.

How to eliminate wrong answers

Option A is wrong because Cloud Composer is an orchestration service for workflows, not a polling mechanism for repository changes; it would add unnecessary complexity and latency. Option C is wrong because using a Cloud Function to evaluate changes and invoke the pipeline is an overengineered solution; Cloud Build triggers natively support file glob filtering without needing an intermediary. Option D is wrong because modifying the pipeline to ignore unrelated changes would still consume resources to start the pipeline and then abort, wasting time and cost.

Option E is wrong because adding a conditional step in the pipeline to abort if no relevant changes still requires the pipeline to start and run until the conditional check, incurring unnecessary execution time and cost.

Full explanation →
54
Multi-Selecteasy

A data scientist wants to use Vertex AI Pipelines to automate a low-code ML workflow. Which two statements are correct regarding best practices? (Choose TWO.)

Select 2 answers
A.Use pre-built components from Google's curated component library to avoid custom code.
B.Store all intermediate artifacts in Cloud Storage to enable reproducibility and reuse.
C.Avoid using pre-built components because they are not customizable.
D.Use the Vertex AI Experiments to track and compare pipeline runs.
E.Use the Kubeflow Pipelines SDK to define the pipeline, which requires extensive coding.
AnswersA, B

Pre-built components enable low-code pipeline construction.

Why this answer

Vertex AI Pipelines offers a curated library of pre-built components that encapsulate common ML tasks (e.g., data preprocessing, training, evaluation). Using these components reduces the need for custom code, aligning with the low-code ML workflow requirement. This approach accelerates development while maintaining reliability through Google-tested implementations.

Exam trap

The trap here is that candidates confuse Vertex AI Experiments (a tracking tool) with a pipeline design best practice, or they assume pre-built components are rigid and cannot be customized, leading them to incorrectly select D or C.

Full explanation →
55
Multi-Selecteasy

An ML engineer wants to monitor the performance of a Vertex AI Endpoint. Which TWO metrics are available in Cloud Monitoring for Vertex AI Endpoints? (Choose 2)

Select 2 answers
A.Model accuracy
B.Error count
C.Feature skew score
D.SHAP values
E.Prediction latency (p50, p95, p99)
AnswersB, E

Correct: Error count is available as a metric.

Why this answer

Cloud Monitoring for Vertex AI Endpoints includes metrics like prediction latency (p50, p95, p99) and error count/rate. CPU/GPU utilization is also available for endpoint machines.

Full explanation →
56
Multi-Selectmedium

You are deploying a large deep learning model on Vertex AI endpoints. The model requires GPU acceleration and you want to minimize cold-start latency. Which TWO actions should you take? (Choose 2 correct answers)

Select 2 answers
A.Set minReplicaCount to 0 to allow scale-to-zero.
B.Use a custom container that loads the model during startup.
C.Increase maxReplicaCount to a high number.
D.Use batch prediction instead of online prediction.
E.Set minReplicaCount to 1 to always have at least one replica running.
AnswersB, E

Pre-loading the model reduces latency for the first prediction.

Why this answer

Loading the model during container startup (e.g., in the Dockerfile's ENTRYPOINT or CMD) ensures that the model is already in memory when the first prediction request arrives, drastically reducing cold-start latency. This is a standard practice for Vertex AI endpoints where the container must be ready to serve immediately after scaling up.

Exam trap

Google often tests the misconception that scale-to-zero (minReplicaCount=0) reduces latency, when in fact it increases cold-start latency; the correct approach is to keep at least one replica always warm (minReplicaCount=1) and pre-load the model during container startup.

Full explanation →
57
MCQeasy

A company is deploying a machine learning model for real-time fraud detection. The model must respond to requests within 100ms. The model is a TensorFlow model and will be deployed on Google Kubernetes Engine (GKE). Which Google Cloud service should be used to serve the model to minimize latency?

A.Deploy the model on Cloud Run with minimum instances set to 1.
B.Deploy the model as a Cloud Function triggered by HTTP requests.
C.Deploy the model on Vertex AI Prediction with a custom container.
D.Deploy TensorFlow Serving on GKE with a LoadBalancer service.
AnswerD

TensorFlow Serving is optimized for low-latency serving and can be configured on GKE with a LoadBalancer for direct access, minimizing network hops.

Why this answer

Deploying TensorFlow Serving directly on GKE with a LoadBalancer service provides the lowest-latency path for real-time inference. TensorFlow Serving is optimized for high-performance model serving with batching and gRPC support, and GKE allows fine-grained control over node placement, autoscaling, and networking to meet the 100ms SLA. In contrast, serverless options like Cloud Run or Cloud Functions add cold-start latency and lack the low-level optimization for TensorFlow models.

Exam trap

The trap here is that candidates often assume Vertex AI Prediction is always the best choice for serving models, but for ultra-low-latency requirements (<100ms), a direct deployment on GKE with TensorFlow Serving avoids the overhead of a managed prediction platform.

How to eliminate wrong answers

Option A is wrong because Cloud Run, even with minimum instances set to 1, introduces additional latency from its HTTP request routing layer and does not natively support gRPC or TensorFlow Serving's optimized batching, making it harder to consistently meet 100ms. Option B is wrong because Cloud Functions have a maximum timeout of 60 seconds but suffer from cold-start delays (often 500ms-2s) and lack persistent GPU/TPU support, making them unsuitable for sub-100ms real-time inference. Option C is wrong because Vertex AI Prediction with a custom container adds overhead from Vertex AI's managed infrastructure (e.g., request routing, health checks, and autoscaling logic) that can introduce 10-50ms extra latency compared to a direct TensorFlow Serving deployment on GKE.

Full explanation →
58
Multi-Selectmedium

Your organization wants to automate the retraining of a model when new data is available and also on a weekly schedule. Which TWO services would you use together to achieve this? (Choose two.)

Select 2 answers
A.Cloud Functions
B.Cloud Composer
C.Cloud Tasks
D.Dataflow
E.Cloud Scheduler
AnswersA, E

For event-driven trigger on new data.

Why this answer

Cloud Scheduler (E) is used to trigger the retraining on a weekly schedule by sending a message to a Pub/Sub topic or making an HTTP request. Cloud Functions (A) is the serverless compute service that executes the retraining code in response to that trigger, and it can also be triggered directly when new data arrives (e.g., via Cloud Storage or Pub/Sub). Together, they provide both event-driven and scheduled automation without managing infrastructure.

Exam trap

Google often tests the distinction between orchestration (Cloud Composer) and simple scheduling/event-driven triggers (Cloud Scheduler + Cloud Functions), leading candidates to over-engineer the solution by choosing Cloud Composer when a lightweight combination suffices.

Full explanation →
59
MCQmedium

A retail company wants to build a recommendation system for their e-commerce website. They have user purchase history and product metadata. Which Google Cloud service is most suitable for building a 'frequently bought together' recommendation model with minimal custom ML development?

A.Vertex AI Prediction with a custom TensorFlow model
B.BigQuery ML with MATRIX_FACTORIZATION model type
C.Recommendations AI with the 'frequently bought together' model type
D.Vertex AI AutoML Tables
AnswerC

Why this answer

Recommendations AI provides pre-built models for retail recommendations, including 'frequently bought together'. AutoML Tables could be used but requires more customisation. Vertex AI Prediction and BigQuery ML are not purpose-built for this use case and would require more development.

Full explanation →
60
MCQhard

Your company uses a custom container for model serving on Vertex AI. After a recent update, the model returns predictions but they are clearly wrong (e.g., negative probabilities for a classification model). The logs show no errors. What is the most likely cause?

A.The preprocessing code in the container was updated but the model was not retrained on the new preprocessing
B.The model file is corrupted
C.The model file was accidentally replaced with a different model
D.The container is using an incompatible version of the serving framework
AnswerA

Feature transformation mismatch leads to incorrect predictions.

Why this answer

The most likely cause of a model returning predictions without errors, but with clearly wrong outputs like negative probabilities, is a mismatch between the preprocessing logic used during training and inference. If the preprocessing code in the container was updated (e.g., scaling, normalization, or feature engineering steps changed) but the model was not retrained on data processed with that new logic, the model receives inputs that are out of distribution, leading to nonsensical outputs. Vertex AI containers run inference with the deployed code, so any change in preprocessing directly affects the input tensor values without raising runtime errors.

Exam trap

Google Cloud often tests the concept that silent prediction errors (no logs, no crashes) are almost always due to data or preprocessing mismatches, not infrastructure or model file issues, which would generate explicit errors.

How to eliminate wrong answers

Option B is wrong because a corrupted model file would typically cause loading failures, runtime errors, or crashes, not silent generation of plausible but wrong predictions like negative probabilities. Option C is wrong because replacing the model file with a different model would likely produce predictions that are consistently wrong in a different pattern (e.g., all zeros, constant values) or cause shape mismatches, not specifically negative probabilities from a classification model. Option D is wrong because an incompatible serving framework version would usually manifest as import errors, missing symbols, or version mismatch warnings in logs, not silent incorrect predictions with no errors.

Full explanation →
61
MCQmedium

You need to run a batch prediction job on Vertex AI using a model that requires custom preprocessing using a Python script. The preprocessing must be applied before inference. Which approach should you use?

A.Use Cloud Functions to preprocess each record individually.
B.Preprocess the data on a single VM and then upload to GCS.
C.Use Dataflow to preprocess the data and write the results to BigQuery or GCS, then launch a batch prediction job on the preprocessed data.
D.Include the preprocessing logic in the custom container used for batch prediction.
AnswerC

Dataflow can handle large-scale preprocessing and then feed the cleaned data to batch prediction.

Why this answer

Dataflow (Apache Beam) is the recommended serverless service for distributed, scalable preprocessing of large datasets on Google Cloud. It can read raw data from GCS, apply custom Python preprocessing logic, and write the preprocessed results to GCS or BigQuery. The batch prediction job then reads the preprocessed data directly, avoiding the need to embed preprocessing in the prediction container or handle data on a single VM.

Exam trap

Google often tests the misconception that preprocessing can be embedded in the prediction container (Option D) to simplify the pipeline, but this violates the separation of concerns principle and leads to slower, less maintainable batch jobs.

How to eliminate wrong answers

Option A is wrong because Cloud Functions is designed for event-driven, lightweight processing of individual records, not for batch preprocessing of large datasets; it has a 9-minute timeout and limited memory, making it unsuitable for scalable batch preprocessing. Option B is wrong because preprocessing on a single VM creates a bottleneck, lacks fault tolerance, and does not scale horizontally for large datasets, violating best practices for production batch pipelines. Option D is wrong because including preprocessing logic in the custom container for batch prediction couples preprocessing with inference, increasing container complexity and startup time, and prevents reuse of the preprocessing pipeline for other downstream tasks.

Full explanation →
62
Multi-Selecteasy

A company wants to transcribe audio from customer service calls and then analyze the sentiment of the transcribed text. Which TWO Google Cloud services should they use?

Select 2 answers
A.Natural Language API
B.Document AI
C.Speech-to-Text
D.Translation API
E.Vision API
AnswersA, C

Why this answer

Speech-to-Text transcribes audio to text, and Natural Language API can analyze sentiment from text. Vision API is for images, Translation for language translation, and Document AI for document processing.

Full explanation →
63
MCQeasy

A company wants to automatically retrain their model every night at 2 AM using Vertex AI Pipelines. Which approach should they use to trigger the pipeline on a schedule?

A.Use Cloud Scheduler to call the Vertex AI pipeline creation API
B.Deploy the pipeline as a Cloud Run job with a cron trigger
C.Use Vertex AI Experiments to schedule runs
D.Configure a cron job inside the pipeline definition
AnswerA

Cloud Scheduler can invoke a Cloud Function that creates a pipeline run at the specified time.

Why this answer

Cloud Scheduler is the correct approach because it can directly invoke the Vertex AI Pipeline creation API via an HTTP trigger at a specified cron schedule (e.g., 2 AM daily). This integrates natively with Vertex AI's pipeline orchestration, allowing the scheduler to submit a pipeline run without additional infrastructure. The other options either lack native Vertex AI pipeline support or introduce unnecessary complexity.

Exam trap

A common mistake is confusing scheduling a pipeline run (using Cloud Scheduler + Vertex AI API) with scheduling tasks inside a pipeline (using cron within the pipeline definition). Neither Vertex AI Experiments nor Cloud Run jobs are designed for scheduled pipeline orchestration.

How to eliminate wrong answers

Option B is wrong because Cloud Run jobs are designed for stateless container execution and do not natively support Vertex AI Pipelines; they would require custom code to call the API, adding overhead and breaking the managed pipeline lifecycle. Option C is wrong because Vertex AI Experiments is used for tracking and comparing model training runs, not for scheduling or triggering pipeline executions. Option D is wrong because a cron job inside the pipeline definition would only schedule tasks within a single pipeline run, not trigger the pipeline itself on a recurring schedule.

Full explanation →
64
MCQmedium

A data scientist trained a custom TensorFlow model using Vertex AI Training and wants to deploy it for online predictions with low latency (<100ms). Which deployment option on Google Cloud is best?

A.Deploy on Cloud Run with a custom container
B.Deploy on Cloud Functions
C.Deploy on AI Platform Prediction (legacy)
D.Deploy on Vertex AI Endpoints
AnswerD

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

Why this answer

Vertex AI Endpoints is the correct choice because it is purpose-built for deploying TensorFlow models with optimized serving infrastructure, including automatic scaling, GPU/TPU support, and built-in monitoring for latency-sensitive online predictions. It provides a managed endpoint that can achieve sub-100ms latency by leveraging model optimization techniques like TensorFlow Serving and hardware accelerators, which are not available in the other options.

Exam trap

Google Cloud often tests the misconception that any serverless option (like Cloud Run or Cloud Functions) is sufficient for low-latency ML inference, ignoring the need for GPU acceleration and optimized serving infrastructure that only Vertex AI Endpoints provides.

How to eliminate wrong answers

Option A is wrong because Cloud Run, while supporting custom containers, lacks native GPU/TPU acceleration and has a cold-start latency that can exceed 100ms, making it unsuitable for low-latency online predictions. Option B is wrong because Cloud Functions has a maximum timeout of 9 minutes and no GPU support, and its cold-start latency often exceeds 100ms, making it impractical for real-time inference. Option C is wrong because AI Platform Prediction (legacy) is being deprecated and does not offer the same level of integration with Vertex AI's model registry, monitoring, and autoscaling features, and it may not achieve the same low-latency guarantees as Vertex AI Endpoints.

Full explanation →
65
MCQhard

A company deploys a model to Vertex AI Prediction with autoscaling enabled. During a flash sale, traffic spikes 10x, but the endpoint fails to scale fast enough, causing high latency. What is the most likely cause and solution?

A.The min_nodes setting is too low; increase min_nodes to handle baseline traffic
B.Switch to preemptible VMs to reduce cost and allow more instances
C.The model container is too large; rebuild with a smaller image
D.Use Cloud Functions to pre-warm instances before the sale
AnswerA

Higher min nodes allow faster scaling as they are already running.

Why this answer

With Vertex AI Prediction autoscaling, the `min_nodes` setting defines the baseline number of instances that are always kept running. During a flash sale, traffic spikes 10x, but if `min_nodes` is set too low, the autoscaler cannot provision new instances quickly enough to handle the sudden load, resulting in high latency. Increasing `min_nodes` ensures a sufficient baseline capacity to absorb the initial spike while the autoscaler scales up additional nodes.

Exam trap

Google Cloud often tests the misconception that autoscaling is instantaneous or that external services like Cloud Functions can directly pre-warm ML instances, when in reality the root cause is an insufficient baseline capacity (`min_nodes`) to handle the initial burst before the autoscaler catches up.

How to eliminate wrong answers

Option B is wrong because preemptible VMs are designed for cost savings on fault-tolerant workloads, but they can be terminated at any time by Google Cloud, which would exacerbate scaling instability and latency during a traffic spike, not solve it. Option C is wrong because the model container size primarily affects cold start time and deployment speed, not the autoscaler's ability to add instances during a traffic spike; a smaller image would not address the scaling latency issue. Option D is wrong because Cloud Functions cannot pre-warm Vertex AI Prediction instances; pre-warming is typically handled by configuring a higher `min_nodes` or using traffic splitting with canary deployments, not by an external serverless function.

Full explanation →
66
Multi-Selectmedium

A data science team is building a real-time feature engineering pipeline for ML model training and serving. They need to compute features from streaming data, store them for low-latency serving, and ensure consistency between training and serving. Which TWO Google Cloud services should they use?

Select 2 answers
A.Vertex AI Feature Store
B.BigQuery
C.Cloud Functions
D.Cloud Dataflow
E.Cloud SQL
AnswersA, D

Feature Store provides low-latency serving and ensures consistent feature definitions for training and serving.

Why this answer

Vertex AI Feature Store (A) is correct because it provides a centralized repository for storing, serving, and sharing feature data with low-latency online serving and batch serving for training, ensuring consistency between training and serving through point-in-time lookups and feature value time-stamping. Cloud Dataflow (D) is correct because it is a fully managed stream and batch processing service based on Apache Beam, enabling real-time feature engineering from streaming data with exactly-once processing semantics and automatic scaling.

Exam trap

A common trap in Google PMLE exams is assuming BigQuery can serve as a low-latency online feature store for real-time inference, but it is designed for analytical queries with seconds-to-minutes latency, not sub-millisecond serving required for real-time ML inference.

Full explanation →
67
MCQeasy

A company uses Vertex AI Model Registry to manage multiple model versions. They want to designate a model version as 'champion' for production deployment and another as 'challenger' for A/B testing. Which feature of the registry should they use?

A.Model version labels
B.Model lineage
C.Model aliases
D.Model evaluation metrics
AnswerC

Aliases like 'champion' and 'challenger' can be assigned to versions and used for deployment.

Why this answer

Model Registry aliases allow tagging model versions with labels like 'champion' or 'challenger', enabling easy routing and comparison.

Full explanation →
68
Multi-Selectmedium

Which THREE factors should you consider when deciding between online prediction and batch prediction on Vertex AI?

Select 3 answers
A.The type of machine learning model architecture (e.g., CNN vs RNN)
B.Cost per prediction: batch is often cheaper per request
C.Latency requirements (real-time vs. asynchronous)
D.Traffic pattern: sporadic vs. sustained load
E.Availability of GPU instances in the region
AnswersB, C, D

Batch prediction is typically more cost-effective for large volumes.

Why this answer

Latency requirements, cost structure, and data volume patterns are key factors. Instance availability is similar for both; model architecture does not dictate prediction type.

Full explanation →
69
MCQmedium

A data engineer wants to create a BigQuery table snapshot for point-in-time recovery of a critical dataset. The snapshot should be created daily and retained for 30 days. What should they use?

A.BigQuery copy job
B.BigQuery time travel
C.BigQuery scheduled queries with CREATE SNAPSHOT
D.BigQuery export to Cloud Storage
AnswerC

Scheduled queries can create snapshots daily; retention can be set in the snapshot definition.

Why this answer

BigQuery table snapshots are created using the CREATE SNAPSHOT statement and can be scheduled with a retention period.

Full explanation →
70
MCQeasy

A retail company uses Vertex AI AutoML to train a product recommendation model. They have a dataset of past purchases stored in BigQuery. The data science team wants to iteratively train and improve the model. They need to track which dataset version was used for each model and preserve the exact data for reproducibility. They currently export data to CSV files and store them in Cloud Storage. However, the dataset is updated daily, and they want to ensure that models are trained on a consistent snapshot. What should they do?

A.Use Vertex AI Dataset service to create a dataset and export it to BigQuery.
B.Use BigQuery snapshots to capture a versioned dataset and reference the snapshot in the training pipeline.
C.Train the model directly on the BigQuery table and let AutoML handle versioning.
D.Export the data to a timestamped CSV file and store it in Cloud Storage before each training run.
AnswerB

Snapshots provide point-in-time consistency and are easy to manage.

Why this answer

BigQuery snapshots provide a consistent, versioned view of the dataset at a specific point in time, ensuring reproducibility without duplicating data. By referencing the snapshot in the Vertex AI training pipeline, the team can train models on the exact same data snapshot, even as the source table is updated daily. This approach avoids the overhead of exporting to CSV and Cloud Storage while maintaining data integrity and lineage.

Exam trap

Google Cloud often tests the misconception that exporting to CSV or using Vertex AI Dataset is sufficient for versioning, when in fact BigQuery snapshots provide the native, scalable, and auditable mechanism for point-in-time data consistency without data duplication.

How to eliminate wrong answers

Option A is wrong because the Vertex AI Dataset service is designed for managing training data within Vertex AI, but exporting to BigQuery does not inherently create a versioned snapshot; it simply moves data back to BigQuery without preserving a consistent point-in-time copy. Option C is wrong because training directly on a live BigQuery table does not guarantee a consistent snapshot; AutoML does not handle versioning, and the table may change between training runs, breaking reproducibility. Option D is wrong because exporting to a timestamped CSV file in Cloud Storage is a manual workaround that introduces storage overhead, potential data drift from export timing, and lacks the built-in versioning and query capabilities of BigQuery snapshots.

Full explanation →
71
MCQmedium

A data-processing pipeline using Dataflow needs to incorporate a custom ML prediction step. The team wants to maintain fast processing and minimize latency. What is the optimal approach?

A.Write the data to Cloud Storage, trigger a Cloud Function to call the model, and write results back
B.Use a custom ParDo transform in Dataflow that calls Vertex AI Prediction API directly
C.Send data to a Pub/Sub topic and have a separate subscriber that runs predictions
D.Stream data through Cloud Functions that serve predictions and write to BigQuery
AnswerB

Inline calls within Dataflow are efficient and keep the pipeline linear.

Why this answer

Using a custom ParDo transform in Dataflow allows the pipeline to call the Vertex AI Prediction API synchronously within each worker, avoiding the overhead of external triggers, intermediate storage, or asynchronous messaging. This keeps the data in-memory and minimizes latency by processing predictions inline with the Dataflow streaming or batch pipeline.

Exam trap

Google Cloud often tests the misconception that adding external services like Cloud Functions or Pub/Sub improves modularity without considering the latency penalty, leading candidates to choose options that introduce unnecessary hops instead of keeping prediction inline within the Dataflow pipeline.

How to eliminate wrong answers

Option A is wrong because writing data to Cloud Storage and triggering a Cloud Function introduces significant I/O latency and additional orchestration overhead, breaking the low-latency requirement. Option C is wrong because sending data to Pub/Sub and having a separate subscriber decouples the prediction step, adding network round-trips and potential backpressure issues that increase end-to-end latency. Option D is wrong because streaming data through Cloud Functions for predictions and then writing to BigQuery creates a multi-hop architecture with cold-start risks and no native Dataflow optimization for parallelism or state management.

Full explanation →
72
MCQmedium

A company deploys a model on Vertex AI Endpoints for real-time inference. They need to minimize latency for prediction requests that are identical to previous requests. Which approach should they use?

A.Use a regional load balancer with session affinity.
B.Implement a caching layer using Cloud Memorystore with request hashing.
C.Use Cloud CDN to cache prediction responses.
D.Enable prediction caching on Vertex AI Endpoints.
AnswerB

Cloud Memorystore (Redis) can cache prediction results keyed by a hash of the input request, reducing latency for duplicate requests.

Why this answer

Caching identical prediction requests using Cloud Memorystore with request hashing reduces latency by serving cached responses directly from an in-memory cache, avoiding redundant model inference. This approach is ideal for real-time inference where many requests are identical, as it bypasses the model endpoint entirely for cached requests, minimizing response time.

Exam trap

The trap here is that candidates may confuse Vertex AI's built-in features with external caching mechanisms, assuming 'prediction caching' is a native endpoint option when it is not, leading them to select option D.

How to eliminate wrong answers

Option A is wrong because a regional load balancer with session affinity distributes traffic based on client sessions, not request content, so it does not cache or reuse responses for identical requests, failing to reduce latency for repeated predictions. Option C is wrong because Cloud CDN caches static content at edge locations, but prediction responses from Vertex AI are dynamic and often require authentication or vary per request, making CDN caching unsuitable for real-time inference. Option D is wrong because Vertex AI Endpoints do not have a built-in 'prediction caching' feature; caching must be implemented externally, such as with Cloud Memorystore or Redis.

Full explanation →
73
MCQmedium

A team is using TensorFlow Transform (tf.Transform) to create preprocessing functions that will be used both in training and serving. They want to ensure consistency. Which artifact should they save after analyzing the training data?

A.A trained model checkpoint.
B.A analyzed_dataset directory with statistics.
C.A flattened schema file (schema.pbtxt).
D.A transform_fn SavedModel.
AnswerD

The transform_fn is the output of tf.Transform that applies the same transformation to new data.

Why this answer

The correct artifact to save after analyzing training data with tf.Transform is the `transform_fn` SavedModel. This SavedModel encapsulates the exact preprocessing logic (e.g., scaling, normalization, vocabulary mapping) computed from the training dataset, ensuring that the same transformations are applied consistently during both training and serving. Without this artifact, the serving pipeline would need to recompute or duplicate the transformation logic, risking skew between training and inference.

Exam trap

A common pitfall is to confuse intermediate analysis outputs (like statistics or schema) with the executable artifact (the SavedModel) that actually applies the transformation, leading candidates to mistakenly select the schema or statistics directory as the key artifact.

How to eliminate wrong answers

Option A is wrong because a trained model checkpoint stores the model weights and optimizer state after training, not the preprocessing function; it is used for resuming training or inference, not for ensuring consistent data transformations. Option B is wrong because an analyzed_dataset directory with statistics (e.g., mean, variance) is an intermediate output used to compute the transformation, but it is not the executable artifact that applies the transform; the actual transformation logic must be saved as a SavedModel. Option C is wrong because a flattened schema file (schema.pbtxt) describes the data schema (e.g., feature names, types, shapes) but does not contain the transformation operations; it is used for validation and metadata, not for executing the preprocessing pipeline.

Full explanation →
74
MCQhard

A company has a large dataset of 1 million unlabeled images for object detection. They want to use AutoML Vision but need to minimize labeling effort. Which strategy should they use?

A.Use Vertex AI Active Learning to choose a subset for labeling
B.Apply data augmentation techniques to increase dataset size
C.Manually label all 1 million images
D.Train a custom object detection model on unlabeled data with unsupervised learning
AnswerA

Active learning selects the most valuable images, reducing labeling effort significantly.

Why this answer

Vertex AI Active Learning is the correct strategy because it intelligently selects the most informative unlabeled images for human labeling, maximizing model accuracy while minimizing labeling effort. This approach uses the model's uncertainty to prioritize data points that will most improve performance, making it ideal for large datasets where manual labeling of all images is impractical.

Exam trap

Google Cloud often tests the misconception that data augmentation can replace the need for initial labeling, when in reality it only expands existing labeled data and does not address the core challenge of obtaining labels for unlabeled images.

How to eliminate wrong answers

Option B is wrong because data augmentation techniques increase dataset size by creating modified copies of existing labeled images, but they do not reduce the initial labeling effort required for the original dataset. Option C is wrong because manually labeling all 1 million images is prohibitively time-consuming and expensive, directly contradicting the goal of minimizing labeling effort. Option D is wrong because unsupervised learning cannot train a custom object detection model without labeled data; object detection requires bounding box annotations or similar labels to learn object locations and classes.

Full explanation →
75
MCQhard

A financial services company deploys a model on Vertex AI Endpoints with GPU acceleration. They notice that the p99 latency for predictions has increased from 200ms to 1.2s over the past week. CPU utilisation is low, but GPU utilisation is high. Which action should they take to reduce latency?

A.Increase the CPU machine type for the endpoint.
B.Switch to a more powerful GPU type (e.g., from T4 to A100).
C.Increase the number of replicas in the endpoint deployment.
D.Reduce the sampling rate for monitoring to free up resources.
AnswerC

More replicas spread the prediction load, reducing per-request latency.

Why this answer

High GPU utilisation with low CPU utilisation suggests the model is compute-bound on GPU. Scaling out by adding more replicas distributes the load, reducing queuing and latency.

Full explanation →

Page 1 of 14

Page 2

All pages

1234567891011121314

Practice PMLE by domain

Target a specific domain to shore up weak areas.

Automating and Orchestrating ML PipelinesCollaborating Within and Across Teams to Manage Data and ModelsServing and Scaling ModelsMonitoring ML SolutionsArchitecting Low-Code ML SolutionsScaling Prototypes into ML ModelsCollaborating to manage data and models
See all domains with question counts →