MLA-C01 Deployment and Orchestration of ML Workflows Practice Question

A machine learning engineer needs to optimize a trained TensorFlow model for deployment on edge devices with limited compute. Which SageMaker feature should they use to compile the model for target hardware?

⚠ Common exam trap

Candidates often confuse SageMaker Neo with SageMaker Elastic Inference, mistakenly thinking Elastic Inference compiles models for edge devices, when in fact Elastic Inference only accelerates cloud inference by attaching a fractional GPU and does not perform compilation or target edge hardware.

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

✓

SageMaker Neo

SageMaker Neo is the correct choice because it is specifically designed to compile trained machine learning models into an optimized format for target hardware architectures, such as ARM, Intel, or NVIDIA, enabling efficient inference on edge devices with limited compute resources. It uses a compiler to apply hardware-specific optimizations like operator fusion and memory layout tuning, reducing latency and memory footprint without requiring manual code changes.

Answer analysis

Option-by-option breakdown

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

✗
SageMaker Model Monitor
Why it's wrong here
Model Monitor detects data drift, not inference optimization.
✓
SageMaker Neo
Why this is correct
Neo compiles models for target hardware, optimizing for edge deployment.
✗
SageMaker Debugger
Why it's wrong here
Debugger monitors training, not deployment optimization.
✗
SageMaker Elastic Inference
Why it's wrong here
Elastic Inference is a GPU acceleration add-on for inference, not compilation for edge.

Go deeper

MLA-C01 Deployment and Orchestration of ML Workflows Practice Question

Why each option matters

Option-by-option breakdown

Related to this question