Explain
Choose among data, training, inference, orchestration, monitoring, security, and generative-AI patterns from constraints rather than product-name recall.
Build decision-making skill across the complete AWS ML lifecycle: trustworthy data, reproducible development, safe delivery, observable operations, secure generative and agentic systems, and responsible AI.
Choose among data, training, inference, orchestration, monitoring, security, and generative-AI patterns from constraints rather than product-name recall.
Produce two reproducible systems: one conventional production-ML workload and one evidence-grounded, bounded agentic workflow.
Demonstrate quality gates, least privilege, observability, cost boundaries, canary release, rollback, incident response, and cleanup.
Use the sequence as a default, not a promise of required preparation time. Adjust after a diagnostic and preserve at least one review cycle. Each week ends with evidence, not hours watched.
Week 1 - Data contracts and leakage
Evidence: Versioned synthetic dataset, data contract, leakage tests, and feature parity test.
Week 2 - Development and evaluation
Evidence: Baseline comparison with immutable data, code, image, parameters, metrics, and artifacts.
Week 3 - Orchestration
Evidence: One clean pipeline run plus a deliberately failing candidate blocked from promotion.
Week 4 - Deployment
Evidence: Decision matrix, canary exercise, alarm proof, and measured rollback.
Week 5 - Monitoring and security
Evidence: Four injected failures with distinct alerts and responses, plus denied-access tests.
Week 6 - Generative AI and RAG
Evidence: RAG report separating retrieval failures from unsupported generation.
Week 7 - Agentic AI and LLMOps
Evidence: Read-only agent with trajectory evaluation, kill switch, release manifest, and rollback.
Week 8 - Synthesis
Evidence: Updated objective checklist, error log with remediations, and two sanitized portfolio walkthroughs.
| Workload signal | Start with | Validate before choosing | Common trap |
|---|---|---|---|
| Low-latency synchronous traffic with steady or controllable demand | Real-time endpoint | Load, p95/p99 latency, auto scaling, availability, and instance cost | Provisioning from average traffic only |
| Intermittent synchronous traffic and tolerable cold starts | Serverless Inference | Supported features, memory, concurrency, cold-start behavior, payload, and regional availability | Assuming serverless fits every model or latency target |
| Long-running requests or larger payload patterns with deferred results | Asynchronous Inference | Queueing, result delivery, timeout, retry, scaling-to-zero behavior, and client contract | Using it when the caller requires an immediate response |
| Scheduled or one-time scoring of a bounded dataset | Batch Transform | Input partitioning, throughput, output reconciliation, job completion objective, and temporary compute cost | Paying for an always-on endpoint with no online caller |
Do not use a single practice percentage as proof of readiness. Ask whether you can do the following without relying on answer-pattern memory:
Source links were reviewed on 2026-09-11. Product behavior, availability, and URLs can change.