Amazon Bedrock Knowledge Bases for RAG with Source Attribution

Q: Why is DynamoDB wrong for storing reasoning traces?

DynamoDB requires custom schema design and management, increasing operational overhead compared to simply logging to S3.

Q: Does Bedrock Knowledge Bases support step-by-step reasoning?

Knowledge Bases handles retrieval and attribution; the LLM (Claude) generates reasoning. The combination in Option A satisfies both via managed integration.

Implement application integration patterns and development tools.

Answer Correct answer: A — Use Amazon Bedrock Knowledge Bases with source attribution enabled to retrieve information and link data claims automatically.

A company is building an AI advisory application by using Amazon Bedrock. The application will provide recommendations to customers. The company needs the application to explain its reasoning process and cite specific sources for data. The application must retrieve information from company data sources and show step-by-step reasoning for recommendations. The application must also link data claims to source documents and maintain response latency under 3 seconds. Which solution will meet these requirements with the LEAST operational overhead?

Use Amazon Bedrock Knowledge Bases with source attribution enabled. Use the Anthropic Claude Messages API with RAG to set high-relevance thresholds for source documents. Store reasoning and citations in Amazon S3 for auditing purposes. Correct Answer
Use Amazon Bedrock with Anthropic Claude models and extended thinking. Configure a 4,000-token thinking budget. Store reasoning traces and citations in Amazon DynamoDB for auditing purposes.
Configure Amazon SageMaker AI with a custom Anthropic Claude model. Use the model's reasoning parameter and AWS Lambda to process responses. Add source citations from a separate Amazon RDS database.
Use Amazon Bedrock with Anthropic Claude models and chain-of-thought reasoning. Configure custom retrieval tracking with the Amazon Bedrock Knowledge Bases API. Use Amazon CloudWatch to monitor response latency metrics.

Community Insight

The exam tests the ability to distinguish between custom-built AI architectures and fully managed service integrations, identifying that 'least operational overhead' is best achieved by using native features like source attribution rather than manual auditing pipelines.

This question evaluates the design of a GenAI advisory application using Amazon Bedrock, specifically focusing on Retrieval-Augmented Generation (RAG) and operational efficiency. The correct solution leverages fully managed services to minimize overhead while meeting strict latency and attribution requirements.

Many candidates incorrectly choose Option B or D because they focus heavily on the 'explain reasoning' requirement, overlooking that 'least operational overhead' disqualifies custom storage solutions (DynamoDB/RDS) and manual monitoring setups (CloudWatch). They also misinterpret 'extended thinking' as the primary solution for attribution rather than just reasoning traces.

Community Discussion (10 comments)

SSSam26 👍 1 Selected: B

Why A is Wrong ? - No explicit reasoning mechanism : KB + source attribution provides CITATIONS but not step-by-step REASONING traces - Claude Messages API ≠ reasoning traces Why B is Correct ? - Explain reasoning process - Step-by-step reasoning - Audit trail : Reasoning traces + citations stored in DynamoDB (fast read/write) ** Extended thinking is the ONLY Bedrock feature that produces auditable, step-by-step reasoning traces. No other approach gives you the model's actual reasoning process as a first-class output.

Chibuzo1 👍 2 Selected: B

RequirementHow Option B Addresses ItStep-by-step reasoningExtended thinking provides explicit, visible reasoning traces nativelyCite specific sourcesClaude models with extended thinking naturally attribute claims to sourcesRetrieve from company dataBedrock Knowledge Bases integration handles RAG retrievalResponse latency < 3 seconds4,000-token thinking budget is appropriately scoped — large budgets (e.g. 16K tokens) would risk breaching the 3s SLAAudit trailDynamoDB stores reasoning traces and citations with low-latency writesLeast operational overhead

Chibuzo1 👍 3

Correct answer is A Option A leverages Amazon Bedrock Knowledge Bases as a fully managed vector store with built-in source attribution—eliminating the need to architect custom retrieval, citation, or reasoning pipelines. This is purpose-built for RAG scenarios and minimizes operational complexity while meeting all stated requirements.

bonds 👍 3 Selected: D

