AWS MLA-C01 Complete Exam Guide
AWS Certified Machine Learning Engineer - Associate (MLA-C01) arrived in 2024 as a distinct voice in AWS's certification lineup. Where the older MLS-C01 focused on data scientists and researchers, MLA-C01 is squarely aimed at engineers who build and operate ML systems in production. The exam does not stop at model training. It asks how you deploy, monitor, secure, and cost-optimize the entire ML lifecycle on AWS.
If you have built ML pipelines in production, you will recognize the problems the exam is testing. The four domains map almost directly onto the phases of a real ML project, with SageMaker threading through all of them as the central platform.
Exam Specifications
| Item | Details | |------|---------| | Exam Code | MLA-C01 | | Total Questions | 65 (50 scored + 15 unscored) | | Duration | 170 minutes | | Passing Score | 720 out of 1000 | | Cost | $150 USD | | Question Types | Single-answer and multiple-response | | Validity | 3 years | | Recommended Experience | 1+ year hands-on ML engineering experience |
At 170 minutes for 65 questions, you have roughly 2 minutes 37 seconds per question. The 15 unscored questions are not labeled, so treat every question the same. Multiple-response questions require careful reading since partial credit is not awarded for selecting only some of the correct answers.
Four Domain Breakdown
| Domain | Name | Weight | |--------|------|--------| | D1 | Data Preparation for ML | 28% | | D2 | ML Model Development | 26% | | D3 | Deployment and Orchestration of ML Workflows | 22% | | D4 | ML Solution Monitoring, Maintenance, and Security | 24% |
D1 carries the most weight, which reflects reality well. Data preparation and feature engineering consume 60–80% of effort in real ML projects, and AWS knows this. D4's monitoring and security section at 24% is also substantial. Responsible production operation of models matters as much as building them.
!MLA-C01 exam domain weight breakdown
Domain Details
D1: Data Preparation for ML (28%)
This domain covers the entry point of the ML pipeline. The three sub-domains are data ingestion and storage, data transformation and feature engineering, and data quality and governance.
For ingestion and storage, you need to understand how S3, Kinesis Data Streams, Kinesis Firehose, Glue Data Catalog, and Lake Formation work together to form a data lake for ML workloads. For transformation and feature engineering, SageMaker Data Wrangler, SageMaker Processing, Glue ETL, and SageMaker Feature Store are the primary tools. For data quality and governance, the focus is on detecting data drift, identifying bias in datasets, and tracking data lineage.
D2: ML Model Development (26%)
This domain is less about algorithm theory and more about using SageMaker's training capabilities effectively. The sub-domains are choosing a modeling approach, training and tuning, and model analysis and evaluation.
SageMaker JumpStart and Autopilot represent different entry points: JumpStart provides pre-trained foundation models for fine-tuning, while Autopilot automates model selection and training from raw data. For tuning, SageMaker Hyperparameter Tuning (Bayesian and random strategies) and SageMaker Experiments for tracking are central. For evaluation, SageMaker Clarify handles bias detection and explainability, while SageMaker Debugger inspects tensor values during training.
D3: Deployment and Orchestration (22%)
This domain covers everything from model deployment options to CI/CD pipeline construction. The four inference modes are a frequent exam topic: Real-time Endpoints for low-latency synchronous inference, Batch Transform for large offline datasets, Serverless Inference for infrequent workloads with cold-start tolerance, and Async Inference for large payloads with asynchronous response patterns.
For orchestration, SageMaker Pipelines provides ML-native workflow management, while Step Functions, CodePipeline, CodeBuild, and EventBridge cover broader CI/CD integration. SageMaker Model Registry sits at the handoff point between development and deployment, providing versioning and approval workflows.
D4: Monitoring, Maintenance, and Security (24%)
Once a model is in production, the work is not done. SageMaker Model Monitor detects data drift and model drift in real time. CloudWatch provides infrastructure-level metrics, while X-Ray traces requests through distributed systems.
Security topics include IAM least-privilege roles for SageMaker execution, KMS encryption for data at rest and in transit, VPC isolation for training and inference instances, PrivateLink for private connectivity to AWS services, and CloudTrail for audit logging. Cost optimization includes Managed Spot Training for up to 90% savings on training jobs, appropriate instance type selection, and SageMaker Savings Plans.
The SageMaker Ecosystem
The most important framing shift for MLA-C01 is understanding that SageMaker is not a single service. It is a platform with dozens of components, each addressing a specific stage in the ML lifecycle. Once you have the SageMaker map in your head, the four domains start to feel like four views of the same workflow rather than four separate topics.
| SageMaker Component | Domain | Primary Role | |--------------------|--------|-------------| | Data Wrangler | D1 | No-code data transformation and feature engineering | | Feature Store | D1 | Online and offline feature storage | | Processing | D1, D2 | Large-scale preprocessing jobs | | Built-in Algorithms | D2 | AWS-optimized algorithm containers | | JumpStart | D2 | Pre-trained models and ML solution templates | | Autopilot | D2 | AutoML pipeline generation | | Hyperparameter Tuner | D2 | Automated hyperparameter optimization | | Experiments | D2 | Experiment tracking and comparison | | Debugger | D2 | Tensor-level training analysis | | Clarify | D2, D4 | Bias detection and model explainability | | Model Registry | D3 | Model versioning and deployment approval | | Pipelines | D3 | ML workflow orchestration | | Real-time Endpoints | D3 | Synchronous low-latency inference | | Batch Transform | D3 | Offline batch inference | | Serverless Inference | D3 | Pay-per-use serverless inference | | Async Inference | D3 | Asynchronous large-payload inference | | Neo | D3 | Model compilation and optimization for target hardware | | Model Monitor | D4 | Production model quality monitoring |
Study Strategy by Background
Data scientists will find D2 comfortable but should invest time in D3 deployment infrastructure and D4 MLOps practices. Focus on the four inference endpoint types, SageMaker Pipelines vs Step Functions tradeoffs, and cost optimization with Spot Training.
Backend or DevOps engineers will be at home with D3 CI/CD topics and D4 security patterns. The investment should go into ML-specific services: Feature Store online vs offline semantics, Model Monitor's drift detection mechanisms, and Clarify's bias reports. Understanding what makes these tools different from generic data pipelines is the key.
Generalist AWS engineers who know the surrounding services (S3, Kinesis, Glue, Lambda, Step Functions) have an advantage in integration scenarios. Bridge the gap with ML fundamentals: when to choose XGBoost vs linear models vs deep learning, what hyperparameters actually control, and how evaluation metrics connect to business requirements.
Exam Tips
"Data drift vs model drift" -- Data drift is a change in input feature distributions. Model drift is degraded prediction quality for similar inputs. SageMaker Model Monitor detects both. "Choosing inference mode" -- Real-time for low latency, Async for large payloads, Serverless for sporadic traffic, Batch Transform for offline datasets. The scenario's traffic pattern and payload size guide the answer. "Feature Store: online vs offline" -- Online store serves millisecond-latency reads for real-time inference. Offline store backs batch training. Most production systems use both simultaneously. "Managed Spot Training" -- Up to 90% cost reduction. Requires checkpointing to S3 so interrupted jobs resume without full retraining. "SageMaker Pipelines vs Step Functions" -- Pipelines is ML-native with first-class SageMaker steps. Step Functions is broader and preferred when mixing SageMaker with Lambda, ECS, or other services in one workflow. "VPC isolation" -- Best practice is to place training and inference instances inside a VPC with no direct internet access, using PrivateLink for AWS service connectivity. "SageMaker Clarify scope" -- Pre-training data bias detection plus post-training model bias detection plus SHAP-based explainability reports in a single service. "SageMaker Neo use case" -- Model compilation and optimization for specific hardware targets, including edge devices. Appears in IoT and edge inference scenarios. "Multi-model Endpoint" -- Hosts multiple models behind one endpoint to reduce infrastructure costs. Best for models with similar memory footprints and non-simultaneous traffic. "Autopilot vs JumpStart" -- Autopilot runs AutoML to find the best model from your data. JumpStart provides pre-trained foundation models ready for fine-tuning or direct deployment.
Closing Thoughts
MLA-C01 is a practical certification that rewards engineers who have worked through real ML pipelines rather than those who have only studied ML theory. The preparation process is itself a useful exercise in mapping AWS services to the stages of a production ML system.
The most effective study approach is to trace a single ML project from raw data to monitored production deployment, identifying which AWS service handles each step and why. When you can walk through that workflow with confidence, the exam's scenario-based questions become much more approachable.
---
Domain Deep-Dive Series and Next Steps
With the big picture from this guide, continue with the deep-dive posts belo