Study guide
11.6 AWS AI Practitioner Final Mixed Review
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
11.6 AWS AI Practitioner Final Mixed Review
Key Takeaways Explain This Topic AI
Final mixed review should force switching across domains because real readiness depends on recognizing the cue before choosing the AWS concept or service.
A practitioner should be able to decide when AI is appropriate, which AWS service path fits, and what governance or security question must be asked.
The best review prompts include business value, data readiness, model behavior, cost, responsible AI, IAM, privacy, and monitoring.
Mixed review should end with concise service-selection, risk, and timing checklists rather than more unfocused reading.
Last updated: October 2026
Final mixed review: switch domains on purpose
The real challenge at the end of AIF-C01 study is not remembering one isolated definition. It is recognizing what kind of decision a scenario is asking you to make. A customer-support chatbot scenario may test generative AI, RAG, Bedrock, Guardrails, IAM, privacy, hallucination, and human review in the same paragraph. A forecasting scenario may test data suitability, model lifecycle, metrics, cost-benefit, and whether AI is appropriate at all.
Use final mixed review to practice switching domains. Do not label every practice prompt before answering it. Read the scenario, identify the cue, and then decide which domain is most active. If the cue is labeled historical data and prediction, think supervised learning and business metrics. If the cue is current private documents, think RAG and Knowledge Bases. If the cue is unsafe output or sensitive data in prompts, think responsible AI, Guardrails, IAM, privacy, and logging.
Scenario cue Likely concept or service Practitioner question
Need current company policy answers RAG with Amazon Bedrock Knowledge Bases Are sources authoritative, permissioned, current, and cited?
Need managed foundation model access Amazon Bedrock Which model balances quality, latency, cost, modality, Region, and governance?
Need enterprise assistant for workplace tasks Amazon Quick where appropriate What data and permission boundaries apply?
Need no-code business ML exploration SageMaker Canvas Is the data suitable and is a managed no-code path enough?
Need custom ML development control SageMaker AI Is the team ready for builder ownership, lifecycle, and operations?
Need speech, translation, image, document, or text extraction Managed AI services such as Transcribe, Translate, Rekognition, Textract, or Comprehend Does a purpose-built service avoid overbuilding?
Need content safety or topic control Amazon Bedrock Guardrails and review workflow What should be blocked, masked, refused, or escalated?
Need auditability and access control IAM, CloudTrail, CloudWatch, KMS, AWS Config, and governance services Who can access data, who can invoke models, and what is logged?
Ten final scenario questions to ask yourself
Is AI useful here, or would deterministic rules, search, reporting, or a normal workflow be safer?
What data is needed, and is it labeled, current, clean, permissioned, and relevant?
Is the problem classification, summarization, generation, retrieval, forecasting, recommendation, extraction, translation, speech, image analysis, or action orchestration?
Does the scenario need a managed AI service, Amazon Bedrock, Amazon Quick, SageMaker AI, SageMaker Canvas, or no AI service at all?
If generative AI is involved, how will the team handle hallucination, context limits, prompt injection, unsafe output, and human review?
If private knowledge is involved, should the design use RAG before assuming fine-tuning?
If actions are involved, what API, permission, validation, confirmation, logging, and rollback controls are required?
Which responsible AI issue is most visible: fairness, explainability, privacy, safety, transparency, accountability, or monitoring?
Which security or governance control is missing: IAM, least privilege, encryption, logging, CloudTrail, CloudWatch, Config, KMS, Secrets Manager, Macie, Artifact, Inspector, Trusted Advisor, or retention policy?
What business metric proves the solution is worth using: accuracy, AUC, F1, cost, latency, ROI, customer satisfaction, user feedback, or reduced manual effort?
Final service-boundary refresh
Amazon Bedrock is your managed foundation model anchor. It can support model choice, prompt testing, inference, Knowledge Bases, AI agents, Guardrails, evaluation, and customization features where supported. It does not remove the need for IAM, data governance, cost planning, monitoring, or human review. If a scenario says the team wants generative AI without managing model-serving infrastructure, Bedrock is often the starting point.
Amazon SageMaker AI is broader ML builder territory. It appears when a team needs custom model development, training, experiments, notebooks, deployment options, or ML lifecycle control. The AIF-C01 target candidate does not need to implement those pipelines, but should know when the requirement has moved beyond a simple managed foundation model application.
Purpose-built managed AI services remain important. Amazon Comprehend can help with text analysis. Amazon Rekognition can analyze images and video. Amazon Textract extracts text and data from documents. Amazon Transcribe converts speech to text. Amazon Translate handles translation. Amazon Lex supports conversational interfaces. Amazon Polly converts text to speech. Amazon Personalize supports recommendations. Human review workflows catch uncertain predictions (AWS's managed service for this, Amazon A2I, is no longer open to new customers).
Final risk refresh
Responsible AI is not a separate moral appendix. It changes the answer. A fast model that produces biased, unsafe, unexplained, or unreviewed outputs may be the wrong choice. Privacy matters when prompts contain sensitive information. Transparency matters when users need to know that AI is involved. Accountability matters when a business process acts on generated recommendations.
Security and governance are also part of AI service selection. The organization must decide who can invoke models, which data can be used, how prompts and outputs are logged, how keys and secrets are protected, how suspicious use is monitored, and how policies are reviewed. AWS services such as IAM, KMS, Secrets Manager, CloudTrail, CloudWatch, AWS Config, Artifact, Inspector, Trusted Advisor, and Macie may appear as controls around the AI workflow.
Final readiness checklist:
Explain every official domain in one or two sentences.
Recreate the domain weights from memory and give extra review time to the 28% foundation model applications domain.
Answer every timed practice item, because blanks are incorrect and guessing has no penalty.
Use official AWS practice resources and avoid exam dumps or live-question claims.
Know that the exam is 90 minutes, 65 questions, and uses a 100-1000 scale with 700 as the minimum passing score.
Know that certification is valid for 3 years and that failed attempts require a 14-calendar-day wait before retake.
A strong final mixed review should feel practical. You are not trying to become an ML engineer in one night. You are proving that you can recognize AI use-case fit, AWS service fit, model and data risk, responsible AI issues, and security governance boundaries at a foundational practitioner level.