PMLE Practice Test 4 — 10 Questions

Question 1

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

Accepted Answer

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

Answer

Kubeflow Pipelines

Answer

Custom TensorFlow model

Answer

BigQuery ML

Question 2

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

Accepted Answer

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

Answer

Use Cloud Composer to orchestrate preprocessing

Answer

Write shared Python packages in Artifact Registry

Answer

Use Cloud Dataflow templates

Question 3

A data engineering team needs to compute rolling window features (7-day average, 30-day sum) from a high-volume stream of e-commerce events stored in BigQuery. They must output the features to Vertex AI Feature Store for online serving. Which approach is MOST cost-effective and scalable?

Accepted Answer

Use Dataflow with Apache Beam, reading from BigQuery, computing windowed aggregations, and writing to Vertex AI Feature Store. Dataflow (Apache Beam) is ideal for processing large-scale batch and streaming data. It can read from BigQuery, perform windowing computations, and write to Feature Store's online store. Cloud Functions have timeouts, Cloud Composer is not optimal for streaming, and BigQuery scheduled queries are not designed for streaming-feature computation.

Answer

Use Cloud Composer (Airflow) with a daily DAG to run SQL queries on BigQuery and export results

Answer

Schedule a query in BigQuery using scheduled queries and export results to Feature Store

Answer

Use Cloud Functions triggered by Pub/Sub to compute features on the fly

Question 4

A financial services company has deployed a credit risk ML model on Vertex AI. They want to monitor the model for fairness across demographic groups to ensure no biased outcomes. Which TWO actions should they take as best practices? (Choose TWO.)

Accepted Answer

Use Vertex Explainable AI to understand feature attributions and compare their distributions across demographic groups.. Vertex Explainable AI provides feature attribution scores that can be compared across demographic groups to detect if the model relies on sensitive attributes or proxies. This enables fairness auditing by revealing whether the model's decision logic differs systematically for protected groups, which is a best practice for monitoring bias.

Answer

Eliminate all features that are correlated with protected attributes from the model input to ensure fairness.

Answer

Periodically compare the model's performance metrics (e.g., AUC) on the overall population versus the holdout test set.

Answer

Store all model predictions in BigQuery but do not capture ground truth labels to avoid privacy issues.

Question 5

An ML team wants to use Vertex AI Hyperparameter Tuning to tune a custom training job. They have a budget of 50 trials and want to use an algorithm that balances exploration and exploitation. Which algorithm should they choose?

Accepted Answer

Bayesian optimization (Vizier default). Bayesian optimization (the default algorithm in Vertex AI Vizier) is the correct choice because it explicitly balances exploration and exploitation by building a probabilistic model of the objective function and using an acquisition function to select the next hyperparameter configuration. With a budget of 50 trials, this algorithm efficiently converges to optimal regions while still exploring uncertain areas, making it ideal for tuning custom training jobs where each trial is computationally expensive.

Answer

Random search

Answer

Grid search

Answer

Manual search

Question 6

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

Accepted Answer

Enable feature monitoring on the feature group with drift threshold and notification channel.. Feature monitoring in Vertex AI Feature Store allows defining drift thresholds and alerting via Cloud Monitoring.

Answer

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

Answer

Use Vertex AI Experiments to compare distributions.

Answer

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

Question 7

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

Accepted Answer

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

Answer

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

Answer

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

Answer

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

Question 8

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?

Accepted Answer

Deploy both models to the same endpoint and use traffic splitting.. 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.

Answer

Deploy the challenger to a separate endpoint and use a proxy to split traffic.

Answer

Use Cloud Load Balancing with weighted backend services.

Answer

Use Vertex AI Experiments to manage model versions.

Question 9

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.)

Accepted Answer

Pipeline execution status, duration, and failure rates for each component.. Option A is correct because tracking pipeline execution status, duration, and failure rates per component gives the operational observability needed to detect where a training, evaluation, or batch prediction step fails or slows down. Option C is correct because model evaluation metrics such as accuracy and AUC after training and validation are essential to monitor model quality and detect degradation before deployment. Option D is correct because data validation reports with anomaly counts and feature statistics surface input data drift, skew, and schema issues that directly affect pipeline and model reliability. Option B is not appropriate because raw Compute Engine CPU and memory logs for each step are low-level infrastructure telemetry, not the pipeline-level observability components the scenario requires. Option E is not appropriate because online prediction latency and request counts apply to a deployed endpoint, whereas this pipeline uses batch prediction and has no online serving endpoint.

Answer

Compute engine CPU and memory logs for each pipeline step.

Answer

Online prediction latency and request count from the deployed model endpoint.

Question 10

Drag and drop the steps to set up a BigQuery ML linear regression model for forecasting in the correct order.

Accepted Answer

Prepare training data → Create model → Evaluate model → Use model for predictions. For BigQuery ML linear regression, the correct order is: 1) Prepare training data by selecting and preprocessing features in a SQL query; 2) Create the model using `CREATE MODEL` with the training data; 3) Evaluate the model using `ML.EVALUATE` to check metrics like R²; 4) Use the model for predictions with `ML.PREDICT`. This sequence ensures the model is built on clean data, validated, and then applied.

Answer

Prepare training data → Create model → Use model for predictions → Evaluate model

Answer

Create model → Prepare training data → Evaluate model → Use model for predictions

Answer

Prepare training data → Evaluate model → Create model → Use model for predictions