Study guide
10.7 Full AIF-C01 Business Simulation
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
10.7 Full AIF-C01 Business Simulation
Key Takeaways Explain This Topic AI
A full business simulation should connect AI fundamentals, generative AI, foundation model applications, responsible AI, and security governance in one decision packet.
The practitioner role is to identify fit, ask evidence-based questions, choose managed AWS services where appropriate, and avoid overbuilding when a simpler workflow works.
The best answer in scenario work often depends on constraints: data quality, risk level, latency, cost, permissions, human review, and current AWS service availability.
Original practice questions should build reasoning skill without claiming to reproduce real exam items.
A final review habit is to document assumptions, state tradeoffs, and choose the lowest-risk path that meets the business goal.
Last updated: October 2026
Full business simulation: AI steering committee packet
You are advising an AI steering committee at a regional healthcare services company. The committee has four proposals: an employee knowledge assistant, a patient contact-center summarizer, a document intake workflow for insurance forms, and a predictive dashboard for appointment no-shows. The organization uses AWS for core applications, has a small cloud operations team, and has business analysts who can use managed tools but no dedicated ML engineering team for the first release. The committee wants a practical recommendation, not a technology showcase.
This simulation combines the five AIF-C01 domains. You must identify whether AI is useful, decide whether generative AI or traditional ML fits, choose AWS services at a practitioner level, describe responsible AI concerns, and request security and governance evidence. Do not treat this as a real exam question set. Treat it as a business lab where every answer needs a reason, an assumption, and a failure-mode check.
Proposal Likely AI pattern AWS services to consider Main risk question
Employee knowledge assistant Enterprise search or RAG Amazon Quick, Bedrock Knowledge Bases, Amazon OpenSearch Service, S3, IAM Identity Center Can permissions and authoritative sources be enforced?
Contact-center summarizer GenAI summarization and classification Amazon Transcribe, Amazon Bedrock, Guardrails, Comprehend, CloudWatch Are transcripts redacted, reviewed, and monitored for unsafe summaries?
Insurance document intake Document extraction and assisted review Textract, Bedrock, a human review queue, S3, KMS, Macie, CloudTrail Does a human approve high-impact or low-confidence outputs?
No-show prediction dashboard Traditional ML or no-code prediction SageMaker Canvas, SageMaker AI, Quick Sight, S3, Glue Are labels valid, features appropriate, and actions fair to patients?
Start with the employee knowledge assistant. The problem is finding trusted internal information. If the organization wants a managed employee assistant with connectors and permission-aware answers, Amazon Quick may be a strong first path. If builders need a custom application experience with generated answers from a specific corpus, Bedrock Knowledge Bases may fit. If the main need is search results rather than generated answers, Amazon OpenSearch Service can be considered (Amazon Kendra is no longer open to new customers). The committee should not approve indexing every shared folder until owners remove stale and restricted content.
For the contact-center summarizer, the flow may start with Amazon Transcribe to convert calls to text, then Bedrock to summarize, classify reason codes, and draft follow-up notes. Guardrails can help with unsafe content, prompt attacks, and sensitive information rules. The summary should be agent-reviewed before it becomes part of a customer record. The committee should ask what happens when audio quality is poor, when a customer gives protected information, when a summary omits a complaint, or when the model suggests an action the agent is not allowed to take.
For insurance document intake, Textract is the likely extraction service for forms and tables, while Bedrock can help summarize extracted text and flag missing fields. An internal review queue can route low-confidence or high-impact cases to humans. S3 with KMS, Macie, IAM, CloudTrail, and retention controls matter because insurance documents can contain sensitive personal information. The committee should reject any proposal where generated summaries become final determinations without review evidence.
For appointment no-show prediction, a traditional ML pattern may be more appropriate than generative AI. The business wants a risk score or dashboard, not creative text. SageMaker Canvas can let analysts experiment with a no-code prediction approach if the data is prepared. SageMaker AI can support a custom path later if builders need control. The fairness review is essential: using features that proxy for sensitive status can create harmful outreach patterns. The action should be supportive, such as reminder options, not punitive denial of care.
Committee decision workflow:
State the business outcome and non-AI baseline for each proposal.
Classify the AI type: search, RAG, generation, extraction, recommendation, forecasting, classification, or decision support.
Check data readiness, data permissions, and source ownership.
Choose the simplest AWS service path that meets the need and skill level.
Define human review, refusal behavior, and escalation for high-risk outputs.
Estimate cost and performance drivers before launch.
Require monitoring for quality, safety, usage, drift, errors, and business outcome.
Approve one or two bounded pilots instead of funding every idea at full scale.
A strong recommendation might approve the employee knowledge assistant for a narrow HR and IT corpus, approve the contact-center summarizer as agent-assist only, defer the document intake workflow until sample-document handling and reviewer evidence are designed, and require a fairness review before the no-show model pilot. This is not anti-AI. It is disciplined sequencing. The organization learns safely, proves value, and avoids turning unmanaged experiments into production obligations.
Simulation failure modes:
The committee picks Bedrock for every problem, including cases where search, Textract, Personalize, SageMaker Canvas, or a rules-based workflow is better.
The team assumes managed AWS services remove responsibility for IAM, privacy, logging, human review, and data quality.
The pilot measures demo quality but not business outcome.
Sensitive data appears in prompts, responses, feedback, or logs without retention and access review.
A model is changed without rerunning the evaluation set.
A prediction dashboard influences customers or employees without appeal, explanation, or fairness review.
Costs rise because pilots lack budgets, tags, owners, and shutdown criteria.
Review prompts before the quiz:
Which proposal is the safest first pilot and why?
Which proposal needs the most human review before production?
Which proposal is generative AI, and which is traditional prediction?
Which AWS managed service reduces build effort without removing governance responsibility?
What assumption would change your recommendation if it turned out to be false?