Where AI Fits, and Where It Does Not

Certification Blueprint

Field	Coverage
Exam	AWS Certified AI Practitioner (AIF-C01), exam guide v1.1
Domain	Content Domain 1 — Fundamentals of AI and ML
Exam weight	20% of scored content
Task statement	1.2 Identify practical use cases for AI
Objectives	1.2.1 value · 1.2.2 when not appropriate · 1.2.3 techniques · 1.2.4 applications · 1.2.5 AWS managed services · 1.2.6 traditional ML vs FM

What This Chapter Covers

Chapter 01 taught classification — what a system is, what its data permits, how it will be served. This chapter teaches selection: whether to use AI at all, which technique the output shape requires, which AWS service already solves the problem, and whether the answer is a traditional model or a foundation model.

The unusual part is that selection includes saying no. Objective 1.2.2 asks you to identify when AI/ML is not an appropriate solution, and the exam genuinely marks the non-AI option correct when the scenario calls for it. Most of this exam rewards recognising the right answer. Task 1.2 rewards recognising that three plausible, technically accurate answers are wrong.

Chapter 01 answered	Chapter 02 answers
What is this system?	Should we build it with AI at all?
Which learning type does the data permit?	Which technique does the output shape require?
How will it be served?	Which AWS service already does this?
—	Traditional ML or a foundation model?

Where AI/ML Provides Value

Objective 1.2.1 names three patterns, and the exam expects the names.

Pattern	What it looks like	The tell in a scenario
Assisted decision making	Surface a recommendation; a human decides	"help the team prioritise", "flag for review"
Solution scalability	Handle volume no team could review manually	"millions of items", "cannot hire enough reviewers"
Automation	Remove repetitive judgment work	"currently done manually for every case"

These overlap in real systems — a claims triage tool is arguably all three. On the exam, pick the one the scenario spends its words on. If two sentences describe the size of the backlog, it is scalability. If the scenario stresses that a person still signs off, it is assisted decision making even though work is clearly being saved.

When AI Is the Wrong Answer

What to remember from this diagram: three gates, and two of them are exits. Most people picture AI adoption as a funnel ending in "yes". This one ends in "no" three ways out of four, and that is the shape Objective 1.2.2 is testing.

Reject AI/ML in these cases:

• A specific guaranteed outcome is required, not a prediction. Tax owed, a statutory benefit entitlement, interest accrued, a bill computed from a published tariff. The correct answer is defined by rule, so a prediction is wrong by construction. A model that is 99.7% accurate is a defect here — ask what the other 0.3% means when it is somebody's tax bill.
• Cost-benefit fails. Labeling, re-labeling, training, re-training on drift, monitoring and on-call are all recurring costs.
• Data is insufficient or unstable. Either no outcomes were ever recorded — which removes supervised learning entirely, per Chapter 01's label signal — or the underlying process changes so often that historical data no longer describes the current world. The second is subtler and is usually signalled by a phrase about the business changing frequently.

The cost-benefit test has a baseline problem

The trap is comparing the model against nothing, where it always looks good. The honest comparison is against the alternative that actually exists, which is usually a rules table maintained by two people.

Cost that recurs	Often forgotten
Labeling and re-labeling	Yes
Training and re-training on drift	Yes
Monitoring, alerting, on-call	Yes
Inference at production volume	Sometimes
A rules table maintained by two people	This is the comparison

If a deterministic rules table reaches the same outcome, it wins — it is cheaper, exact, and explainable at no extra cost. That last property is worth naming: explainability is free in a rules table and expensive in a model.

Choosing the Technique

What to remember from this diagram: classification and clustering both produce groups. The difference is that classification's groups already have names.

Output shape	Technique	Example
A continuous number	Regression	Beds occupied, price, demand
One of N known categories	Classification	Fraud/legitimate, defect type
Groups nobody defined	Clustering	Customer segments

Ask what the output looks like, not what the domain is. Healthcare is not a technique. Neither is "text" and neither is "images".

