Low-Latency Feature Serving for Real-Time Ad Ranking
Short answer
B Enable Agent Platform Feature Store and use FetchFeatureValues to serve the frequently updated BigQuery user features with low latency and minimal operational overhead.
Question
Key Takeaways
It tests choosing a managed online feature store for a strict 100 ms inference SLA, and the main trap is that Memorystore for Redis looks fast but shifts cache operations onto your team.
This PMLE question tests low-latency online feature serving for a real-time ad-ranking model. The correct answer is B: use Agent Platform Feature Store with FetchFeatureValues instead of querying BigQuery at request time.
Common mistake: Option C is tempting because Redis is low-latency and Dataflow can populate it, but it requires building and operating cache synchronization, eviction, failover, and scaling—precisely the operational overhead the question asks to minimize.
Expert Analysis
The real constraint is request-time feature serving
The model needs hundreds of user-level features for every ad request while holding a 100 ms inference SLA. BigQuery is the source of truth updated by Dataflow, but issuing request-time BigQuery queries for those features is the bottleneck. Option B matches the requirement: Agent Platform Feature Store provides a managed online serving layer, and FetchFeatureValues retrieves an entity's features by key with low latency and automatic scaling.
Why Redis is the tempting wrong turn
Option C sounds strong because Memorystore for Redis is fast and the Dataflow pipeline can write fresh feature values into the cache. It satisfies low-latency retrieval and update propagation, but it stops being correct on the requirement to minimize operational overhead. You would own provisioning, sharding, replication, failover, eviction, TTL, warm-up/backfill, schema changes, cache consistency, and monitoring. As the user base grows, that becomes a separate cache platform rather than a managed feature-serving layer.
The other distractors fall short
Option A still uses BigQueryReadClient in the inference path, so it keeps request-time BigQuery dependency and does not provide a purpose-built online feature API. Option D uses BI Engine, which accelerates analytical SQL and dashboard queries; it is not designed for high-QPS point lookups of hundreds of user features and does not guarantee the 100 ms SLA.
What the discussion confirms
The supplied comments explain that Feature Store's online serving layer is built for fast lookups and scales automatically, while alternatives either still rely on BigQuery or require building and operating a separate Redis caching layer and synchronizing it. That reasoning supports B as the managed, low-latency choice.
Official Reference
- https://cloud.google.com/vertex-ai/docs/featurestore/overview
- https://cloud.google.com/biengine/docs/intro
These links open the official vendor documentation in a new tab.
Exam Strategy
When a stem demands both sub-100 ms retrieval and minimal operational overhead, eliminate options that keep request-time BigQuery reads and options that require you to run your own cache tier. Look for the managed, purpose-built online feature-serving service and its native fetch API. If a self-managed Redis layer is offered, treat it as a distractor unless the question explicitly asks for custom cache control or the feature store cannot meet a stated constraint.
Frequently Asked Questions
Why isn't Memorystore for Redis the best choice for these features?
Does BigQuery BI Engine make request-time feature fetches meet the 100 ms SLA?
What role does Dataflow play with Agent Platform Feature Store?
Community Votes
100% of anonymous learners picked answer B. Votes are pick records left by other test-takers — they are not the verified answer.
Discussion 2 contributions
Compiled from public community threads and reader submissions, lightly edited for clarity. Handles and vote tallies are shown as recorded, and comments reflect the views of individual contributors.
From public community threads 2
-
taylz876 👍 1 Answered BSimilar to Q253, Q262 and Q348 Why B is right • Low-latency feature retrieval at request time: Feature Store's online serving layer is built for fast lookups of hundreds of user features, well within a 100 ms limit. • Scales automatically with minimal operational overhead: it's managed, and it can sync from the BigQuery data that the streaming pipeline keeps updated. Why the others are wrong • A: Streaming from BigQuery at request time is the slow approach that caused the problem. • C: A Redis cache on Memorystore works, but you'd build and operate the cache and the writing component yourself. • D: BI Engine speeds up analytic queries, but BigQuery still isn't designed for low-latency per-request serving.
-
n2183712847 👍 1 Answered BCorrect answer: B. Agent Platform Feature Store is designed for low-latency, scalable online feature serving with managed operations, making it appropriate for retrieving frequently updated features within a strict inference SLA; A and D still rely on BigQuery for request-time retrieval, while C can provide low latency but requires you to build and operate a separate Redis caching layer and synchronization logic.
Reader comments & corrections
No reader corrections yet — spotted an error or have a note? Share it below.
Related Analysis
Practice All PMLE Questions
Access 65 questions with complete answers and detailed explanations.
View Full PMLE Practice Test →