PMLE Practice Question: Collaborating Within and Across Teams to Manage Data and Models
A team wants to use Vertex AI Workbench for collaborative notebook development. They need a persistent environment that can be stopped and restarted without losing installed packages and data. Which instance type should they choose?
⚠ Common exam trap
The trap is assuming 'managed' means 'better persistence' — in fact, user-managed notebooks give the user direct control over the persistent VM and disk, which is what preserves custom packages and data.
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
✓
User-managed notebooks
User-managed notebooks are Compute Engine instances where the user controls the environment, including installed packages, kernel state, and persistent disk contents. Because the underlying VM and its boot/data disks persist across stop and start operations, installed packages and data remain intact. This makes them the right choice for a persistent, customizable environment.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
User-managed notebooks
Why this is correct
User-managed notebooks give a persistent Compute Engine instance with a customisable environment, so installed packages and data survive stopping and restarting. This satisfies the stem's requirement for persistence, unlike managed notebooks with ephemeral or containerised runtimes.
- ✗
Managed notebooks
Why it's wrong here
Managed notebooks are Google-managed environments where lifecycle and dependencies are controlled by the platform, so custom packages and local data may not persist reliably across stop and restart. It is tempting because it reduces administrative overhead, suiting teams wanting hands-off notebook infrastructure. User-managed instances provide the persistence required.
- ✗
Colab Enterprise notebooks
Why it's wrong here
Colab Enterprise notebooks are managed, serverless environments that do not persist installed packages or local data across stop and restart cycles. It is tempting because it offers collaborative notebooks with Google-managed infrastructure, suiting exploratory analysis. Persistent user-managed instances that retain packages and data across restarts are required here.
- ✗
Vertex AI Pipelines
Why it's wrong here
Vertex AI Pipelines orchestrates ML workflows as containerised steps; it does not provide an interactive notebook environment at all. It is tempting because it is part of Vertex AI and supports reproducible, scheduled ML processes, suiting production pipeline automation. Persistent collaborative notebook development needs a Workbench instance type, not a pipeline orchestrator.
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.