Vertex AI Platform

Vertex AI is GCP's unified ML platform. It brings together training, prediction, Feature Store, pipelines, model monitoring, and experiment tracking under one service.

Training Options (Decision Tree)

Exam tip: The exam loves asking "which training approach should you use?" The answer depends on: (1) team expertise, (2) data volume, (3) customization needs, (4) time constraints. If the question mentions "SQL-familiar analysts" → BigQuery ML. If it says "minimal ML expertise" → AutoML. If it requires "custom architecture" → Custom Training.

Vertex AI Feature Store

A centralized repository for organizing, storing, and serving ML features. Solves the critical problem of training-serving skew and feature reuse across teams.

Key Capabilities

Training-serving skew happens when features are computed differently in training vs. serving. Feature Store mitigates this by providing a single source for both. If an exam question describes model quality degradation in production, consider whether training-serving skew or feature staleness is the root cause.

Model Deployment & Serving

Vertex AI Endpoints

Model Monitoring

MLOps with Vertex AI Pipelines

Vertex AI Pipelines orchestrate ML workflows using Kubeflow Pipelines or TFX. They define reproducible, end-to-end ML workflows: data prep → training → evaluation → deployment.

BigQuery ML

Train and serve models using SQL, directly in BigQuery. No data movement, no separate infrastructure.

Supported Model Types

RegressionLINEAR_REG
ClassificationLOGISTIC_REG
ClusteringKMEANS
Time SeriesARIMA_PLUS
Boosted TreesBOOSTED_TREE_*
Deep LearningDNN_*
Matrix FactorizationMATRIX_FACTORIZATION
Import TF modelsTENSORFLOW
CREATE OR REPLACE MODEL `project.dataset.fraud_model`
OPTIONS(
  model_type='BOOSTED_TREE_CLASSIFIER',
  input_label_cols=['is_fraud'],
  auto_class_weights=TRUE,
  data_split_method='AUTO_SPLIT'
) AS
SELECT * FROM `project.dataset.training_features`
WHERE transaction_date BETWEEN '2024-01-01' AND '2024-12-31';

📝 Practice Questions — Machine Learning

Question 1 — Vertex AI Feature Store & ML Pipeline Design
Your ML team has built a fraud detection model that uses 200+ features derived from transaction data, user behavior, and merchant profiles. Features are computed by multiple teams using different pipelines — some in Dataflow, some in Spark on Dataproc, and some as BigQuery scheduled queries. During a recent incident, the model's prediction quality degraded because the batch pipeline computing velocity features was delayed by 6 hours, causing stale features to be served for online predictions. You need to redesign the architecture to prevent feature staleness from silently degrading model quality. What should you do?
A Migrate all feature computation to a single Dataflow streaming pipeline so all features are updated in real time, eliminating the risk of batch pipeline delays
B Register all features in Vertex AI Feature Store with feature freshness monitoring, configure alerts when feature timestamps exceed staleness thresholds, and implement a fallback strategy in the serving layer that either uses default values or rejects predictions when critical features are stale
C Move all feature computation into BigQuery scheduled queries running every 15 minutes so that all features share the same refresh cadence and any delay is immediately visible
D Add a Cloud Composer DAG that checks the last-modified timestamp of each feature table before the model prediction endpoint is called, and blocks predictions if any table is older than 2 hours
Answer: B. Vertex AI Feature Store with freshness monitoring is the purpose-built solution for this problem. It provides: (1) a central registry for all features regardless of how they're computed, (2) automatic freshness tracking with configurable alerting thresholds, (3) the serving layer can implement fallback logic (defaults or rejection) when features are stale. Option A is impractical — not all features can be computed in real time (some require batch aggregations). Option C forces all features into the same tool, which may not be suitable. Option D adds a fragile custom solution that doesn't scale and adds latency to every prediction request.
Question 2 — Choosing the Right Training Approach
A retail analytics team at your company wants to build a demand forecasting model. They have 3 years of daily sales data for 10,000 SKUs stored in BigQuery. The team is composed of business analysts proficient in SQL but with no Python or ML framework experience. They need weekly forecasts updated every Monday morning, and the model should account for seasonality and holidays. What is the most appropriate approach?
A Use Vertex AI AutoML Tables to train a regression model on the sales data, schedule weekly batch predictions using Cloud Scheduler
B Train a custom Prophet model on Vertex AI Custom Training, deploy it to an endpoint, and call it weekly from a Cloud Function
C Export the BigQuery data to CSV, upload to a Jupyter notebook on Vertex AI Workbench, and have the analysts learn to use statsmodels for ARIMA
D Use BigQuery ML's ARIMA_PLUS model type, which handles seasonality and holiday effects automatically, and schedule weekly retraining and forecasting with a BigQuery scheduled query
Answer: D. BigQuery ML's ARIMA_PLUS is ideal here: (1) the team already knows SQL, (2) data is already in BigQuery (no movement needed), (3) ARIMA_PLUS automatically handles seasonality, holiday effects, and trend decomposition, (4) scheduled queries natively support the weekly cadence requirement. Option A (AutoML) requires more ML overhead and data export. Option B requires Python expertise the team doesn't have. Option C requires the analysts to learn a new tool and language.
Question 3 — Model Monitoring & Drift Detection
Your fraud detection model was deployed 6 months ago with 95% precision. Over the past month, the precision has dropped to 82%, but no code or infrastructure changes were made. Investigation shows that the distribution of transaction amounts in production has shifted significantly compared to the training data — many more high-value international transactions are now flowing through the system. What is the most comprehensive solution to detect and mitigate this type of issue going forward?
A Retrain the model monthly on a rolling 6-month window of data to keep it current
B Enable Vertex AI Model Monitoring on the prediction endpoint with feature skew and prediction drift detection, configure alerting thresholds, and set up an automated retraining pipeline in Vertex AI Pipelines that triggers when drift exceeds the threshold
C Add a logging sink from the prediction endpoint to BigQuery, and create a Looker dashboard that tracks precision and recall metrics daily
D Switch from a static model to an online learning model that continuously updates weights with each new prediction
Answer: B. Vertex AI Model Monitoring provides automated detection of both feature skew (training vs. serving distribution differences) and prediction drift (output distribution changes over time). Combined with alerting and an automated retraining pipeline, this creates a closed-loop system that detects and responds to drift. Option A (blind monthly retraining) wastes resources when data is stable and may still miss sudden shifts. Option C (dashboards) is passive monitoring that requires human intervention. Option D (online learning) is architecturally complex and introduces stability risks for fraud detection.