Courseiva

Google Professional Machine Learning Engineer (PMLE) — Questions 301–375

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

Take a mock examExam hub
Page 4

Page 5 of 14

Page 6
301
Multi-Selecthard

A company is migrating from an on-premises ML serving infrastructure to Vertex AI. They have multiple models that need to be served from the same endpoint with different traffic percentages. They also need to monitor prediction quality. Which THREE actions should they take? (Choose 3)

Select 3 answers
A.Deploy multiple model versions on the same endpoint with traffic_split parameter.
B.Deploy each model as a separate endpoint and use Cloud Load Balancing.
C.Enable Vertex AI Model Monitoring to detect prediction drift.
D.Use Cloud Monitoring to create custom metrics based on business outcomes.
E.Export logs to BigQuery for manual analysis only.
AnswersA, C, D

Vertex AI supports this natively for A/B testing.

Why this answer

Vertex AI endpoints support deploying multiple model versions and using the `traffic_split` parameter to distribute traffic percentages among them. This allows the company to serve different models from a single endpoint while controlling the proportion of requests each model receives, meeting the requirement for a unified serving infrastructure.

Exam trap

The trap here is that candidates may think separate endpoints with a load balancer (Option B) are required for traffic distribution, overlooking Google Vertex AI's built-in traffic splitting on a single endpoint, which is simpler and more aligned with the platform's design.

Full explanation →
302
Multi-Selecthard

A company is building a document processing pipeline using Document AI to extract data from invoices. They want to ensure high accuracy and handle edge cases where the model may be uncertain. Which THREE steps should they include in their pipeline?

Select 3 answers
A.Regularly retrain the processor using human-verified data
B.Use the pre-built invoice parser without any modifications
C.Use AutoML Vision to classify invoice types
D.Enable Human-in-the-Loop (HITL) to review documents with low confidence scores
E.Use a custom processor trained on their specific invoice format
AnswersA, D, E

Continuous improvement with human-labeled data helps the model learn from edge cases.

Why this answer

To improve accuracy, use human review for low-confidence documents, create a custom processor (or use a pre-built one) tailored to their invoice format, and continuously improve the model with human-labeled data. Using the form parser is a good start but not enough; they need to enable HITL and potentially train a custom processor.

Full explanation →
303
MCQmedium

A retailer uses BigQuery ML to build a linear regression model for sales forecasting. The model's evaluation shows high RMSE. Which step should they take first?

A.Use a more complex model like XGBoost
B.Increase the number of features
C.Set a larger training budget
D.Examine the data for outliers and missing values
AnswerD

Correct: Data quality inspection is the first step.

Why this answer

High RMSE in a linear regression model often indicates issues with data quality, such as outliers or missing values, which can disproportionately skew the model's predictions. BigQuery ML's linear regression is sensitive to such anomalies, so examining and cleaning the data is the most appropriate first step before considering model complexity or feature engineering.

Exam trap

Google Cloud often tests the misconception that high RMSE is always a model complexity issue, leading candidates to jump to advanced algorithms or feature engineering without considering fundamental data quality checks.

How to eliminate wrong answers

Option A is wrong because switching to a more complex model like XGBoost without first addressing data quality issues can amplify overfitting and does not fix the root cause of high RMSE. Option B is wrong because blindly increasing the number of features can introduce noise and multicollinearity, potentially worsening RMSE rather than improving it. Option C is wrong because setting a larger training budget in BigQuery ML does not improve model accuracy; it only allocates more resources for training, which is irrelevant when the issue stems from data problems.

Full explanation →
304
MCQmedium

An ML team wants to run a hyperparameter tuning job on Vertex AI using a pre-built pipeline component. Which component should they use?

A.AutoMLTabularTrainingJobRunOp
B.CustomTrainingJobRunOp with hyperparameter arguments.
C.ModelTrainComponent
D.HyperparameterTuningJobRunOp
AnswerD

This is the correct pre-built component for tuning.

Why this answer

The HyperparameterTuningJobRunOp is the correct pre-built Vertex AI pipeline component specifically designed to launch a hyperparameter tuning job. It wraps the Vertex AI HyperparameterTuningJob API, allowing you to specify the worker pool spec, metric target, and parameter specifications directly within a Kubeflow Pipelines (KFP) or Vertex AI Pipelines orchestration context.

Exam trap

A common mistake on the Google PMLE exam is confusing the pre-built HyperparameterTuningJobRunOp with CustomTrainingJobRunOp that accepts hyperparameter arguments, but the latter requires manual tuning logic rather than leveraging the built-in hyperparameter tuning service.

How to eliminate wrong answers

Option A is wrong because AutoMLTabularTrainingJobRunOp is used to launch an AutoML training job for tabular data, which does not support custom hyperparameter tuning; it uses AutoML's own search. Option B is wrong because CustomTrainingJobRunOp with hyperparameter arguments is not a pre-built component for tuning; it launches a single custom training job and would require manual orchestration to implement a tuning loop, whereas the question asks for a pre-built component. Option C is wrong because ModelTrainComponent is not a standard pre-built Vertex AI pipeline component; it is a generic name that does not correspond to any official Vertex AI component, and using it would require custom implementation.

Full explanation →
305
MCQhard

Two teams independently develop two different versions of a model for the same use case. They both deploy to the same Vertex AI endpoint, causing conflicts. What is the best way to manage multiple model versions and avoid conflicts in a collaborative environment?

A.Have each team work on a separate Google Cloud project
B.Use custom metadata to tag each version and rely on team coordination
C.Deploy each team's model to a separate endpoint
D.Use Vertex AI Model Registry with staging and production channels, and implement CI/CD to control promotions
AnswerD

Model registry with staging/production allows controlled version management and rollback.

Why this answer

Vertex AI Model Registry with staging and production channels provides a centralized system to manage model versions, track lineage, and control promotions via CI/CD pipelines. This prevents conflicts by enforcing a structured workflow for version updates. Option A is wrong because separate projects increase management overhead and do not address versioning within the same endpoint.

Option B is wrong because custom metadata lacks enforcement of deployment order and can lead to manual errors. Option C is wrong because deploying to separate endpoints does not resolve version conflicts; it merely isolates models, increasing complexity and cost.

Full explanation →
306
MCQhard

An organization is deploying a loan approval model and wants to monitor for fairness across demographic subgroups. They have ground truth labels stored in BigQuery. How can they use Vertex AI to evaluate performance disparities between groups?

A.Upload predictions and labels to Vertex AI Model Evaluation and specify slicing columns
B.Query BigQuery and manually compute metrics per group, then visualize in Looker
C.Enable Vertex AI Model Monitoring with fairness detection
D.Use Vertex AI Explainable AI to get feature attributions per subgroup
AnswerA

Sliced evaluation in Vertex AI Model Evaluation can compare metrics across subgroups defined by columns.

Why this answer

Vertex AI Model Evaluation provides sliced evaluation, which computes metrics (e.g., accuracy, precision) per subgroup when slicing columns are specified. This enables detection of performance disparities.

Full explanation →
307
MCQeasy

A company needs to extract entities (e.g., names, dates) from customer emails using a pre-trained model. Which service should they use?

A.Translation API
B.Natural Language API
C.Dialogflow
D.Vision API
AnswerB

Natural Language API can extract entities from text.

Why this answer

The Natural Language API provides entity extraction as a pre-trained model. Vision API is for images, Translation API for translation, and Dialogflow for conversational agents.

Full explanation →
308
MCQmedium

A data scientist needs to train a large PyTorch model on a custom dataset using Vertex AI. The training script expects data from Cloud Storage and uses GPU acceleration. Which option correctly configures a custom training job with a pre-built container for PyTorch and attaches a single NVIDIA V100 GPU?

A.Use a custom container built from PyTorch base image and specify accelerator_count=1 in the machine spec
B.Use the pre-built container 'us-docker.pkg.dev/vertex-ai/training/pytorch-gpu.1-12:latest' and in worker_pool_specs set machine_type='n1-standard-4', accelerator_type='NVIDIA_TESLA_V100', accelerator_count=1
C.Use the AI Platform Training service with gcloud ai-platform jobs submit training and --scale-tier BASIC_GPU
D.Create a training pipeline with AutoML and select GPU runtime
AnswerB

This correctly uses a pre-built container, sets the proper machine type and GPU accelerator.

Why this answer

In Vertex AI, worker_pool_specs define machine types and accelerators. Using a pre-built container for PyTorch 1.12 with image_uri 'us-docker.pkg.dev/vertex-ai/training/pytorch-gpu.1-12:latest' and specifying worker_count=1, machine_type='n1-standard-4' (or similar), and accelerator_type='NVIDIA_TESLA_V100' with count=1 sets up the job correctly.

Full explanation →
309
MCQmedium

An engineer deploys a model to a Vertex AI endpoint with minReplicas=1 and maxReplicas=3. The endpoint receives a sudden traffic spike, but it does not scale up beyond 1 replica. The CPU utilization target is 60%. What is the most likely cause?

A.The model is not deployed correctly.
B.The endpoint is configured with the wrong machine type.
C.The CPU utilization is below the target threshold, so the autoscaler does not add replicas.
D.The endpoint is using GPU which cannot autoscale.
AnswerC

If CPU utilization is below 60%, the autoscaler sees no need to scale up.

Why this answer

Vertex AI's autoscaler uses CPU utilization as a metric to decide when to add replicas. If the CPU utilization remains below the 60% target threshold, the autoscaler will not trigger scale-up, even during a traffic spike. The endpoint is configured with minReplicas=1 and maxReplicas=3, but without exceeding the target, it stays at the minimum.

Exam trap

The trap here is that candidates assume any traffic spike automatically triggers scaling, but Vertex AI's autoscaler only scales based on the configured metric (CPU utilization), not request volume directly.

How to eliminate wrong answers

Option A is wrong because the model being deployed correctly is unrelated to autoscaling behavior; a misdeployment would typically cause prediction failures or errors, not a failure to scale. Option B is wrong because the machine type affects performance and cost, but does not directly prevent the autoscaler from adding replicas when CPU utilization exceeds the target. Option D is wrong because GPU-enabled endpoints can autoscale; Vertex AI supports autoscaling for GPU instances, though GPU metrics may require custom configuration.

Full explanation →
310
MCQhard

A team deploys a TensorFlow model using a custom container to Vertex AI Endpoint. The container expects the saved model at the /model directory, but predictions fail with a 'model not found' error. The team used the default Vertex AI serving container in the past. What is the most likely cause?

A.The container does not have a GPU accelerator configured.
B.The model artifact must be downloaded from Cloud Storage and placed in /gcs.
C.The container reads from a fixed directory /model, but Vertex AI mounts the model at /tmp/model.
D.The model was saved in a different format (e.g., SavedModel vs. HDF5).
AnswerC

Custom containers must adapt to the Vertex AI model mount point.

Why this answer

When using a custom container, Vertex AI mounts the saved model artifact at the path specified by the environment variable AIP_STORAGE_URI, typically /tmp/model. The team's container expects the model at /model, but it is actually at /tmp/model, resulting in the 'model not found' error. Option A is wrong because the error is not related to GPU configuration.

