MLA-C01 Practice Question: Refer to the exhibit

Exhibit

[ERROR] 2024-03-15 10:23:45,123 - sagemaker - 1321 - root - ERROR - InvocationException: Received response status code 404 from container. Error: ResourceNotFoundException: Model 'my-model-v2' is not found. You may be using an outdated endpoint configuration.

Refer to the exhibit. A data engineer investigates why a SageMaker endpoint is returning errors. The endpoint configuration has been updated to point to a new model version. What is the MOST likely cause of the error?

⚠ Common exam trap

AWS often tests the distinction between updating an endpoint configuration and actually deploying that configuration to the endpoint, leading candidates to assume that changing the configuration automatically updates the endpoint.

Answer choices

Why each option matters

Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.

Correct answer & explanation

✓

The endpoint is still using the previous configuration.

When a SageMaker endpoint configuration is updated to point to a new model version, the endpoint itself does not automatically switch to the new configuration unless a subsequent UpdateEndpoint or Deploy call is made. The endpoint continues serving the previous model until the update is explicitly applied, so the errors are most likely caused by the endpoint still using the old configuration.

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

✗
The endpoint instance type is insufficient.
Why it's wrong here
An insufficient instance type produces latency or out-of-memory failures, not errors triggered specifically by repointing the endpoint configuration to a new model version. It is tempting because undersized instances genuinely cause endpoint failures, and resizing would be correct if the error appeared under increased inference load rather than after a version change.
✗
The container image for the new model is not compatible.
Why it's wrong here
An incompatible container image fails at model load time, yet the stem attributes the error to the configuration update pointing at a new model version, which leaves the image unchanged. It is tempting because container incompatibility genuinely breaks SageMaker endpoints, and it would be correct if the image itself had been swapped alongside the model.
✗
The IAM role does not have permission to invoke the endpoint.
Why it's wrong here
Invoke permissions govern caller access to the endpoint, so a missing policy yields AccessDenied for clients rather than errors introduced by repointing the configuration to a new model version. It is tempting because IAM misconfiguration genuinely blocks endpoint invocation, and it would be correct if callers, not the model version, had changed.
✓
The endpoint is still using the previous configuration.
Why this is correct
Updating an endpoint configuration does not automatically redeploy the live endpoint; the existing endpoint keeps serving the previous model version until the update is applied. The mismatch between the new configuration and the running endpoint therefore causes inference errors, making a stale configuration the most likely cause.
✗
The new model artifact is not properly uploaded to S3.
Why it's wrong here
A missing S3 artifact causes failure when the endpoint loads the model, but the stem's error follows a configuration update to a new model version, which implies the artifact exists at a new location. It is tempting because absent artifacts genuinely break deployments, and it would be correct if the upload step had been skipped.

Go deeper

MLA-C01 Practice Question: Refer to the exhibit

Exhibit

Why each option matters

Option-by-option breakdown

Related to this question