Module 6 · RAG and Enterprise AI

Enterprise Knowledge Bases

Enterprise knowledge bases organize governed business information for search, RAG, support, and decision assistance.

Article available nowVideo lesson coming later

This reading lesson is complete and can be studied independently. The video will be added here when it is published.

Core idea

Enterprise Knowledge Bases

Enterprise knowledge bases organize governed business information for search, RAG, support, and decision assistance.

RAG principle: Retrieval supplies evidence; generation turns that evidence into a useful response. Neither step guarantees correctness without evaluation.

Architecture diagram

Ingestion time

1Approved sources
2Identity + ACLs
3Sync and version
4Governed index

Query time

1Authenticated user
2Permission-aware retrieval
3Citations
4Audit and feedback

Practical example

Use the design in context

A bank indexes approved procedures but applies the user's document permissions during retrieval and records the cited source version.
Source qualityUse authoritative, current, permissioned information.
Retrieval qualityMeasure whether the right evidence appears near the top.
Answer qualityTest support, completeness, citations, and abstention.
OperationsMonitor freshness, latency, cost, attacks, and user feedback.

Failure map

01

Missing evidence

The required information was never ingested or is stale.

02

Poor chunk

The relevant fact is split from the context needed to interpret it.

03

Retrieval miss

Embedding, query, index, filter, or ranking fails to surface evidence.

04

Generation error

The model ignores, distorts, or exceeds retrieved evidence.

05

Permission leak

Retrieval returns content the user is not authorized to access.

06

Evaluation gap

The test set fails to represent real questions and failure costs.

AWS Certified AI Practitioner

Exam reasoning

  • Connect approved sources
  • Control access
  • Index current content
  • Trace answers to evidence
  • RAG adds external context at inference time; it does not retrain the foundation model.
  • Knowledge Bases, permissions, guardrails, citations, and evaluation address different layers of risk.

Key takeaways

  • Connect approved sources
  • Control access
  • Index current content
  • Trace answers to evidence

Check your understanding

  1. Can you explain this concept in two sentences without using jargon?
  2. Can you identify the input, process, output, and validation step in the example?
  3. Can you name one suitable use case and one case where another approach is better?
  4. Which risk or limitation should a responsible implementation address?

Research references

Public sources and further reading

This lesson is original educational writing informed by the public references below. Use the sources to explore definitions, technical details, and current AWS exam objectives.