Option B is wrong because Vertex AI does not download the model to /gcs; rather, it mounts the model directory. Option D is wrong because the model format (SavedModel vs HDF5) is not mentioned as an issue; the problem is the directory location.

Full explanation →
311
MCQmedium

A retailer wants to implement a recommendation engine that suggests products based on a user's current cart. They have limited ML expertise and want a quick deployment. Which Recommendations AI model type should they use?

A.Others you may like
B.Recently viewed
C.Recommended for you
D.Frequently bought together
AnswerD

Why this answer

The 'Frequently bought together' model type is the correct choice because it directly leverages collaborative filtering based on co-purchase patterns in historical transaction data, enabling the retailer to recommend items commonly purchased alongside the current cart contents. This model requires minimal ML expertise and can be quickly deployed using pre-built Recommendations AI templates, as it does not require user-level personalization or real-time session data.

Exam trap

In Google PMLE exams, candidates often mistakenly select 'Recommended for you' thinking it is the default or most versatile model, but the trap here is that they overlook the specific requirement of 'based on a user's current cart' and the need for quick deployment with limited ML expertise, which points to the simpler, cart-focused 'Frequently bought together' model instead.

How to eliminate wrong answers

Option A is wrong because 'Others you may like' is a generic model that relies on item similarity or user-based collaborative filtering, which typically requires more extensive user interaction history and ML tuning, not just the current cart context. Option B is wrong because 'Recently viewed' is a session-based model that recommends items based on the user's browsing history, not the contents of the current cart, and it does not capture co-purchase relationships. Option C is wrong because 'Recommended for you' is a personalized model that requires user-level behavioral data and often uses deep learning techniques, making it more complex to deploy and less suitable for a quick, low-ML-expertise solution focused on cart-based suggestions.

Full explanation →
312
Multi-Selecteasy

An organization wants to implement continuous delivery for their ML model. After a new model is trained and evaluated, they want to automatically deploy it to a staging endpoint, run validation tests, and if passed, promote to production. Which two components should they include in their delivery pipeline? (Choose two.)

Select 2 answers
A.Conditional component that checks evaluation metrics and promotes if successful
B.Dataflow job to preprocess data
C.ModelDeploymentOp to deploy to staging
D.Importer component to bring in the model
E.A/B testing component to split traffic
AnswersA, C

A conditional gate based on metrics decides whether to promote to production.

Why this answer

A conditional component that checks evaluation metrics (e.g., accuracy, precision, recall) against a predefined threshold is essential for automated promotion. This component acts as a gate, ensuring only models that meet quality criteria are promoted to production, which is a core requirement for continuous delivery in ML pipelines.

Exam trap

In Google Cloud ML pipelines, the key distinction is between deployment components (like ModelDeploymentOp in Vertex AI Pipelines) and data processing components (like Dataflow jobs). Candidates often mistakenly include preprocessing steps in the deployment pipeline instead of focusing on the deployment and validation logic.

Full explanation →
313
MCQeasy

A machine learning engineer needs to run batch predictions on 50 TB of data stored in BigQuery using a Vertex AI model. The model is a custom container. What is the most efficient way to set up the batch prediction job?

A.Create a Vertex AI batch prediction job with BigQuery source and BigQuery destination.
B.Use Dataflow to process the data and call the model via Vertex AI online prediction.
C.Export BigQuery data to CSV in GCS, then create a batch prediction job with GCS source.
D.Create a Cloud Function to iterate over BigQuery rows and call the endpoint.
AnswerA

Vertex AI batch prediction supports BigQuery directly for input and output.

Why this answer

Vertex AI batch prediction supports BigQuery as both input and output source, which is the most direct approach. Dataflow preprocessing is optional only if needed.

Full explanation →
314
MCQeasy

A data scientist wants to track machine learning experiments, including parameters, metrics, and artifacts, and compare runs. Which Vertex AI service should they use?

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

Correct service for experiment tracking and comparison.

Why this answer

Vertex AI Experiments is designed for tracking and comparing ML experiment runs, capturing parameters, metrics, and artifacts. It integrates with MLflow for autologging.

Full explanation →
315
Multi-Selectmedium

An organization is building a continuous training (CT) pipeline that retrains a model whenever one of the following conditions is met: (1) new training data is available in Cloud Storage, (2) it's the first day of the month, or (3) the model's performance degrades below a threshold. Which TWO mechanisms should they combine to trigger the pipeline?

Select 2 answers
A.Cloud Scheduler to trigger the pipeline on a cron schedule (e.g., first day of month)
B.Monitoring alerts from Cloud Monitoring to trigger a Cloud Function that starts the pipeline
C.Cloud Build trigger on code push to repository
D.BigQuery scheduled query to trigger the pipeline after data transformation
E.Cloud Storage Pub/Sub notifications to trigger a Cloud Function that starts the pipeline
AnswersA, E

Correct. Cloud Scheduler can trigger the pipeline on a cron schedule, satisfying condition (2) (first day of month).

Why this answer

Cloud Scheduler can trigger the pipeline on a cron schedule, such as the first day of every month, directly satisfying condition (2). Option E is correct because Cloud Storage Pub/Sub notifications can be configured to fire a Cloud Function whenever new training data is uploaded, satisfying condition (1). Condition (3), performance degradation, is not directly covered by any single option in the list; it would require a separate mechanism like Vertex AI Model Monitoring with Cloud Monitoring alerts.

Therefore, among the given options, A and E are the best combination for the conditions that have direct native support.

Exam trap

Candidates often confuse Cloud Monitoring (infrastructure metrics) with model performance monitoring. Cloud Monitoring does not natively evaluate model metrics like accuracy or F1 score, so using it to trigger retraining on performance degradation is incorrect.

Full explanation →
316
MCQeasy

A machine learning engineer is building a Vertex AI pipeline that uses a pre-built Google Cloud Pipeline Components (GCPC) to train a custom model. Which component should the engineer use to submit a custom training job to Vertex AI?

A.HyperparameterTuningJob
B.CustomJob
C.BatchPredictionJob
D.ModelDeploy
AnswerB

Correct: CustomJob (or TrainingJob) is the GCPC component to run a custom training job on Vertex AI.

Why this answer

The CustomJob component is the correct choice because it is the pre-built GCPC component specifically designed to submit a custom training job to Vertex AI. It allows the engineer to specify a custom container image or a Python training script, along with machine configuration and hyperparameters, directly within a Vertex AI pipeline. Other components serve different purposes, such as hyperparameter tuning, batch predictions, or model deployment.

Exam trap

The trap here is that candidates may confuse HyperparameterTuningJob with CustomJob because both involve training, but HyperparameterTuningJob is for multi-trial optimization, not a single training run, and ModelDeploy is a distractor that does not exist as a GCPC component.

How to eliminate wrong answers

Option A is wrong because HyperparameterTuningJob is used for optimizing hyperparameters across multiple trials, not for submitting a single custom training job. Option C is wrong because BatchPredictionJob is for running batch predictions on a trained model, not for training. Option D is wrong because ModelDeploy is not a standard GCPC component; the correct component for deploying a model to an endpoint is ModelDeployer or a similar deployment component, and ModelDeploy does not exist in the GCPC library.

Full explanation →
317
Multi-Selecthard

An ML team uses Vertex AI Workbench managed notebooks and wants to version their notebook code and collaborate using Git. Which THREE steps are required to set up Git integration? (Select 3)

Select 3 answers
A.Configure Git credentials (username/email) using git config.
B.Create a Cloud Source Repositories mirror of the GitHub repo.
C.Install git in the notebook environment if not already present.
D.Enable the Vertex AI Notebooks API for Git sync.
E.Clone the repository using git clone in a notebook cell.
AnswersA, C, E

Required for committing.

Why this answer

To use Git in managed notebooks, you need to install git, configure credentials, and clone the repository.

Full explanation →
318
MCQmedium

A data science team wants to share a set of engineered features across multiple projects and teams to reduce training-serving skew and ensure consistency. They need low-latency serving (single-digit milliseconds) for online predictions and also need to retrieve historical feature values for training. Which approach should they take?

A.Use Vertex AI Feature Store to define features once, serve online predictions from the online store, and retrieve historical features from the offline store for training.
B.Create a shared BigQuery dataset where each team writes features; serve predictions by querying BigQuery synchronously.
C.Store features in Cloud Storage Parquet files and load them into BigQuery for training; serve predictions from a custom microservice that reads from Cloud Storage.
D.Use Cloud Memorystore (Redis) to store the latest feature values for low-latency serving; each team independently computes features and pushes to Redis.
AnswerA

Vertex AI Feature Store provides both online (low-latency) and offline serving, centralizes features, and supports point-in-time queries to avoid leakage.

Why this answer

Vertex AI Feature Store is designed exactly for this purpose: it centralizes feature definitions and serves features online (using an online store) and offline (using BigQuery). The online store provides low-latency serving, and point-in-time queries allow training data creation without data leakage. This reduces training-serving skew across teams.

Full explanation →
319
MCQeasy

An organization needs to serve a large model (10 GB) with low latency across multiple regions. Which Vertex AI feature best meets this requirement?

A.Private endpoints
B.Batch prediction
C.Model Monitoring
D.Global endpoints
AnswerD

Global endpoints automatically route to the closest region, providing low latency across regions.

Why this answer

Global endpoints, is correct because Vertex AI Global Endpoints automatically route prediction requests to the nearest region with capacity, reducing latency for geographically distributed users. Option A, Private endpoints, is for secure VPC access, not multi-region latency. Option B, Batch prediction, is for offline batch jobs, not real-time serving.

Option C, Model Monitoring, is for observing model performance and drift, not for serving.

Full explanation →
320
MCQhard

A Vertex AI Pipeline contains a task that may produce outputs that are not always needed. The engineer wants to conditionally execute downstream tasks only if a specific artifact is produced. Which KFP SDK v2 construct allows the engineer to implement this conditional execution?

A.dsl.If
B.dsl.ExitHandler
C.dsl.Collected
D.dsl.Condition
AnswerA

dsl.If allows conditional branching based on task outputs or pipeline parameters.

Why this answer

The dsl.If construct in KFP SDK v2 allows conditional execution of tasks based on the presence or value of an output from a previous task. dsl.Collected is for parallel loops, exit handlers are for cleanup, and dsl.Condition is not a valid construct.

Full explanation →
321
MCQmedium

You are an ML engineer at a fintech company. You have a prototype credit risk model built using XGBoost that achieves high accuracy on historical data. The model is trained on a dataset with 500,000 rows and 50 features. The company wants to deploy this model to production to score loan applications in real-time. The production environment must handle a peak load of 100 requests per second with a latency under 200ms. You have decided to use Vertex AI for deployment. After deploying the model as a Vertex AI endpoint with a single n1-standard-4 machine, you notice that latency exceeds 500ms at peak load and some requests time out. You have verified that the model prediction itself (excluding network overhead) takes about 50ms on average. What should you do to meet the latency and throughput requirements?

A.Change the machine type to a GPU-accelerated machine like n1-standard-4 with a T4 GPU.
B.Prune the model to reduce size and improve prediction speed.
C.Enable autoscaling with a minimum of 2 replicas and use a larger machine type (e.g., n1-standard-8) to handle more concurrent requests.
D.Switch from online prediction to batch prediction using Vertex AI Batch Prediction.
AnswerC

