PMLE Collaborating to manage data and models Practice Question

You are collaborating with a team of data scientists on a Vertex AI Workbench notebook that preprocesses data for a machine learning model. You need to ensure that all team members can work on the notebook simultaneously without overwriting each other's changes, and that the notebook's execution environment remains consistent across the team. (Choose two.)

⚠ Common exam trap

The trap here is assuming that Vertex AI Workbench has built-in real-time collaboration or automatic syncing, when in fact you must use external tools like Git and Artifact Registry for effective teamwork.

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

✓

Store the notebook in a Cloud Source Repositories repository and use Git for version control.

Git-based version control via Cloud Source Repositories enables concurrent work with conflict resolution, while a shared custom container image ensures a consistent environment. Together, they allow team members to collaborate effectively without overwriting changes and with identical dependencies. Other options either lack robust version control or misstate Vertex AI Workbench capabilities.

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

✓
Store the notebook in a Cloud Source Repositories repository and use Git for version control.
Why this is correct
Using Cloud Source Repositories with Git provides version control, allowing multiple team members to work on the notebook concurrently by branching and merging. It tracks changes and resolves conflicts, ensuring that no work is overwritten. This is a standard collaborative practice for code and notebooks, and it integrates with Vertex AI Workbench.
✗
Use Vertex AI Workbench's managed notebooks, which automatically sync all user changes to a central repository without requiring Git.
Why it's wrong here
Managed notebooks in Vertex AI Workbench do not automatically sync changes to a central repository for collaboration. They provide a managed environment but still require you to set up version control separately. This option misrepresents the feature set and does not solve the collaboration need.
✗
Enable the notebook's built-in real-time collaboration feature, which allows multiple users to edit the same notebook simultaneously.
Why it's wrong here
Vertex AI Workbench does not have a built-in real-time collaboration feature like Google Docs. While JupyterLab supports some collaborative extensions, they are not natively integrated or recommended for production use. Relying on such a feature would not provide robust version control or conflict resolution.
✗
Schedule regular exports of the notebook to a shared Cloud Storage bucket, and have team members import the latest version before making changes.
Why it's wrong here
Manual exports and imports are error-prone and can lead to overwrites if two people export at the same time. This approach lacks automatic conflict resolution and does not provide a consistent execution environment. It is not a reliable collaboration method for simultaneous work.
✓
Configure the notebook to use a custom container image stored in Artifact Registry, and share the image with the team.
Why this is correct
A custom container image ensures that the execution environment, including libraries and dependencies, is identical for all team members. By storing the image in Artifact Registry and referencing it in the Vertex AI Workbench instance, you guarantee consistency. This eliminates environment drift and makes collaboration smoother, as everyone runs the same software stack.

Go deeper

PMLE Collaborating to manage data and models Practice Question

Why each option matters

Option-by-option breakdown

Related to this question