CertNote/ Commute Study Notes
Roadmap
KOEN
CLF-C02 · FoundationalCloud Practitioner - Foundational
DVA-C02 · AssociateDeveloper - Associate
SAA-C03 · AssociateSolutions Architect - Associate
SOA-C02 · AssociateCloudOps Engineer - Associate
SAP-C02 · ProfessionalSolutions Architect - Professional
DOP-C02 · ProfessionalDevOps Engineer - Professional
Linux Master 2 · 2급KAIT Linux Master - Level 2
SCS-C03 · SpecialtySecurity - Specialty
Linux Master 1 · 1급KAIT Linux Master - Level 1
MLA-C01 · AssociateMachine Learning Engineer - Associate
  • Week 1
    • 1.The ML Lifecycle and the Role of the ML Engineer
    • 2.ML Problem Types and Evaluation Metric Basics
    • 3.AWS ML Stack at a Glance
    • 4.SageMaker Overview: Studio, Training/Inference, Built-in Algorithms
    • 5.Week 1 Comprehensive Review — ML Fundamentals & AWS Stack
  • Week 2
  • Week 3
  • Week 4
  • Week 5
  • Week 6
  • Week 7
  • Week 8
  • Week 9
  • Week 10
    • 1.Domains 1 and 2 Integrated Review: Data Preparation + Model Development
    • 2.Domains 3 & 4 Integrated Review: Deployment & Orchestration + Monitoring & Security
    • 3.Full Mock Exam Pace: A Final Check with the 4-Domain Service Map and Decision Trees
    • 4.Commonly Missed Traps and Keywords: A "Requirement → SageMaker Feature" Translation Table
    • 5.D-Day Wrap-Up: Exam Structure, Time Management, and Scenario Decomposition Strategy
AIF-C01 · FoundationalAI Practitioner - Foundational
DEA-C01 · AssociateData Engineer - Associate
MLS-C01 · SpecialtyMachine Learning - Specialty
SQLD · 개발자SQL Developer (SQLD)

© CertNote · 주간랩스

  • About
  • Changelog
  • Contact
  • Terms
  • Privacy
← MLA-C01/Week 10/Day 3

Based on the MLA-C01 exam guide·Report an error

MLA-C01· AssociateWeek 10 · Day 3~32 min read

Day 3 - Full Mock Exam Pace: A Final Check with the 4-Domain Service Map and Decision Trees

📌 Key Takeaways

  • The real exam does not tell you which domain a question belongs to. A single sentence has 2-3 condition keywords from several domains embedded in it.
  • 65 questions / 130 minutes = an average of 2 minutes per question. The goal is to solve today's 8 questions within 16 minutes.
  • The solving order is fixed: question sentence → extract condition keywords → think of the answer before looking at the options → eliminate options that violate a requirement.
  • When there are multiple conditions, only the option that satisfies all conditions at the same time is correct. If it breaks even one, it is wrong no matter how plausible it looks.
  • For a question you got wrong, review is not finished by memorizing the answer; you must be able to say why the other options were traps.

How to Use the Mock Exam

Today we cut back on concept explanations and solve integrated scenarios mixing the 4 domains at the same pace as the real exam. Solve the 8 questions below within 16 minutes if possible, and before looking at the answer, it is good to first say out loud "which domain is this question, and what is the keyword that decides the answer?"

StepWhat to doTime
First passGo through all 8 questions without stopping16 min
Before self-gradingWrite down each question's domain and deciding keyword4 min
Grading and reviewFor wrong answers, explain "why the other options were wrong"No limit

💡 Related theory: An integrated question usually has 2-3 "condition keywords" embedded in one sentence. Example: "hundreds of same-type models (→ MME candidate)" + "invoked occasionally (→ cost savings reinforced)" + "same framework (→ MME confirmed)". If you separate the keywords, map each to a feature, and then choose the option that satisfies all the keywords at the same time, you can filter out trap options.

A Service Map Across All 4 Domains