Autoscaling increases replicas to handle load, and a larger machine can process more requests concurrently, reducing queueing time.

Why this answer

The latency bottleneck is not the model inference time (50ms) but the inability of a single n1-standard-4 machine to handle 100 concurrent requests per second without queuing. By enabling autoscaling with a minimum of 2 replicas and upgrading to n1-standard-8, you increase both the number of concurrent requests the endpoint can process and the CPU/memory resources per replica, reducing queue wait times and keeping total latency under 200ms. This directly addresses the throughput and latency requirements without changing the model or switching to batch processing.

Exam trap

The trap here is that candidates assume latency issues are always due to model inference speed (leading them to choose GPU or model pruning), when in fact the bottleneck is often the lack of horizontal scaling to handle concurrent requests under load.

How to eliminate wrong answers

Option A is wrong because adding a GPU (e.g., T4) does not reduce latency for XGBoost inference; XGBoost is CPU-optimized and GPU acceleration typically adds overhead for tree-based models, making latency worse. Option B is wrong because pruning the model (e.g., reducing tree depth or number of trees) would only marginally improve the 50ms prediction time, but the primary issue is queuing due to insufficient replicas to handle 100 requests per second, not the raw inference speed. Option D is wrong because batch prediction is designed for offline, asynchronous processing and cannot meet the real-time requirement of under 200ms latency per request; it also does not solve the concurrency problem for online scoring.

Full explanation →
322
Multi-Selecthard

Which TWO actions should be taken to ensure reproducibility of ML experiments when collaborating across teams on Vertex AI?

Select 2 answers
A.Lock dependency versions in a container image used for training
B.Share notebooks via Colab Enterprise with real-time editing
C.Version control datasets using DVC or Vertex AI ML Metadata
D.Allow each team to use their own preferred environment
E.Always use random seeds for all random operations
AnswersA, C

Container images with fixed versions ensure environment reproducibility.

Why this answer

Locking dependency versions in a container image ensures that the exact same software environment (e.g., Python packages, CUDA libraries, system tools) is used every time a training job runs. This eliminates variability from package updates or OS patches, which is a fundamental requirement for reproducibility across teams. Vertex AI supports custom containers for training, making this a direct and reliable method.

Exam trap

The trap here is that candidates often think 'always use random seeds' is a safe blanket rule, but in practice, seeds must be explicitly set and logged per run, and some operations (e.g., certain GPU kernels) are inherently non-deterministic, making this option an oversimplification that is not a guaranteed action for reproducibility.

Full explanation →
323
MCQmedium

You are using KFP SDK v2 to define a pipeline. You need to pass a large dataset between components. What is the best practice for passing data?

A.Use the component's temporary directory to share data between containers.
B.Pass the data as a serialized Python object in memory.
C.Write the data to Cloud Storage and pass the GCS URI as an artifact.
D.Store the data in a BigQuery table and pass the table reference.
AnswerC

This is the recommended best practice for large data in KFP pipelines.

Why this answer

In KFP SDK v2, passing large datasets between components is best done by writing the data to Cloud Storage and passing the GCS URI as an artifact. This approach leverages KFP's built-in artifact tracking, ensures data persistence across container restarts, and avoids memory or disk limitations of ephemeral containers. The artifact is automatically serialized and passed as an input/output parameter, enabling efficient, scalable data exchange.

Exam trap

Google often tests the misconception that temporary directories are shared between containers in a pod, but in KFP each component runs in its own container with isolated storage, making Cloud Storage the correct choice for durable, cross-component data sharing.

How to eliminate wrong answers

Option A is wrong because a component's temporary directory is ephemeral and not shared between containers; each container runs in its own isolated filesystem, so data written there is lost after the component finishes. Option B is wrong because passing a serialized Python object in memory is limited by the container's memory capacity and cannot handle large datasets; KFP does not support in-memory object passing between components. Option D is wrong because storing data in a BigQuery table and passing the table reference is overkill for intermediate pipeline data; it introduces unnecessary latency, cost, and complexity compared to using Cloud Storage artifacts, which are the standard for KFP artifact passing.

Full explanation →
324
Multi-Selecthard

Which THREE of the following are valid ways to share a Vertex AI model across two different Google Cloud projects?

Select 3 answers
A.Use Vertex AI Model Registry's cross-project sharing feature with IAM conditions.
B.Publish the model to Google Cloud Marketplace.
C.Export the model to a Cloud Storage bucket accessible by both projects and import into the second project.
D.Use IAM to grant the second project's service account Vertex AI User role on the model resource.
E.Use the gcloud ai models copy command to copy the model across projects.
AnswersA, C, D

Model Registry supports sharing model versions across projects with fine-grained IAM.

Why this answer

Vertex AI Model Registry supports cross-project sharing by allowing you to grant IAM roles with conditions on the model resource. This enables a model registered in one project to be accessed by a service account from another project without moving or copying the model artifacts.

Exam trap

The trap here is that candidates may assume a dedicated copy command exists for moving models across projects, but Vertex AI relies on IAM-based sharing or export/import workflows instead.

Full explanation →
325
MCQeasy

A data scientist wants to evaluate the performance of a BigQuery ML classification model on a test dataset. Which function should they use?

A.ML.PREDICT
B.ML.FEATURE_IMPORTANCE
C.ML.EVALUATE
D.ML.TRAIN
AnswerC

Why this answer

ML.EVALUATE is the correct function because it computes classification metrics (e.g., precision, recall, accuracy, F1 score, ROC AUC) directly on a trained BigQuery ML model using a provided test dataset or evaluation input. This is the dedicated function for assessing model performance after training, aligning with the task of evaluating a classification model on held-out test data.

Exam trap

Google often tests the distinction between prediction (ML.PREDICT) and evaluation (ML.EVALUATE), trapping candidates who confuse generating outputs with measuring performance, especially when the question mentions 'evaluate performance' but the candidate fixates on 'predict' as the primary ML function.

How to eliminate wrong answers

Option A is wrong because ML.PREDICT is used to generate predictions (class labels or probabilities) on new data, not to compute evaluation metrics like accuracy or precision. Option B is wrong because ML.FEATURE_IMPORTANCE is used to retrieve feature weights or importance scores from a trained model (e.g., for interpretability), not to evaluate overall model performance on a test set. Option D is wrong because ML.TRAIN is used to initiate the training process of a BigQuery ML model, not to evaluate an already trained model on test data.

Full explanation →
326
MCQeasy

A small business wants to build a sentiment analysis model for customer reviews without writing any code. They have a small labeled dataset with 500 positive and 500 negative reviews. Which Google Cloud service should they use?

A.AutoML Natural Language
B.Natural Language API
C.Vertex AI custom training with PyTorch
D.BigQuery ML with logistic regression
AnswerA

Allows training a custom model with a GUI and no code.

Why this answer

AutoML Natural Language is the correct choice because it allows the business to train a custom sentiment analysis model using their own labeled dataset without writing any code. It provides a low-code interface for uploading data, training, and deploying the model, which aligns with the requirement of no coding and a small labeled dataset.

Exam trap

The trap here is that candidates often confuse the pre-trained Natural Language API with AutoML Natural Language, assuming the API can be customized with labeled data, but the API is fixed and cannot be retrained, while AutoML is designed for custom model training without code.

How to eliminate wrong answers

Option B is wrong because the Natural Language API is a pre-trained model that cannot be fine-tuned with custom labeled data; it only offers general sentiment analysis and would not leverage the business's specific 500/500 dataset. Option C is wrong because Vertex AI custom training with PyTorch requires writing code to define the model architecture and training loop, which violates the 'without writing any code' constraint. Option D is wrong because BigQuery ML with logistic regression is designed for structured tabular data, not for text sentiment analysis, and it would require feature engineering and SQL-based model definition, which is not a true no-code solution for text.

Full explanation →
327
MCQmedium

A data scientist is using Vertex AI Workbench user-managed notebooks. They need to collaborate with a colleague on the same notebook. The colleague should be able to edit the notebook simultaneously. What should they do?

A.Store the notebook in Cloud Source Repositories and have the colleague clone it
B.Share the underlying Compute Engine VM's SSH access with the colleague
C.Export the notebook to Colab and share the link
D.Share the notebook instance URL with the colleague; both can edit simultaneously
AnswerD

Vertex AI Workbench supports real-time collaboration through the same instance.

Why this answer

Vertex AI Workbench user-managed notebooks support real-time collaboration by sharing the notebook instance URL. When you share the URL with a colleague, both users can edit the notebook simultaneously because the underlying JupyterLab environment is multi-user and supports concurrent editing sessions. This is the intended method for synchronous collaboration on the same notebook instance.

Exam trap

Google Cloud often tests the misconception that version control (like Cloud Source Repositories) is the correct way to collaborate on notebooks, but the question specifically asks for simultaneous editing, which requires a real-time collaboration feature like sharing the notebook instance URL.

How to eliminate wrong answers

Option A is wrong because Cloud Source Repositories is a Git-based version control system for storing code, not a real-time collaboration tool; cloning a notebook does not allow simultaneous editing. Option B is wrong because sharing SSH access to the Compute Engine VM would give the colleague full system-level access, which is insecure and unnecessary for notebook editing, and it does not enable simultaneous editing in JupyterLab. Option C is wrong because exporting to Colab creates a separate copy of the notebook in a different environment, breaking the connection to the original Vertex AI Workbench instance and preventing simultaneous editing on the same notebook.

Full explanation →
328
MCQmedium

A company has a model serving predictions on Vertex AI Endpoints and wants to monitor for prediction drift. They enable Vertex AI Model Monitoring but also need to see a confusion matrix over time. How should they set up the confusion matrix monitoring?

A.Use Cloud Monitoring to create a custom dashboard with a confusion matrix chart
B.Export predictions to Cloud Storage and run a Dataflow job to compute confusion matrices
C.Upload ground truth data to BigQuery and use Vertex AI Model Monitoring's model quality monitoring
D.Enable Vertex AI Explainable AI and configure it to output confusion matrices
AnswerC

Model quality monitoring in Vertex AI Model Monitoring uses ground truth from BigQuery to generate confusion matrices.

Why this answer

Vertex AI Model Monitoring can compute confusion matrices when ground truth labels are provided in BigQuery. The service compares predictions against actuals and can output confusion matrices over time windows.

Full explanation →
329
Multi-Selecteasy

Which TWO actions can help reduce the latency of online prediction requests for a deep learning model served on Vertex AI?

Select 2 answers
A.Increase the number of CPU vCPUs per machine.
B.Set min_replica_count to 0 to avoid idle instances.
C.Use a GPU accelerator for the deployed model.
D.Decrease the number of replicas to reduce resource contention.
E.Enable request batching to process multiple inputs together.
AnswersC, E

GPU accelerates deep learning inference.

Why this answer

Using a GPU accelerator speeds up inference, and batching requests reduces overhead per request. Minimizing replicas doesn't help latency; increasing CPU doesn't always help if GPU is better.

Full explanation →
330
MCQmedium

