PMLE Collaborating to manage data and models Practice Question

A team uses Vertex AI Feature Store for storing features. They want to share feature definitions with other teams in a collaborative manner. What is the best way to collaborate on feature definitions?

⚠ Common exam trap

Many candidates assume direct write access (Option B) is efficient for collaboration, but the exam tests understanding that feature stores require controlled, versioned updates to maintain data integrity and avoid breaking downstream models.

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 a shared repository with feature definition files and CI/CD to update the feature store.

Using a shared repository with feature definition files and CI/CD pipelines enables version control, peer review, and automated deployment to Vertex AI Feature Store. This approach ensures consistency, traceability, and collaboration without risking direct, uncoordinated changes to the production feature 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.

✓
Use a shared repository with feature definition files and CI/CD to update the feature store.
Why this is correct
Feature definitions stored as version-controlled files in a shared repository let multiple teams review, reuse and propose changes collaboratively. CI/CD then applies those definitions to Vertex AI Feature Store consistently, satisfying the requirement for collaborative sharing rather than ad-hoc manual updates.
✗
Grant all teams write access to the same feature store so they can modify definitions directly.
Why it's wrong here
Granting every team write access to one feature store removes ownership boundaries, letting any team overwrite or delete another's feature definitions. It tempts because shared access genuinely enables collaboration, and would be correct for a single team managing its own features, not multiple teams needing isolation.
✗
Export the feature definitions as CSV and email them to the other teams.
Why it's wrong here
CSV emailed as an attachment is a static snapshot with no lineage, versioning or registry linkage, so Vertex AI Feature Store cannot ingest or track it. It tempts because CSV export is a real Feature Store capability, and would be correct for one-off offline analysis rather than ongoing cross-team collaboration.
✗
Use a wiki page to document feature definitions and update it manually.
Why it's wrong here
A manually updated wiki page holds no machine-readable schema, so Vertex AI Feature Store cannot consume or version the definitions, and drift is inevitable. It tempts because wikis are genuinely collaborative, and would suit narrative documentation of features rather than the registry itself.

Go deeper

PMLE Collaborating to manage data and models Practice Question

Why each option matters

Option-by-option breakdown

Related to this question