AWS MLA-C01 30-, 60-, and 90-day study plan for ML pipelines, endpoints, drift, review loops, and final-week priorities.
This page answers the question most candidates actually have: “How do I structure my MLA-C01 prep?” Below are three realistic schedules built around the current official weighted domains and the new chapterized online guide for this exam.
Use the plan that matches your available time, then follow this loop: study chapter -> run a small experiment or deployment rep -> timed questions -> review misses -> re-drill the weak section.
Typical ranges based on background:
| Your starting point | Typical total study time | Best-fit timeline |
|---|---|---|
| You deploy SageMaker models and pipelines already | 40-60 hours | 30-60 days |
| You know ML but are newer to AWS or SageMaker | 60-90 hours | 60-90 days |
| You are newer to ML engineering and MLOps | 90-120+ hours | 90 days |
Choose a plan based on hours per week:
| Time you can commit | Recommended plan | What it feels like |
|---|---|---|
| 10-15 hrs/week | 30-day intensive | Fast learning plus lots of practice |
| 6-9 hrs/week | 60-day balanced | Steady progress plus room for review |
| 3-5 hrs/week | 90-day part-time | Slow and solid with repetition |
| Domain | Weight | What you should be good at |
|---|---|---|
| 1. Data Prep | 28% | ingest, transform, validate, label, and protect data for training |
| 2. Model Dev | 26% | choose, train, tune, evaluate, explain, and version models |
| 3. Deployment | 22% | endpoint selection, infrastructure, autoscaling, CI/CD, and rollback |
| 4. Operations | 24% | drift, observability, cost control, and security of live ML systems |
If you want one rule: spend roughly 60% learning and 40% practice early, then invert it to about 30% learning and 70% practice in the final one or two weeks.
Try to keep one small runnable ML workflow alive while you study. For MLA-C01, that baseline should include:
| If you are… | Use the plan like this |
|---|---|
| already comfortable with SageMaker | move faster through learning blocks and increase timed practice sooner |
| stronger in ML than AWS | spend more time on endpoint fit, monitoring, IAM, and deployment controls |
| stronger in AWS than ML | spend more time on metric choice, feature quality, drift, and model-behavior judgment |
| short on time | finish one complete pass of all four domains before chasing edge-case detail |
| Minutes | What to do | Why |
|---|---|---|
| 0-15 | review one lesson or section with the official task wording in mind | keeps the session tied to real exam scope |
| 15-30 | write or say aloud the key trade-off rules | turns passive reading into retrieval |
| 30-45 | do a small scenario drill or timed question set | exposes whether you can actually classify the situation |
| 45-60 | write miss rules and route the weakness to one chapter | makes the next session targeted instead of random |
Target pace: about 10-15 hours/week.
Goal: cover the official domains quickly, then harden instincts through drills and mixed sets.
| Week | Focus | What to do | Links |
|---|---|---|---|
| 1 | 1. Data Prep | Build strong ingest-to-features instincts: formats, storage, feature store, transformation, quality, and bias basics. | Resources • Cheat Sheet • Glossary |
| 2 | 2. Model Dev | Focus on model selection, built-in algorithms versus AI services, training and tuning, explainability, and experiment comparison. End with one 30-40 question mixed set. | Cheat Sheet • Glossary |
| 3 | 3. Deployment | Drill endpoint choices, containers, IaC, autoscaling, VPC hosting, CI/CD, retraining, and rollback. | Resources • FAQ |
| 4 | 4. Operations + review | Finish drift, infrastructure observability, cost tuning, IAM, VPC isolation, encryption, and compliance. Do 2 mixed sets plus 1 timed run (65Q / 130m). |
FAQ • Glossary |
Target pace: about 6-9 hours/week.
Goal: spaced repetition and deeper drills while steadily increasing practice volume.
| Weeks | Focus | What to do |
|---|---|---|
| 1-2 | 1. Data Prep | Drill ingest, formats, transformations, labeling, quality, bias, and readiness repeatedly. |
| 3-4 | 2. Model Dev | Work model selection, tuning, registry, metrics, explainability, and shadow comparisons. |
| 5-6 | 3. Deployment | Focus on deployment targets, autoscaling, VPC hosting, ML CI/CD, retraining, and rollback. |
| 7-8 | 4. Operations + final review | Drill drift, cost, rightsizing, IAM, encryption, and live-system security. Do 2 timed runs and re-drill the weakest sections. |
Target pace: about 3-5 hours/week.
Goal: slow repetition with consistent drills and periodic mixed sets.
| Weeks | Focus |
|---|---|
| 1-3 | 1. Data Prep |
| 4-6 | 2. Model Dev |
| 7-9 | 3. Deployment |
| 10-11 | 4. Operations |
| 12 | Final review plus timed runs |
Use spaced re-drills on weak sections. 48-72 hour spacing works well because the same ML engineering confusion often repeats unless you revisit it deliberately.
48-72 hours later until the same failure mode stops repeating.| Step | What to record |
|---|---|
| 1 | the weak domain: data prep, model development, deployment, or monitoring/security |
| 2 | the real failure mode: service fit, endpoint choice, metric choice, rollout safety, or control separation |
| 3 | the single rule you should have applied |
| 4 | the exact chapter or lesson to revisit next |
If your review log keeps producing the same miss rule, stop taking mixed sets for a session and rework that chapter directly.
If your exam is close and you are out of time, do this:
| Day | Focus |
|---|---|
| 7 | 1. Data Prep and 2. Model Dev weak spots only |
| 6 | 3. Deployment endpoint and rollback review |
| 5 | 4. Operations drift, cost, IAM, and VPC review |
| 4 | One mixed timed set and a miss log |
| 3 | Re-drill only repeated miss patterns |
| 2 | One final timed run at lighter intensity |
| 1 | Cheat sheet, glossary, and short recall only; no heavy new topics |
| Weak domain | Fix approach |
|---|---|
| Data Preparation | Rebuild storage-format, feature-store, and labeling instincts before more timed sets |
| Model Development | Rework model-family choice, tuning loop, and metric selection with short scenario drills |
| Deployment | Re-drill endpoint type, autoscaling, registry, retraining, and rollback choices |
| Monitoring and Security | Re-separate drift, infra signals, IAM, VPC, encryption, and secrets until they stop blurring together |
Before you sit the exam, you should be able to: