Study guide
13.1 Organizing & Versioning Models in Model Registry
Google Cloud Professional Machine Learning Engineer PMLE
Track your progress as you read
Finished sections get a check mark.
1 Chapter 1: Exam Overview & the Agent Platform Map
1.1 PMLE Exam Facts, Policies & the June 2026 Blueprint 1.2 From Vertex AI to Gemini Enterprise Agent Platform: The Product Name Map
2 Chapter 2: Low-Code ML with BigQuery ML
2.1 Choosing, Training & Predicting with BigQuery ML Models 2.2 Feature Engineering & Feature Selection in BigQuery ML 2.3 Fine-Tuning & Evaluating Gemini Models from BigQuery
3 Chapter 3: AutoML & Google Cloud AI APIs
3.1 Training Models with Agent Platform AutoML 3.2 Building with Document AI, Vision, Translation & Other AI APIs
4 Chapter 4: Foundation Models in Model Garden
4.1 Evaluating & Selecting Models in Model Garden 4.2 Building & Tuning Solutions with Gemini, Imagen, Veo & MaaS 4.3 Optimizing Gemini Applications for Cost, Latency & Availability
5 Chapter 5: Exploring, Preprocessing & Protecting Data
5.1 Organizing & Exploring Tabular, Text & Image Data 5.2 Choosing a Preprocessing Tool: BigQuery, Dataflow, Spark or Python 5.3 Creating & Consolidating Features in Agent Platform Feature Store 5.4 Protecting PII & Sensitive Data in ML Workflows
6 Chapter 6: Notebooks, Prototyping & Experiment Tracking
6.1 Workbench vs. Colab Enterprise: Secure, Collaborative Notebooks 6.2 Prototyping with PyTorch, scikit-learn, JAX & Model Garden in Notebooks 6.3 Experiment Environments, Tracking & Lineage with Experiments and ML Metadata
7 Chapter 7: Evaluating Predictive & Generative AI Solutions
7.1 Evaluation Metrics for Predictive Models 7.2 Evaluating Gen AI: Computation Metrics, Rubrics & LLM-as-a-Judge
8 Chapter 8: Choosing the Modeling Approach
8.1 Choosing the Model Type: ARIMA, Trees, DNNs & LLMs 8.2 Choosing the Product & Deployment Strategy 8.3 Modeling Techniques for Interpretability Requirements
9 Chapter 9: Training Data & Training SDKs
9.1 Organizing & Ingesting Training Data from Cloud Storage & BigQuery 9.2 Custom Training on Agent Platform: Containers, Jobs & Worker Pools 9.3 Kubeflow on GKE, AutoML & Tabular Workflows as Training Choices
10 Chapter 10: Troubleshooting, Hyperparameter Tuning & Fine-Tuning
10.1 Troubleshooting ML Training Failures 10.2 Hyperparameter Tuning on Agent Platform 10.3 Fine-Tuning Foundation Models & When to Tune
11 Chapter 11: Training Hardware & Distributed Training
11.1 Choosing CPUs, GPUs & TPUs for Training 11.2 Distributed Training: Data & Model Parallelism
12 Chapter 12: Deploying Models for Inference
12.1 Batch vs. Online Inference on Agent Platform 12.2 Serving Beyond Agent Platform Endpoints: Model Garden, Cloud Run & GKE 12.3 Prebuilt & Custom Serving Containers
13 Chapter 13: Model Versions, Rollouts & Inference Logic
13.1 Organizing & Versioning Models in Model Registry 13.2 Rollout Strategies: A/B Tests, Canaries & Traffic Splits 13.3 Inference Preprocessing & Postprocessing
14 Chapter 14: Scaling Online Serving
14.1 Serving Features Online with Feature Store 14.2 Public, Dedicated & Private Endpoints 14.3 Serving Hardware & Autoscaling for Throughput 14.4 Tuning Models for Production Training & Serving
15 Chapter 15: End-to-End ML Pipelines
15.1 Validating Data & Models in Pipelines 15.2 Agent Platform Pipelines with KFP: Components, Templates & Caching 15.3 Ensuring Consistent Preprocessing Between Training & Serving
16 Chapter 16: Orchestration with Managed Airflow & Ray
16.1 Orchestrating ML Workflows with Managed Service for Apache Airflow 16.2 Ray on Agent Platform for Distributed ML Workloads
17 Chapter 17: Automating Retraining & CI/CD/CT
17.1 Choosing a Retraining Policy 17.2 CI/CD/CT for ML with Cloud Build
18 Chapter 18: Securing AI Systems, Responsible AI & Explainability
18.1 Protecting AI Systems from Data & Model Exfiltration 18.2 Defending Gen AI Apps: Safety Filters, Model Armor & Regex Guardrails 18.3 Responsible AI: Detecting & Monitoring Bias 18.4 Model Explainability on Agent Platform
19 Chapter 19: Monitoring AI Solutions
19.1 Configuring Model Monitoring on Agent Platform 19.2 Training-Serving Skew, Data Drift, Concept Drift & Attribution Drift 19.3 Monitoring, Testing & Evaluating Gen AI Solutions in Production
13.1 Organizing & Versioning Models in Model Registry
Key Takeaways Explain This Topic AI
Agent Platform Model Registry manages custom models, AutoML tabular and image models, and registered BigQuery ML models in one place.
The first version of a new model automatically gets the default alias, and exactly one version must carry the default alias at all times.
A model alias is a mutable, named pointer to one version, so moving an alias to a new version removes it from the old one.
Labels organize and filter models, while aliases identify which version plays a role such as default or champion.
Copying a model to another region or project reuses the exact trained artifacts, but BigQuery ML models can't be copied that way.
Last updated: September 2026
The exam guide lists organizing and versioning models in Gemini Enterprise Agent Platform Model Registry . Model Registry answers operational questions: which models exist, which version is in production, how each version performed, and how to roll back.
- What Model Registry Manages
- Custom-trained models (prebuilt or custom serving containers)
- AutoML models (tabular and image)
- BigQuery ML models , registered without export
Imported models trained elsewhere, when artifacts meet prebuilt-container requirements or come with a custom container
From a version's detail page you can evaluate , deploy to an endpoint , run batch inference , and view performance metrics. Knowledge Catalog makes models searchable across projects and regions.
Models, Versions, Aliases, and Labels
- Concept What it is Example
- Model A logical model resource that groups versions fraud-detector
- Version A specific trained artifact with its own ID and serving container Version 7, trained 2026-09-10
Alias A mutable, named reference to one version, like a Git branch or Docker tag default , champion , challenger , staging
- Label Key-value metadata for organizing and filtering team=risk , use_case=cards , data_version=v12
- Description Free text for context "Adds merchant-category crosses. Recall at 90% precision +3%"
- Alias rules
The first version of a new model automatically gets the default alias.
Exactly one version carries default at all times. When a command doesn't name a version, the default version is used.
An alias points to one version per model . Assigning an existing alias to another version moves it there.
Aliases must match the format [a-z][a-z0-9-]{0,126}[a-z0-9] and can't be purely numeric, so they're never confused with version IDs.
Aliases aren't labels. Aliases select a version by role. Labels describe and group.
Creating Versions
Source How a version lands in the registry
Custom training Upload the artifacts with parent_model set to the existing model (API models.upload with parentModel ). A TrainingPipeline can upload automatically
Console import Import as new version , then optionally set it as default
BigQuery ML MODEL_REGISTRY = 'VERTEX_AI' , optionally with VERTEX_AI_MODEL_ID and VERTEX_AI_MODEL_VERSION_ALIASES
AutoML Training creates a model, and retraining can add versions
Pipelines A model upload component registers the version as part of the run, with lineage model_v8 = aiplatform.Model.upload(
- display_name="fraud-detector",
- parent_model="projects/p/locations/us-central1/models/1234",
- artifact_uri="gs://ml-artifacts/fraud/2026-09-17/",
- serving_container_image_uri=XGB_PREBUILT_IMAGE,
- version_aliases=["challenger"],
- is_default_version=False,
- labels={"data_version": "v13", "team": "risk"},
- )
- Versions and Evaluations
Attach model evaluations to each version, either from the registry or through the evaluation pipeline component (Chapter 7). You can then compare versions side by side before promotion. Combined with ML Metadata lineage (Chapter 6), each version links back to its dataset, code, and training run.
A Promotion Workflow
The training pipeline uploads a new version with the alias challenger . It is not default.
The evaluation component compares challenger with champion on the same test set.
If it meets the gates, a canary rollout sends a small share of endpoint traffic to the challenger (Section 13.2).
After online checks pass, move the champion alias (and default ) to the new version.
Rollback means moving the alias back and shifting traffic to the previous deployed version, with no retraining.
Because deployments and batch jobs can reference versions by alias, moving an alias is a clean, auditable promotion step.
Copying Models Across Regions and Projects
Copy model duplicates a registered model into another location in the same project or another project . Use it to deploy the exact same trained model in several regions, or to promote from a dev project to a prod project. Retraining isn't a substitute, because training is non-deterministic. If you don't name a version, the default version is copied. BigQuery ML models can't be copied this way.
Organizing at Scale
One model resource per use case (such as churn-mobile ), with versions over time. Don't create a new model resource for every retrain.
Labels for ownership and context: team, cost center, data version, regulatory scope.
Separate projects for environments (dev, staging, prod), with copy model or CI/CD promotion between them.
IAM to control who can upload versions or move production aliases.
Retire old versions that are neither deployed nor needed for audits, keeping records required by policy.
Governance Questions the Registry Should Answer
Question Where the answer lives
Which version is serving production traffic right now? Endpoint deployed models plus the champion or default alias
- Who approved it, and when? Labels or description plus CI/CD records
- What data and code produced it? ML Metadata lineage from the pipeline run
- How did it perform before release? Evaluations attached to the version
- What can we roll back to? The previous version, still registered and possibly still deployed at 0% traffic
- Exam Traps
Deploying by version ID in scripts that should follow the "current production" model. Use aliases so promotion doesn't require code changes.
Using labels to mark the production model. Labels don't enforce one-version-per-role, but aliases do.
Retraining in each region to "replicate" a model instead of copying it.
Forgetting that a registered BigQuery ML model can be deployed to an endpoint directly from the registry without export.