Study guide
7.7 AWS AI Service Selection Case Lab
AWS AI Practitioner Study Guide Exam
Track your progress as you read
Finished sections get a check mark.
1 Chapter 1: AIF-C01 Orientation and Official Source Control
1.1 Credential Scope, Code, and Search Language 1.2 Exam Format, Cost, Score, and Delivery 1.3 Official Exam Guide, Skill Builder, and Practice Workflow 1.4 Target Candidate Boundaries and Out-of-Scope Tasks 1.5 Domain Weights and Study Prioritization 1.6 Exam Policy, Retake, Results, and Recertification
2 Chapter 2: AI/ML Foundations and Use-Case Fit
2.1 AI, ML, Deep Learning, and Core Terminology 2.2 Supervised, Unsupervised, and Reinforcement Learning 2.3 Data Types, Labels, Structure, and Quality 2.4 Inference Patterns: Batch, Real-Time, and Embedded AI 2.5 AI Use-Case Fit and No-AI Decisions 2.6 Classification, Regression, Clustering, Forecasting, and Recommendation 2.7 AI/ML Foundations Case Lab
3 Chapter 3: ML Lifecycle, Metrics, and Practitioner MLOps
3.1 Data Collection, EDA, Preprocessing, and Feature Concepts 3.2 Training, Evaluation, Deployment, and Monitoring Lifecycle 3.3 Model Sources: Managed APIs, Open Source, and Custom Models 3.4 Evaluation Metrics and Business Metrics 3.5 Practitioner MLOps: Repeatability, Monitoring, and Retraining 3.6 SageMaker Lifecycle Service Map 3.7 ML Lifecycle Case Lab
4 Chapter 4: Generative AI Foundations and Inference Concepts
4.1 Foundation Models, LLMs, Transformers, and Modalities 4.2 Tokens, Context Windows, Embeddings, and Vector Search 4.3 Inference Parameters: Temperature, Top-p, and Output Controls 4.4 Hallucination, Grounding, and Context Quality 4.5 GenAI Use-Case Fit and Risk Triage 4.6 Prompt Injection, Data Leakage, and User Input Risk 4.7 Generative AI Foundations Case Lab
5 Chapter 5: Prompting, Model Selection, Customization, and Evaluation
5.1 Prompt Engineering Patterns and Business Quality 5.2 Zero-Shot, Few-Shot, Templates, and Instruction Design 5.3 Model Selection: Capability, Latency, Cost, and Risk 5.4 RAG vs Fine-Tuning vs Prompting vs Custom Models 5.5 Model Evaluation, Human Review, and Red-Team Feedback 5.6 Cost, Performance, and Throughput Decision-Making 5.7 Prompting and Model Selection Case Lab
6 Chapter 6: Amazon Bedrock, RAG, Agents, and Guardrails
6.1 Bedrock Core Concepts, Model Access, and Managed FM Choice 6.2 Knowledge Bases, RAG, Data Sources, and Grounding 6.3 AI Agents, Tools, Orchestration, and Business Workflows 6.4 Guardrails, Content Filters, Denied Topics, and Sensitive Data 6.5 Bedrock Model Evaluation, Monitoring, and Human Feedback 6.6 Bedrock Cost, Latency, Throughput, and Operational Fit 6.7 Bedrock, RAG, and Agents Case Lab
7 Chapter 7: AWS Managed AI/ML Services and SageMaker Map
7.1 Managed AI Services vs Foundation Model Apps vs Custom ML 7.2 Text, Language, Search, and Document AI Services 7.3 Vision, Speech, Contact Center, and Personalization Services 7.4 Amazon Quick, Amazon Q Developer, Kiro, and Practitioner Fit 7.5 SageMaker Canvas, Studio, Clarify, Autopilot, and Data Wrangler 7.6 Data Foundation Services: S3, Glue, OpenSearch, and Quick Sight 7.7 AWS AI Service Selection Case Lab
8 Chapter 8: Responsible AI, Human Review, and Safety
8.1 Fairness, Bias, Transparency, and Explainability 8.2 Privacy, Safety, Human Review, and Accountability 8.3 Guardrails, Clarify, Human Review, and Content Safety Controls 8.4 Responsible AI Risk Registers and Governance Workflows 8.5 Monitoring, Feedback, Drift, and Incident Response 8.6 Responsible AI Case Lab
9 Chapter 9: Security, Compliance, Governance, and Cost Controls
9.1 Shared Responsibility, IAM, and Least Privilege for AI 9.2 Encryption, Secrets, Networking, and Data Privacy 9.3 Prompt Injection, Data Exfiltration, and GenAI Threat Modeling 9.4 Logging, Monitoring, CloudTrail, CloudWatch, and Config 9.5 Compliance: Artifact, Config, Macie, and Policy Evidence 9.6 AI Cost Controls, Pricing, Throughput, and Budget Governance 9.7 Security and Governance Case Lab
10 Chapter 10: Integrated AWS AI Business Scenario Labs
10.1 Customer Support GenAI Assistant Lab 10.2 Document Intelligence and Compliance Review Lab 10.3 Personalization, Forecasting, and Fraud Detection Lab 10.4 Enterprise Search, RAG, and Knowledge Management Lab 10.5 Responsible AI and Security Review Board Lab 10.6 Cost, Performance, and Operations Review Lab 10.7 Full AIF-C01 Business Simulation
11 Chapter 11: Final Review, Exam Readiness, and Recertification
11.1 Final 30-Day AIF-C01 Study Plan 11.2 Official Practice Resources and Weak-Domain Remediation 11.3 90-Minute Exam Timing, Flagging, and Guessing Workflow 11.4 Test-Day Checklist: Online or Test Center 11.5 Post-Exam Results, Retake, and Recertification Plan 11.6 AWS AI Practitioner Final Mixed Review
7.7 AWS AI Service Selection Case Lab
Key Takeaways Explain This Topic AI
Service-selection cases should be solved by identifying the outcome, modality, data readiness, risk level, and ownership model before naming a service.
Many business problems combine services, such as Textract for extraction, Comprehend for classification, Bedrock for summarization, and Quick Sight for reporting.
A good practitioner recommendation includes boundaries, assumptions, governance questions, and a reason not to overbuild.
High-impact decisions need stronger review, explainability, monitoring, and human oversight than low-risk productivity assistance.
AWS Skill Builder and official practice activities should be used to rehearse service boundaries, not to memorize supposed live exam items.
Last updated: October 2026
Case method for AWS AI service selection
A service list is easy to memorize and easy to misuse. Case judgment is the skill that matters. A practitioner should read a scenario, identify the outcome, map the data type, decide whether the task is common or custom, check whether probabilistic output is acceptable, and name the AWS service path with boundaries. The strongest answer usually includes what the service does not solve.
Start with the outcome. Does the user need extracted fields, a transcript, a translation, a search result, a generated response, a recommendation, a forecast, a fraud signal, a dashboard, or a custom model? Then identify the modality: document, text, audio, image, video, tabular data, clickstream, logs, or mixed sources. This prevents service names from being chosen because they sound familiar rather than because they fit.
Next, decide whether the task is a managed capability, a foundation model application, or custom ML. If the task is a common AI API, start with a managed service. If the task is language generation, summarization, or question answering over context, start with Amazon Quick or Bedrock. If the task is a unique prediction that needs training on company data and lifecycle control, consider SageMaker AI. If the problem is deterministic reporting or workflow routing, avoid unnecessary AI.
Case signal Strong starting point Why it fits Boundary to state
Extract invoice fields from scanned PDFs Amazon Textract Document extraction is the primary outcome. Add validation and human review for low-confidence fields.
Summarize approved policy documents for employees Amazon Quick or Bedrock RAG The need is grounded generative assistance. Enforce permissions, source quality, and answer evaluation.
Transcribe customer calls and analyze trends Amazon Transcribe plus analytics or NLP services Audio must become text before analysis. Separate transcript accuracy from sentiment or summary quality.
Recommend products from user events and item data Amazon Personalize Recommendation is the primary outcome. Confirm data volume, consent, and monitoring.
Predict churn using proprietary labeled records SageMaker Canvas or SageMaker AI The prediction is company-specific. Define labels, metrics, bias review, and production ownership.
Show monthly support volume by category Quick Sight or analytics workflow A dashboard may solve the need without ML. Do not add AI unless it changes the decision quality.
Case 1: Accounts payable automation. The business wants vendor name, invoice number, totals, dates, and line items from uploaded invoices. The best first service is Textract, not a general chatbot. The implementation may store files in S3, use validation rules, route exceptions to humans, and publish metrics to Quick Sight. A foundation model might later summarize notes, but extraction is the core service-selection signal.
Case 2: Internal policy assistant. Employees ask questions about benefits, travel rules, and IT procedures. Amazon Quick can be a strong managed assistant fit if documents are current and permissions are respected. A Bedrock RAG application may fit if the team needs a custom app experience, model choice, or specialized guardrails. The practitioner should flag stale content, source ownership, restricted documents, feedback loops, and user training.
Case 3: Contact center improvement. Leaders want better visibility into customer calls and faster after-call work. Transcribe can create call transcripts. Lex may handle simple self-service intents. Comprehend or contact center analytics can help identify topics or sentiment. Bedrock might summarize calls or draft notes. The answer is a workflow, not one magic service. Privacy, recording notice, retention, and review are mandatory questions.
Case 4: Recommendation engine. A streaming service wants personalized content rows. Personalize is the managed recommendation service to evaluate if the company has interaction events, content metadata, and user context. If the catalog is tiny or data is sparse, a simple rules-based list may be better at first. Personalization quality should be judged by business metrics and user feedback, not by whether the service can technically run.
Case 5: High-impact prediction. A lender wants to predict default risk from applicant data. This is not a casual AI use case. A custom ML path might involve SageMaker AI, but the governance bar is high: fairness, explainability, data lineage, monitoring, human review, compliance review, and appeal processes. A practitioner should not recommend a black-box automated decision simply because ML is available.
Use this five-step case lab method:
Name the user outcome in one sentence.
Identify the input data type and sensitivity.
Choose managed AI, foundation model app, custom ML, analytics, or no AI.
State the AWS service starting point and the reason it fits.
Add the top governance risk, human review need, and operational owner.
Official practice should reinforce this method. Use AWS Skill Builder, official practice question sets, labs, and sandbox console exploration to compare service inputs and outputs. Do not search for exam dumps or supposed live questions. They are unreliable and violate the point of certification study. Scenario practice should teach judgment that transfers to real AWS work.
The final habit is to answer with assumptions. For example: If the task is extracting structured fields from documents, start with Textract. If the task is an employee assistant over governed documents, evaluate Amazon Quick. If the task is custom prediction from proprietary labels, discuss SageMaker AI readiness. If the task is a simple monthly trend report, use analytics first. That style shows practitioner-level service selection and responsible scope control.