You are designing a distributed training job on Vertex AI for a PyTorch model using DataDistributedParallel (DDP). You have 4 nodes, each with 4 GPUs. What is the total number of workers that should be configured in the TF_CONFIG equivalent for PyTorch?

A.4
B.8
C.1
D.16
AnswerD

Total GPUs across all nodes: 4 nodes * 4 GPUs = 16 workers.

Why this answer

In PyTorch DDP on Vertex AI, each GPU typically runs one process. With 4 nodes each with 4 GPUs, the world size is 16 (total GPUs). Vertex AI distributed training uses TF_CONFIG to set up the cluster; for PyTorch, you need to set the number of workers to the total number of processes, which is 16.

Full explanation →
331
MCQhard

A data scientist uses Vertex AI Pipelines to orchestrate an ML workflow. They want to reuse a component from Google's curated repository. What is the recommended way to incorporate it?

A.Import the component from Google Cloud Build
B.Use the 'aiplatform' Python SDK to define the component
C.Use prebuilt components from the Google Cloud Pipeline Components repository
D.Copy the component code into the pipeline definition
AnswerC

These are officially maintained and can be directly used in Vertex AI Pipelines.

Why this answer

Google provides a curated set of prebuilt components in the Google Cloud Pipeline Components repository, which are designed to be directly imported and used within Vertex AI Pipelines. These components encapsulate common ML tasks (e.g., model training, deployment) and are maintained by Google, ensuring compatibility and reducing custom code. Using them is the recommended approach to avoid reinventing the wheel and to leverage Google's best practices.

Exam trap

The trap here is that candidates may confuse the 'aiplatform' SDK (used for direct API calls) with the pipeline components SDK, or assume that copying code is acceptable for reusability, when Google specifically recommends using the curated prebuilt components to ensure compatibility and reduce maintenance overhead.

How to eliminate wrong answers

Option A is wrong because Google Cloud Build is a CI/CD service for building and testing code, not a repository for reusable pipeline components; importing a component from Cloud Build would not provide the curated, prebuilt component logic needed for Vertex AI Pipelines. Option B is wrong because the 'aiplatform' Python SDK is used to interact with Vertex AI services (e.g., creating datasets, jobs) but does not define or import prebuilt pipeline components; defining a component from scratch would bypass the curated repository. Option D is wrong because copying component code into the pipeline definition defeats the purpose of reusability and maintainability, and it is not the recommended method; the curated repository provides versioned, tested components that should be referenced rather than duplicated.

Full explanation →
332
Multi-Selecteasy

Which TWO actions are appropriate when you detect that a production model's prediction distribution has shifted significantly from the training distribution?

Select 2 answers
A.Immediately roll back to the previous model version
B.Increase logging for future predictions
C.Retrain the model using the most recent data
D.Investigate the cause of the shift before taking corrective action
E.Reduce the traffic to the model to minimize impact
AnswersC, D

Adapts model to new distribution.

Why this answer

Retraining the model on the most recent data directly addresses the distribution shift by adapting the model to the new data patterns. This is a standard practice in MLOps when the shift is confirmed and the cause is understood, ensuring the model remains accurate and reliable in production.

Exam trap

Google Cloud often tests the misconception that immediate rollback or traffic reduction is the correct first action, when in fact the proper response is to investigate the cause before taking corrective action like retraining.

Full explanation →
333
MCQeasy

Which Vertex AI service is used to track the lineage of ML pipeline components, artefacts, and executions?

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

Metadata is the ML metadata store for lineage.

Why this answer

Vertex AI Metadata (ML Metadata) stores and queries lineage information.

Full explanation →
334
MCQhard

You need to preprocess a large dataset (terabytes) for training a TensorFlow model. The preprocessing includes scaling and bucketizing features, and the same transformations must be applied during serving. Which tool should you use?

A.Dataflow with Apache Beam and tf.Transform
B.Dataproc with Spark ML
C.Vertex AI Feature Store
D.BigQuery ML
AnswerA

tf.Transform runs on Dataflow to scale, and produces a saved model for consistent serving.

Why this answer

TensorFlow Transform (tf.Transform) allows you to define preprocessing pipelines that are applied consistently during training and serving. It computes statistics over the full dataset and creates a TensorFlow graph for serving.

Full explanation →
335
MCQhard

A team is using Vertex AI AutoML to train a forecasting model. They need to retrain the model weekly and only if the new week's data significantly changes the data distribution. What is the most efficient way to achieve this?

A.Use a scheduled pipeline that always retrains
B.Use Cloud Monitoring alerts on data drift to trigger retraining
C.Use Vertex AI Model Monitoring to detect drift and trigger a pipeline
D.Use Cloud Functions on schedule to compare distributions
AnswerC

Correct: Native drift detection and retriggering.

Why this answer

Vertex AI Model Monitoring can be configured to detect data drift on the model's input features, and when drift exceeds a threshold, it can trigger a Cloud Function or a Vertex AI pipeline to retrain the model. This approach avoids unnecessary retraining when the data distribution has not changed significantly, which is more efficient than always retraining. The integration with Cloud Functions or Pub/Sub allows for a serverless, event-driven retraining pipeline that only runs when needed.

Exam trap

Google Cloud often tests the distinction between infrastructure monitoring (Cloud Monitoring) and model-specific monitoring (Vertex AI Model Monitoring), and candidates mistakenly choose Cloud Monitoring because they think it can detect data drift, but it lacks the statistical algorithms needed for feature-level distribution comparison.

How to eliminate wrong answers

Option A is wrong because a scheduled pipeline that always retrains ignores the requirement to retrain only when the new week's data significantly changes the data distribution, leading to wasted compute resources and potential model instability from unnecessary retraining. Option B is wrong because Cloud Monitoring alerts are designed for infrastructure and application metrics (e.g., CPU, latency), not for detecting data drift in model features; data drift detection requires feature-level statistical analysis, which is not a built-in capability of Cloud Monitoring. Option D is wrong because using Cloud Functions on a schedule to compare distributions would require custom code to compute statistical tests (e.g., KS test) and manage state, which is less efficient and more error-prone than using Vertex AI Model Monitoring's managed drift detection service.

Full explanation →
336
MCQhard

You are a machine learning engineer at a financial technology company. You have deployed a complex ensemble model consisting of three sub-models (XGBoost, TensorFlow, and PyTorch) for real-time fraud detection. The model is served on Vertex AI online prediction with a custom container that orchestrates the three models sequentially. The endpoint currently uses n1-highmem-8 machines with no accelerators. You are experiencing high latency (avg 500ms) during peak trading hours (9:30 AM - 4:00 PM EST), exceeding the 200ms SLA. The container is CPU-bound, and memory usage is around 60%. The model weights total 500 MB. You have already tried increasing the batch size per request from 1 to 4, which reduced latency slightly but not enough. The traffic pattern is very spiky, with sudden bursts of up to 1000 requests per second. Your goal is to meet the latency SLA without significantly increasing cost. Which action should you take?

A.Add a NVIDIA T4 GPU accelerator to the existing machine type.
B.Reduce the min_replica_count to 0 to allow scaling down aggressively and add more replicas during spikes.
C.Increase the machine type to n1-highmem-16 with more vCPUs.
D.Switch the model to Vertex AI batch prediction and run predictions every hour.
AnswerA

GPU accelerates the deep learning parts, reducing total latency.

Why this answer

Adding a GPU accelerator (e.g., NVIDIA T4) to the instances can significantly speed up the TensorFlow and PyTorch components, which are deep learning models. The XGBoost part runs on CPU but the overall latency bottleneck is likely the deep learning models. GPU will accelerate inference of those models, reducing total latency.

Increasing CPUs will help only marginally as the main bottleneck is compute. Reducing min replicas may increase cold start and queue. Switching to batch prediction changes the model from real-time to batch, which does not meet the latency requirement.

Full explanation →
337
MCQmedium

A company implements an ML pipeline using Vertex AI Pipelines. The pipeline trains a model using custom training jobs and then deploys it to an endpoint. The team notices that the endpoint occasionally serves an older model version for a few minutes after a new pipeline run completes. What is the most likely cause?

A.The new model artifact is temporarily unavailable, so the endpoint falls back to the previous version.
B.The prediction cache is returning cached results from the old model.
C.The pipeline failed to update the endpoint with the new model ID.
D.The endpoint is configured with a canary traffic split, and the old model is still receiving a fraction of traffic during the rollout.
AnswerD

Canary deployments gradually shift traffic, so some requests hit the old model until the rollout is complete.

Why this answer

D is correct because Vertex AI endpoints can be configured with a canary (gradual) traffic rollout strategy. When a new model is deployed, traffic is shifted incrementally from the old model to the new one over a specified duration. During this rollout window, the old model continues to serve a fraction of requests, which explains why users occasionally see the older model version for a few minutes after the pipeline completes.

Exam trap

The trap here is that candidates confuse a canary rollout with a deployment failure or caching issue, assuming the old model persists due to an error rather than recognizing it as an intentional traffic-splitting mechanism during a gradual rollout.

How to eliminate wrong answers

Option A is wrong because Vertex AI endpoints do not automatically fall back to a previous model version when a new artifact is temporarily unavailable; instead, the deployment would fail or the endpoint would return an error. Option B is wrong because Vertex AI endpoints do not have a built-in prediction cache that returns cached results from an old model; caching is not a default behavior for model serving. Option C is wrong because if the pipeline failed to update the endpoint with the new model ID, the endpoint would consistently serve the old model, not just occasionally for a few minutes.

Full explanation →
338
Multi-Selecthard

A company runs a Vertex AI pipeline that uses a container component to preprocess data. The component downloads a large file from a public URL and saves the output to Cloud Storage. The pipeline fails intermittently with a 'timeout' error. Which THREE steps should the team take to improve reliability? (Choose three.)

Select 3 answers
A.Make the component idempotent by checking for existing output before processing.
B.Increase the component's timeout setting.
C.Reduce the size of the file being downloaded.
D.Implement retries with exponential backoff in the component.
E.Increase the machine type for the component.
AnswersA, B, D

Correct: Idempotency ensures that if a retry occurs, it doesn't cause duplicate work.

Why this answer

Making the component idempotent by checking for existing output before processing prevents redundant work and avoids timeout failures when the file has already been downloaded. In Vertex AI pipelines, idempotent components can safely skip processing if the output already exists in Cloud Storage, reducing the risk of hitting timeout limits on subsequent pipeline runs.

Exam trap

Google exams often test the distinction between fixing the symptom (increasing timeout) and addressing the root cause (idempotency and retries), leading candidates to overlook that idempotency and retries together with a reasonable timeout form the most robust solution.

Full explanation →
339
Multi-Selecthard

You are designing a batch prediction pipeline using Vertex AI. The input data is 100 TB of images stored in Cloud Storage. The model is a custom TensorFlow model that expects TFRecord format. The pipeline must be cost-effective and run within a time window of 2 hours. Which THREE steps should you include?

Select 3 answers
A.Store batch prediction results in BigQuery.
B.Create a Vertex AI batch prediction job with input from GCS (TFRecord files).
C.Use Dataflow to read images and write TFRecord files to GCS.
D.Store batch prediction results in GCS.
E.Use Cloud Functions to convert images to TFRecord.
AnswersB, C, D

