hardMultiple Choice
PDE Practice Question: A company uses Vertex AI Feature Store for…
A company uses Vertex AI Feature Store for serving features to both training and prediction. The team notices that predictions made shortly after training use different feature values, causing a training-serving skew. What is the most effective way to prevent this skew?
⚠ Common exam trap
A common pitfall is assuming that retraining more frequently or switching prediction methods can resolve training-serving skew. The root cause is temporal inconsistency in feature values, which requires point-in-time lookups to ensure the same feature values are used during training and prediction.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Configure the Feature Store to use point-in-time lookup using the training timestamp
Point-in-time lookup ensures that feature values used during training are exactly the same as those used during prediction by retrieving the feature value as it existed at the training timestamp. This directly addresses training-serving skew caused by time-dependent feature changes, which is a common issue in Vertex AI Feature Store when features are updated after training.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
Configure the Feature Store to use point-in-time lookup using the training timestamp
Why this is correct
Point-in-time lookup retrieves feature values as they existed at the training timestamp, rather than the latest values. This aligns serving-time features with those seen during training, directly eliminating the training-serving skew caused by time-dependent feature drift.
- ✗
Retrain the model more frequently to adapt to the new feature distributions
Why it's wrong here
Retraining more often chases the drift rather than removing its cause, because training and serving still read features through different paths. It is the right response when genuine concept drift occurs, not when the same feature is computed inconsistently.
- ✗
Use batch prediction instead of online prediction to ensure consistent features
Why it's wrong here
Batch prediction changes only the serving mode; it does not align the feature values used at training with those served at prediction, so skew persists. It is correct when latency is irrelevant and large volumes are scored on a schedule.
- ✗
Ensure that the training and prediction environments use identical compute resources
Why it's wrong here
Matching CPU, memory or accelerator types does not reconcile feature values; skew originates from divergent feature computation and retrieval logic, not hardware. Identical compute is correct when benchmarking performance or reproducing latency measurements across environments.
Go deeper
Related to this question
About these practice questions
Courseiva writes every PDE question from scratch — 747 in total, each with an explanation and a wrong-answer breakdown. None are copied from real exams or dumps. Learn why practice questions differ from exam dumps →
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
This PDE practice question is part of Courseiva's free Google Cloud certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the PDE exam.