As you read a question, first pinpoint "which cell of this map are we in now," and many of the options are eliminated immediately.

 Ingestion     Storage      Preparation   Training      Tuning
 ─────         ─────        ─────         ─────         ─────
 Kinesis  ─▶   S3      ─▶  Data Wrangler ─▶ Training Job ─▶ AMT
 Firehose      Glue        Processing Job   Built-in/Custom Bayesian
 Ground Truth  Catalog     Glue ETL/EMR     File·Pipe      Random·Grid
 (labeling)                Athena(query)    FastFile       Hyperband
                          Feature Store     Spot+checkpoint
                          Clarify(pre-training bias)  Debugger
                                                  │
   ┌──────────────────────────────────────────────┘
   ▼
 Evaluation    Deployment                  Monitoring            Security
 ─────         ─────                       ──────────            ─────
 Choose metric ─▶ Model Registry(version·approval) ─▶ Data capture ─▶ IAM (least privilege)
 Accuracy/F1   Real-time · Serverless      Model Monitor        VPC (endpoints·isolation)
 AUC · RMSE    Async · Batch Transform     ├ Data Quality       KMS (encryption at rest)
 Clarify       MME · MCE · Inference Pipeline ├ Model Quality   TLS (encryption in transit)
 (post-training bias) Variant weights (A/B) ├ Bias Drift        CloudTrail(audit)
               Pipelines · EventBridge     └ Attribution Drift  CloudWatch(metrics)
                                                    │
                                            CloudWatch alarm ─▶ retraining trigger

Quick Keyword Reference by Domain

Domain 1 - Data Preparation (28%)

KeywordCorrect feature
Real-time stream ingestionKinesis Data Streams / Firehose
Bulk loading into a data lakeS3
Serverless ETL, schema catalogGlue / Glue Data Catalog
Visual cleaning without codeData Wrangler
Run my own preprocessing script as a managed jobProcessing Job
SQL queries without moving S3 dataAthena
Humans must attach labelsGround Truth
Training-inference feature consistency and reuseFeature Store
Bias check before deployment / explaining feature contributionClarify (SHAP)
Handling class imbalanceResampling, class weights

Domain 2 - Model Development (26%)

KeywordCorrect feature
Demand for the next N days, multiple related time seriesDeepAR
Unlabeled outliers, stream anomaliesRandom Cut Forest
Structured table classification/regressionXGBoost, Linear Learner
Grouping without labelsK-Means
Too many featuresPCA
Sparse user x item recommendationFactorization Machines
Document classification, word embeddingsBlazingText
Efficient tuning with few trialsBayesian
Early stopping of hopeless trainingHyperband
Training data larger than the diskPipe / Fast File mode
I/O bottleneck from repeated reads every epochFSx for Lustre
Reduce training cost (interruption allowed)Managed Spot + checkpoints
Diagnosing bottlenecks and overfitting during trainingDebugger

Domain 3 - Deployment and Orchestration (22%)

KeywordCorrect feature
Steady traffic, immediate responseReal-time endpoint
Intermittent traffic, scale to zero, cold start acceptableServerless inference
Large payload, long processing, individual requestsAsynchronous inference
Bulk scoring of an entire datasetBatch Transform
Hundreds to thousands of same-type modelsMME
A few models with different frameworksMCE
Apply the same preprocessing to inference as wellInference pipeline
A/B testing, gradual migrationProduction variant weights
ML workflow DAG, CI/CDSageMaker Pipelines
Register only when criteria are metConditionStep + Model Registry
Retrain when new data arrivesEventBridge → Pipeline
Reduce deep learning inference unit costInferentia

Domain 4 - Monitoring and Security (24%)

KeywordCorrect feature
Whether the input distribution changedModel Monitor (Data Quality)
Whether performance against the truth droppedModel Monitor (Model Quality) + ground truth
Bias change in productionBias Drift (Clarify integration)
Feature contribution change in productionFeature Attribution Drift
Access S3 and ECR without the internetVPC endpoints (Gateway/Interface)
Block container outbound communicationEnableNetworkIsolation
Encrypt data at restKMS
Encrypt data in transitTLS
Who called which APICloudTrail
Latency and error-rate alarmsCloudWatch
Model documentation and governanceModel Cards
Data → training → model lineageLineage Tracking
A role with excessive permissionsIAM least privilege

Three Frequently Used Decision Trees

[1) Inference options]
  Need an immediate response? ──No──▶ Bulk over the whole dataset? ──Yes──▶ Batch Transform
        │Yes                        └No (individual, large, long) ──▶ Asynchronous
        ▼
  Steady traffic? ──Yes──▶ Real-time (minimum 1 instance, cannot scale to 0)
        └No ──▶ Cold start acceptable? ──Yes──▶ Serverless
                                    └No ──▶ Real-time + auto scaling
 