The scenario says…	Technique	Why
"Predict how many beds will be occupied next Tuesday"	Regression	A continuous number
"Decide whether this transaction is fraudulent"	Classification	Two known categories
"Find natural groupings of customers we haven't defined"	Clustering	Groups do not exist yet
"Sort defects into the six fault codes we already use"	Classification	The categories are already named
"Forecast next quarter's demand"	Regression	Continuous, over time

Rows three and four are a deliberate pair — same shape of sentence, opposite answers, and a single clause decides it. Named categories → classification. Unnamed groups → clustering.

Applications and Their Technique Families

What to remember from this diagram: both v1.1 additions — knowledge bases and agentic AI — hang off language models. If you are revising from material written before 2026-04-30, neither appears in your copy of this objective.

Application	Technique family
Computer vision	Deep learning on images
NLP	Language models
Speech recognition	Audio → text
Recommendation systems	Collaborative/content filtering
Fraud detection	Supervised classification
Forecasting	Time-series regression
Knowledge bases (new in v1.1)	Retrieval over a corpus
Agentic AI (new in v1.1)	Multi-step tool-using systems

AWS Managed AI Services

What to remember from this diagram: read the arrow, not the service name. Transcribe and Polly are the same edge travelled in opposite directions, and swapping them is the single most common distractor in this domain.

These services are pre-built: no training, no labeled data, no model to manage.

Service	Does	Reverse service
Amazon Transcribe	Speech → text	Polly
Amazon Polly	Text → speech	Transcribe
Amazon Translate	Language → language	—
Amazon Comprehend	Text → entities, sentiment, topics	—
Amazon Lex	Conversational interfaces	—
Amazon SageMaker AI	Build, train, deploy your own	—

The scenario says…	Service	The tell
"Generate an audio version of each article"	Polly	Producing speech
"Search the call archive by what was said"	Transcribe	Producing text from audio
"Detect the sentiment of support tickets"	Comprehend	Extracting meaning from text
"Serve the help centre in nine languages"	Translate	Language to language
"Build a phone menu that understands intent"	Lex	Conversational interface
"We need a custom model on our own data"	SageMaker AI	Nothing pre-built fits

SageMaker AI is correct only in that last row, and it is correct because nothing pre-built fits — not because it is more powerful. If a managed service already solves the stated problem, building a custom model is the wrong answer, and it will be offered, because it is a true statement about AWS and therefore hard to eliminate on knowledge alone.

Traditional ML or Foundation Model

What to remember from this diagram: notice what is absent — the industry, the data type, and how modern the company sounds. Every one of those appears in distractors.

Objective 1.2.6 was added at v1.1 and names exactly three deciding factors:

1. Regulatory concerns
2. Explainability requirements
3. Operational constraints

The instinct is to choose by task — text implies a foundation model, tabular implies traditional ML. The objective is explicitly constraint-driven. A text classification task under a regulator, with plenty of labeled examples and a tight per-inference cost budget, is traditional ML, and the fact that it involves language changes nothing.

Constraint	Choose	Why
Must be explained to a regulator	Traditional ML	Coefficients are inspectable and reproducible
Auditable, reproducible outputs	Traditional ML	Deterministic, fixed feature set
Narrow task, plenty of labels	Traditional ML	Cheaper, faster, usually more accurate
Broad language understanding, many tasks	Foundation model	Generalises without task-specific data
Very little labeled data	Foundation model	In-context learning needs no training set
Content must be generated	Foundation model	Traditional models score; they don't generate
Tight latency + cost at high volume	Traditional ML	Far cheaper per inference

Explainability is not articulacy

A foundation model asked why it declined an application will produce a fluent, plausible, well-structured paragraph. That paragraph is generated text about a decision. It is not a faithful account of the computation that produced the decision, and it is not reproducible — ask twice and you may get two different paragraphs.

A regulator requires the second thing. The test to apply: could an auditor re-run the process and obtain the same factor weights? For a linear model, yes. For a generated explanation, no.

This single distinction decides the hardest Domain 1 questions, and it returns in Chapters 12 and 13.

Decision Rules and Exam Signals

Rule 1 — screen before selecting. Run the three suitability gates before naming any technique or service. Two of the three are exits.

