Study guide

5.3 Model Selection: Capability, Latency, Cost, and Risk

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

5.3 Model Selection: Capability, Latency, Cost, and Risk

Key Takeaways Explain This Topic AI

Model selection balances capability, modality, context needs, latency, throughput, cost, safety, data handling, and operational support.

The largest or most capable model is not automatically the best choice if a smaller model meets the business quality bar at lower cost and latency.

AWS practitioners should distinguish Amazon Bedrock foundation models, Amazon Quick, managed AI services, SageMaker AI paths, and non-AI alternatives.

Riskier use cases need stronger grounding, guardrails, evaluation, monitoring, and human review before model approval.

Last updated: October 2026

A Decision Framework For Model Choice

Model selection starts with the job to be done. A chatbot that answers employee policy questions, a document classifier, a sales email drafter, and an image moderation workflow have different requirements. Do not start by asking for the biggest model. Start by asking what the user needs, what data is allowed, how fast the response must be, how much variation is acceptable, and what happens if the output is wrong.

Amazon Bedrock gives teams access to foundation models through a managed service. Different models can vary by text capability, image capability, embeddings, context window, language support, latency, cost, safety behavior, and customization options. A practitioner does not need to memorize every provider detail, but should know that model choice affects quality and operations.

Requirement Model or service question AWS direction

General text generation Does the task need broad language capability? Compare suitable Amazon Bedrock text models.

Semantic search or RAG Do we need embeddings for retrieval? Use an embedding model with a supported vector store.

Enterprise assistant Is the main need a managed business assistant? Consider Amazon Quick where it fits the use case.

Document extraction Is there a purpose-built managed service? Consider Amazon Textract before a generic FM.

Sentiment or entity detection Is standard NLP enough? Consider Amazon Comprehend.

Custom ML prediction Is this a classic ML problem with data and labels? Consider SageMaker AI or SageMaker Canvas.

Deterministic rule Must the result always follow exact rules? Use workflow logic, queries, or rules instead of GenAI.

Capability includes more than intelligence. A model must support the input and output modality: text, image, embeddings, or another format. It must support the needed language, context length, tool use pattern, and customization method. It should also be available in the intended AWS Region and meet the organization's data handling and compliance expectations.

Latency matters when the user is waiting. A customer chat response may need to arrive quickly. A nightly report summary can run more slowly. Larger prompts, larger models, longer outputs, and retrieval steps can increase response time. If a smaller model meets the quality bar, it may be the better production choice.

Cost is not only model price. It includes input tokens, output tokens, retrieval storage and search, orchestration, monitoring, evaluation, human review, and engineering support. A model that produces overly long outputs can be expensive even when the per-token rate looks acceptable. Prompt templates should limit output to what the workflow actually needs.

Risk changes the approval standard. A low-risk internal brainstorming tool can tolerate more variation than a customer-facing agent answering medical, legal, financial, safety, or employment questions. Higher-risk scenarios need stronger grounding, Amazon Bedrock Guardrails where applicable, human review, logging, and clear escalation rules. Some scenarios should be rejected or redesigned.

Model selection workflow:

State the use case, user audience, and decision impact.

Identify data sources, sensitivity, and whether outputs are customer-facing.

Decide whether a managed AI service, Amazon Quick, Amazon Bedrock, SageMaker AI, or ordinary automation best fits.

Create a small evaluation set with representative cases and edge cases.

Test candidate models against quality, latency, cost, and safety criteria.

Choose the simplest model and service design that meets the acceptance bar.

Document fallback behavior, monitoring, and the review cadence.

A common practitioner mistake is using a foundation model for every AI-related need. If the task is to extract tables from invoices, Amazon Textract may be a better first option. If the task is to translate text, Amazon Translate may be a better fit. If business users need no-code predictions from tabular data, SageMaker Canvas may be appropriate. If the task is an enterprise assistant with access to company systems, Amazon Quick may fit better than building from scratch.

SageMaker AI is important when the organization needs to build, train, customize, evaluate, or deploy ML models beyond a simple managed API pattern. That path can be powerful, but it brings more responsibility for data preparation, lifecycle, deployment, monitoring, and model governance. The exam target candidate is not expected to implement those pipelines, but should know when the path is heavier than needed.

Good model selection produces a defendable decision. The answer should say why the selected model or service fits the data, task, latency, cost, and risk. It should also say what was not selected and why. That judgment is central to practitioner-level AWS AI work.