Batch prediction supports GCS input.

Why this answer

Vertex AI batch prediction jobs natively accept TFRecord files stored in Cloud Storage as input, which aligns with the requirement for a custom TensorFlow model. This approach is cost-effective and can complete within 2 hours by leveraging Vertex AI's managed infrastructure, avoiding the need to spin up and manage compute resources manually.

Exam trap

Google often tests the misconception that Cloud Functions can handle large-scale data processing tasks, but the trap here is that Cloud Functions have strict timeout and memory limits, making them unsuitable for converting 100 TB of images to TFRecord format.

Full explanation →
340
MCQeasy

You have an online prediction model that is showing increasing prediction latency. You have already verified that the request rate and input data size are unchanged. Which of the following should you investigate next?

A.Check if the model was recently updated to a larger version
B.Check the monitoring dashboard configuration
C.Check if the feature engineering logic was changed
D.Check the geographic location of the endpoint
AnswerA

Larger model increases inference latency.

Why this answer

If request rate and input data size are unchanged, increased prediction latency often points to a change in the model itself. A larger model (e.g., deeper neural network, more parameters) requires more computation per inference, directly increasing latency. This is a common root cause when monitoring ML pipelines, as model version updates can silently alter performance characteristics.

Exam trap

Google Cloud often tests the distinction between network-level latency (e.g., geographic location) and compute-level latency (e.g., model size), tempting candidates to pick the geographic option when the root cause is model-related.

How to eliminate wrong answers

Option B is wrong because the monitoring dashboard configuration only affects how metrics are displayed or alerted, not the underlying latency of predictions. Option C is wrong because feature engineering logic changes would alter input data size or structure, but the question states input data size is unchanged. Option D is wrong because the geographic location of the endpoint affects network latency, not the model's prediction latency (which is server-side compute time).

Full explanation →
341
MCQmedium

A company wants to transcribe customer service calls in real-time. The audio is telephony quality (8 kHz). Which Speech-to-Text model should they specify?

A.latest_short
B.latest_long
C.telephony
D.default
AnswerC

Why this answer

The 'telephony' model is optimised for audio from phone calls (8 kHz). 'latest_long' is for long-form non-telephony audio, 'latest_short' for short utterances, and there is no 'default' model.

Full explanation →
342
MCQmedium

A machine learning engineer needs to deploy a model to an endpoint for real-time predictions. The model is registered in Vertex AI Model Registry. Which command should they use to create an endpoint and deploy the model with the alias 'champion'?

A.gcloud ai models upload --model=my-model --alias=champion --endpoint=my-endpoint
B.gcloud ai endpoints deploy-model --endpoint=my-endpoint --model=my-model --alias=champion
C.gcloud ai endpoints predict --model=my-model --alias=champion
D.gcloud ai endpoints create --model=my-model --alias=champion
AnswerB

This deploys the model version with alias 'champion' to the endpoint.

Why this answer

The correct command uses `gcloud ai endpoints deploy-model` with the model's resource name and alias.

Full explanation →
343
MCQmedium

A company needs to analyze customer feedback from app reviews to identify common themes and sentiment. They have millions of reviews in multiple languages. Which combination of pre-built APIs should they use?

A.Speech-to-Text then Natural Language API
B.Natural Language API only
C.Translation API then Natural Language API
D.Vision API then Natural Language API
AnswerC

Translate reviews to a common language, then analyze sentiment and entities.

Why this answer

Natural Language API can perform sentiment analysis and entity extraction. Translation API can translate non-English reviews to English before analysis. Speech-to-Text is for audio.

Vision API is for images.

Full explanation →
344
MCQmedium

A data science team needs to serve multiple versions of the same ML model on Vertex AI Endpoints for A/B testing. They want to gradually shift traffic from the current 'champion' model to a new 'challenger' model. Which feature should they use?

A.Deploy the challenger to a separate endpoint and use a proxy to split traffic.
B.Use Cloud Load Balancing with weighted backend services.
C.Deploy both models to the same endpoint and use traffic splitting.
D.Use Vertex AI Experiments to manage model versions.
AnswerC

Vertex AI endpoints allow deploying multiple model versions and assigning traffic percentages to each, enabling gradual rollouts and A/B testing.

Why this answer

Vertex AI Endpoints natively support traffic splitting, allowing you to deploy multiple model versions (e.g., champion and challenger) to the same endpoint and assign a percentage of traffic to each. This enables gradual A/B testing without additional infrastructure, as the endpoint automatically routes requests based on the configured split. Option C is correct because it leverages this built-in feature, which is designed specifically for this use case.

Exam trap

The PMLE exam often tests the misconception that traffic splitting requires external load balancers or proxies, when in fact Vertex AI Endpoints provide this capability natively, and candidates may overlook the built-in feature in favor of more complex architectures.

How to eliminate wrong answers

Option A is wrong because deploying the challenger to a separate endpoint and using a proxy adds unnecessary complexity, latency, and management overhead; Vertex AI Endpoints already provide traffic splitting without external proxies. Option B is wrong because Cloud Load Balancing operates at the network layer (HTTP(S) or TCP/UDP) and is designed for distributing traffic across regional backends, not for splitting traffic between model versions on the same Vertex AI Endpoint; it would require separate endpoints and does not integrate with Vertex AI's model versioning. Option D is wrong because Vertex AI Experiments is a tool for tracking and comparing model training runs and hyperparameters, not for serving or routing live traffic; it has no mechanism to split traffic between deployed models.

Full explanation →
345
MCQhard

A company uses Vertex AI Prediction with a custom container for a TensorFlow model. They notice that after deploying a new model version, requests still go to the old version. What is the most likely cause?

A.The custom container is not compatible with Vertex AI
B.The model is cached and needs cache invalidation
C.Traffic is not split to the new model version
D.The new model version was not deployed to the same endpoint
AnswerC

Traffic splitting must be adjusted to route to the new version.

Why this answer

In Vertex AI Prediction, when you deploy a new model version to an existing endpoint, you must explicitly allocate traffic to it. By default, the new version receives 0% traffic, so all requests continue to be served by the old version. The correct fix is to update the endpoint's traffic split, for example via the console or the `gcloud ai endpoints update` command with the `--traffic-split` flag.

Exam trap

Google Cloud often tests the misconception that deploying a new model version automatically replaces the old one, when in fact Vertex AI requires an explicit traffic split update to shift requests to the new version.

How to eliminate wrong answers

Option A is wrong because Vertex AI supports custom containers for TensorFlow models as long as they implement the required HTTP health check and prediction endpoints; incompatibility would cause deployment failure, not silent routing to an old version. Option B is wrong because Vertex AI does not cache model predictions at the endpoint level; caching is not a factor in traffic routing between model versions. Option D is wrong because deploying to the same endpoint is exactly what the user did; the issue is that the new version was deployed but not given any traffic share, not that it was deployed to a different endpoint.

Full explanation →
346
Multi-Selecthard

A retail company deploys a new recommendation model alongside the current champion on Vertex AI Endpoints. They want to gradually shift traffic to the challenger while monitoring business metrics (conversion rate). Which two steps are required? (Choose 2)

Select 2 answers
A.Use Vertex AI Experiments to track the traffic split percentages.
B.Enable Cloud Memorystore to cache identical requests for both models.
C.Deploy the challenger model to the same endpoint as the champion with a separate deployed model.
D.Configure traffic split in the endpoint's traffic_split field (e.g., champion:90, challenger:10).
E.Use Cloud Monitoring to track custom metrics like conversion rate per model version.
AnswersC, D

Multiple models can be deployed on one endpoint with traffic allocation.

Why this answer

Vertex AI Endpoints support deploying multiple model versions (champion and challenger) to the same endpoint, each as a separate deployed model. This allows the endpoint to serve both models simultaneously, enabling traffic splitting without requiring separate endpoints or infrastructure.

Exam trap

This question tests the distinction between monitoring (which is optional after deployment) and the actual configuration steps required to shift traffic; candidates mistakenly select Cloud Monitoring (Option E) as a required step, but the question specifically asks for steps to 'gradually shift traffic,' which is accomplished by deploying to the same endpoint and setting the traffic split, not by monitoring after the fact.

Full explanation →
347
MCQmedium

A data engineer needs to version large datasets (multiple TB) in a Data Lake on Google Cloud. They require ACID transactions to ensure consistency when multiple jobs read/write concurrently. Which solution should they use?

A.Delta Lake on Dataproc
B.BigQuery table snapshots
C.DVC (Data Version Control)
D.Vertex AI Feature Store
AnswerA

Delta Lake provides ACID transactions on cloud storage, ideal for concurrent reads/writes on data lakes.

Why this answer

Delta Lake on Dataproc provides ACID transactions on cloud storage data lakes, enabling concurrent reads/writes with consistency.

Full explanation →
348
MCQmedium

You are monitoring a machine learning pipeline that runs on Vertex AI Pipelines. The pipeline occasionally fails with a 'ResourceExhausted' error when attempting to read data from BigQuery. Which action should you take to resolve this issue?

A.Switch from BigQuery to Cloud Storage for data source
B.Increase the memory allocated to the pipeline step
C.Reduce the complexity of the BigQuery query or increase the reservation size
D.Reduce the batch size of the data being read
AnswerC

ResourceExhausted error is due to BigQuery limits; simplifying query or increasing slots can help.

Why this answer

The 'ResourceExhausted' error when reading from BigQuery indicates that the query is consuming more resources than the BigQuery reservation allows. Option C is correct because reducing query complexity (e.g., using fewer JOINs, aggregations, or partitions) or increasing the reservation size directly addresses the root cause by either lowering resource demand or allocating more capacity. Other options like switching to Cloud Storage or adjusting pipeline memory do not fix the BigQuery-specific quota or slot exhaustion.

Exam trap

Google Cloud often tests the misconception that memory or batch size adjustments in the pipeline environment can fix backend service quota errors, when in fact the error is specific to BigQuery's resource management (slots/queries) and requires query optimization or reservation changes.

How to eliminate wrong answers

Option A is wrong because switching to Cloud Storage does not resolve the BigQuery resource exhaustion; it changes the data source but introduces new latency and format compatibility issues without addressing the query's resource consumption. Option B is wrong because increasing memory allocated to the pipeline step only affects the compute environment (e.g., the container running the pipeline), not the BigQuery service's slot or query quota limits. Option D is wrong because reducing the batch size of data being read may reduce memory pressure on the pipeline but does not affect the BigQuery query's resource usage; the error originates from BigQuery's backend, not from the client-side read volume.

Full explanation →
349
MCQhard

A company has a prototype ML model that achieves 85% accuracy on historical data. In production, accuracy drops to 70% after two weeks due to data drift. They need an automated retraining pipeline with minimal manual oversight. Which solution is most cost-effective?

A.Use Cloud Functions to trigger a Dataflow job that trains the model using custom containers
B.Deploy the model on a GPU-equipped Compute Engine VM and run retraining every time new data arrives
C.Set up Vertex AI Model Monitoring to detect drift, which triggers a Cloud Function that submits a Vertex AI Training job with new data
D.Schedule a weekly Cloud Composer DAG that runs a new training job with all available data
AnswerC