Rule 2 — the output shape picks the technique. Not the industry, not the data type. Continuous number, named category, or undefined group.

Rule 3 — named groups mean classification. If the scenario tells you what the buckets are called, clustering is wrong.

Rule 4 — read the arrow, not the service name. Verbalise every managed service as "from X to Y".

Rule 5 — a managed service beats a custom model when it already fits. SageMaker AI is the escape hatch, not the default.

Rule 6 — Objective 1.2.6 is constraint-driven. Regulatory, explainability, operational. Data type is not on the list.

Distractor Patterns

Pattern	What it looks like	How to defuse it
AI offered where it is forbidden	A prediction proposed for a statutory calculation	Ask whether an exact answer is legally required
Real service, wrong direction	Polly offered for transcription	Read the arrow, not the name
Custom model over managed service	SageMaker AI where Comprehend fits	Ask if something pre-built already does it
Technique chosen by industry	"Healthcare, so classification"	Ask what the output looks like
Clustering for named categories	Clustering offered for six known fault codes	If the groups have names, it is classification
FM chosen by data type	"It's text, so a foundation model"	Objective 1.2.6 is constraint-driven
Fluent explanation accepted as explainability	An FM that "explains its reasoning" for a regulator	Plausible text is not a reproducible account

The last two separate a pass from a fail on this task statement.

Scenario Walkthrough

A utility must calculate each customer's bill from meter readings and a published tariff. The regulator publishes the tariff and audits the calculation. The company also wants to reduce the 900,000 support emails it receives each year by routing them automatically to the right team, and to publish an audio version of every bill explanation for accessibility.

Requirement	Reading	Decision
Calculate the bill from a published tariff	Exact answer legally defined	Not AI/ML — deterministic calculation
Route 900,000 emails to the right team	Text → one of N known teams	Classification; Comprehend fits
Publish an audio version	Text → speech	Amazon Polly

Three requirements, three different answers — and one of them is "do not use AI".

The failure mode is answering all three with a single service. Real exam questions do a smaller version of this by embedding one disqualifying clause inside an otherwise ordinary scenario.

Key Concepts

Term	Definition
Assisted decision making	An AI value pattern where the system surfaces a recommendation and a human makes the final decision
Solution scalability	An AI value pattern where the system handles a volume of work no team could review manually
Automation	An AI value pattern where repetitive judgment work is removed from people entirely
Regression	A technique producing a continuous numeric output, such as price or demand
Classification	A technique assigning an input to one of N categories that already exist and have names
Clustering	A technique discovering groupings that nobody defined in advance; a human interprets what they mean afterwards
Knowledge base	An application pattern retrieving over a corpus of documents; added to Objective 1.2.4 at v1.1
Amazon Transcribe	Managed service converting speech to text
Amazon Polly	Managed service converting text to speech — the reverse of Transcribe
Amazon Translate	Managed service converting text from one language to another
Amazon Comprehend	Managed service extracting entities, sentiment and topics from text
Amazon Lex	Managed service for building conversational interfaces
Amazon SageMaker AI	Service for building, training and deploying your own models when nothing pre-built fits
Traditional ML	A model with a fixed feature set and inspectable, reproducible behaviour; preferred under regulatory, explainability or tight cost constraints
Foundation model	A large pre-trained model that generalises across tasks; preferred when labels are scarce, the task is broad, or content must be generated
Explainability	A faithful, reproducible account of how a decision was computed — not a fluent description of it

Revision Flashcards

Say the answer aloud before revealing it.

1. Name the three value patterns in Objective 1.2.1. → Assisted decision making, solution scalability, and automation.

2. What are the two ways a scenario disqualifies AI/ML? → A specific guaranteed outcome is required rather than a prediction, or the cost-benefit analysis fails against the honest alternative.

3. Why is a 99.7% accurate model a defect for a statutory calculation? → Because the correct answer is defined by rule. A prediction is wrong by construction, and the 0.3% is somebody's real entitlement.

4. What is the correct baseline for a cost-benefit comparison? → The honest alternative that already exists — usually a deterministic rules table — not "doing nothing".