[2) Algorithm]
  Are there labels? ──No──▶ Looking for outliers? ──Yes──▶ RCF
        │Yes                    └No ──▶ Grouping K-Means / dimensionality reduction PCA
        ▼
  Is the time axis central? ──Yes──▶ DeepAR
        └No ──▶ What is the data?
                      ├ Table ──▶ XGBoost / Linear Learner
                      ├ Text     ──▶ BlazingText
                      ├ Image     ──▶ Image Classification / Object Detection
                      └ Sparse interactions ──▶ Factorization Machines
 
[3) Evaluation metric]
  Classification? ──No──▶ Regression: RMSE (sensitive to large errors) / MAE (dampens outliers) / R²
     │Yes
     ▼
  Imbalanced? ──No──▶ Accuracy is OK
     │Yes
     ▼
  Is the cost of a miss high? ──Yes──▶ Recall
     └No ──▶ Is the cost of a false alarm high? ──Yes──▶ Precision
                            └No ──▶ F1 / AUC-ROC

Reading Superlative Qualifiers

When a sentence has several conditions, what decides at the end is usually the qualifier.

QualifierComparison axisAnswer direction
MOST cost-effectiveCostMME, serverless, batch, Spot, Inferentia
LEAST operational overheadOperational burdenManaged and serverless services (Glue, Pipelines, serverless inference)
MOST secureSecurityVPC endpoints + network isolation + KMS + least privilege
LEAST latencyLatencyReal-time endpoint, Feature Store online, caching
FASTEST to implementImplementation speedBuilt-in algorithms, Data Wrangler, managed features
MINIMUM code changesCode changesKeep the existing setup + solve with configuration changes

⚠️ Trap: Several options technically all work. The superlative qualifier is the only criterion that narrows the answer to one. An option that breaks the performance or availability requirement while "reducing cost" (scaling real-time to zero, discarding data, using a GPU for XGBoost) is wrong even if the cost goes down. Conversely, for "reduce operational burden," an option that builds directly on EC2 is wrong even if it works.

Practice Decomposing Compound Conditions

This is an example not of the question format but of the habit of decomposing conditions. Follow with your eyes which cell each condition goes to.

Case A - "There are 2,000 per-store XGBoost models across the country, and each is invoked only a few times a day. Minimize cost."

Condition fragmentTranslation
2,000 modelsMany models → MME candidate
All XGBoostSame framework → MME confirmed (MCE eliminated)
Invoked only a few times a dayLow frequency → sharing instances is advantageous
Minimize costQualifier = cost

Case B - "You train on regulated data. It must not pass through the internet, the container must not send data outside, and data at rest must be encrypted."

Condition fragmentTranslation
No internet traversalVPC endpoints (Gateway for S3, Interface for ECR)
Block outbound communicationEnableNetworkIsolation
Encryption at restKMS
3 conditions at onceOnly an option containing all three is correct

Case C - "A real-time fraud detection model has been deployed. Monitor whether accuracy drops over time, and retrain automatically if it does."

Condition fragmentTranslation
Whether accuracy dropsModel Quality monitor
Prerequisite for computing accuracyNeed to collect ground truth labels
Automatic retrainingCloudWatch alarm → EventBridge → Pipeline
Real-time fraudImbalanced, so the metric is not Accuracy

When the conditions span two domains as monitoring + automation, as in Case C, one of the options usually does "monitoring only" and another does "automation only." The option that contains both is the answer. Conversely, an option that adds a lot of features when there is only one condition is over-engineered and loses under the "LEAST operational overhead" criterion. Matching the number of conditions against the number of components in each option is also a quick elimination method.

Wrong-Answer Patterns: Symptom → Cause → Fix

Symptom (how people tend to get it wrong)CauseFix
Chose Accuracy for imbalanced dataReflexive reaction to the word "accuracy"Build the habit of first finding the sentence with the data ratio
Chose the option that scales a real-time endpoint to 0Forgot the real-time minimum of 1 instanceScaling to 0 is only for serverless, asynchronous, and batch
Chose Batch Transform for individual requestsJudged only by payload size"Individual requests" means asynchronous, "entire dataset" means batch
Chose KMS for a network requirementSimple association of security = encryptionFor network use VPC endpoints and isolation; for storage use KMS
Chose CloudWatch for an audit questionConfused because both are "logs""Who" is CloudTrail; "how slow and when" is CloudWatch
Chose a regression algorithm for a time seriesAssociation of forecasting = regressionIf the time axis is central, DeepAR
Chose a technically workable option and it was wrongDid not read the superlative qualifierUnderline the qualifier in the last line of the question
Chose an option that satisfies only 2 of 3 conditionsDid not count the conditions to the endCount the conditions and check each option