Monitoring detects drift, automation triggers retraining with new data, cost-effective.

Why this answer

It combines automated drift detection via Vertex AI Model Monitoring with a serverless retraining trigger (Cloud Function) that submits a Vertex AI Training job, minimizing manual oversight while only incurring costs when drift is detected. This avoids the expense of continuous retraining or always-on GPU instances, making it the most cost-effective solution for the described scenario.

Exam trap

The trap here is that candidates often choose scheduled retraining (Option D) as the simplest automation, overlooking the cost savings and precision of event-driven retraining triggered by actual drift detection, which is a key concept in the PMLE exam for scaling prototypes to production.

How to eliminate wrong answers

Option A is wrong because using Cloud Functions to trigger a Dataflow job for training with custom containers introduces unnecessary complexity and cost for batch processing of training data, whereas Vertex AI Training is purpose-built for ML model training and integrates seamlessly with drift detection. Option B is wrong because deploying a GPU-equipped Compute Engine VM for retraining every time new data arrives incurs high costs for idle GPU time and requires manual management of the VM lifecycle, contradicting the requirement for minimal manual oversight. Option D is wrong because scheduling a weekly Cloud Composer DAG to retrain with all available data ignores the cost savings of event-driven retraining triggered by actual drift, and may waste resources retraining when no drift has occurred.

Full explanation →
350
Multi-Selecthard

An ML engineer is building a monitoring dashboard for a Vertex AI pipeline that includes training, evaluation, and batch prediction. Which THREE components should be included to provide comprehensive observability? (Select THREE.)

Select 3 answers
A.Pipeline execution status, duration, and failure rates for each component.
B.Compute engine CPU and memory logs for each pipeline step.
C.Model evaluation metrics (e.g., accuracy, AUC) after training and validation.
D.Data validation reports showing anomaly counts and feature statistics.
E.Online prediction latency and request count from the deployed model endpoint.
AnswersA, C, D

Core pipeline health metrics.

Why this answer

Pipeline execution status, duration, and failure rates are fundamental metrics for monitoring the health and performance of a Vertex AI pipeline. These metrics allow the ML engineer to quickly identify bottlenecks, track overall workflow progress, and detect failures in training, evaluation, or batch prediction steps, which is essential for comprehensive observability.

Exam trap

The trap here is that candidates often confuse infrastructure monitoring (CPU/memory logs) or serving-layer metrics (online prediction latency) with pipeline-specific observability, leading them to select options that are relevant to different stages of the ML lifecycle rather than the pipeline itself.

Full explanation →
351
Multi-Selectmedium

A data science team collaborates using Vertex AI Workbench user-managed notebooks. They want to version control their notebook code and share it with team members. Which TWO tools should they use? (Choose 2)

Select 2 answers
A.Git integration in Vertex AI Workbench
B.Cloud Functions
C.Vertex AI Model Registry
D.Vertex AI Experiments
E.Cloud Source Repositories
AnswersA, E

Allows version control of notebooks directly in Workbench.

Why this answer

Git integration in Workbench allows version control, and sharing via Cloud Source Repositories or GitHub provides collaboration.

Full explanation →
352
MCQhard

You have a very large language model that does not fit on a single GPU. You need to train it efficiently across multiple GPUs on a single machine. Which approach should you use?

A.Data parallelism with MirroredStrategy
B.Data parallelism with MultiWorkerMirroredStrategy
C.Use TPU training as TPUs have more memory
D.Model parallelism using pipeline parallelism
AnswerD

Splits model layers across GPUs, enabling training of models larger than memory.

Why this answer

When a model is too large for a single GPU, model parallelism (specifically pipeline parallelism) splits the model across GPUs. Data parallelism would require each GPU to hold the full model, which is not possible.

Full explanation →
353
MCQeasy

Refer to the exhibit. A team runs this command to upload a model to Vertex AI. They want to create this model as a new version under an existing model named 'my_model'. What is missing from the command?

A.--description='Second version'
B.--version=v2
C.--labels=team=ml
D.--service-account=sa@project.iam.gserviceaccount.com
E.--parent-model=my_model
AnswerE

The --parent-model flag indicates the existing model to add a version to.

Why this answer

The `--parent-model` flag is required when uploading a new model version to an existing model in Vertex AI. Without specifying the parent model name, the command would attempt to create a brand-new model rather than adding a version to the existing 'my_model'. The `gcloud ai models upload` command uses this flag to associate the new version with the specified parent model.

Exam trap

Google Cloud often tests the distinction between creating a new model versus adding a version to an existing model, and the trap here is that candidates assume a `--version` flag exists (like in some other services) instead of recognizing the required `--parent-model` parameter.

How to eliminate wrong answers

Option A is wrong because `--description` is an optional metadata field and does not affect versioning or parent-model association. Option B is wrong because Vertex AI does not support a `--version` flag; model versions are automatically assigned by the service based on the order of uploads under the same parent model. Option C is wrong because `--labels` are optional key-value pairs for organizing resources and have no role in version creation.

Option D is wrong because `--service-account` is used for specifying a custom service account for model deployment, not for versioning or parent-model linkage.

Full explanation →
354
MCQeasy

What is the primary purpose of Vertex AI Edge Manager?

A.To run batch predictions on edge devices
B.To deploy and manage ML models on edge devices at scale
C.To convert models to TensorFlow Lite automatically
D.To train models on edge devices using federated learning
AnswerB

Correct: Edge Manager handles model deployment, monitoring, and lifecycle on edge devices.

Why this answer

Vertex AI Edge Manager is specifically designed to deploy, monitor, and manage ML models on edge devices at scale. It handles model packaging, over-the-air updates, and health monitoring across fleets of edge devices, which is distinct from simply running batch predictions or converting model formats.

Exam trap

Google Cloud often tests the distinction between 'managing models at scale' (deployment, updates, monitoring) and 'running inference' or 'converting formats' — candidates confuse the operational management role with the execution or preprocessing steps.

How to eliminate wrong answers

Option A is wrong because batch predictions on edge devices are a use case, not the primary purpose; Vertex AI Edge Manager focuses on lifecycle management (deployment, updates, monitoring) rather than just executing predictions. Option C is wrong because model conversion to TensorFlow Lite is handled by tools like the TensorFlow Lite Converter or Vertex AI's model optimization services, not by Edge Manager itself. Option D is wrong because training on edge devices using federated learning is a separate paradigm (e.g., TensorFlow Federated) and is not a core function of Vertex AI Edge Manager, which manages already-trained models.

Full explanation →
355
MCQeasy

To enable collaboration on notebook-based experiments across teams, what is the recommended approach in Google Cloud?

A.Use Colab Enterprise notebooks with shared runtimes and IAM permissions
B.Share Docker images containing the notebook environment
C.Each team member works on their own local Jupyter notebook and shares screenshots
D.Store notebooks in a Cloud Storage bucket and open them with Vertex AI Workbench
AnswerA

Colab Enterprise enables collaborative editing and shared compute resources.

Why this answer

Colab Enterprise notebooks with shared runtimes and IAM permissions is the recommended approach because it provides a fully managed, collaborative environment where multiple users can work on the same notebook simultaneously, with fine-grained access control via IAM and consistent runtime configurations. This eliminates version conflicts and environment drift, which are common in distributed notebook workflows.

Exam trap

Google Cloud often tests the misconception that shared storage (like Cloud Storage) alone is sufficient for collaboration, but the key requirement is shared runtimes and concurrent editing, which only Colab Enterprise provides among the options.

How to eliminate wrong answers

Option B is wrong because sharing Docker images containing the notebook environment addresses environment reproducibility but does not enable real-time collaboration or shared runtime execution; each user would still need to launch their own instance and manually sync changes. Option C is wrong because each team member working on their own local Jupyter notebook and sharing screenshots is a manual, non-scalable approach that lacks version control, concurrent editing, and centralized data access, making it unsuitable for team collaboration. Option D is wrong because storing notebooks in a Cloud Storage bucket and opening them with Vertex AI Workbench provides shared storage but does not inherently support shared runtimes or concurrent editing; Vertex AI Workbench instances are typically single-user, and multiple users would need to coordinate access to avoid conflicts.

Full explanation →
356
MCQhard

A retail company deployed a demand forecasting model using TensorFlow on Vertex AI Batch Prediction. The model runs weekly on a large dataset stored in BigQuery. Over the past month, the prediction accuracy has degraded significantly. The ML engineer reviews the monitoring dashboard and sees that the feature distribution for 'product_price' has shifted from a mean of $50 to $55, and the new product category 'electronics' now represents 20% of the data, whereas it was only 5% in training. The model was never retrained after initial deployment six months ago. The engineer also notices that the Vertex Explainable AI feature importance scores have changed: 'product_price' used to be the top feature (importance 0.35) but now ranks third (importance 0.20). The company requires minimal downtime and wants to improve accuracy as quickly as possible without incurring high costs from excessive retraining. Which course of action should the ML engineer take?

A.Increase the complexity of the model by switching from a feedforward neural network to a gradient boosted tree ensemble, and then deploy without retraining.
B.Route all predictions to human reviewers until the model can be re-evaluated, and then manually correct the outputs.
C.Retrain the model using the most recent 3 months of data, including all new product categories, and deploy the updated model via a new Vertex AI endpoint.
D.Adjust the prediction threshold for the 'product_price' feature to account for the price shift, and monitor for another month.
AnswerC

Retraining with recent data addresses both covariate shift and concept drift, and is the standard approach for maintaining accuracy.

Why this answer

The correct action is to retrain the model with the latest data because the feature distributions and data composition have changed significantly, indicating covariate shift and concept drift. Retraining on the most recent 3 months of data (including the new 'electronics' category) will adapt the model to the current data distribution, improving accuracy with minimal downtime by deploying via a new Vertex AI endpoint. Option A (switching to a more complex model without retraining) would not address the drift and may overfit.

Option B (routing predictions to human reviewers) is costly, not scalable, and introduces latency. Option D (adjusting prediction thresholds) is insufficient because the model's internal representations are outdated due to the distribution shift, and thresholds alone cannot correct inaccurate predictions.

Full explanation →
357
MCQhard

A large organization uses a multi-project setup with a central data lake. Different teams manage their own models. To enable cross-team sharing of features, they want to use Vertex AI Feature Store. What is the best practice to manage access?

A.Create a single Feature Store in a central project and grant fine-grained IAM roles
B.Export features to Cloud Storage
C.Create separate Feature Stores per team project
D.Use BigQuery authorized views
AnswerA

A central Feature Store with IAM enables sharing while controlling access.

Why this answer

Creating a single Feature Store in a central project with fine-grained IAM roles is the best practice because it centralizes feature management while allowing cross-team access control at the feature group or feature level. Vertex AI Feature Store supports IAM roles like `aiplatform.featureStoreAdmin` and `aiplatform.featureStoreDataViewer` to grant granular permissions, enabling teams to share features without duplicating data or exposing sensitive information. This approach avoids data silos and ensures consistent governance across the organization.

Exam trap

Google Cloud often tests the misconception that separate Feature Stores per team are needed for isolation, but the correct approach is to use a single Feature Store with fine-grained IAM to enable sharing while maintaining security.

