Study guide
10.4 Enterprise Search, RAG, and Knowledge Management 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.4 Enterprise Search, RAG, and Knowledge Management Lab
Key Takeaways Explain This Topic AI
Enterprise search and RAG projects succeed only when source ownership, permission enforcement, metadata, freshness, and citation behavior are designed before launch.
Amazon Quick, Amazon OpenSearch Service, and Bedrock Knowledge Bases solve overlapping but different knowledge-access problems; Amazon Q Business and Amazon Kendra are no longer open to new customers.
Prompt injection can live inside documents, tickets, wiki pages, or emails, so retrieved content should not be treated as trusted instructions.
The best enterprise knowledge lab tests retrieval quality, access boundaries, stale content, conflicting sources, and answer refusal for unsupported questions.
A decision log should state which corpus is authoritative, how indexing is refreshed, who can see each source, and how users report bad answers.
Last updated: October 2026
Lab scenario: enterprise knowledge assistant
A growing company has policy PDFs in S3, engineering runbooks in a wiki, support tickets in a case system, onboarding material in shared drives, and old process documents in several folders. Employees ask the same questions repeatedly because they do not know which source is current. Leadership wants an internal assistant that answers questions, cites sources, respects permissions, and helps knowledge owners find stale content. The pilot audience is employees, not external customers.
The first design question is whether the organization needs search, RAG, or a broader managed assistant. Search returns ranked documents or passages. RAG retrieves relevant context and asks a model to answer from it. A managed enterprise assistant can add connectors, conversational experience, and permission-aware knowledge access. These options overlap, but the correct choice depends on the user experience, source systems, answer style, security model, and operations team.
Need AWS option to consider When it fits
Managed enterprise assistant Amazon Quick Employees need a managed AI assistant across connected business sources, with knowledge-base and document-level access controls where supported.
Search and vector search Amazon OpenSearch Service Users need search results, including similarity search over embeddings, rather than generated answers.
Custom generative answer with private corpus Amazon Bedrock Knowledge Bases Builders want RAG for an app, API, agent, or custom workflow using approved data sources.
Simple document browsing S3, OpenSearch, wiki search, or existing portal The problem is discoverability, not generation.
Data warehouse questions Redshift, Athena, Quick Sight, or supported structured retrieval paths Users need governed analytics, not free-form answers from mixed documents.
Start with a source inventory. List each repository, owner, content type, audience, update cadence, classification, retention rule, and access model. Mark which sources are authoritative and which are legacy. A common failure mode is indexing everything because it is easy, then watching the assistant answer from old onboarding decks or draft legal text. A knowledge assistant is only as trustworthy as the content lifecycle behind it.
Permissions need direct testing. If the HR policy folder includes compensation documents, the assistant must not expose those documents to all employees. If engineering runbooks include incident response steps, access may depend on team or role. Permission enforcement can use the managed service capability, source-system permissions, IAM, application authorization, metadata filters, source partitioning, or separate corpora. The lab should include two users with different access and the same question. The expected result is different retrieved content where permissions differ.
RAG design should include metadata and citation rules. Metadata such as department, region, product, effective date, source owner, document status, and audience helps retrieval choose the right answer. Citations help users verify. The prompt should instruct the model to answer only from retrieved sources, include source links where available, and state when the answer is not found. It should not turn one weak passage into a confident enterprise policy.
Prompt injection is an enterprise search problem, not only a chatbot problem. A ticket, wiki page, or document can contain text telling the model to ignore instructions, reveal hidden prompts, or exfiltrate data. Retrieved content should be treated as data, not as higher-priority instructions. Guardrails, prompt design, tool limits, source sanitation, and least privilege all help. If the assistant can take actions, action permissions must be separate from search permissions.
Decision log example:
Pilot corpus: HR public policies, IT onboarding guides, and product support runbooks approved by their owners.
Excluded corpus: draft legal documents, customer contracts, employee records, and old migration folders.
Service path: Amazon Quick for managed employee assistant, or Bedrock Knowledge Bases if the team needs a custom app experience.
Freshness rule: content owner must update or retire documents; indexes refresh on a defined schedule.
Permission test: employee, manager, HR partner, and engineer roles each run the same set of questions.
Bad-answer process: users can flag answers, and owners review retrieval source, model response, and corpus quality.
Failure modes to test:
The assistant answers from a superseded policy because effective date metadata is absent.
The assistant retrieves a document the user should not see.
The assistant gives a generated answer without citations for a policy question.
Conflicting sources exist and the answer hides the conflict.
A wiki page contains prompt injection text and the assistant follows it.
A source connector fails silently and employees rely on incomplete answers.
The answer is correct for one country but wrong for another.
Review prompts before the quiz:
Which source is authoritative when two documents conflict?
Who owns stale content removal, not just assistant tuning?
Which user roles must be tested for permission boundaries?
Where should the assistant return search results instead of a generated answer?
What operational metric shows knowledge management is improving: fewer repeat tickets, faster onboarding, higher search success, or fewer flagged answers?