Now it is time for the real thing. Solve 8 questions. Tomorrow we reorganize these wrong-answer patterns by trap type.

📖 Glossary

  • Integrated scenario question: A case-style question in which conditions from several domains are mixed into one question. It is the mainstream format on the real exam.
  • Condition keyword: A decisive word that separates the answer (intermittent, bulk, imbalanced, time series, drift, internet blocked, and so on). Extract these first from the question.
  • Superlative qualifier: An expression that specifies the comparison criterion, such as MOST cost-effective or LEAST operational overhead. When several options all work, it narrows the answer to one.
  • Elimination method: A solving approach that reduces candidates by crossing out options that violate even one requirement. The more conditions, the more powerful it is.
  • Over-engineered option: An option that presents a much more complex setup than the requirement. It tends to be wrong in questions based on operational burden.
  • Scale to zero: Bringing instances down to 0 when there are no requests, eliminating cost. Possible only for serverless, asynchronous, and batch, not real-time.
  • Ground truth: The actual outcome label used to judge whether a prediction was correct. Without it, Model Quality monitoring cannot work.
  • Pace: The time budget of an average of 2 minutes per question. The discipline of guessing, marking, and moving on when stuck keeps the pace.

📝 Practice Questions

Click a choice to reveal the answer and explanation.

Question 1

A fintech company wants to detect credit card fraud in real time. 99.7% of transactions are legitimate, and the cost of missing fraud is very high. Which evaluation metric should take priority?

Question 2

There are per-store demand forecasting XGBoost models for 2,000 stores nationwide. Each model is invoked only a few times a day, and the cost of 2,000 endpoints is a burden. What is the most cost-effective deployment?

Question 3

A medical imaging model receives a 250 MB image per individual request and runs inference for about 8 minutes, and the result is retrieved from S3 after completion. What is the most appropriate inference option?

Question 4

You train on regulated data, and the training container must access S3 and ECR without going through the internet and must block data exfiltration to the outside. What is the most appropriate setup?

Question 5

A data scientist wants to visually explore and clean an S3 dataset with almost no code, apply missing-value imputation and encoding, and then export that flow into a training pipeline. What is the most appropriate tool?

Question 6

You want to monitor whether the prediction accuracy of a production model drops over time (against the actual truth). What setup is needed?

Question 7

You want to forecast demand for the next 30 days from multivariate time series sales data. Which SageMaker built-in algorithm is best suited to learning the patterns of multiple related time series together?

Question 8

Whenever new training data arrives in S3, you want to automatically perform retrain → evaluate → (if criteria are met) register, and manage model versions and approval status. What is the most appropriate combination?

PreviousDomains 3 & 4 Integrated Review: Deployment & Orchestration + Monitoring & SecurityWeek 10 · Day 2Next Commonly Missed Traps and Keywords: A "Requirement → SageMaker Feature" Translation TableWeek 10 · Day 4

Official references

  • MLA-C01 official exam page(opens in a new tab)
  • Amazon S3 documentation(opens in a new tab)
  • Amazon VPC documentation(opens in a new tab)
  • AWS KMS documentation(opens in a new tab)
  • Amazon EventBridge documentation(opens in a new tab)
  • Amazon CloudWatch documentation(opens in a new tab)

On this page

  • Key Takeaways
  • How to Use the Mock Exam
  • A Service Map Across All 4 Domains
  • Quick Keyword Reference by Domain
  • Domain 1 - Data Preparation (28%)
  • Domain 2 - Model Development (26%)
  • Domain 3 - Deployment and Orchestration (22%)
  • Domain 4 - Monitoring and Security (24%)
  • Three Frequently Used Decision Trees
  • Reading Superlative Qualifiers
  • Practice Decomposing Compound Conditions
  • Wrong-Answer Patterns: Symptom → Cause → Fix
  • Glossary
  • Practice Questions