Study guide
6.2 Knowledge Bases, RAG, Data Sources, and Grounding
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
6.2 Knowledge Bases, RAG, Data Sources, and Grounding
Key Takeaways Explain This Topic AI
Retrieval Augmented Generation uses relevant retrieved context to improve model responses without retraining the foundation model on private data.
Amazon Bedrock Knowledge Bases manages much of the RAG workflow, including data source connection, ingestion, embeddings, retrieval, and response generation.
RAG quality depends on source quality, chunking, metadata, embedding model choice, retrieval settings, permissions, citations, and evaluation against expected answers.
Knowledge Bases can connect to unstructured sources and structured stores, but data readiness and access boundaries still belong to the organization.
Grounding is strongest when responses cite retrieved sources, refuse out-of-scope answers, and are tested with realistic questions and known failure cases.
Last updated: October 2026
RAG and Knowledge Bases
Foundation models know patterns from training, but they do not automatically know a company's current policies, product catalog, contract language, or support procedures. Retrieval Augmented Generation, usually shortened to RAG, adds relevant information at inference time. The application retrieves passages, records, or query results from approved data sources, then asks the model to answer using that context. This is often a better first customization step than fine-tuning when the problem is factual freshness or private knowledge.
Amazon Bedrock Knowledge Bases provides a managed RAG capability. A team can connect supported data sources, ingest content, convert content into embeddings, store or use a vector index, retrieve relevant results, and generate grounded responses. The application can use Retrieve to return sources or RetrieveAndGenerate to retrieve context and produce a natural-language answer. An AI agent can also query a knowledge base when it needs enterprise knowledge before deciding what action to take.
RAG component What it does Practitioner risk to ask about
Data source Holds the raw information, such as documents or structured data Is it current, approved, permissioned, and clean enough?
Ingestion Reads and processes the data source How often do updates sync and who owns failed ingestion?
Chunking and parsing Breaks content into retrievable pieces Are chunks too small to carry meaning or too large to retrieve precisely?
Embedding model Turns text or multimodal content into vectors Does the model support the language, modality, and domain terms?
Vector store or index Stores embeddings for similarity search Are metadata filters, access, encryption, and capacity planned?
Generation model Writes the answer from retrieved context Does it cite sources and refuse unsupported claims?
Data source selection matters. Bedrock Knowledge Bases supports unstructured sources such as Amazon S3 and several connectors, plus custom ingestion patterns. AWS documentation also describes structured data store support where natural language can be converted into SQL-like queries through a query engine for supported stores. A practitioner does not need to build the pipeline, but should know that a PDF repository, a wiki, a CRM, and a data warehouse have different readiness, security, and freshness issues.
RAG can reduce hallucination, but it is not magic. If the source documents contradict each other, are outdated, or contain marketing claims mixed with policy text, the generated answer can still be wrong. If chunking separates a definition from its exception, retrieval can miss the nuance. If metadata filters are missing, a user might retrieve a document for the wrong product, country, customer tier, or effective date. The quality of RAG is only as strong as the retrieval path and the governance around the source content.
Grounding means the answer is tied to retrieved evidence. Good RAG applications show citations, source names, dates, or links so a human can verify the answer. They also tell the model how to behave when sources do not support the answer. In many business workflows, the best answer is not a guess. It is a clear response such as the available sources do not contain enough information, followed by a handoff to a human or a search result list.
Permissions are a common scenario trap. A knowledge base may index content from multiple teams, but the application still needs to enforce who can ask about what. Do not approve a design where every employee can retrieve every HR, legal, or customer document simply because the vector store can find it. The app architecture should preserve access boundaries using IAM, application authorization, metadata filters, source partitioning, or separate knowledge bases where appropriate.
RAG decision workflow:
Identify the knowledge gap: current facts, private procedures, domain vocabulary, or regulated references.
Confirm the data source is authoritative and has an owner for updates and removal.
Choose the ingestion pattern, chunking strategy, metadata, embedding model, and vector store design.
Test retrieval before judging generation. The model cannot answer well from missing context.
Add response rules for citations, refusal, uncertainty, and source date handling.
Evaluate with known questions, expected source passages, and examples where the answer should not be found.
Monitor retrieval misses, user feedback, source drift, and cost as the corpus grows.
Scenario: a benefits team wants an employee assistant. Bedrock with a Knowledge Base can retrieve handbook content, policy updates, and FAQ pages. The approval questions are whether HR owns the source corpus, whether old policy PDFs are excluded, whether country-specific metadata is applied, whether sensitive employee records are outside the corpus, and whether the assistant refuses individualized legal or medical advice. The model is only one piece of the control design.
Scenario: a field service team wants technicians to ask about equipment repair steps. RAG is valuable because manuals, service bulletins, and part numbers change. The knowledge base should include current manuals, use metadata for model number and region, and return citations. If the answer could create safety risk, the workflow should require human confirmation or link directly to the official procedure rather than presenting generated text as final authority.
AWS Skill Builder practice should include testing retrieval failures. Upload a small, non-sensitive sample corpus in a lab environment if provided, ask questions that are directly answered, partly answered, and not answered, then compare retrieved chunks with generated text. The key skill is seeing whether a bad answer came from bad retrieval, bad instructions, bad data, or an unsuitable model.