How to eliminate wrong answers

Option B is wrong because exporting features to Cloud Storage introduces data duplication, latency, and manual synchronization overhead, defeating the purpose of a centralized feature store for real-time serving. Option C is wrong because creating separate Feature Stores per team project creates data silos, preventing cross-team sharing and requiring complex cross-project networking or data replication. Option D is wrong because BigQuery authorized views are designed for table-level access control in BigQuery, not for managing access to Vertex AI Feature Store entities like feature groups or online/offline stores, and they lack the low-latency serving capabilities of Feature Store.

Full explanation →
358
MCQhard

A machine learning team uses Vertex AI Pipelines to orchestrate their training pipeline. They want to trigger the pipeline automatically in response to new data arriving in a Cloud Storage bucket, and also support a scheduled run every day at 6 AM. Which combination of services should they use to achieve both event-driven and schedule-based triggers?

A.Cloud Scheduler for the schedule, and Cloud Pub/Sub with Push subscription to Vertex AI for event-driven.
B.Cloud Functions for both schedule and event-driven, using cron trigger.
C.Cloud Scheduler for the schedule, and Cloud Functions triggered by Cloud Storage events to call the Vertex AI API for event-driven.
D.Vertex AI Pipelines built-in scheduler for schedule, and Cloud Pub/Sub for event-driven.
AnswerC

Correct: Cloud Scheduler for cron schedule, Cloud Functions for event-driven from Cloud Storage.

Why this answer

Cloud Scheduler can trigger the pipeline at 6 AM daily via a cron job, while Cloud Functions, triggered by Cloud Storage events (e.g., object finalize), can call the Vertex AI API to start the pipeline when new data arrives. This combination provides both schedule-based and event-driven triggers without requiring custom infrastructure.

Exam trap

The trap here is that candidates often assume Vertex AI Pipelines has a built-in scheduler or that Pub/Sub can directly trigger pipelines, but in reality, Cloud Functions (or Cloud Run) is needed as an intermediary to translate events into API calls.

How to eliminate wrong answers

Option A is wrong because Cloud Pub/Sub with a Push subscription cannot directly trigger Vertex AI Pipelines; Vertex AI does not accept Pub/Sub push messages as a trigger source. Option B is wrong because Cloud Functions does not support a native cron trigger; it requires Cloud Scheduler to invoke it on a schedule, making it unsuitable for the schedule requirement alone. Option D is wrong because Vertex AI Pipelines does not have a built-in scheduler; it relies on external services like Cloud Scheduler for time-based triggers.

Full explanation →
359
MCQeasy

Which Vertex AI feature allows you to reduce the size of a trained model to improve inference speed on edge devices without significant accuracy loss?

A.Vertex AI Model Optimization
B.Vertex AI Model Monitoring
C.Vertex AI Matching Engine
D.Vertex AI Continuous Training
AnswerA

Correct: Model Optimization offers quantization and compilation to reduce model size and speed up inference.

Why this answer

Vertex AI Model Optimization is the correct feature because it provides model quantization, pruning, and distillation techniques specifically designed to reduce model size and improve inference latency on edge devices. This service applies post-training quantization (e.g., FP32 to INT8) and structured weight pruning to shrink the model footprint while maintaining accuracy within acceptable thresholds, directly addressing the need for efficient deployment on resource-constrained hardware.

Exam trap

Google PMLE exams often test the distinction between 'optimization' (size/speed improvements) and 'monitoring' (observability), leading candidates to confuse Model Monitoring with performance tuning because both involve 'model performance' terminology.

How to eliminate wrong answers

Option B is wrong because Vertex AI Model Monitoring is used for detecting prediction drift, data skew, and feature attribution changes in deployed models, not for reducing model size or optimizing inference speed. Option C is wrong because Vertex AI Matching Engine is a vector similarity search service for large-scale embedding-based retrieval (e.g., recommendation systems), not a model compression or optimization tool. Option D is wrong because Vertex AI Continuous Training automates retraining pipelines based on new data or schedules, but it does not perform model size reduction or inference optimization.

Full explanation →
360
Multi-Selecthard

Which THREE of the following are valid best practices when using Vertex AI AutoML for tabular data?

Select 3 answers
A.Normalize the data into multiple tables to reduce data size
B.Enable automatic feature engineering to improve model performance
C.Disable early stopping for best model quality if budget allows
D.Use the max time budget parameter to control costs
E.Keep training data with heavy class imbalance as-is to let AutoML correct it
AnswersB, C, D

Creates cross features and handling missing values.

Why this answer

Enabling automatic feature engineering in Vertex AI AutoML for tabular data allows the service to automatically create, select, and transform features (e.g., polynomial combinations, cross features, and numerical transformations) to improve model accuracy without manual intervention. This is a built-in capability that leverages Google's AutoML algorithms to discover the most predictive feature representations from the raw data.

Exam trap

Google Cloud often tests the misconception that cost-control parameters like max time budget are best practices for model quality, when in fact they are operational constraints, and that disabling early stopping is beneficial for quality, when it actually risks overfitting and wasted resources.

Full explanation →
361
MCQmedium

A retail company wants to build a product recommendation system using BigQuery ML for their e-commerce platform. The data includes customer purchase history, product metadata, and clickstream logs. The ML engineer needs to minimize manual feature engineering and leverage pre-built solutions. Which approach should the engineer take?

A.Use a pre-built recommendation model from Vertex AI Model Garden and deploy it to an endpoint.
B.Write a custom TensorFlow model using the Vertex AI Training service and deploy it via Vertex AI Prediction.
C.Export the data to CSV and use AutoML Tables to train a recommendation model.
D.Use BigQuery ML's matrix factorization model (CREATE MODEL with model_type='matrix_factorization') to train directly on historical interaction data.
AnswerD

BigQuery ML provides low-code matrix factorization for recommendations.

Why this answer

BigQuery ML's matrix factorization model (model_type='matrix_factorization') is purpose-built for recommendation systems using implicit or explicit feedback data. It trains directly on historical interaction data (e.g., user-item purchases) without requiring manual feature engineering, aligning with the goal of minimizing low-code ML effort. This approach leverages BigQuery's native SQL interface and scales automatically, making it ideal for the described e-commerce scenario.

Exam trap

The trap here is that candidates may assume Vertex AI Model Garden (Option A) is the go-to for pre-built ML, but it does not offer a pre-trained recommendation model that can be directly deployed without custom training on the company's data.

How to eliminate wrong answers

Option A is wrong because Vertex AI Model Garden provides pre-built models for tasks like vision or NLP, not a ready-to-use recommendation model that can be directly deployed without training on the company's specific interaction data. Option B is wrong because writing a custom TensorFlow model and training it via Vertex AI Training contradicts the requirement to minimize manual feature engineering and leverage pre-built solutions. Option C is wrong because exporting data to CSV and using AutoML Tables would require additional data preparation and does not natively handle the user-item interaction structure as efficiently as BigQuery ML's matrix factorization, which operates directly on the data in place.

Full explanation →
362
MCQhard

A machine learning team wants to implement a continuous delivery pipeline for their ML models using Vertex AI Pipelines. The pipeline should automatically deploy a model to a staging endpoint after evaluation passes, and then after manual approval, promote it to production. Which strategy should they use to manage model versions in the Vertex AI Model Registry?

A.Use Vertex AI Model Registry aliases: assign the model version an alias 'staging' initially, and after approval, change the alias to 'production' via the API.
B.Store model artifacts in Cloud Storage with versioned paths and deploy directly from Storage without using the Model Registry.
C.Create two separate models in the registry: one for staging and one for production, and copy artifacts between them after approval.
D.Upload each model version with the same model ID and use labels to differentiate staging vs production.
AnswerA

Aliases like 'staging' and 'production' allow controlled promotion of model versions.

Why this answer

Vertex AI Model Registry supports versioning and alias management. By uploading models with an alias like 'staging' and later changing the alias to 'production', the team can control promotion. The other options either lack the required functionality or add unnecessary complexity.

Full explanation →
363
MCQmedium

A logistics company uses a regression model to predict delivery times. The model currently uses features: distance (km), traffic index, weather condition, and time of day. The data scientist notices that the model's predictions are systematically too low for deliveries during peak traffic hours. Which action would best address this issue?

A.Switch to a deep neural network model
B.Remove the traffic index feature as it is causing bias
C.Add a cross-feature that multiplies distance by traffic index
D.Collect more training data during peak traffic hours
AnswerC

This interaction term allows the model to capture the combined effect.

Why this answer

The model's systematic underestimation during peak traffic hours indicates a missing interaction effect between distance and traffic. Adding a cross-feature (distance × traffic index) allows a linear model to capture the non-linear relationship where traffic disproportionately increases delivery time over longer distances. This directly addresses the bias without discarding useful data or unnecessarily complicating the model.

Exam trap

Google Cloud often tests the misconception that systematic bias is always due to insufficient data or the wrong model type, when in fact it is frequently caused by missing feature interactions that can be fixed with simple feature engineering.

How to eliminate wrong answers

Option A is wrong because switching to a deep neural network is overkill and does not guarantee fixing systematic bias; it may even introduce overfitting without addressing the root cause of missing feature interactions. Option B is wrong because removing the traffic index feature would eliminate a key predictor entirely, likely worsening the model's accuracy and increasing bias rather than correcting it. Option D is wrong because collecting more data during peak hours would not fix the model's inability to model the interaction between distance and traffic; the model would still systematically underpredict unless the feature representation is improved.

Full explanation →
364
MCQeasy

A company needs to detect objects in real-time from a live video feed. They want to use a pre-trained model with minimal setup. Which Google Cloud service should they use?

A.Vertex AI AutoML Video
B.Video Intelligence API
C.Document AI
D.Cloud Vision API
AnswerB

Why this answer

The Video Intelligence API is the correct choice because it provides pre-trained models for real-time video analysis, including object detection, with minimal setup. It is designed to extract metadata from video streams without requiring custom training, making it ideal for real-time live video feeds. Vertex AI AutoML Video, in contrast, requires custom training and is not pre-trained for immediate use.

Exam trap

The trap here is that candidates confuse Cloud Vision API (static images) with video analysis, or assume Vertex AI AutoML Video is pre-trained, when in fact it requires custom model training and is not a 'minimal setup' solution.

How to eliminate wrong answers

Option A is wrong because Vertex AI AutoML Video requires custom training on labeled data, not a pre-trained model, and involves more setup for real-time detection. Option C is wrong because Document AI is specialized for document processing (e.g., OCR, form parsing), not video object detection. Option D is wrong because Cloud Vision API is designed for static image analysis, not real-time video streams, and lacks native video frame processing capabilities.

Full explanation →
365
Multi-Selectmedium

You are deploying a model on Vertex AI and need to ensure high availability and low latency. Which THREE configurations should you implement?

Select 3 answers
A.Choose a machine type with GPUs for compute-intensive models.
B.Enable logging and monitoring for the endpoint.
C.Use a custom endpoint with a static IP address.
D.Deploy with min_replicas=2 and max_replicas=10 across multiple zones.
E.Deploy to a single zone to reduce network latency.
AnswersA, B, D

