Study guide
1.5 Domain Weights and Study Prioritization
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
1.5 Domain Weights and Study Prioritization
Key Takeaways Explain This Topic AI
Applications of Foundation Models is the largest AIF-C01 domain at 28 percent.
Fundamentals of GenAI is 24 percent, and Fundamentals of AI and ML is 20 percent.
Guidelines for Responsible AI and Security, Compliance, and Governance for AI Solutions are each 14 percent.
Weights guide study allocation, but scenarios often combine domains such as Bedrock, responsible AI, IAM, cost, and data readiness.
Last updated: October 2026
Weighted study map
A candidate who studies every domain for the same amount of time may feel organized while ignoring the official weighting signal. The AIF-C01 exam guide lists five domains with different weights. Applications of Foundation Models is the largest at 28 percent, followed by Fundamentals of GenAI at 24 percent, Fundamentals of AI and ML at 20 percent, Guidelines for Responsible AI at 14 percent, and Security, Compliance, and Governance for AI Solutions at 14 percent.
Weights are not an exact question counter. A 28 percent domain does not tell you the order of questions or the exact number of items you will see. It tells you where AWS expects more exam emphasis. Use the percentages to plan study time, practice review, and hands-on exploration. Then adjust based on your error log.
Domain Weight Study priority Scenario cue
Fundamentals of AI and ML 20% Build the core language of models, data, lifecycle, metrics, and use-case fit. Is AI appropriate, and what kind of learning or data is involved?
Fundamentals of GenAI 24% Learn foundation models, LLMs, tokens, embeddings, prompts, inference, and customization concepts. Can a generative model solve the task, and what risks follow?
Applications of Foundation Models 28% Spend the most time on Bedrock, RAG, agents (including Amazon Bedrock AgentCore), guardrails, prompt management, evaluation, and service selection. Which AWS foundation model path fits the business requirement?
Guidelines for Responsible AI 14% Study fairness, explainability, privacy, safety, transparency, accountability, and human review. What could go wrong for people, users, or the organization?
Security, Compliance, and Governance 14% Study IAM, encryption, logging, monitoring, privacy, policies, and governance lifecycle. Who can access what, where data goes, and how controls are verified?
Why the largest domain needs scenario depth
Applications of Foundation Models is the largest domain because it sits closest to current business demand. Teams want copilots, knowledge assistants, summarizers, content generators, search experiences, and task automation. On AWS, that pulls in Amazon Bedrock, model selection, Amazon Quick, SageMaker AI, SageMaker Canvas, Knowledge Bases, Amazon Bedrock AgentCore, Guardrails, embeddings, vector search, RAG, model evaluation, and cost/performance tradeoffs.
A shallow plan would memorize that Bedrock is associated with foundation models. A serious plan asks which model capability is needed, whether retrieval from enterprise content is required, whether a vector store or embeddings are part of the design, whether an agent should call tools, whether guardrails should constrain outputs, how to evaluate quality, and how latency and cost affect the choice. That is the level of practitioner decision-making the domain weighting deserves.
Do not starve the 14 percent domains
Responsible AI and Security, Compliance, and Governance are each 14 percent, but they are not small in real projects. A solution can be technically correct and still unacceptable if it exposes sensitive prompts, lacks human review, produces biased recommendations, ignores transparency, or grants broad permissions. These domains often appear as constraints inside larger foundation model scenarios.
For example, a human resources team wants AI to screen resumes. The AI/ML domain asks whether the use case is appropriate and what data exists. The GenAI domain asks whether a foundation model is suitable. The foundation model application domain asks whether to use a managed service, RAG, guardrails, or evaluation. Responsible AI asks about fairness, explainability, and human oversight. Security and governance ask about IAM, data privacy, logging, retention, and compliance review.
Study allocation model
Weekly study block Suggested share Work product
Foundation model applications 30% Service-selection table, Bedrock/RAG/agent/guardrail scenarios, cost notes.
GenAI fundamentals 25% Prompting, tokens, embeddings, inference parameters, model customization map.
AI/ML fundamentals 20% Use-case fit matrix, lifecycle notes, metrics and data type drills.
Responsible AI 12.5% Risk checklist for fairness, privacy, safety, transparency, and human review.
Security and governance 12.5% IAM/shared responsibility/logging/encryption/governance checklist.
This allocation is close to the official weights, with a slight rounding for practical scheduling. After each practice set, update the allocation. If you repeatedly miss responsible AI questions, increase responsible AI time even though its official weight is lower. If you know AI/ML vocabulary but miss Bedrock service boundaries, move time toward foundation model applications.
Cross-domain decision tree
Identify the business outcome: classify, summarize, generate, forecast, recommend, extract, translate, converse, or search.
Decide whether AI is suitable: check data quality, deterministic needs, risk, value, and governance readiness.
Pick the concept family: traditional ML, managed AI service, generative AI, foundation model application, or no-AI path.
Map to AWS services at practitioner depth: Bedrock, Amazon Quick, SageMaker AI, SageMaker Canvas, or a managed AI service as appropriate.
Add responsible AI controls: fairness, explainability, safety, privacy, transparency, accountability, and human review.
Add security and governance controls: IAM, encryption, logging, monitoring, data retention, compliance evidence, and cost tracking.
Priority traps
The first trap is studying GenAI as if it replaced all AI/ML foundations. You still need supervised, unsupervised, and reinforcement learning concepts, data types, model lifecycle, evaluation metrics, and when AI is not appropriate. The second trap is studying security as generic cloud trivia. In AIF-C01, security must be tied to AI prompts, model access, data privacy, logging, monitoring, and governance.
The third trap is ignoring business value. The exam is not only asking which service can do a task. It can ask whether the task should be automated, whether the organization has suitable data, whether human review is needed, or whether a managed AWS service avoids unnecessary build complexity. Use domain weights to decide volume, but use scenarios to decide quality.