The answer is to create a new endpoint configuration referencing the new image and then call update-endpoint. This is necessary because SageMaker endpoint configurations are immutable—you cannot edit an existing configuration to point to a different model version. Instead, you must create a fresh configuration (e.g., my-endpoint-config-v2) that specifies the new ECR image tag ':2', then invoke update-endpoint with that configuration name to trigger a zero-downtime deployment. On the AWS Certified Machine Learning Engineer Associate MLA-C01 exam, this concept tests your understanding of SageMaker’s deployment lifecycle and the distinction between mutable model artifacts and immutable endpoint configurations. A common trap is assuming you can simply modify the existing config in place, which SageMaker does not allow. Remember: to update an endpoint to a new model version, always create a new config first—think of it as “new image, new config, then update.”
MLA-C01 Deployment and Orchestration of ML Workflows Practice Question
This MLA-C01 practice question tests your understanding of deployment and orchestration of ml workflows. The scenario asks you to isolate a root cause — eliminate options that address a different problem before choosing. After answering, compare your reasoning against the explanation and wrong-answer breakdown below. Once you have made your selection, read the full explanation to reinforce the concept and understand why each distractor is designed to mislead on exam day.
An engineer runs: aws sagemaker describe-endpoint --endpoint-name my-endpoint and receives the exhibit output. The engineer wants to update the endpoint to use a new model version stored in ECR with tag ':2'. Which step is necessary to perform the update?
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Create a new endpoint configuration (my-endpoint-config-v2) referencing the new image, then call update-endpoint with the new config name.
Option A is correct because SageMaker endpoints are immutable with respect to their configuration; you cannot modify an existing endpoint configuration in place. To update an endpoint to use a new model version, you must create a new endpoint configuration (e.g., my-endpoint-config-v2) that points to the new ECR image tag ':2', then call update-endpoint with the new configuration name. This triggers a zero-downtime deployment where SageMaker gradually shifts traffic to the new variant.
Key principle: Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
✓
Create a new endpoint configuration (my-endpoint-config-v2) referencing the new image, then call update-endpoint with the new config name.
Why this is correct
Standard process: create new endpoint config, then update endpoint to use it.
Related concept
Read the scenario before looking for a memorised answer.
✗
Modify the existing endpoint configuration (my-endpoint-config-v1) to use the new image, then update the endpoint.
Why it's wrong here
Endpoint configurations are immutable; you cannot modify them after creation.
✗
Use the update-endpoint command directly with the new image ARN.
Why it's wrong here
The update-endpoint command only accepts an endpoint config name, not an image ARN directly.
✗
Delete the endpoint and recreate it with the new model image.
Why it's wrong here
Deleting the endpoint causes downtime; updating is the correct approach.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates assume endpoint configurations are mutable like a text file, but AWS SageMaker enforces immutability — you must create a new configuration for any change, even a simple image tag update.
Trap categories for this question
Command / output trap
The update-endpoint command only accepts an endpoint config name, not an image ARN directly.
Detailed technical explanation
How to think about this question
Under the hood, SageMaker uses endpoint configurations to define the model variant, instance type, and initial instance count. When you call update-endpoint with a new configuration, SageMaker performs a rolling update: it provisions new instances with the new model, waits for them to become healthy, then shifts traffic and terminates old instances. This process relies on the endpoint's 'EndpointStatus' transitioning through 'Updating' and 'InService' states, and the new configuration must reference a valid model ARN that points to the ECR image (e.g., account-id.dkr.ecr.region.amazonaws.com/repo:2).
KKey Concepts to Remember
Read the scenario before looking for a memorised answer.
Find the constraint that changes the correct option.
Eliminate answers that are true in general but not in this case.
TExam Day Tips
→Watch for words such as best, first, most likely and least administrative effort.
→Review why wrong options are wrong, not only why the correct option is correct.
Key takeaway
Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Real-world example
How this comes up in practice
A cloud solutions architect for a retail company is evaluating services for a new workload. The correct answer here reflects best practice for the specific scenario described — not a general cloud recommendation. Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option. Cloud exam questions reward reading the constraint carefully: the same technology can be right or wrong depending on the use case.
What to study next
Got this wrong? Here's your next step.
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
Deployment and Orchestration of ML Workflows — This question tests Deployment and Orchestration of ML Workflows — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: Create a new endpoint configuration (my-endpoint-config-v2) referencing the new image, then call update-endpoint with the new config name. — Option A is correct because SageMaker endpoints are immutable with respect to their configuration; you cannot modify an existing endpoint configuration in place. To update an endpoint to use a new model version, you must create a new endpoint configuration (e.g., my-endpoint-config-v2) that points to the new ECR image tag ':2', then call update-endpoint with the new configuration name. This triggers a zero-downtime deployment where SageMaker gradually shifts traffic to the new variant.
What should I do if I get this MLA-C01 question wrong?
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
What is the key concept behind this question?
Read the scenario before looking for a memorised answer.
About these practice questions
Courseiva creates original exam-style practice questions with explanations and wrong-answer analysis. It does not publish real exam questions, exam dumps, or protected exam content. Learn why practice questions differ from exam dumps →
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
This MLA-C01 practice question is part of Courseiva's free Amazon Web Services 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 MLA-C01 exam.
Question Discussion
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
Sign in to join the discussion.