Study guide
10.1 Customer Support GenAI Assistant Lab
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.1 Customer Support GenAI Assistant Lab
Key Takeaways Explain This Topic AI
A support assistant should start with a bounded workflow, approved knowledge sources, measurable support outcomes, and a human escalation path.
Amazon Bedrock with Knowledge Bases and Guardrails is a common managed pattern for grounded answers, but Amazon Lex, Transcribe, Comprehend, and existing ticketing APIs can also fit parts of the workflow.
The main practitioner risks are hallucinated answers, stale source content, prompt injection, accidental disclosure of customer data, and unclear accountability for generated responses.
A decision log should capture model choice, retrieval design, guardrail settings, data handling, escalation rules, cost assumptions, and operational owners.
Successful pilots test normal questions, ambiguous requests, unauthorized actions, unsafe content, missing sources, and downstream system failures.
Last updated: October 2026
Lab scenario: support assistant for a SaaS help desk
A midmarket SaaS company wants to reduce agent handle time and improve answer consistency. Support agents currently search a product documentation site, internal troubleshooting articles, release notes, and a ticketing system. Leadership asks for a generative AI assistant that drafts answers, cites approved sources, summarizes customer conversations, and suggests when a case should be escalated. The business does not want the assistant to make billing adjustments or close cases automatically during the pilot.
The first practitioner move is to define the job clearly. This is not a general chatbot project. The pilot should answer questions from approved support content, draft agent-facing replies, summarize case history, and identify missing facts. Customer-facing automation may come later only after quality, safety, and escalation controls are proven. A non-builder should ask what the assistant is allowed to do, what it must refuse, and who remains accountable for the final customer response.
Design decision Practical choice Why it matters
Primary generative layer Amazon Bedrock Managed access to foundation models, evaluation paths, Knowledge Bases, and Guardrails, with agents built on Amazon Bedrock AgentCore.
Grounding source Amazon Bedrock Knowledge Bases over approved S3 or connector content Keeps answers tied to current product articles instead of relying only on model memory.
Voice or call summaries Amazon Transcribe before summarization Converts calls to text so the assistant can summarize and extract follow-up items.
Intent capture Amazon Lex or existing support UI Useful when a conversational front end is needed, but not required for an agent-assist panel.
Entity and sentiment signals Amazon Comprehend where simple NLP extraction is enough Can classify text, find entities, and detect sentiment without building a custom model.
Safety controls Amazon Bedrock Guardrails plus application rules Helps block unsafe topics, prompt attacks, and sensitive data exposure.
Audit and operations CloudTrail, CloudWatch, KMS, IAM, and ticket metadata Supports investigation, access control, encryption, and trend monitoring.
Build the pilot as an agent-assist experience first. A support agent opens a case, selects Ask Assistant, and the app sends the case subject, product, customer tier, and a redacted issue description to Bedrock. The Knowledge Base retrieves approved passages from product docs and troubleshooting articles. The model drafts a response with citations and a confidence note. The agent edits the draft, sends it through the normal support tool, and tags whether the answer was useful. This design keeps a human in the loop while the team learns where the assistant helps.
The decision log should be written before implementation starts. Record the selected foundation model, backup model, source repositories, chunking and metadata plan, PII handling rule, guardrail policies, logging destinations, retention settings, and pilot metrics. Include business metrics such as average handle time, first-contact resolution, escalation rate, agent satisfaction, and customer complaint rate. Also include a stop condition, such as repeated unsupported answers in a regulated topic or evidence that agents are copying drafts without review.
End-to-end lab workflow:
Choose two support categories with high volume and low regulatory risk, such as login issues and product setup questions.
Curate approved articles in S3 or a supported content source, remove stale documents, and assign a content owner.
Create metadata for product, version, audience, region, and effective date so retrieval can filter the right sources.
Configure a Bedrock Knowledge Base and test retrieval separately from generation.
Compare two candidate models with the same prompt template, source set, and scoring rubric.
Add Guardrails for prompt attacks, unsafe content, denied topics, and sensitive information handling.
Integrate the draft into the support UI with citations, refusal behavior, feedback capture, and escalation options.
Monitor usage, latency, cost, blocked prompts, retrieval misses, and agent edits during the pilot.
Common failure modes should be reviewed as part of the lab, not discovered after launch. The assistant may cite the wrong product version because metadata is missing. It may answer from an old article because the content owner did not retire stale pages. It may hallucinate when retrieval returns weak passages. It may leak customer details if prompts, logs, or feedback fields are not redacted. It may follow a prompt injection hidden in a customer email. It may suggest a refund or credit even though the pilot explicitly excludes financial actions.
The fallback plan is as important as the happy path. If retrieval fails, the assistant should say that the approved sources do not contain enough information and offer search results or escalation. If a prompt is blocked, the UI should show a clear internal message and route the case normally. If Bedrock invocation is throttled or unavailable, agents should continue with existing tools. If citations disagree, the assistant should surface the conflict rather than inventing a tie-breaker.
Review prompts before the quiz:
Which support categories are safe enough for a first pilot, and which should stay human-only?
Which fields must be redacted before prompts or logs are stored?
How will the team know whether a bad answer came from retrieval, prompt design, model choice, or stale source content?
What action is the assistant explicitly not allowed to perform?
Who owns article freshness, guardrail tuning, cost review, and support agent training?