5. What decides the technique: regression, classification or clustering? → The shape of the required output. A continuous number, one of N named categories, or groups nobody has defined.

6. What separates classification from clustering? → Classification's groups already exist and have names. Clustering discovers groupings nobody defined, and a human interprets them afterwards.

7. Which direction does Amazon Transcribe run, and what is its reverse? → Speech to text. Its reverse is Amazon Polly, which runs text to speech.

8. When is Amazon SageMaker AI the right answer? → Only when nothing pre-built fits and a custom model on your own data is genuinely required — not because it is more capable.

9. Name the three deciding factors in Objective 1.2.6. → Regulatory concerns, explainability requirements, and operational constraints.

10. The scenario says the data is text. Does that select a foundation model? → No. Data type is not one of the three deciding factors. A text task under a regulator with plenty of labels is traditional ML.

11. Why is a foundation model's fluent explanation not explainability? → It is generated text about a decision rather than a faithful, reproducible account of how the decision was computed. Asking twice may produce two different answers.

12. Which two applications were added to Objective 1.2.4 at v1.1, and what family do they belong to? → Knowledge bases and agentic AI. Both hang off language models.

The Four-Beat Answer

The core question this chapter prepares you for: "How do you decide whether — and how — to apply AI to a business problem?"

Four beats, checked in this order. Missing a beat is a failure state.

1. Suitability — is an exact answer required by rule, is the data sufficient and stable, and does the value beat the honest alternative? Say out loud that "don't use AI" is a real outcome of this step, because that is what separates a considered answer from an enthusiastic one.
2. Value pattern — name which of the three the problem is: assisted decision making, scalability, or automation. This tells you where the human sits.
3. Technique — derive it from the shape of the required output, not from the industry or the data type, and say which shape you saw.
4. Build versus buy, and which kind of model — check whether a managed service already solves it before proposing a custom model, then apply the three constraints to choose traditional ML or a foundation model.

A strong answer names the constraint that decided each beat. A weak answer names services.

Why This Helps You

On the job: beat 1 is the conversation nobody has. Teams commit to a model for a problem where a rules table would have been exact, cheaper and auditable — and then spend a year maintaining it. Being the person who asks whether an exact answer is required is disproportionately valuable.

In interviews: "when would you not use machine learning?" is a standard senior screening question, and enthusiasm is the wrong answer. Naming the two disqualifiers and the correct cost-benefit baseline reads as experience.

On the exam: Task 1.2 questions are built to make the non-AI or managed-service answer feel too simple. Three of four options will be true statements about AWS. The habit of screening before selecting is what keeps you from picking a capable answer to a question that wanted a correct one.

Chapter Checklist

• I can name the three value patterns and pick the one a scenario spends its words on
• I can recognise both ways a scenario disqualifies AI/ML
• I can state why a highly accurate model is a defect for a legally defined calculation
• I can compare a model against the honest alternative rather than against nothing
• I can choose regression, classification or clustering from the output shape alone
• I can separate classification from clustering using whether the groups already have names
• I can map each Objective 1.2.4 application to its technique family, including both v1.1 additions
• I can name the direction each AWS managed AI service runs in, and its reverse where one exists
• I can say when SageMaker AI is the right answer and when it is a distractor
• I can apply Objective 1.2.6's three factors instead of choosing by task or data type
• I can explain why a fluent explanation is not explainability, and give the auditor test

After the Chapter

1. Complete student/project.md — parts 7, 8 and 9 of the AI/ML Decision Sheet you began in Chapter 01. Bring the same sheet; do not start a new one.
2. Take student/quiz.md closed-book, then review the reasoning for every question you guessed, including the ones you got right.
3. Open the official v1.1 exam guide's Domain 1 page and confirm you can attach a concept from this chapter to each of the six bullets under Task 1.2.
4. Next chapter: Chapter 03 — The AI/ML Lifecycle and MLOps (Domain 1, Task 1.3). The pipeline from business goal to monitoring and what each stage produces; where models come from and how they are served; what MLOps adds beyond "the model works"; and choosing between precision, recall, F1 and a business metric from the cost of being wrong. Chapter 03 completes Domain 1.