I'd go with either B or D. A is not the correct answer. D could be it because CoT B is likely because of extended thinking which is something Claude models do.

potters7 👍 1 Selected: A

I dont think any answer is perfect. Without least operational overhead I'd go with D as A lacks "explain its reasoning process".

potters7 👍 2 Selected: A

I believe A addresses the most req. I did think B but with 4k token thinking + response that might not address the response times.

ArunRav 👍 2 Selected: A

Amazon Bedrock Knowledge Bases is a fully managed capability hence we can use it for this use case as it need minimal operational overhead.

eesa 👍 2 Selected: A

Opción A - MEJOR SOLUCIÓN: ✅ Source attribution nativa: Knowledge Bases proporciona citaciones automáticas a documentos fuente ✅ RAG integrado: Recupera información de fuentes de datos de la empresa automáticamente ✅ Baja latencia: Optimizado para respuestas rápidas (<3s) ✅ Mínimo overhead operacional: Servicio completamente administrado ✅ Razonamiento con Claude: El modelo explica su proceso de pensamiento naturalmente ✅ Auditoría simple: S3 para almacenamiento de logs es straightforward

GiorgioGss 👍 2 Selected: A

"link data claims to source documents" - RAG aka Knowledge base

67bdb19 👍 1 Selected: B

If I had to guess, I’d pick B based on the wording of the question.

Comments & Corrections

No comments yet — spotted an error or have a note? Share it below.

Expert Analysis

Why the Answer Is Correct

Option A is the correct answer because it utilizes Amazon Bedrock Knowledge Bases, a fully managed vector store that natively handles retrieval and source attribution. This directly addresses the requirement to "link data claims to source documents" without requiring custom code for citation generation. By using the Anthropic Claude Messages API with RAG, the system can provide recommendations efficiently. Storing reasoning and citations in Amazon S3 is a standard, low-overhead pattern for auditing compared to managing complex NoSQL schemas in DynamoDB or relational databases in RDS.

Why the Other Options Are Wrong

Option B is incorrect because storing reasoning traces in Amazon DynamoDB requires significant operational overhead to design the schema, manage indexing, and handle scaling, violating the "least operational overhead" constraint. Additionally, extended thinking alone does not guarantee source attribution from company data sources unless integrated with a knowledge base. Option C involves SageMaker AI and Lambda, which represents a high-operational-cost custom build compared to the managed Bedrock experience. Option D suggests using CloudWatch for latency metrics, which adds operational burden for monitoring, whereas the question asks for the solution to meet requirements, not just monitoring; furthermore, custom retrieval tracking via the API is more work than using the built-in capabilities of Knowledge Bases.

Community Comment Notes

Community consensus strongly favors Option A, with multiple users noting that Bedrock Knowledge Bases are purpose-built for this exact scenario. One user noted, "Knowledge Bases provides automatic citations," highlighting the key differentiator. Another commenter pointed out that Option B's use of DynamoDB introduces unnecessary complexity for simple audit trails. While some users debated the reasoning aspects of Extended Thinking, the prevailing view is that managed attribution outweighs the manual tracing efforts in other options.

Official Reference

https://docs.aws.amazon.com/bedrock/latest/userguide/knowledge-base.html

Exam Strategy

When questions emphasize "least operational overhead" or "fully managed," prioritize AWS native PaaS offerings (like Knowledge Bases, Comprehend, Translate) over custom integrations involving EC2, SageMaker notebooks, or manual Lambda/DynamoDB plumbing. Look for keywords like "source attribution" which map directly to specific feature flags in managed services.

Frequently Asked Questions

Why is DynamoDB wrong for storing reasoning traces?

DynamoDB requires custom schema design and management, increasing operational overhead compared to simply logging to S3.

Does Bedrock Knowledge Bases support step-by-step reasoning?

Knowledge Bases handles retrieval and attribution; the LLM (Claude) generates reasoning. The combination in Option A satisfies both via managed integration.

More AIP-C01 FAQ →

Related Analysis

Practice All AIP-C01 Questions

Access 110 questions with complete answers and detailed explanations.

View Full AIP-C01 Practice Test →

← Back to AIP-C01 Study Guide