PMLE Practice Question: Collaborating Within and Across Teams to Manage Data and Models
A team uses Vertex AI Workbench notebooks for collaborative model development. They want to ensure that code changes are version-controlled, that multiple data scientists can work on the same notebook without conflicts, and that the environment is reproducible across team members. Which approach should they take?
⚠ Common exam trap
The trap is thinking that sharing a VM or Cloud Storage bucket enables collaboration — the exam expects you to recognize that Git integration and custom containers are required for version control and reproducibility.
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 Vertex AI Workbench managed notebooks with Git integration and a custom container image for environment reproducibility.
Vertex AI Workbench managed notebooks support Git integration for version control and custom container images for reproducible environments. This combination allows multiple data scientists to collaborate on notebooks with version history and ensures the runtime environment is consistent across team members.
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 JupyterLab instance launched on a single VM; data scientists connect simultaneously.
Why it's wrong here
A shared JupyterLab instance gives concurrent editing with no Git history and one mutable environment, so version control, conflict avoidance and reproducibility all fail. It is tempting because shared notebooks feel collaborative, and would suit ad-hoc exploration where reproducibility is not required.
- ✓
Use Vertex AI Workbench managed notebooks with Git integration and a custom container image for environment reproducibility.
Why this is correct
Git integration in managed notebooks provides branch-based version control and conflict resolution for concurrent editors, while a custom container image pins library versions so every data scientist gets an identical runtime. This satisfies the stem's three constraints: version-controlled changes, conflict-free collaboration, and reproducible environments across the team.
- ✗
Store notebooks in Cloud Storage and share the bucket; each user edits their own copy.
Why it's wrong here
Cloud Storage buckets provide object storage with no merge, branching or commit history, so concurrent edits overwrite each other and reproducibility depends on manual discipline. Sharing buckets suits distributing static artefacts or datasets, not collaborative notebook development requiring version control and conflict resolution.
- ✗
Use Vertex AI Pipelines to run all code as pipelines; data scientists only view results in notebooks.
Why it's wrong here
Pipelines execute code but notebooks remain the editing surface, so code changes are not version-controlled and concurrent editing conflicts persist. It is tempting because pipelines do give reproducible execution, and would be correct if the requirement were orchestration rather than collaborative notebook development.
Go deeper
Related to this question
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 and reviewed by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
Last reviewed September 2026 · checked against the official Google Cloud exam blueprint
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.