AIP-C01 lesson on RAG data preparation, vector-store design, retrieval tuning, prompt governance, and compliance-aware GenAI boundaries.
Many AIP-C01 misses happen before the prompt reaches the model. The real problem is often document quality, chunking, metadata, retrieval filters, prompt-template discipline, or an unsafe data boundary between source documents, embeddings, prompts, logs, and output.
The official Domain 1 outline includes data validation, vector-store design, retrieval mechanisms, prompt optimization, and compliance-aware data flow. In exam terms, the best answer usually improves the pipeline around the model, not the model alone.
Think in this order:
If a scenario says answers are stale, ungrounded, overbroad, or leaking sensitive material, the architecture probably failed in one of those layers.
Good retrieval depends on more than “put documents in a vector store.” The exam expects you to reason about:
If answer choices differ only by model size, but the prompt describes bad search relevance or stale documents, retrieval design is usually the real target.
RAG quality starts before embeddings. Weak ingestion creates weak retrieval even when the model is strong.
| Data issue | Better answer direction |
|---|---|
| duplicate, stale, or conflicting documents | validate sources, deduplicate, classify, and define freshness rules |
| long documents with mixed topics | chunk by semantic section instead of arbitrary oversized blocks |
| missing ownership or policy context | add metadata for owner, date, document type, sensitivity, tenant, and access group |
| regulated content | classify, encrypt, restrict retrieval, and control logging/retention |
| frequent source updates | automate re-indexing or incremental sync rather than manual reloads |
The exam trap is skipping directly to “use a bigger model.” If the vector store contains stale or poorly segmented material, a bigger model can produce a more fluent wrong answer.
AIP-C01 expects you to know what a vector database is, but the questions usually test design judgment:
| Design choice | Why it matters |
|---|---|
| embedding model | determines what semantic relationships can be retrieved well |
| chunk size and overlap | balances context precision against missing surrounding meaning |
| metadata schema | enables filtering by tenant, classification, date, product, role, or region |
| re-indexing process | keeps retrieved content aligned with source changes |
| encryption and access policy | protects embeddings and retrieved context, not only source documents |
| evaluation set | proves retrieval quality instead of relying on one manual search |
Amazon Bedrock Knowledge Bases can reduce integration work for AWS-native RAG patterns, but the exam still expects you to understand the underlying choices: data source, embedding, vector store, sync, retrieval, guardrails, and observability.
| Scenario clue | Strong first move |
|---|---|
| user asks with fuzzy language | semantic vector search |
| exact product code, policy ID, error code, or legal term matters | hybrid or lexical-aware retrieval |
| users must see only authorized documents | identity-aware metadata filters before generation |
| answers cite irrelevant sources | tune chunking, metadata, top-k, ranking, and reranking |
| answers are stale | source sync, freshness metadata, and re-indexing |
| answer is too generic | retrieve narrower context or improve prompt assembly, not just more context |
More context is not automatically better. Large context can increase cost, latency, and distraction. A strong answer retrieves the right context, not the most context.
Prompting on AIP-C01 is not just “write a clever instruction.” Production prompt work includes:
Prompt quality without prompt operations is not a production answer.
Strong prompt architecture separates sources of authority:
| Prompt part | Treat it as |
|---|---|
| system instruction | highest-priority behavior and safety rules |
| developer/application instruction | task format, output schema, and business constraints |
| retrieved context | evidence to use, not instructions to obey blindly |
| user input | request data, not trusted control text |
| tool output | external evidence that may still require validation |
This matters because prompt injection often hides inside retrieved documents or user text. The stronger answer constrains what retrieved text can do, validates output structure, and keeps privileged instructions outside user-controlled content.
When prompts change, production systems need:
If a scenario says a prompt update broke behavior, inspect the assembled prompt and variables before redesigning the model or retrieval architecture.
The exam repeatedly tests whether sensitive data can leak through the GenAI pipeline. Check all four layers:
| Layer | What can go wrong |
|---|---|
| source documents | overbroad collection or missing classification |
| embeddings and vector store | sensitive content becomes searchable outside intended scope |
| prompt assembly | one user or tenant can inject or retrieve another tenant’s data |
| model output and logs | protected content can be returned, cached, or retained too broadly |
| Risk | Strong control |
|---|---|
| tenant data leakage | authorization before retrieval plus tenant metadata filters |
| sensitive document exposure | classification, encryption, least privilege, and output filtering |
| prompt injection through retrieved content | delimiter discipline, instruction hierarchy, guardrails, and source validation |
| unsafe retention | retention policy for prompts, outputs, logs, traces, and evaluation data |
| audit requirement | log model version, prompt version, retrieved document IDs, and decision outcome |
Hybrid search is often stronger when exact terms, identifiers, codes, or policy names matter. Pure semantic similarity can miss the precise lexical cue that the user really needs. AIP-C01 likes questions where the answer is not “use more context,” but “improve retrieval ranking and filters.”
The best answer usually narrows access before generation:
If the scenario mentions regulated data, legal retention, or auditability, “just put everything into a vector index” is almost never strong enough.
If the model is hallucinating facts from internal content, first inspect retrieval and prompt assembly. If the answer choices only change model family while leaving bad chunks, weak filters, or poor context assembly untouched, those choices are usually distractors.