GPUs reduce inference latency for deep learning models.

Why this answer

GPUs are essential for compute-intensive models, such as deep neural networks, as they provide parallel processing capabilities that significantly reduce inference latency compared to CPUs. On Vertex AI, selecting a machine type with GPUs (e.g., n1-standard-4 with NVIDIA T4) ensures that the model can handle high-throughput requests with low latency, which is critical for real-time serving.

Exam trap

The trap here is that candidates often confuse static IP addresses with reliability, not realizing that Vertex AI endpoints already provide a stable DNS name with built-in load balancing, and that single-zone deployments are a common anti-pattern for high availability.

Full explanation →
366
MCQmedium

A machine learning engineer notices that the online prediction latency for a custom TensorFlow model deployed on Vertex AI has increased significantly over the past week. Cloud Monitoring shows that the CPU utilization of the endpoints remains below 40%, but the number of concurrent requests has doubled. What is the most likely cause of the latency increase?

A.Data skew causing longer inference time
B.Memory leak in the serving container
C.Insufficient number of replicas for autoscaling
D.Model overfitting
AnswerC

If the number of replicas is not scaling fast enough to match increased concurrency, requests queue up, leading to higher latency while each replica's CPU is underutilized.

Why this answer

The CPU utilization remains below 40% while concurrent requests have doubled, indicating that the existing replicas are not saturated on CPU but are bottlenecked by request queuing or thread contention. Vertex AI autoscaling scales based on CPU utilization by default; if the threshold is not crossed, new replicas are not provisioned, causing requests to queue and latency to spike. The engineer should verify the autoscaling configuration and consider scaling on request count or reducing the CPU utilization target.

Exam trap

Google Cloud often tests the misconception that low CPU utilization always means there is spare capacity, when in reality the bottleneck can be request queuing or thread pool exhaustion that does not raise CPU usage.

How to eliminate wrong answers

Option A is wrong because data skew would cause a persistent increase in per-request inference time, but the observation shows CPU utilization is low and latency increased only after request volume doubled, not due to a change in data distribution. Option B is wrong because a memory leak would manifest as increasing memory usage over time, potentially causing OOM kills or garbage collection pauses, but the described symptom is low CPU and doubled concurrency, not memory pressure. Option D is wrong because model overfitting affects prediction accuracy, not inference latency; overfitting does not change the computational cost of a forward pass.

Full explanation →
367
MCQeasy

A data scientist needs to share a BigQuery dataset with a colleague in a different team so they can run queries. What is the simplest and most secure way to grant access?

A.Export the dataset to Cloud Storage and share the bucket
B.Add the colleague's account as a BigQuery Data Viewer on the dataset
C.Share the service account key of a BigQuery job user with the colleague
D.Add the colleague's account as a Project Viewer on the entire project
AnswerB

Direct IAM binding on the dataset provides least-privilege access.

Why this answer

Adding the colleague's account as a BigQuery Data Viewer on the dataset grants read-only access to the specific dataset, which is the simplest and most secure method. Option A is wrong because exporting to Cloud Storage adds complexity and data staleness. Option C is wrong because sharing the entire project grants excessive permissions.

Option D is wrong because sharing the service account key poses a security risk.

Full explanation →
368
MCQeasy

You have a TensorFlow training script that runs on a single machine. To speed up training on Vertex AI with 8 GPUs on a single machine, which strategy should you use?

A.tf.distribute.ParameterServerStrategy
B.tf.distribute.MirroredStrategy
C.tf.distribute.TPUStrategy
D.tf.distribute.MultiWorkerMirroredStrategy
AnswerB

MirroredStrategy is designed for single-machine multi-GPU synchronous training.

Why this answer

MirroredStrategy performs synchronous data parallelism across multiple GPUs on a single machine. MultiWorkerMirroredStrategy is for multiple machines, not needed here. ParameterServerStrategy is for distributed asynchronous training.

TPUStrategy is for TPUs.

Full explanation →
369
MCQeasy

Your team is using Vertex AI Pipelines to build an automated training pipeline. You need to share the pipeline definition with another team so they can run it in their own project. Which format should you use?

A.Copy the pipeline artifacts to a Cloud Storage bucket and share the bucket.
B.Package the pipeline as a Docker container image.
C.Share the Python code that compiles the pipeline.
D.Export the pipeline as a YAML file using the Kubeflow Pipelines SDK.
AnswerD

YAML file defines the pipeline graph and components.

Why this answer

Vertex AI Pipelines is built on Kubeflow Pipelines, and the standard way to share a pipeline definition is to export it as a YAML file using the Kubeflow Pipelines SDK (`kfp.compiler.Compiler().compile()`). This YAML file contains the complete pipeline specification, including all components, dependencies, and execution order, and can be uploaded and run in any Vertex AI project without requiring the original Python code or build environment.

Exam trap

Google Cloud often tests the misconception that sharing the Python code or Docker images is sufficient for pipeline portability, but the exam expects you to recognize that the compiled YAML is the portable, self-contained artifact that decouples pipeline definition from the build environment.

How to eliminate wrong answers

Option A is wrong because copying pipeline artifacts (such as intermediate outputs or model files) does not share the pipeline definition itself; the other team would need the pipeline specification to recreate the execution graph. Option B is wrong because a Docker container image packages the runtime environment and code for a single component, not the entire pipeline DAG (directed acyclic graph) definition. Option C is wrong because sharing the Python compilation code requires the other team to have the exact same dependencies, SDK versions, and build environment to reproduce the pipeline, which is error-prone and not the intended portable format.

Full explanation →
370
MCQmedium

An organisation wants to monitor fairness of their loan approval model across demographic subgroups. They have predictions stored in BigQuery along with ground truth. Which GCP service can evaluate model performance for each subgroup and identify disparities?

A.Cloud Data Loss Prevention (DLP)
B.Vertex AI Explainable AI
C.Vertex AI Model Evaluation
D.Vertex AI Model Monitoring
AnswerC

Correct: supports sliced evaluation for fairness analysis.

Why this answer

Vertex AI Model Evaluation supports sliced evaluation, where metrics are computed for each subgroup defined by feature values (e.g., gender, race) in BigQuery. This helps identify performance disparities.

Full explanation →
371
MCQeasy

What is the purpose of the 'importer' component in Vertex AI Pipelines?

A.To import data from external sources into the pipeline.
B.To import existing ML artifacts (e.g., models, datasets) into a pipeline as inputs.
C.To import Python libraries into the pipeline environment.
D.To import pipeline definitions from other projects.
AnswerB

This is the correct use of the importer component.

Why this answer

The importer component allows you to bring existing artifacts (e.g., a model in Vertex AI Model Registry) into a pipeline for downstream use.

Full explanation →
372
MCQeasy

A company wants to classify customer support emails into categories like 'billing', 'technical', or 'account'. They have labeled email text data. Which AutoML solution should they use?

A.AutoML Tables
B.AutoML Natural Language
C.AutoML Video
D.AutoML Vision
AnswerB

Why this answer

AutoML Natural Language is designed for text classification. AutoML Vision is for images, AutoML Video for video, and AutoML Tables for tabular data.

Full explanation →
373
MCQhard

In a Vertex AI Pipeline, a component produces a Metrics artifact that includes an evaluation metric. The engineer wants to use this metric value as a condition to decide whether to deploy the model. However, the metric value is stored in the artifact's metadata and not directly as a pipeline parameter. How can the engineer pass the metric value to a downstream conditional task?

A.Configure the component that produces the Metrics artifact to also output the metric as a pipeline parameter.
B.Use the importer component to convert the artifact into a parameter.
C.Add a component that reads the artifact's metadata and outputs the metric as a parameter, then use that parameter in the condition.
D.Use the artifact directly in the dsl.If condition, as artifacts are comparable.
AnswerC

A small Python function component can extract the metric value from the artifact's metadata and output it as a string or float parameter, which can then be used in dsl.If.

Why this answer

Vertex AI Pipeline conditions require pipeline parameters (typed values) to evaluate expressions like `dsl.If`. A Metrics artifact's metadata is stored as an artifact property, not a pipeline parameter, so a custom component must read that metadata and output the metric as a parameter. This parameter can then be used in the `dsl.If` condition to control downstream deployment.

Exam trap

A common trap in this Google exam is the misconception that artifact metadata can be directly used in pipeline conditions, but conditions require typed parameters, not artifact objects or their metadata fields.

How to eliminate wrong answers

Option A is wrong because modifying the upstream component to output the metric as a pipeline parameter would require changing the component's implementation, which may not be feasible if the component is from a shared library or third-party. Option B is wrong because the importer component is designed to bring external artifacts into the pipeline, not to extract metadata from an existing artifact and convert it into a parameter. Option D is wrong because artifacts are not directly comparable in `dsl.If` conditions; conditions only work with pipeline parameters (e.g., integers, strings), not with artifact objects or their metadata.

Full explanation →
374
MCQeasy

You want to deploy a TensorFlow model to a Vertex AI endpoint and enable online predictions. The model requires GPU for inference. Which machine type should you select when deploying the model?

A.n1-standard-4
B.e2-standard-4
C.a2-highgpu-1g (with A100 GPU)
D.n1-highmem-8
AnswerC

Correct. This is a GPU-enabled machine type suitable for model inference.

Why this answer

The a2-highgpu-1g machine type is specifically designed for GPU-accelerated workloads on Vertex AI, featuring an NVIDIA A100 GPU that meets the inference requirements of a TensorFlow model. Vertex AI online prediction endpoints require a machine type that supports GPU attachment, and the A2 series is the only option among the choices that provides a dedicated GPU for inference.

Exam trap

The trap here is that candidates often assume any standard machine type (like n1 or e2) can be used with a GPU by simply attaching one later, but the question specifically asks for the machine type to select, and only the A2 series provides an integrated GPU option for Vertex AI endpoints.

How to eliminate wrong answers

Option A is wrong because n1-standard-4 is a general-purpose machine type that does not include a GPU by default; while it can be attached with a GPU via a separate configuration, the question asks for the machine type to select, and n1-standard-4 alone lacks the GPU required for inference. Option B is wrong because e2-standard-4 is a cost-optimized machine type that does not support GPU attachment at all, making it unsuitable for GPU-dependent model inference. Option D is wrong because n1-highmem-8 is a memory-optimized machine type without a built-in GPU; although it can be paired with a GPU, the machine type itself does not provide the GPU, and the question expects a machine type that inherently includes GPU capability.

Full explanation →
375
MCQmedium

You are performing hyperparameter tuning on Vertex AI with Vizier. You want to maximize the accuracy of your model, and you have a budget of 50 trials. Which algorithm should you choose to best explore the search space?

A.No algorithm; use default Vertex AI tuning
B.Bayesian optimization
C.Grid search
D.Random search
AnswerB

Bayesian optimization builds a probabilistic model and selects promising hyperparameters, efficient for 50 trials.

Why this answer

Bayesian optimization is the default and recommended algorithm for most use cases as it balances exploration and exploitation efficiently. For a budget of 50 trials, Bayesian optimization is suitable.

Full explanation →
Page 4

Page 5 of 14

Page 6

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 →