Amazon Web Services Updated AIP-C01 Exam Questions and Answers by bradley

Option A is the only listed choice that satisfies the hard requirement that PII must not reach the Bedrock model. AWS explicitly states that Knowledge Base guardrails apply to the user input and generated model response, but not to references retrieved from the Knowledge Base at runtime. Therefore, Options B, C, and D can still place PII-bearing retrieved chunks into model context even though a guardrail is configured. Amazon Comprehend can detect PII, enabling the Lambda preprocessing step in A to remove sensitive data before embeddings are created and before retrieved context is ever sent to the foundation model. Although semantic chunking would normally be preferable for records containing multiple unrelated topics, privacy is a mandatory constraint. Option A has more custom processing, but it is the only option that enforces PII removal upstream of model invocation.

Option D is the correct solution because the Amazon Bedrock Converse API is purpose-built for multi-turn conversational interactions and is designed to work consistently across SDKs and compute environments. The Converse API standardizes how messages, roles, and context are represented, which ensures consistent behavior whether the application is running in AWS Lambda with Python or in Amazon EKS with JavaScript.

By passing previous messages in the messages array, the application explicitly maintains conversational context across turns without relying on external state stores. This approach is recommended by AWS for conversational GenAI workflows because it avoids state synchronization complexity and ensures deterministic model behavior across environments.

Using IAM roles for authentication provides a single, consistent security model for both Lambda and EKS. IAM roles integrate natively with AWS SDKs, eliminating the need for custom authentication logic or environment-specific credentials. This aligns with AWS best practices for least privilege and simplifies governance.

Option A introduces inconsistent authentication and custom formatting logic, increasing complexity. Option B unnecessarily introduces ElastiCache for state management, which is not required when using the Converse API correctly. Option C stores state in process memory, which is unsafe and unreliable for serverless and containerized workloads.

Therefore, Option D best satisfies the requirements for conversational consistency, multi-environment support, shared model usage, and consistent authentication with minimal operational overhead.

This scenario requires strict data residency, regional processing, classification, and auditable decision trails, which Option C addresses using AWS-native governance services.

Region-specific Amazon S3 buckets enforce geographic data boundaries. Amazon S3 Object Lock ensures immutability of stored data and logs, supporting regulatory retention and non-repudiation requirements. Pre-processing data within the same Region before invoking Amazon Bedrock ensures that inference and data handling do not cross continental boundaries.

Amazon Macie provides managed, automated data classification for sensitive data types such as PII and financial records, fulfilling the classification requirement without custom tooling.

AWS CloudTrail immutable logs provide comprehensive audit trails of all API calls, model invocations, and data access events, ensuring traceability of AI decision-making processes.

Option A violates residency rules through cross-Region inference. Option B does not provide data classification. Option D introduces high operational overhead and relies on manual compliance reporting.

Therefore, Option C is the most compliant, scalable, and operationally efficient solution for regionally governed GenAI workloads.

Option C is correct because it combines complete inference capture, immutable retention, and offline evaluation without placing an evaluator in the synchronous request path. Amazon Bedrock model invocation logging can record request data, response data, and metadata to CloudWatch Logs and Amazon S3. S3 Object Lock provides write-once-read-many protection that can prevent retained audit objects from being overwritten or deleted. Bedrock model evaluation jobs can then assess stored or prepared response data offline, supporting regression and quality analysis without adding judge-model latency to every live clinical request. CloudTrail complements the audit record for service API activity. Option A depends on manual reviews. Option B records API activity but not the full inference payloads needed for quality evaluation, and ordinary versioning is not equivalent to WORM retention. Option D scores every request in production, adding runtime overhead. AWS Documentation

================