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 and quality deviations in deployed endpoints; it does not compile or convert models for target hardware. It is tempting because it belongs to the SageMaker deployment toolchain, and would be correct when the requirement is ongoing production monitoring of inference data rather than edge compilation.
- ✓
SageMaker Neo
Why this is correct
SageMaker Neo compiles trained models into optimised executables for specific target hardware, reducing compute and memory footprint on constrained edge devices. It satisfies the stem's requirement to compile a TensorFlow model for the target edge hardware without manual re-engineering.
- ✗
SageMaker Debugger
Why it's wrong here
Debugger captures training tensors and metrics to diagnose convergence issues; it does not compile models for edge targets. It is tempting because it is a model optimisation-adjacent SageMaker feature, and would be correct when the requirement is inspecting training jobs for vanishing gradients or poor weight initialisation rather than deployment compilation.
- ✗
SageMaker Elastic Inference
Why it's wrong here
Elastic Inference attaches fractional GPU acceleration to existing endpoints to reduce inference cost; it does not compile a model for edge hardware. It is tempting because it addresses inference performance, and would be correct when the goal is cheaper GPU-backed hosting in the cloud rather than optimising for constrained edge devices.
Go deeper
Related to this question
About these practice questions
This MLA-C01 question is part of Courseiva's 665-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam dumps. Learn why practice questions differ from exam dumps →
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
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.