Instiq
Chapter 2 · Collaborating within and across teams to manage data and models·v1.0.0·Updated 7/30/2026·~14 min

What's changed: Created Professional Machine Learning Engineer Chapter 2 (Domain 2 "Collaboration": org data sources (Cloud Storage/BigQuery/Spanner/Cloud SQL/Spark/Hadoop), Agent Platform datasets, preprocessing (Dataflow/TFX/BigQuery), Feature Store on Gemini Enterprise Agent Platform, PII/PHI privacy; Jupyter backends (Gemini Enterprise Agent Platform Workbench/Colab Enterprise/Dataproc), security, frameworks (TensorFlow/PyTorch/sklearn/Spark/JAX), Model Garden, experiment tracking (Experiments on Agent Platform/Kubeflow Pipelines/TensorBoard), gen AI evaluation).

2.2Notebooks and experiment tracking

Key points

Understand choosing the Jupyter backend on Google Cloud (Gemini Enterprise Agent Platform Workbench, Colab Enterprise, notebooks on Dataproc), security best practices in Gemini Enterprise Agent Platform Workbench, Spark kernels, code-repository integration, developing with frameworks (TensorFlow/PyTorch/sklearn/Spark/JAX), leveraging foundation/open-source models in Model Garden, tracking ML experiments (Experiments on Agent Platform, Kubeflow Pipelines, Vertex AI TensorBoard), and evaluating generative AI solutions.

Prototype in notebooks and record experiments systematically. Trial-and-error without records cannot be reproduced.

2.2.1Notebook environments and frameworks

Choose the Jupyter backend by requirement: serious ML development = managed Gemini Enterprise Agent Platform Workbench; collaboration/ease = Colab Enterprise; running on existing Spark/Hadoop = notebooks on Dataproc (Spark kernels). In Workbench, apply security best practices (least-privilege SA, private, user-managed vs managed) and version code via code-repository integration. Develop with familiar frameworks—TensorFlow, PyTorch, sklearn, Spark, JAX—and leverage foundation/open-source models in Model Garden. Map "managed ML dev environment = Gemini Enterprise Agent Platform Workbench" and "use Spark = Dataproc notebooks."

2.2.2Experiment tracking and evaluating gen AI

For reproducibility, record experiments systematically. Compare params/metrics/artifacts with Experiments on Agent Platform, visualize learning curves with Vertex AI TensorBoard (TensorFlow/PyTorch), and run pipeline-style experiments with Kubeflow Pipelines. For generative AI, beyond accuracy, perform generative AI evaluation (automatic metrics, human evaluation, LLM-as-judge for quality/safety/groundedness) and iterate. Map "record/compare experiments = Experiments on Agent Platform," "visualize learning curves = TensorBoard," and "evaluate gen AI quality = eval metrics/human/judge."

Exam point

Common: requirement → means. E.g., "managed Jupyter for serious ML dev" = Gemini Enterprise Agent Platform Workbench; "easy collaboration" = Colab Enterprise; "on existing Spark" = Dataproc notebooks; "record/compare params/metrics" = Experiments on Agent Platform; "visualize learning curves" = Vertex AI TensorBoard; "evaluate gen AI output quality" = gen AI evaluation (auto/human/judge).

Warning

Watch the mix-ups: (1) Experiments on Agent Platform (record/compare) vs TensorBoard (visualize learning curves) play different roles—use both. (2) Do not neglect notebook security (broad SA, public IP)—least privilege/private. (3) Gen AI cannot be measured by accuracy alone—evaluate quality/safety/groundedness.

Diagram of Jupyter backends (Gemini Enterprise Agent Platform Workbench/Colab Enterprise/Dataproc), experiment tracking (Experiments on Agent Platform/TensorBoard/Kubeflow Pipelines), and evaluating gen AI for quality/safety/groundedness.
Record runs and evaluate

2.2.3Section summary

  • Jupyter = Gemini Enterprise Agent Platform Workbench (serious)/Colab Enterprise (easy)/Dataproc (Spark); secure Workbench
  • Record/compare experiments = Experiments on Agent Platform; learning curves = TensorBoard; pipeline experiments = Kubeflow Pipelines
  • Evaluate gen AI for quality/safety/groundedness (auto metrics/human/judge)

Sign in to track progress — Log in.

Quick check

(just a quick review)

Q1. For serious ML development in a managed Jupyter environment with least privilege and private networking, which is best?

Q2. To record params, metrics, and artifacts across runs and compare them later, which is best?

Q3. To visualize loss curves and accuracy over training as graphs, which is best?

Q4. To develop in notebooks with Spark kernels on an existing Spark/Hadoop cluster, which is best?

Q5. To evaluate a generative AI solution beyond accuracy—on quality, safety, and groundedness—which is best?

Check your understandingPractice questions for Chapter 2: Collaborating within and across teams to manage data and models

Keep track of your progress

The full study guide is free to read. Sign up free to practice with the question bank, track what you have read, review your mistakes, and highlight passages.