Study guide

2.5 AI Use-Case Fit and No-AI Decisions

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

2.5 AI Use-Case Fit and No-AI Decisions

Key Takeaways Explain This Topic AI

Good AI use cases have an uncertain or high-volume decision, relevant data, measurable value, and an acceptable risk profile.

No-AI is the correct decision when rules are deterministic, data is poor, benefit is weak, risk is too high, or governance is not ready.

Use-case approval should compare managed AI services, foundation model workflows, custom ML, analytics, automation, and human process changes.

Practitioners should require clear success metrics, failure handling, and ownership before endorsing an AI solution.

Last updated: October 2026

Start With the Decision, Not the Model

A good AI use case starts with a business decision or workflow that can improve. The decision may be too slow, too inconsistent, too expensive, or too large for manual handling alone. Examples include classifying support tickets, detecting unusual transactions, recommending products, summarizing long documents, forecasting demand, translating content, transcribing calls, and helping employees find policy answers.

A weak AI use case starts with a vague request to add AI without a defined action. If no one can say what will change after the model produces output, the project is not ready. A dashboard, search improvement, training update, workflow rule, or process redesign may solve the real problem with less risk. Practitioners should be comfortable recommending no AI when the facts point there.

No-AI is not a failure. It is often the most professional recommendation. Use deterministic logic when the rule is known, testable, and must always produce the same outcome. Use traditional reporting when leaders need visibility rather than prediction. Use workflow automation when the process is repeatable. Use human review when context, ethics, legal judgment, or customer impact makes automation too risky.

Business need AI fit signal AWS path to consider No-AI alternative

Forecast demand Historical time patterns and measurable forecast error SageMaker Canvas or SageMaker AI options Human planning spreadsheet if volume is small

Detect fraud Rare patterns, labeled history, review process Custom ML path in SageMaker AI, or AWS WAF (Amazon Fraud Detector is closed to new customers) Fixed controls for known fraud rules

Recommend items User-item history and ranking objective Amazon Personalize Popular items or merchandising rules

Extract documents Repeated forms and review workflow Amazon Textract plus review Manual entry for low volume

Summarize knowledge Large trusted text corpus Amazon Quick or Bedrock retrieval workflow Curated FAQ or search index

Enforce policy threshold Known deterministic condition Not usually AI Application rule or Lambda workflow

Cost-benefit analysis should include more than service pricing. AI projects require data preparation, security review, monitoring, user training, exception handling, and maintenance. A model that saves minutes for a small team may not justify the operational burden. A model that changes a high-volume workflow may be worth investment if errors are manageable and the business can measure improvement.

Risk changes the acceptable level of automation. A retail recommendation that is occasionally irrelevant may be tolerable. A medical, financial, legal, hiring, or safety-related recommendation may require strict review, explainability, auditability, and human approval. Controls such as human review queues, Amazon Bedrock Guardrails, CloudWatch, CloudTrail, IAM, KMS, and policy controls can support governance, but they do not remove the need for accountability.

Fit also depends on data. A fraud model needs enough examples of fraud and legitimate behavior to learn meaningful differences. A recommendation system needs interaction history. A chatbot over enterprise knowledge needs current, approved documents. A vision inspection model needs representative images. If data is sparse, biased, inaccessible, or legally restricted, the correct near-term answer may be data work before AI.

A service-first shortcut can lead to overbuilding. Amazon Bedrock is powerful for generative AI, but it is not the answer for every prediction. Amazon SageMaker AI supports custom ML, but it may be unnecessary when a managed AI service directly solves the task. Amazon Quick can help employees interact with enterprise information, but a simple curated knowledge base may be enough for stable policies and exact answers.

Use this approval checklist:

The business action changed by the AI output is written down.

The baseline process and success metric are known.

The required data is available, permitted, and representative.

The team compared managed AI, GenAI, custom ML, analytics, automation, and no-AI options.

Failure modes, human review, escalation, and fallback behavior are defined.

Owners are named for cost, security, model quality, user feedback, and retirement.

Scenario: a service desk wants to reduce time spent reading long internal articles. If agents need fast summaries and answers from approved knowledge, Amazon Quick or a Bedrock retrieval workflow may fit. If the article set is small and stable, better tagging and search might be enough. If generated answers could misstate refund policy, the workflow should show sources and route uncertain cases to human review.

Scenario: an operations team wants to block all shipments to a sanctioned country list. This should be a deterministic control using approved reference data. AI would add uncertainty to a requirement that needs exact enforcement. AI might later help detect suspicious address variations, but the core policy block should remain a rules-based compliance control.

Scenario: a sales group wants lead scoring. This may fit supervised learning if historical leads include outcomes such as converted or not converted, the sales process is stable, and the score changes follow-up behavior. It may be a poor fit if the CRM data is incomplete, outcomes are inconsistently recorded, or the team cannot agree on how to use the score. A reporting cleanup might come first.