PMLE Serving and Scaling Models Practice Question
A company uses Vertex AI Matching Engine for a product recommendation system. They need to update the index with new product embeddings every hour, but the index is used for online queries with low latency. Which index update strategy should they use?
⚠ Common exam trap
Google often tests the misconception that batch updates are required for consistency or that streaming updates cannot handle frequent changes, leading candidates to choose hybrid or batch approaches when incremental streaming is both sufficient and optimal for low-latency online serving.
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
✓
Use streaming updates to insert new embeddings incrementally
Streaming updates in Vertex AI Matching Engine allow incremental insertion of new embeddings into an existing index without rebuilding it. This satisfies the requirement for hourly updates while maintaining low-latency online queries, as the index remains available and consistent during the update process.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
Use streaming updates to insert new embeddings incrementally
Why this is correct
Streaming updates let Matching Engine insert or delete datapoints incrementally while the index stays queryable, so hourly embedding refreshes avoid the rebuild-and-redeploy cycle that batch updates require. This preserves the low-latency online serving the stem demands, since queries continue against the live index throughout.
- ✗
Use a hybrid approach with batch for daily full rebuild and streaming for hourly
Why it's wrong here
The hybrid approach still relies on a daily batch rebuild, so hourly additions only arrive via the streaming path, and the batch component cannot meet the one-hour freshness requirement on its own. It is tempting because it balances cost and freshness, and it would be correct if updates were daily rather than hourly.
- ✗
Use batch updates to replace the index every hour
Why it's wrong here
Batch updates rebuild or swap the deployed index, so queries hit stale data until the replacement finishes, and the swap itself interrupts low-latency serving. It is tempting because hourly batching matches the stated cadence, and it would be correct for offline or nightly-refreshed indexes where query latency is not critical.
- ✗
Recreate the index from scratch each hour
Why it's wrong here
Recreating the index each hour discards the serving endpoint, forcing redeployment and leaving queries unavailable or stale during rebuild — incompatible with continuous low-latency online serving. It is tempting because it guarantees a clean, fully consistent index, and it would be correct for infrequent rebuilds where downtime is acceptable.
About these practice questions
Courseiva writes every PMLE question from scratch — 775 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 PMLE 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 PMLE exam.