Home / artificial-intelligence-machine-learning / AWS Certified Machine Learning Engineer - Associate (MLA-C02) / Cheat Sheet
AWS Certified Machine Learning Engineer - Associate (MLA-C02)

MLA-C02 Cheat Sheet

MLA-C02 Tests Running ML and FM Workloads in Production — Not Data Science Theory

MLA-C02 has been in English-only beta since 29 September 2026, with general availability expected in early 2027. It rewards managed, automated and reversible SageMaker AI and Bedrock choices over custom code.

Check Your Readiness →
Among the harder certs
Avg: Not published by Amazon Web Services
Pass: 750 / 1000
Most candidates understand AWS Certified Machine Learning Engineer - Associate (MLA-C02) concepts — and still fail. This exam tests how you apply knowledge under pressure.

MLA-C02 Domain Map (beta exam guide)

C02 brings AI and foundation models into every domain name and moves weights from 28/26/22/24 to 28/24/24/24. Scenarios give traffic, payload, latency and compliance constraints; answers with built-in rollback, registries and infrastructure as code beat one-off scripts.

  1. 01
    Data Preparation for ML and AI (28%) — ingestion, Glue vs. DataBrew vs. Data Wrangler, Feature Store, imbalance, chunking
  2. 02
    ML Model and FM Development (24%) — algorithm choice, FM customization, tuning, training speedups, evaluation metrics
  3. 03
    Deployment and Orchestration of ML and AI Workflows (24%) — SageMaker AI inference options, Bedrock capacity, Pipelines, Model Registry
  4. 04
    Operating, Monitoring and Securing ML and AI Solutions (24%) — Model Monitor types, cost controls, VPC isolation, IAM over API keys

Wrong instinct vs correct approach

A model's validation loss rises while its training loss keeps falling
✕ Wrong instinct

Add layers so the model can learn more

✓ Correct approach

That pattern is overfitting. Apply early stopping, regularization, dropout or more training data; extra capacity makes it worse. Tune with Bayesian search in SageMaker AI automatic model tuning rather than an exhaustive grid.

An internal knowledge assistant must reflect policy documents that change every week
✕ Wrong instinct

Fine-tune the Bedrock model weekly on the new documents

✓ Correct approach

Fine-tuned weights capture a snapshot. Use Bedrock Knowledge Bases for RAG and start ingestion sync automatically when S3 documents change, for example through EventBridge. Fine-tune to change task behavior; distill to cut cost and latency.

A team must read invoices and extract totals, dates and vendor names
✕ Wrong instinct

Train a custom OCR model in SageMaker AI

✓ Correct approach

Amazon Textract already extracts text, forms and tables, including expense documents. Use the managed AI service first and reserve custom training for requirements Textract cannot meet.

A SageMaker AI endpoint processing regulated data must have no path to the internet
✕ Wrong instinct

Restrict who can invoke it with IAM policies

✓ Correct approach

IAM controls who calls the endpoint, not where traffic goes. Deploy in a VPC with private subnets, enable network isolation for the container, and reach SageMaker AI and S3 through VPC endpoints.

A production app embeds a long-term Bedrock API key and auditors flag it
✕ Wrong instinct

Rotate the API key manually every quarter

✓ Correct approach

Bedrock API keys suit quick starts and exploration. Production workloads should call Bedrock with IAM roles, which provide temporary credentials, least-privilege scoping and CloudTrail attribution without keys stored in code.

Know these cold

  • ▸ Real-time for steady low latency, serverless for spiky traffic, async for big payloads, batch transform for datasets
  • ▸ Model quality monitoring needs ground truth; data quality and drift monitors do not
  • ▸ Split first, then resample; SMOTE before splitting leaks synthetic rows into the test set
  • ▸ Online store serves inference in milliseconds; offline store in S3 serves training and batch
  • ▸ Data parallel for huge datasets; model parallel when the model will not fit one GPU
  • ▸ Bedrock on-demand for variable load, batch for bulk jobs, provisioned throughput for steady volume
  • ▸ Model Registry approval gates deployment; SageMaker Pipelines trains and evaluates, CodePipeline promotes
  • ▸ Use managed Spot training with checkpoints; never put live inference on reclaimable Spot capacity
  • ▸ AWS Config proves endpoints stayed in a VPC; CloudTrail only shows who changed them
  • ▸ Guardrails filter content, not identity; who may call a model is an IAM decision

Can you answer these without checking your notes?

In this scenario: "A model's validation loss rises while its training loss keeps falling" — what should you do first?
That pattern is overfitting. Apply early stopping, regularization, dropout or more training data; extra capacity makes it worse. Tune with Bayesian search in SageMaker AI automatic model tuning rather than an exhaustive grid.
In this scenario: "An internal knowledge assistant must reflect policy documents that change every week" — what should you do first?
Fine-tuned weights capture a snapshot. Use Bedrock Knowledge Bases for RAG and start ingestion sync automatically when S3 documents change, for example through EventBridge. Fine-tune to change task behavior; distill to cut cost and latency.
In this scenario: "A team must read invoices and extract totals, dates and vendor names" — what should you do first?
Amazon Textract already extracts text, forms and tables, including expense documents. Use the managed AI service first and reserve custom training for requirements Textract cannot meet.

Common Exam Mistakes — What candidates get wrong

Studying the MLA-C01 outline for the C02 exam

C01 ended in English on 28 September 2026. C02 shifts weight from model development (26% to 24%) to deployment and orchestration (22% to 24%) and adds Bedrock customization and capacity choices, knowledge bases and FM access security.

Using asynchronous inference to score a whole dataset each night

Asynchronous inference queues individual large or slow requests against a running endpoint. Batch transform scores a complete S3 dataset with no persistent endpoint. Serverless inference fits spiky traffic that tolerates cold starts; real-time endpoints bill while idle.

Applying SMOTE before splitting training and test data

Synthetic minority samples leak into the test set and inflate metrics. Do a stratified split first, then oversample, undersample or set class weights on the training split only. Keep outliers in fraud data, where they are often the signal.

Scheduling model quality monitoring when ground truth labels never arrive

Model Monitor model quality jobs merge predictions with ground truth labels. Without labels, run data quality monitoring against a baseline, Clarify-based bias drift and SHAP-based feature attribution drift. CloudWatch invocation metrics never reveal accuracy loss.

Reading the Feature Store offline store from a real-time endpoint

The offline store sits in S3 for training and batch scoring; millisecond inference lookups use the online store. Data Wrangler exports features to Feature Store or Pipelines, while Glue DataBrew suits analysts preparing data without Spark.

Resources to help you pass AWS ML Engineer - Associate on your first attempt

MLA-C02 rewards managed, reversible ML operations. Check your readiness for the new C02 scope.