Home › Certifications › AWS Certified Machine Learning Engineer MLA-C01 › ML Solution Monitoring, Maintenance, and Security
40 multiple-choice questions and 9 flashcards on ML Solution Monitoring, Maintenance, and Security, about 19% of the AWS Certified Machine Learning Engineer MLA-C01 bank. Every one carries a written rationale.
ML Solution Monitoring, Maintenance, and Security is one of 4 chapters in CoStudy's AWS Certified Machine Learning Engineer — Associate (MLA-C01) bank, and it holds 40 of the bank's 210 multiple-choice questions — roughly 19% of the total. That proportion is not arbitrary: chapters follow the certifying body's published exam outline, and the number of questions in each is set by that domain's published weight, so the share of your practice time this chapter takes matches the share of the real exam it accounts for.
Studying by chapter is worth doing once you have a diagnostic score. A single overall percentage tells you whether you are close; it does not tell you which domain is dragging. Working a weak chapter in isolation, and re-testing it in isolation, is the fastest way to move a score that has stalled — and it is why the mock exams in CoStudy report by domain rather than as one number.
5 questions drawn from this chapter, with the full rationale shown — the controlling principle behind the right answer, and why each wrong option tempts and fails.
Finance wants an automatic notification the moment monthly ML spend is forecasted to exceed a set dollar threshold, before the month even ends. Which service provides this?
Answer: A — AWS Budgets with a forecasted-spend alert
AWS Budgets supports forecasted-spend alerts that notify before the threshold is actually reached, not just after; Cost Explorer reports are backward-looking and require someone to check them; a manually run CUR isn't proactive; a CloudWatch billing dashboard without an alarm attached won't notify anyone.
A SageMaker execution role currently has AdministratorAccess so training jobs 'just work.' A security review flags this. What's the correct fix?
Answer: B — Scope the role to only the specific S3 buckets, KMS keys, and services the job needs
Least-privilege scoping to only the specific resources needed is the correct security fix; leaving Administrator access is the flagged problem, not a fix; PowerUserAccess is still far broader than needed; using the root account is a severe anti-pattern, never appropriate for a service role.
A company wants to guarantee that SageMaker training jobs can only read from an approved list of S3 buckets across the whole organization, even if an individual role is later misconfigured. Which control enforces this org-wide?
Answer: B — An AWS Organizations Service Control Policy (SCP) restricting S3 access
An SCP at the AWS Organizations level sets a hard boundary no account-level role can exceed, providing org-wide enforcement; per-role policies can still drift or be misconfigured individually; Model Monitor checks data distributions, not access control; a CloudWatch alarm only notifies after the fact, it doesn't prevent the access.
An endpoint's live input feature distributions must be compared against the training data distribution, alerting when they diverge beyond a threshold. Which SageMaker Model Monitor type is this?
Answer: B — Data Quality Monitor
Data Quality Monitor compares live input statistics to a training-data baseline; Model Quality needs ground-truth labels to score accuracy, not just input drift; Bias Drift tracks fairness metric changes; Feature Attribution Drift tracks SHAP-value shifts, not raw input distribution.
A team registers a new model version every week and needs old, superseded versions to remain available for audit and potential rollback without cluttering the 'latest' view. Which Model Registry practice supports this?
Answer: C — A single Model Package Group holding every versioned package, with status/version tracked per entry
A single Model Package Group accumulates every version with its own status and metadata, preserving history for audit/rollback while still surfacing the latest approved version; deleting old versions removes rollback ability; overwriting loses history entirely; a new unrelated group each week fragments lineage and makes rollback across groups awkward.
4 cards from the 9 in this chapter.
Cost optimization for SageMaker training?
Use Spot instances (up to 90% off), right-sized instances, managed warm pools, pipe mode to reduce I/O, distributed training when applicable.
Training/serving skew?
Online performance degrades because inference data or transformations differ from those used at training. Shared feature pipelines (Feature Store) mitigate.
Data card / model card?
Structured documentation of a dataset (or model) — intended use, composition, collection, biases, evaluation, limitations — supporting transparency and responsible AI.
SageMaker Clarify?
Detects bias (pre/post-training) + provides explainability (SHAP values).
These are a sample. The full ML Solution Monitoring, Maintenance, and Security chapter runs 49 items with per-chapter progress tracking, on the web and in the iOS app.
Open AWS Certified Machine Learning Engineer MLA-C01 in CoStudy →
All AWS Certified Machine Learning Engineer MLA-C01 practice questions →