How Long Does It Take to Prepare for the AWS Machine Learning Engineer Associate (MLA-C02) Exam?
AWS ML Engineer Associate · Study Planning

How Long Does It Take to Prepare for the AWS Machine Learning Engineer Associate (MLA-C02) Exam?

Most candidates need 10 to 12 weeks of part-time study, roughly 80 to 90 hours, to pass the AWS Certified Machine Learning Engineer Associate (MLA-C02) exam. Engineers who already ship models on Amazon SageMaker AI and build on Amazon Bedrock often need 4 to 6 weeks. Arriving ready for MLA-C01, plan 3 to 5 weeks to close the generative AI gap.

Last updated September 2026.

Which exam you sit depends on your test date

The updated exam is in beta, and in English the beta and the outgoing exam do not overlap by a single day. Registration for the beta, exam code ME1-C02, opened on September 1, 2026, and beta delivery starts on September 29, 2026. The last day to take MLA-C01 in English is September 28, 2026. The beta is English only, and the standard MLA-C02 exam is expected in all four exam languages in early 2027.

So the calendar decides: if you are not booked and ready for MLA-C01 by September 28, you are studying for MLA-C02, and everything below is written for that case.

The rule of thumb: a plan that runs past September 28, 2026 is an MLA-C02 plan. Do not squeeze ten weeks into three to beat the cutoff.

The changeover dates are from the comparison page of the official MLA-C02 exam guide; the beta code and language availability are from the AWS Training and Certification announcement. The outgoing exam's timeline is in the MLA-C01 study-plan post.

Pick your timeline by starting point

4 to 6 wk
You ship both. Training and deploying on SageMaker AI and building on Bedrock are already part of your week.
10 to 12 wk
One toolchain, not two. Data engineer, backend developer, or data scientist with SageMaker AI or Bedrock exposure, not both. The typical case.
14 to 16 wk
New to SageMaker AI and Bedrock. Traditional ML tooling and the generative AI stack at once, two curves rather than one.

These assume 7 to 8 hours a week. The exam guide describes its target candidate as someone with at least one year of experience using Amazon SageMaker AI, Amazon Bedrock, and other AWS services for ML engineering, plus at least one year in a related role (backend developer, DevOps developer, data engineer, or data scientist), with experience in both traditional ML and generative AI. It expects two toolchains, and most adjacent-role candidates arrive with one, which is why MLA-C02 takes longer than MLA-C01.

The target candidate description is from the official MLA-C02 exam guide. It describes who the exam is written for, not an entry requirement. The timelines are our own estimates.

Four domains, almost even, and every one now carries AI

MLA-C02 keeps four content domains and spreads its 50 scored questions across them at 28%, 24%, 24%, and 24%. The largest domain is four points ahead of the other three, about two scored questions.

DomainWeightScored questionsOf an 85-hour plan
1. Data Preparation for ML and AI28%About 14About 24 hours
2. ML Model and Foundation Model (FM) Development24%About 12About 20 hours
3. Deployment and Orchestration of ML and AI Workflows24%About 12About 20 hours
4. Operating, Monitoring, and Securing ML and AI Solutions24%About 12About 20 hours

Domain titles and weights from the official MLA-C02 exam guide, applied to 50 scored questions and rounded.

Two things changed from MLA-C01, which ran 28 / 26 / 22 / 24: model development gave two points to deployment and orchestration, and AWS added generative AI, agentic AI, and foundation model workloads without adding a domain. The guide's comparison page maps all twelve MLA-C01 task statements onto the twelve MLA-C02 tasks one to one, so the new material is new skills inside tasks you already knew. That is the planning headline: there is no separate GenAI week to bolt onto an MLA-C01 plan, because the additions sit in every domain you were already studying.

What the update actually adds

MLA-C01 validated implementing, deploying, and maintaining ML solutions. MLA-C02 validates building, operationalizing, deploying, and maintaining AI and ML solutions, for traditional models and foundation models alike. The comparison page lists the added skills task by task; these are the ones that reshape a plan:

A few MLA-C01 items were removed: loading training data from EFS and FSx, model size reduction, edge optimization with SageMaker Neo, bring your own container, and two infrastructure monitoring statements. The format keeps its shape: 65 questions, 50 scored and 15 unscored, a passing score of 720, and compensatory scoring, one overall total with no per-domain minimum.

Additions and deletions from the Comparison of MLA-C01 and MLA-C02 page of the official exam guide. Format and scoring from the guide itself.

A concrete 11-week plan (the typical case)

