Enforcing a Manual Model Approval Gate in a SageMaker Pipeline Before Production Deployment

MLA-C01 By islever Editorial Last updated

Use automated orchestration tools to set up continuous integration and continuous delivery (CI/CD) pipelines.

Short answer

D The Model Registry holds each version's approval status, and a SageMaker Pipeline can set it to Approved via the AWS SDK, so only approved models pass the gate.

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 must implement a manual approval-based workflow to ensure that only approved models can be deployed to production endpoints. Which solution will meet this requirement?
  1. Use SageMaker Experiments to facilitate the approval process during model registration.
  2. Use SageMaker ML Lineage Tracking on the central model registry. Create tracking entities for the approval process.
  3. Use SageMaker Model Monitor to evaluate the performance of the model and to manage the approval.
  4. Use SageMaker Pipelines. When a model version is registered, use the AWS SDK to change the approval status to "Approved." Correct Answer

Key Takeaways

The SageMaker Model Registry holds a per-version approval status, and that status can be set through the AWS SDK, so a pipeline can register a model version and then gate on an approval transition, which is exactly the mechanism that enforces an approved-models-only deployment policy.

A company building a SageMaker-based web application must implement a manual approval-based workflow so that only approved models can be deployed to production endpoints. The approval decision is a deliberate human gate, and the surrounding application already has experimentation, training, a model registry, deployment, and monitoring in scope.

Common mistake: Reaching for SageMaker Experiments, ML Lineage Tracking, or Model Monitor, none of which can approve a model version. Experiments tracks runs, Lineage tracks artifact lineage, and Monitor watches deployed model quality, so none of them expresses a deployment authorization decision.

Expert Analysis

Why the Answer Is Correct

The requirement is a manual approval-based workflow that ensures only approved models reach production endpoints, and the approval state itself lives in the SageMaker Model Registry, where each registered model version carries an approval status. A SageMaker Pipeline can register a model version and then, through the AWS SDK, change that approval status to Approved, which is the documented way to update approval programmatically. Because the pipeline consults that status, an unapproved version cannot pass the gate, so the approval workflow is enforced structurally rather than by convention. The vote was unanimous at 100 for D. GiorgioGss quoted the SageMaker documentation stating that you can update the approval status of a model version by using the AWS SDK, and tigrex73 and Laxma99 both described the registry providing the functionality to manually or programmatically approve models for production deployment.

Why the Other Options Are Wrong

Using SageMaker Experiments to facilitate approval during model registration (A) is a category error, because Experiments organizes and tracks experiment runs and their metrics, and it has no approval state to gate a deployment on, as ninomfr64 noted. Using SageMaker ML Lineage Tracking and creating tracking entities for the approval process (B) has the same defect, since lineage tracking records relationships among models, datasets, and artifacts and cannot authorize a deployment. Using SageMaker Model Monitor to evaluate model performance and manage the approval (C) confuses monitoring with authorization, because Model Monitor watches deployed endpoints for quality, bias, and drift, and its findings can inform a decision but cannot record or enforce an approval status.

Community Comment Notes

The community was unanimous at 100 for D, and ninomfr64 explicitly flagged that the option is not clearly worded while still identifying it as correct, then walked through all three rejected options on exactly the grounds that approval state belongs only to the Model Registry. S_201996 described the intended design, noting that you can define a pipeline step where a manual approval is required before the model status changes to Approved for deployment. The consensus rests on the same point the documentation makes: approval status is a Model Registry field, and the AWS SDK is the supported way to change it.

Official Reference

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

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

Community Votes

D
100%

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

Discussion 4 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 4

  1. GiorgioGss 👍 3 Answered D
    https://docs.aws.amazon.com/en_us/sagemaker/latest/dg/model-registry-approve.html "You can update the approval status of a model version by using the AWS SDK "
  2. ninomfr64 👍 1 Answered D
    This tricked my as option D is not clearly worded: A. No, SageMaker Experiments allows to track and organize your experiment but not for approving models B. No, SageMaker ML Lineage Tracking allows to track model lineage but do not allow to approve a model C. No, SageMaker Model Monitor allows to monitor data quality, model quality, bias and feature attribution D. Yes, After you create a model version, you typically evaluate its performance and then update the approval status of the model version. You can update the approval status of a model version by using the SDK, SageMaker Studio console or with a condition step in a SageMaker AI pipeline
  3. S_201996 👍 1 Answered D
    SageMaker Pipelines is designed to orchestrate machine learning workflows, including manual approval steps for model registration. You can define a step in the pipeline where a manual approval process is required before the model's status is changed to "Approved" for deployment.
  4. Laxma99 👍 1 Answered D
    The SageMaker Model Registry within the pipeline provides functionality to manually or programmatically approve models for production deployment.

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