Amazon Web Services AIP-C01 Exam Dumps Questions and Answers

Option C is the correct solution because it directly addresses both correctness and performance issues by grounding the model’s responses in authoritative product data using Retrieval Augmented Generation. Amazon Bedrock Knowledge Bases are designed to connect foundation models to trusted enterprise data sources, ensuring that generated responses are constrained to known, validated content.

By ingesting the product catalog into a knowledge base, the GenAI application retrieves only products that actually exist in the catalog. This prevents hallucinated or unavailable recommendations, which is a common issue when models rely solely on prompt instructions without retrieval grounding. RAG ensures that the model’s output is based on retrieved facts rather than learned generalizations.

Setting the PerformanceConfigLatency parameter to optimized enables Bedrock to prioritize lower-latency retrieval and inference paths, improving responsiveness for real-time recommendation scenarios. This directly addresses the reported performance issues without requiring provisioned throughput or caching strategies that are ineffective for mostly unique interactions.

Option A improves safety and latency predictability but does not ensure recommendations are limited to valid products. Option B relies on prompt constraints, which are not sufficient to prevent hallucinations. Option D introduces additional validation and caching layers but increases complexity and does not improve generation relevance.

Therefore, Option C best resolves both relevance and latency challenges using AWS-native, low-maintenance GenAI integration patterns.

Option C is the best answer because the scenario is centered on a foundation-model GenAI application that needs explainability, fairness iteration, and responsible AI controls inside an Amazon Bedrock workflow. Amazon Bedrock Agents support tracing, and AWS documentation states that traces can show the agent’s path from user input to response, including action group inputs and outputs, knowledge base queries, and the reasoning the agent uses to decide which action or query to take. AWS also describes trace data as a way to understand how an agent arrived at a response. This directly addresses clinicians’ need to review diagnostic reasoning and decision flow.

Amazon Bedrock Guardrails are also the right service for policy compliance in GenAI applications. AWS documentation states that Guardrails can implement safeguards aligned with responsible AI policies, configure denied topics, filter harmful content, and remove sensitive information. For healthcare and life sciences GenAI use cases, AWS Prescriptive Guidance recommends evaluating bias, fairness, and hallucinations and implementing guardrails to prevent harmful responses. This supports strict governance and privacy-sensitive clinical workflows.

The prompt testing and A/B testing component supports rapid iteration. AWS guidance for generative AI operations recommends prompt template management, creating and testing prompt variants, using A/B testing workflows for prompt variants, and analyzing performance against metrics. This is relevant for testing fairness behavior across demographic prompt sets and clinical scenarios.

Option A includes SageMaker Clarify, which is useful for bias detection and model explainability, but it is less directly aligned to Bedrock-native real-time tracing and policy enforcement for an FM application. Option B handles medical text extraction and terminology but not reasoning transparency or governance. Option D provides operational metrics and custom reports, but not native Bedrock reasoning traces or guardrails. Therefore, option C best meets the GenAI governance requirements.

==========

Option B is correct because the workload has predictable short peak periods, strict low-latency requirements, and lower demand between spikes. Amazon SageMaker Serverless Inference is designed for intermittent or unpredictable traffic because SageMaker manages the infrastructure and the customer pays based on usage rather than continuously running idle instances. AWS documentation describes serverless inference as suitable when traffic is intermittent or unpredictable and when users do not want to manage instances or scaling policies.

Provisioned concurrency is the key part of this answer. For latency-sensitive serverless inference workloads, provisioned concurrency keeps the required number of serverless instances initialized and ready to respond. AWS documentation states that SageMaker Serverless Inference integrates with Application Auto Scaling so provisioned concurrency can be scaled up or down based on a target metric or schedule. This fits a daily 2-hour peak window because the company can configure enough provisioned concurrency for 500 concurrent requests during peak periods and scale down when demand decreases.

Deploying each model to a separate serverless endpoint is also important. The categorization, extraction, and response-generation models likely have different memory, latency, and concurrency needs. Separate endpoints allow independent memory sizing, maximum concurrency configuration, monitoring, and scaling for each task. AWS API documentation also shows that serverless endpoint configuration includes maximum concurrency and provisioned concurrency settings, with provisioned concurrency required to be less than or equal to maximum concurrency.

Option A is less suitable because multi-model endpoints are usually best when many models can share infrastructure, but model loading and shared capacity can add latency risk. Option C assumes Amazon Bedrock provisioned throughput for models, but the company is developing specialized NLP models and needs task-specific deployment controls. Request batching can also add latency. Option D uses asynchronous inference, which is inappropriate for a less-than-500-ms synchronous response requirement. Therefore, option B best satisfies latency, concurrency, accuracy isolation, and resource optimization.

==========