Amazon AWS Certified Generative AI Developer - Professional (AIP-C01)

✅

Reasoning: Bedrock Guardrails offer near real-time contextual grounding checks to detect hallucinations with minimal custom work. Storing logs enables text output analysis. CloudWatch anomaly detection on token usage metrics efficiently identifies abnormal consumption, providing early cost warnings with low maintenance overhead. This directly meets all specified requirements. ❌ Why the other choices are incorrect:

• Option A is incorrect: Using AWS Glue and Amazon Athena for hallucination detection requires significant custom NLP development and is not near real-time, violating the minimal custom development constraint.
• Option B is incorrect: Bedrock evaluation jobs are for offline assessment, not real-time production monitoring. A Lambda function adds custom development and maintenance that CloudWatch Anomaly Detection handles natively.
• Option D is incorrect: AWS CloudTrail logs API calls, not detailed token usage for quality analysis. SageMaker Model Monitor requires extensive custom development for GenAI hallucination detection, violating the minimal effort constraint.

✅

Reasoning: Amazon Bedrock AgentCore natively manages memory and session-aware

Reasoning: , fulfilling requirements for state preservation. Its built-in identity support, event handling, and observability make it a highly scalable, managed service for access control and various invocation patterns.

Reasoning: Registering Lambda functions and REST APIs via Amazon API Gateway and Amazon EventBridge as actions for Amazon Bedrock AgentCore enables it to directly invoke these tools. This eliminates custom orchestration, simplifying integration and ensuring a scalable, managed solution for leveraging existing logic. ❌ Why the other choices are incorrect:

• Option C is incorrect: Using AWS Step Functions and Amazon SQS for orchestration and DynamoDB for state introduces custom complexity and operational overhead, duplicating or complicating functionalities Bedrock AgentCore provides natively for agent orchestration and memory.
• Option D is incorrect: Deploying

Reasoning: logic on Amazon ECS with Amazon Aurora for memory and identity requires significant custom development and operational management, making it less scalable and more complex than leveraging a fully managed service like Bedrock AgentCore.

• Option E is incorrect: Building a custom RAG pipeline with Lambda orchestration and S3 for agent state involves extensive custom coding for tool invocation and state management, which is less scalable and increases maintenance compared to Bedrock AgentCore's integrated features.

✅

Reasoning: An Amazon Bedrock knowledge base combined with Retrieval Augmented Generation (RAG) is the definitive solution to ground the LLM with the company's specific product catalog. This prevents the model from hallucinating or recommending unavailable/irrelevant products. The latency optimization directly addresses the slow recommendation generation. ❌ Why the other choices are incorrect:

• Option A is incorrect: Amazon Bedrock Guardrails focus on safety policies (e.g., hate speech, violence), not factual grounding to an external product catalog. Automated

Reasoning: checks are not a standard Bedrock feature for this type of factual grounding.

• Option B is incorrect: Relying solely on prompt engineering for a large, dynamic product catalog with unique interactions is prone to hallucinations and insufficient to ensure factual accuracy. While streaming reduces perceived latency, it doesn't solve the core grounding issue.
• Option D is incorrect: Storing data in OpenSearch is a component, but validating recommendations after generation is reactive and inefficient. Caching responses with DynamoDB is ineffective for "unique" interactions, and it doesn't proactively prevent incorrect recommendations.

✅

Reasoning: Amazon Bedrock Knowledge Bases with source attribution enabled directly addresses the requirements for retrieving information from company data sources, citing specific sources, and linking claims to source documents with the least operational overhead due to its fully managed nature. Anthropic Claude models are effective for

Reasoning: . Storing audit logs in S3 is a standard, low-overhead practice. ❌ Why the other choices are incorrect:

• Option B is incorrect: While using Claude models, it lacks a managed solution like Knowledge Bases for RAG and automated source attribution, leading to higher operational overhead for implementation.
• Option C is incorrect: Using Amazon SageMaker AI with a custom Claude model significantly increases operational overhead compared to using Bedrock's fully managed service. Custom citation logic via RDS and Lambda also adds complexity.
• Option D is incorrect: While using Bedrock Knowledge Bases is correct, "custom retrieval tracking" is unnecessary; Bedrock Knowledge Bases natively provide source attribution. Monitoring with CloudWatch doesn't address the core functional requirements.

✅

Reasoning: Amazon Bedrock Prompt Management natively provides version control and parameterized prompt templates. AWS CloudTrail ensures detailed audit logging of prompt activities. IAM policies are the standard mechanism to control approval permissions for prompt versions. This combination directly addresses all specified requirements for robust governance. ❌ Why the other choices are incorrect:

• Option A is incorrect: Amazon Bedrock Studio offers basic templates but lacks advanced versioning or built-in approval workflows. DynamoDB, Lambda, and CloudWatch would require extensive custom development to meet the governance requirements.
• Option C is incorrect: Storing prompts in S3 with tags for version control is not a robust, scalable solution for hundreds of templates. AWS Step Functions provides workflows but not integrated prompt management capabilities, making it a custom, less efficient approach.
• Option D is incorrect: Amazon SageMaker Canvas is a low-code ML platform, not designed for enterprise-level Bedrock prompt governance. AWS CloudFormation manages infrastructure, not content versioning. AWS Config enforces compliance rules, not content approval policies for prompts.

