Practical AI Use Cases and the AWS AI Service Catalog (AIF-C01)

AI and ML earn their keep in three broad situations that the exam names directly. The first is assisting human decision making: rather than replacing an expert, the model surfaces a prediction or ranking that a person then acts on, such as flagging the transactions most likely to be fraudulent so an analyst reviews those first. The second is scalability: a model can evaluate millions of items consistently and instantly in a way no human team could match, for example screening every product review or every login attempt as it happens. The third is automation: tasks that are repetitive and pattern-based, like sorting support tickets by topic or transcribing thousands of calls, can run without a person in the loop.

Underlying all three is a common signal: the problem involves recognizing patterns or predicting outcomes from data that is too large, too fast, or too nuanced for hand-written rules. If a task requires judgment based on many subtle examples, changes over time, or must operate at a volume beyond human capacity, it is a strong AI/ML candidate. On the exam, phrases like "analyze at scale," "detect patterns humans would miss," "personalize for each user," or "reduce manual effort" all point toward an AI/ML solution being appropriate.

Knowing when to say no is one of the most frequently tested points in this task. The headline rule: AI/ML produces probabilistic predictions, not guaranteed answers, so it is the wrong choice when a problem demands a specific, exact, deterministic outcome every time. If a task can be solved with a clear, fixed rule and must be exactly right, use conventional programming, not machine learning. Calculating sales tax, applying a documented refund policy, or summing a column of numbers all have one correct answer defined by a rule; wrapping them in an ML model would only add uncertainty. A model that is right ninety-nine percent of the time is unacceptable when the requirement is one hundred percent correctness.

The second reason to decline is a poor cost-benefit balance. Machine learning needs quality data, skilled effort, and ongoing operation, so if the problem is small, rarely occurs, or a simple rule already works well, the expense of building and maintaining a model is not justified. A related blocker is lack of sufficient, relevant data: without enough representative examples, a model cannot learn reliably. On the exam, watch for wording like "needs a guaranteed exact answer," "outcome must be exactly correct," or "a simple deterministic rule already solves it" as signals that AI/ML is not appropriate.

When AI/ML does fit, the exam expects you to pick the technique that matches the problem type. The choice hinges on what you are trying to produce. Regression predicts a continuous numeric value, such as a price, a temperature, or an expected demand. Classification predicts a category or class from a fixed set of options, such as spam versus not-spam or which of five product types an image shows; both regression and classification are supervised techniques that need labeled data. Clustering is an unsupervised technique that groups similar items together when you have no labels and want to discover natural segments, such as grouping customers by behavior.

The fastest exam heuristic: a number as the answer means regression, a labeled bucket means classification, and grouping without predefined labels means clustering.

The exam lists concrete application areas, and recognizing each by its description is enough. Computer vision interprets images and video, powering quality inspection, medical image analysis, and face or object detection. Natural language processing (NLP) works with written language for sentiment analysis, entity extraction, and document classification. Speech recognition converts spoken audio into text, enabling call transcription and voice interfaces. Recommendation systems suggest products, content, or connections based on a user's behavior and similar users, and are what drive "customers also bought" features.

Fraud detection spots unusual or suspicious activity by learning what normal transactions look like and flagging the anomalies. Forecasting predicts future values from historical time-series data, such as future demand, staffing needs, or energy usage. Knowledge bases and intelligent search let users ask natural-language questions and get answers pulled from a body of documents, rather than scrolling through keyword results. Agentic AI extends generative AI so a system can plan and carry out multi-step tasks using tools, for example gathering information and completing an action on a user's behalf. On the exam these applications are usually the answer to "which use case fits," so tie each phrase to its capability: images to computer vision, audio to speech recognition, suggestions to recommendation systems, and anomalies to fraud detection.

AWS offers pre-trained, managed AI services so you can add a capability with an API call instead of building and training a model yourself. Task 1.2 focuses on knowing each service by its purpose. Amazon Comprehend is the NLP service: it extracts sentiment, entities, key phrases, language, and personally identifiable information from text. Amazon Transcribe converts speech to text, and Amazon Polly does the reverse, converting text to lifelike speech. Amazon Translate performs language translation between many languages. Amazon Lex builds conversational interfaces and chatbots, using speech recognition and language understanding, and it is the technology behind Amazon Alexa.

Match the verb in the question to the service: the six the exam names most often are Comprehend, Transcribe, Translate, Polly, Lex, and SageMaker AI.

The pre-trained services above solve common, well-defined problems out of the box, but sometimes your problem is specific to your business, such as predicting churn from your own customer data or detecting defects unique to your product. That is where Amazon SageMaker AI fits. SageMaker AI is the fully managed service for the whole custom machine-learning workflow: you use it to build, train, and deploy your own models, with the infrastructure managed for you.

The distinction the exam draws is level of control versus effort. Managed AI services like Comprehend or Rekognition require no ML expertise and no training data of your own; you send a request and get a result, but you cannot change what the model does. SageMaker AI gives you full control to create a model tailored to your data and problem, at the cost of needing data and more skill. A simple decision rule: if a ready-made service already does the task, such as transcription or translation, use it; if you need a custom model trained on your own data, use SageMaker AI. Note that building the model pipeline in detail, along with MLOps and monitoring, belongs to Task 1.3, so here you only need to know what SageMaker AI is for.

A newer Task 1.2 objective asks when a traditional ML model is a better fit than a foundation model (FM). Foundation models are large, general-purpose models (the basis of generative AI) that are powerful and flexible but also large, costly to run, and hard to fully explain. Traditional ML models, such as a regression or decision-tree model trained on your tabular data, are smaller, cheaper, and often far easier to interpret. The right choice depends on constraints, not on which is more advanced.

The exam's favorite trap is assuming the biggest, newest model is always best. When a question stresses that decisions must be explainable, must satisfy regulators, or must run cheaply and predictably, a simpler traditional ML model usually wins. Reserve foundation models for open-ended generation and broad language understanding, which is where their flexibility justifies their cost.

Consider an insurer modernizing its operations, where each need maps to a different Task 1.2 answer. To decide which claims to pay automatically and which to route to a human, it must be able to explain and defend every decision to regulators, so it chooses a traditional ML classification model over a foundation model, and it keeps a person in the loop for borderline cases, an example of AI assisting human decision making. To estimate a fair premium, a continuous dollar amount, it uses regression. To predict next quarter's claim volume from years of history, it uses forecasting on time-series data.

For its contact center, the insurer converts recorded calls to text with Amazon Transcribe, gauges customer sentiment and pulls out key details with Amazon Comprehend, and answers common questions through a chatbot built on Amazon Lex. It reads data from scanned claim forms with Amazon Textract. When it wants to segment customers into groups with no predefined labels, it uses clustering. Finally, it decides not to use AI to calculate policy renewal dates, because that is a fixed, exact rule with one correct answer and needs no prediction. One company, and every core Task 1.2 judgment: value, non-value, technique choice, service choice, and model choice.