mediumMultiple Select
PMLE Practice Question: Which THREE considerations are important when…
Which THREE considerations are important when setting up a shared feature store in Vertex AI Feature Store for multiple teams?
⚠ Common exam trap
Google Cloud often tests the misconception that a shared feature store requires separate physical storage per team (Option B) or fully independent ingestion (Option E), when in reality the value lies in centralization with controlled access and standardized pipelines.
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
✓
Enable feature monitoring for data quality and freshness
Option A is correct because enabling feature monitoring in Vertex AI Feature Store lets you track data quality and freshness metrics (such as drift and staleness) so that multiple consuming teams can trust the shared features. Option C is correct because a shared feature store requires data governance policies that define who can create, modify, and access features, ensuring consistent standards and compliance across teams. Option D is correct because a feature sharing policy enables cross-team discovery and reuse of features, which is the core purpose of a centralized shared feature store. Option B is not appropriate because using separate BigQuery tables per team fragments the store and undermines the centralized sharing model. Option E is not appropriate because independent ingestion pipelines per team lead to duplicated, inconsistent feature definitions rather than a governed shared store.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
Enable feature monitoring for data quality and freshness
Why this is correct
Feature monitoring detects drift and staleness across shared feature views, satisfying the multi-team requirement for trustworthy, reusable features. In Vertex AI Feature Store, monitoring alerts each consuming team when data quality or freshness degrades, preventing silent model failures without duplicating validation effort per team.
- ✗
Use separate BigQuery tables for each team's features
Why it's wrong here
Per-team BigQuery tables fragment the shared feature repository, preventing cross-team feature reuse and consistent point-in-time retrieval that a centralised Vertex AI Feature Store provides. Separate tables suit strict data-residency or billing isolation, not a shared store where teams must discover and reuse each other's features.
- ✓
Implement data governance policies for feature creation and access
Why this is correct
A shared feature store exposes one team's engineered features to others, so governance controls who may create, publish and consume them. Access policies scoped through Vertex AI Feature Store's IAM roles, plus naming and approval conventions, prevent unvetted or duplicated features leaking across team boundaries — the multi-team sharing constraint the stem specifies.
- ✓
Create a feature sharing policy to enable cross-team discovery
Why this is correct
A feature sharing policy directly addresses cross-team discovery, which is essential when multiple teams must locate and reuse each other's features within a shared Vertex AI Feature Store. Without it, teams operate in silos, duplicating features and undermining the shared store's purpose. The policy governs visibility and access, satisfying the multi-team discovery constraint.
- ✗
Allow each team to build independent ingestion pipelines
Why it's wrong here
Independent ingestion pipelines per team bypass the shared store's managed ingestion, producing inconsistent timestamps and duplicate feature values across teams. Letting teams own pipelines suits isolated projects with no shared consumers; a common feature store requires governed, centralised ingestion so all teams read identical, point-in-time-correct values.
Go deeper
Related to this question
About these practice questions
This PMLE question is part of Courseiva's 775-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam 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.