✅

Reasoning: An SCP restricting model use to approved ARNs addresses "only approved models". Requiring a guardrail identifier in the SCP ensures the company's content filtering policy is always applied.

Reasoning: Creating a custom Bedrock guardrail with a block filtering policy directly addresses preventing specific topics/proprietary information. Deploying it via CloudFormation StackSets ensures central, consistent deployment across all accounts. ❌ Why the other choices are incorrect:

• Option A is incorrect: While permissions boundaries can enforce guardrail usage, they don't define the guardrail's content (block policy). Managing PBs on each employee role is less centralized for content filtering than a single, deployed guardrail.
• Option C is incorrect: This option uses an SCP for guardrail enforcement but a permissions boundary for model restriction. An SCP is generally more effective for centralized model restriction across an organization than individual PBs. Crucially, it still lacks the step of creating the guardrail's actual content filtering policy.
• Option E is incorrect: A mask filtering policy replaces sensitive content with asterisks. The requirement is to "prevent specific topics and proprietary information from being included", which implies blocking the content, not just masking it. A block filtering policy (as in D) is required.

✅

Reasoning: An AWS Step Functions Standard workflow is ideal for orchestrating long-running, stateful processes like ML pipelines. S3 can trigger a Lambda function, which then initiates the Step Functions workflow. SageMaker Pipelines are purpose-built for MLOps, handling automated re-training and re-deployment efficiently. This architecture provides robust, automated, and observable continuous integration/continuous delivery (CI/CD) for machine learning models. ❌ Why the other choices are incorrect:

• Option A is incorrect: Invoking a SageMaker AI model endpoint uses real-time inference and does not trigger model re-training or re-deployment.
• Option B is incorrect: While viable, "webhook handlers" are unnecessarily complex for direct S3-to-Lambda integration. Step Functions offers more explicit state management and orchestration capabilities for complex MLOps workflows compared to purely EventBridge-driven execution.
• Option C is incorrect: AWS Step Functions Express workflows are for short-duration, high-event-rate tasks, not long-running ML training and deployment. SageMaker Autopilot might fit, but Express Workflows are not suitable for this orchestration.

✅

Reasoning: AWS Step Functions orchestrates a serverless workflow using Amazon Comprehend for PII detection and Amazon Bedrock for generating embeddings. Integrating directly with Amazon OpenSearch Serverless provides a fully managed, scalable, and low-operational-overhead vector store. This combination effectively processes 50GB within 4 hours while minimizing management burden. ❌ Why the other choices are incorrect:

• Option A is incorrect: While serverless, managing Lambda concurrency and memory settings for 50GB within 4 hours can incur significant optimization effort and operational overhead.
• Option B is incorrect: "PII detection scripts" implies custom code, adding operational overhead. Amazon SageMaker Processing requires managing SageMaker job resources.
• Option C is incorrect: Deploying and managing an Amazon EMR cluster, including Spark UDFs, represents high operational overhead, directly contradicting the requirement.

✅

Reasoning: Amazon MemoryDB, using Redis Stack, is excellent for high-performance, in-memory vector storage. The HNSW algorithm provides an optimal balance of very high accuracy (recall) and superior performance for similarity searches, crucial for RAG applications. Vertical scaling directly boosts computational resources for complex vector operations. ❌ Why the other choices are incorrect:

• Option A is incorrect: The Flat algorithm guarantees 100% accuracy but is computationally exhaustive and can hinder "high performance" compared to HNSW, even for small datasets, as query load increases. Horizontal scaling is less direct for single-index performance.
• Option C is incorrect: While Aurora PostgreSQL can host vector data with pgvector, the IVFFlat algorithm typically provides lower recall than HNSW, thus not "maximizing accuracy" as effectively for this scenario.
• Option D is incorrect: Amazon DocumentDB is a document database not natively designed or optimized for efficient vector similarity search, making it an unsuitable choice for a RAG vector database.

✅

Reasoning: Amazon Bedrock knowledge bases inherently support metadata-aware filtering. By indexing S3 object metadata (e.g., content type, timestamp, origin), the retrieval process can apply specific filters before or during the vector search. This directly allows for "smarter constraints" to scope down results, reducing the number of documents evaluated, improving relevance, and speeding up responses with minimal architectural change. ❌ Why the other choices are incorrect:

• Option A is incorrect: Enhancing embeddings improves the quality of semantic similarity but does not address the root cause of too many documents being evaluated. It doesn't provide a mechanism to apply constraints to limit the search scope.
• Option B is incorrect: Migrating to Amazon OpenSearch Service from an existing Bedrock knowledge base constitutes a significant architectural change. This violates the explicit requirement for "minimal changes to the existing architecture."
• Option D is incorrect: Migrating to an Amazon Q Business index involves a substantial architectural shift. This solution directly contradicts the requirement for implementing a solution with "minimal changes" to the current RAG architecture.