Study guide
4.1 Foundation Models, LLMs, Transformers, and Modalities
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
4.1 Foundation Models, LLMs, Transformers, and Modalities
Key Takeaways Explain This Topic AI
Foundation models are broad pretrained models that can be adapted to many tasks through prompting, retrieval, or customization rather than task-specific training from scratch.
LLMs are foundation models focused on language, while multimodal models can work with text, images, audio, video, or combinations of those inputs and outputs.
Transformers matter at practitioner depth because attention lets a model weigh relationships across tokens, but candidates do not need to build transformer architectures.
AWS service fit depends on whether the team needs a managed model API, a packaged assistant, a task-specific AI service, or a custom ML path.
Last updated: October 2026
Foundation models in plain language
A foundation model is a large model trained on broad data so it can support many downstream tasks. Instead of building a different model for every workflow, a team can often start with a general model and steer it with prompts, retrieved context, examples, guardrails, or later customization. That is why foundation models show up in chat assistants, document search, summarization, extraction, image generation, and code help. The model is foundational because it provides reusable capability, not because it is automatically right for every business problem.
A large language model, or LLM, is a foundation model centered on language. It predicts and generates text as sequences of tokens, which can support answering questions, drafting content, translating tone, classifying messages, or explaining a document. A multimodal foundation model expands the pattern beyond text. Depending on the model, it may accept images, audio, video, or text, and it may produce text, images, or other outputs. A practitioner should ask which modalities are required instead of assuming every model can read every file type.
Transformers are the major architecture behind many LLMs. At exam depth, the key idea is attention: the model can weigh relationships among tokens in the input rather than reading words as isolated items. This helps it connect pronouns to earlier nouns, follow instructions across a prompt, and summarize long passages. You do not need to calculate attention or design neural network layers for the AWS Certified AI Practitioner exam, but you should know why transformers enabled strong language and multimodal performance.
Practitioner comparison table
Concept What it means Practitioner question
Foundation model Broad pretrained model reused across many tasks Is a general model enough, or does the task need a specialized service or customization?
LLM Foundation model focused on language Are the inputs and expected outputs primarily text?
Multimodal model Model that can use more than one content type Does the workflow need images, audio, video, or document layout understanding?
Transformer Architecture that uses attention across tokens Are we discussing capability and limits, not building the model internals?
Inference Using a trained model to produce output What latency, cost, accuracy, and control requirements apply when users call it?
This table is useful because many business conversations use model terms loosely. A team may say it needs an LLM when it actually needs optical text extraction, translation, enterprise search, or a narrow classifier. For example, Amazon Textract is built for extracting text and structured data from documents, while Amazon Bedrock gives managed access to foundation models for generative AI applications. Amazon Quick (for business users) and Amazon Q Developer (for builders) are packaged generative AI assistant experiences.
SageMaker AI is more relevant when a builder team needs deeper ML development, training, customization, or deployment control.
Service fit and modality judgment
A good practitioner starts with the work, not the hype. If a support team wants draft replies to customer emails, a text-capable LLM through Amazon Bedrock may fit because the model can summarize tone, intent, and policy context. If the team wants employees to ask questions over company documents, Amazon Quick or a Bedrock-based retrieval augmented generation solution may be closer. If the task is to detect unsafe objects in images, Amazon Rekognition may be more direct than building a chat experience around a multimodal model.
Use cases also fail when the model capability does not match the operating risk. A general model may produce fluent output that sounds authoritative even when it lacks the required facts. A multimodal model may identify visual patterns but still miss edge cases, low-quality images, or domain-specific details. A text model may produce a good first draft but still need human review before legal, medical, financial, or public communications. Foundation models are useful accelerators, not substitutes for business ownership.
A non-builder candidate should be able to ask four practical questions before approving a generative AI path:
What input and output modalities does the workflow require?
Does AWS already provide a managed AI service that solves the task more directly?
What source of truth will ground the model when factual accuracy matters?
What review, monitoring, security, and cost controls will be used after launch?
The answer often points to a layered architecture. A web app might call Amazon Bedrock for generation, store source documents in Amazon S3, retrieve relevant chunks through a vector index, protect access with IAM, encrypt data with AWS KMS, and log activity with CloudTrail and CloudWatch. At this chapter stage, the important part is not building that architecture line by line. The important part is recognizing the vocabulary and seeing how capability, modality, service selection, and risk connect.