Weeks 1 to 3
Data preparation, the largest domain. Ingestion and storage, transformation and feature engineering, formats and labeling, class imbalance and bias, across S3, AWS Glue, Amazon EMR, Athena, and SageMaker AI Data Wrangler and Feature Store. Then the Domain 1 additions above: vector databases, embeddings, chunking for RAG, and data for fine-tuning.
Weeks 4 to 5
Model development, now including foundation models. Built-in algorithms versus pre-trained versus custom training, tuning, overfitting and underfitting, and reading metrics. Then FM selection, fine-tuning strategies, RAG patterns, and the generative evaluation toolkit, with MLflow on SageMaker AI and Bedrock evaluations for reproducible experiments.
Weeks 6 to 7
Deployment and orchestration, now including agents. Endpoint types and inference options, scaling, infrastructure as code, CI/CD, and SageMaker Pipelines. Then FM deployment options, Bedrock knowledge bases, agents and agent state, Prompt Management, and the agent and knowledge base pipelines. This domain gained weight, so give it the full two weeks.
Weeks 8 to 9
Monitoring, maintenance, security, and responsible AI. Drift detection, A/B testing, CloudWatch, instance and purchasing choices, IAM, and VPC isolation. Then generative AI observability, agent and token cost monitoring, credential types for FMs, and Bedrock Guardrails.
Week 10
Build two things end to end. One classic: train, register, deploy, and monitor a model on SageMaker AI. One generative: a Bedrock knowledge base with an agent in front of it, deployed, guarded, and monitored. Recognition comes from having done it.
Week 11
Drill and book. Work scenario questions across all four domains, re-read the task statements behind your weakest, and book a beta slot on or after September 29, 2026.

Compress or stretch: shipping on both SageMaker AI and Bedrock already? Fold Weeks 1 to 9 into four weeks of targeted review and keep Weeks 10 and 11 intact. New to both toolchains? Add a week to each of the first four blocks.

Already MLA-C01 ready? Close the gap in 3 to 5 weeks

If the cutoff caught you, the weights say where the extra weeks go. Deployment and orchestration gained the two points model development lost, and the new material (RAG deployment, agent orchestration, Bedrock at scale) lands hardest there. Start with it, not with prompt theory, then add the Week 10 build and a full drill if you have the time.

The trap is that the additions are spread across all four domains rather than parked in one. Skip them and you lose two or three questions in each domain, which looks like noise on a practice exam until it adds up to the gap between 700 and 720.

What makes it take longer

Coming from a Databricks background instead? The Databricks Generative AI Engineer Associate timeline is the closest reference point for how the generative half of this exam will feel.

The cheapest hours in the plan

Reading the task statements, the comparison page, and the in-scope services list in the MLA-C02 exam guide takes an evening and is free. Questions are written from those statements, the comparison page lists every added and removed skill, and the in-scope list is where you learn that Amazon Bedrock AgentCore is on it. For a beta with no settled third-party material, it is the blind-spot audit that matters most.

FAQ

How long does it take to prepare for the AWS Machine Learning Engineer Associate (MLA-C02) exam?

Most candidates need 10 to 12 weeks of part-time study, roughly 80 to 90 hours. Engineers already shipping on both SageMaker AI and Bedrock often need 4 to 6 weeks, and someone who was ready for MLA-C01 can usually close the generative AI gap in 3 to 5 weeks.

Should I take MLA-C01 now or the MLA-C02 beta?

If you are booked and ready before September 28, 2026, take MLA-C01, since it is the last day the exam is offered in English. Otherwise plan for MLA-C02: beta delivery starts September 29, 2026 in English only, and the standard version in all four languages is expected in early 2027.

How many hours of study does MLA-C02 need?

Plan for 80 to 90 hours in the typical case, about 7 to 8 hours a week across 10 to 12 weeks. Roughly 24 of those hours belong to data preparation, the 28% domain, and about 20 to each of the other three, which are 24% apiece.

Do I need Amazon Bedrock experience for MLA-C02?

The exam guide describes its target candidate as having at least one year with both Amazon SageMaker AI and Amazon Bedrock, across traditional ML and generative AI. That is a recommendation, not a requirement, but the additions in MLA-C02 (generative AI, agentic AI, foundation models) are where hands-on Bedrock time pays off most.

Is the MLA-C02 beta available in languages other than English?

No. The beta exam, code ME1-C02, is offered in English only. The standard MLA-C02 exam is expected in all four exam languages in early 2027.

Read the official MLA-C02 exam guide

The guide lists the task statements under all four domains, the in-scope services, and a skill-by-skill comparison with MLA-C01. Build your plan from it, not from MLA-C01 notes.

Open the AWS exam guide →