AWS Certified Machine Learning – SpecialtyMachine Learning Implementation and OperationsEasy
A data scientist is deploying a new anomaly detection model to a SageMaker real-time endpoint. During testing, they observe that the endpoint sometimes fails to start up within the default timeout period when deploying new model versions, especially for larger models or those with complex initialization logic. This leads to deployment failures and increased downtime. To resolve this, they need to increase the time SageMaker waits for the container to become healthy after deployment. Which parameter should be adjusted?
- AModelDataDownloadTimeoutInSeconds
- BInferenceTimeoutInSeconds
- CContainerStartupHealthCheckTimeoutInSeconds
- DInstanceType
Show answer & explanationAnswer & explanation
Correct answer: C. ContainerStartupHealthCheckTimeoutInSeconds
The `ContainerStartupHealthCheckTimeoutInSeconds` parameter directly controls how long SageMaker waits for the Docker container within the endpoint to pass its health checks and become ready to serve inferences. Increasing this value is the correct solution for preventing timeouts during the startup phase of a larger or more complex model's deployment.
Why the other options are wrong
- A. This parameter controls the time allowed for model artifacts to be downloaded, not the container startup time.
- B. This parameter controls the maximum time an individual inference request can take, not the container startup time.
- D. Changing the instance type might provide more resources but doesn't directly adjust the timeout period for container startup; the timeout would still need to be adjusted if the startup time exceeds the default.
ContainerStartupHealthCheckTimeoutInSeconds
A SageMaker endpoint configuration parameter that defines the maximum duration, in seconds, for a container to successfully start and pass its health checks before SageMaker declares the deployment failed.
- Crucial for deploying large models or containers with long initialization.
- Default is 600 seconds (10 minutes).
- Prevents deployment failures due to slow container startup.
Memory trick: Startup timeout is the patience meter for your container.