Using the SageMaker Model Registry and Model Groups to Version ML Models with Least Overhead

MLA-C01 By islever Editorial Last updated

Select deployment infrastructure based on existing architecture and requirements.

Short answer

C SageMaker Model Registry with model groups catalogs models, and each model package added to a group automatically increments its version, giving least overhead.

Question

Case Study - A company is building a web-based AI application by using Amazon SageMaker. The application will provide the following capabilities and features: ML experimentation, training, a central model registry, model deployment, and model monitoring. The application must ensure secure and isolated use of training data during the ML lifecycle. The training data is stored in Amazon S3. The company needs to use the central model registry to manage different versions of models in the application. Which action will meet this requirement with the LEAST operational overhead?
  1. Create a separate Amazon Elastic Container Registry (Amazon ECR) repository for each model.
  2. Use Amazon Elastic Container Registry (Amazon ECR) and unique tags for each model version.
  3. Use the SageMaker Model Registry and model groups to catalog the models. Correct Answer
  4. Use the SageMaker Model Registry and unique tags for each model version.

Key Takeaways

SageMaker Model Registry organizes models into model groups, and each trained model added to a group becomes a model package whose version increments automatically, so versioning is a built-in property rather than something bolted on with tags or container repositories.

A company building a web-based AI application on SageMaker needs experimentation, training, a central model registry, deployment, and monitoring, and specifically needs the central registry to manage different versions of its models with the least operational overhead. The registry must handle model versioning as a first-class concept.

Common mistake: Reaching for Amazon ECR to version models, or assuming unique ECR tags can stand in for model versions. ECR stores container images, not trained model artifacts with their metadata, so it cannot serve as a central model registry.

Expert Analysis

Why the Answer Is Correct

The requirement is a central model registry that manages different versions of models, and SageMaker Model Registry is the feature built for exactly that inside the SageMaker ecosystem. In the Model Registry, a model group holds related models, and each model package added to a group is one trained model whose version is a numerical value starting at 1 and incrementing with each new package, so versioning happens automatically without any tagging discipline. Because the registry is part of SageMaker, it integrates directly with the training, deployment, and monitoring pieces of the application. The vote was unanimous at 100 for C, and GiorgioGss, khchan123, motk123, and Laxma99 all described Model Registry and model groups as the native versioning and cataloging mechanism, with motk123 adding that groups can be aggregated into Collections.

Why the Other Options Are Wrong

Creating a separate ECR repository per model (A) and using ECR with unique tags per model version (B) both misapply a container image registry. Amazon ECR stores Docker container images, and the trained model artifacts with their versions and metadata belong in the Model Registry, so ECR cannot act as the central model registry the question requires. Using Model Registry with unique tags for each model version (D) is closer than the ECR options because it uses the right service, but model groups already provide the versioned grouping natively, so relying on ad hoc tags adds a manual naming convention on top of a versioning system that Model Registry implements for you, which is extra operational overhead rather than the least.

Community Comment Notes

The community was unanimous, with all 100 votes for C and every substance comment in agreement. ninomfr64 dismissed both ECR options in one line, noting that ECR is for storing container images, and quoted the Model Registry documentation for the version-increment behavior. prabirg summarized it as Model Registry creating catalog models for production and managing model versions, and S_201996 noted the registry centralizes model management including versioning, approval workflows, and deployment history.

Official Reference

https://docs.aws.amazon.com/sagemaker/latest/dg/model-registry-models.html

This link opens the official vendor documentation in a new tab.

Community Votes

C
100%

100% of anonymous learners picked answer C. Votes are pick records left by other test-takers — they are not the verified answer.

Discussion 8 contributions

Compiled from public community threads and reader submissions, lightly edited for clarity. Handles and vote tallies are shown as recorded, and comments reflect the views of individual contributors.

From public community threads 8

  1. GiorgioGss 👍 8 Answered C
    https://docs.aws.amazon.com/sagemaker/latest/dg/model-registry-models.html "Each model package in a Model Group corresponds to a trained model. The version of each model package is a numerical value that starts at 1 and is incremented with each new model package added to a Model Group. For example, if 5 model packages are added to a Model Group, the model package versions will be 1, 2, 3, 4, and 5."
  2. Neo_2022 👍 4 Answered C
    https://aws.amazon.com/blogs/machine-learning/centralize-model-governance-with-sagemaker-model-registry-resource-access-manager-sharing/
  3. khchan123 👍 3 Answered C
    The correct answer is C. Use the SageMaker Model Registry and model groups to catalog the models. SageMaker Model Registry is specifically designed for managing ML models within the SageMaker ecosystem. It provides built-in versioning and cataloging capabilities for ML models. Model groups in the Model Registry allow for logical organization of related models. It integrates seamlessly with other SageMaker components like training, deployment, and monitoring. This solution offers the least operational overhead as it's a native SageMaker feature designed for this exact purpose. It provides features like model approval workflows, which are crucial for managing models in production environments.
  4. motk123 👍 2 Answered C
    C: The SageMaker Model Registry organizes models into Model Package Groups, tracks versions as Model Packages, and optionally aggregates groups into Collections. This structure ensures robust versioning and manageability for trained models. https://docs.aws.amazon.com/sagemaker/latest/dg/model-registry-models.html
  5. Laxma99 👍 1 Answered C
    SageMaker Model Registry is specifically designed for managing ML models within the SageMaker ecosystem. It provides built-in versioning and cataloging capabilities for ML models. Model groups in the Model Registry allow for logical organization of related models. It integrates seamlessly with other SageMaker components like training, deployment, and monitoring. This solution offers the least operational overhead as it's a native SageMaker feature designed for this exact purpose. It provides features like model approval workflows, which are crucial for managing models in production environments.
Show 3 more comments
  1. ninomfr64 👍 1 Answered C
    A. No, ECR is used to store container images B. No, ECR is used to store container images C. Yes D. No, Each model package in a Model Group corresponds to a trained model. The version of each model package is a numerical value that starts at 1 and is incremented with each new model package added to a Model Group - https://docs.aws.amazon.com/sagemaker/latest/dg/model-registry-models.html
  2. S_201996 👍 1 Answered C
    Amazon SageMaker Model Registry is specifically designed to manage and catalog models in a centralized way, including versioning, approval workflows, and deployment history. It simplifies the process of managing different versions of models, which aligns with the company's requirement to use a central model registry.
  3. prabirg 👍 1 Answered C
    Amazon SageMaker Model Registry creates Catalog models for production and Manage model versions.

Reader comments & corrections

No reader corrections yet — spotted an error or have a note? Share it below.

Log in to comment, report an error, or add a note about this question.

Submitted for moderation before publishing. Keep it helpful and respectful.

Choosing LightGBM in SageMaker for Fraud Detection with Class Imbalance and Correlated Features

S-grade

Processing Mixed CSV JSON XLSX Parquet Files in One S3 Folder with DataBrew and Outputting Apache Parquet

S-grade

Rebuilding the Model Monitor Baseline After a Model Update Causes Data Quality Violations

S-grade

Orchestrating SageMaker ML Workflows as DAGs in Studio with ML Lineage Tracking for Governance

S-grade

Practice All MLA-C01 Questions

Access 115 questions with complete answers and detailed explanations.

View Full MLA-C01 Practice Test →

← Back to MLA-C01 Study Guide