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

Option D best satisfies all functional, performance, and governance requirements while minimizing architectural complexity. The requirement explicitly states that all filtering must complete before content reaches the foundation model, which rules out asynchronous or streaming-based approaches that could delay enforcement.

Amazon Comprehend supports toxicity detection, prompt safety classification, and PII detection with entity redaction as managed capabilities. Running these filters in parallel ensures low end-to-end latency, which is essential for customer-facing communication platforms. Parallel execution avoids the cumulative latency that would be introduced by sequential pipelines.

Toxicity detection identifies offensive or abusive content early. Prompt safety classification detects requests for unethical, harmful, or manipulative advice, which directly addresses inappropriate advice solicitation requirements. PII detection with entity redaction ensures that customer privacy is preserved before data is sent to the FM, preventing sensitive information from being processed or echoed in generated responses.

Configuring thresholds allows fine-grained control over sensitivity while maintaining acceptable false-positive rates. Using CloudWatch metrics and alarms enables continuous monitoring of filtering behavior and intervention rates without adding custom routing or human review pipelines that would slow responses.

Option A lacks PII redaction. Option B introduces unnecessary model-building complexity and delayed PII checks. Option C adds sequential latency and introduces human review routing, which violates the response-time requirement.

Therefore, Option D provides the most robust, performant, and AWS-aligned layered content filtering solution.

Option D is the best fit because it implements a reliable event-driven MLOps workflow that automates retraining and redeployment with clear orchestration, auditability, and production-grade error handling. The requirement is explicit: whenever a new file is uploaded to Amazon S3, the system must retrain and then redeploy the model used by a web application. A common AWS pattern is to use an S3 event notification to trigger an AWS Lambda function, which then starts a controlled workflow. In option D, Lambda serves as the event handler that reacts immediately to the S3 upload event and passes the necessary context (bucket, object key, dataset version) into an AWS Step Functions Standard state machine.

Step Functions Standard is appropriate for model retraining pipelines because training and deployment steps can be long-running and benefit from durable state, retries, and failure handling. It provides execution history, making it easier to troubleshoot why a particular retraining run failed and to prove which dataset version produced which model version. This operational visibility is critical when the dataset is “growing rapidly” and retraining is frequent.

Within the workflow, Amazon SageMaker Pipelines is the right service to run the ML lifecycle stages in a repeatable way: data processing (if needed), training, evaluation/quality checks, model registration, and deployment to an endpoint used by the application. SageMaker Pipelines is purpose-built for CI/CD-style ML, supporting automated redeployments when a new approved model artifact is produced. By calling a pipeline execution from Step Functions, the company can add governance gates (for example, only deploy if evaluation metrics meet thresholds), and can apply consistent rollback and notification steps when deployment fails.

The other options are weaker: A confuses inference with retraining and does not provide deployment orchestration. B adds unnecessary webhook complexity and describes an awkward event bus configuration. C introduces Autopilot/Data Wrangler, which may be useful but adds extra moving parts and is not required to meet the trigger-and-redeploy requirement.

Option B provides the least operational overhead because it keeps the solution primarily inside managed Amazon Bedrock capabilities, minimizing custom orchestration code and infrastructure to operate. The core requirements are domain grounding, reduced semantic dilution for complex questions, and consistent low-latency responses at high request volume. A Bedrock knowledge base is purpose-built for Retrieval Augmented Generation by ingesting domain documents, chunking content, generating embeddings, and retrieving the most relevant passages at runtime. This directly addresses the need to reference domain-specific medical terminology from authoritative documents to reduce ambiguity and improve factual accuracy.

Reducing semantic dilution typically requires improving the retrieval query so that the retriever focuses on the most relevant concepts, especially for long or multi-intent questions. Enabling query decomposition allows the system to break a complex medical query into smaller, more targeted sub-queries. This increases retrieval precision and recall for each sub-question, which helps the model generate a more accurate synthesized response grounded in the retrieved medical context.

Amazon Bedrock Flows provide a managed way to orchestrate multi-step generative AI workflows, such as preprocessing the input, performing retrieval against the knowledge base, invoking a foundation model, and formatting the final response. Because flows are managed, the company avoids maintaining custom state machines, multiple Lambda functions, or bespoke routing logic. This reduces operational overhead while still supporting repeatable, observable execution.

Compared with the alternatives, option A introduces an agent plus API Gateway routing and multiple model choices, increasing configuration and runtime complexity. Option C requires hosting and scaling custom models on SageMaker AI, which adds significant operational burden and latency risk. Option D relies on multiple Lambda functions orchestrated by an agent, which adds more moving parts and increases cold-start and integration overhead. Option B most directly meets the requirements with the smallest operational footprint.

The combination of Options A and B provides the most scalable and AWS-native architecture for building reasoning agents with persistent memory, session awareness, secure access control, and flexible invocation models.

Amazon Bedrock AgentCore is purpose-built to manage agent memory, session context, and identity-aware reasoning across interactions. It eliminates the need for developers to manually store and retrieve agent state, manage session lifecycles, or implement custom memory layers. AgentCore natively supports both synchronous requests and event-driven execution, making it ideal for support workflow automation.

Option B complements AgentCore by enabling seamless tool invocation. By registering AWS Lambda functions and REST APIs as agent actions through API Gateway and EventBridge, the agent can invoke tools reactively or synchronously without custom orchestration code. EventBridge enables event-driven execution, while API Gateway supports synchronous request-response patterns.

This combination provides built-in security, observability, and scaling, while avoiding the operational burden of managing queues, databases, or custom workflow engines.

Option C introduces unnecessary orchestration complexity. Option D increases infrastructure management and cost. Option E stores agent state in S3, which is not suitable for low-latency, session-based reasoning.

Therefore, A and B together deliver the most scalable, secure, and low-overhead solution for production-grade reasoning agents on AWS.