AIP-C01 Exam Dumps - Amazon Web Services AWS Certified Professional Questions and Answers

Option A is the best solution because it satisfies streaming, token control, and retry requirements while keeping operational overhead low by using fully managed, serverless AWS services. Amazon API Gateway HTTP APIs provide a lightweight, cost-effective front door for APIs and integrate cleanly with AWS Lambda for request processing and security controls.

AWS Lambda response streaming allows the API to begin returning content to the client as soon as partial model output is available, reducing perceived latency and improving user experience for long responses. Using Lambda as the integration layer also provides a centralized place to enforce token-aware request handling, such as rejecting oversized requests, truncating optional context, or applying consistent limits across users and tenants to manage compute usage.

Retry logic is best handled in the client or integration layer for transient failures such as timeouts and throttling. Lambda can implement controlled retries with exponential backoff and jitter, while API Gateway timeouts help bound request lifetimes and prevent hung connections from consuming resources indefinitely. Because the model service is managed, the company avoids infrastructure management and focuses only on request shaping, safety, and resiliency behavior.

Option B is not suitable because client-side polling is not true streaming, front-end token enforcement is insecure and inconsistent, and API Gateway does not provide model-aware retry behavior on its own. Option C introduces container hosting and scaling complexity, which increases operational overhead compared to serverless. Option D can work, but REST APIs are generally heavier than HTTP APIs for this pattern and do not reduce overhead compared to Option A.

Therefore, Option A provides the required streaming and resiliency capabilities with the least infrastructure management effort.

Amazon Bedrock AgentCore Gateway is specifically designed to expose existing APIs, Lambda functions, services, and MCP servers to agents through a standardized Model Context Protocol interface. AWS documents that Gateway can transform REST APIs represented by OpenAPI specifications into MCP-compatible tools and provide agents with a unified endpoint for tool discovery and invocation. This directly satisfies the requirement to add or expose warehouse, shipping, and customs capabilities through MCP without repeatedly modifying agent integration code.

AWS Step Functions is appropriate for deterministic workflow orchestration. Task states can represent individual reasoning or tool-execution stages, while built-in Retry configuration supports IntervalSeconds , MaxAttempts , and BackoffRate . These settings provide controlled retries with exponential backoff and a defined maximum retry budget rather than requiring bespoke retry code. AWS explicitly documents MaxAttempts as the mechanism that stops retry behavior after the configured limit is reached.

A Choice state supplies deterministic conditional routing. The shipment value can be evaluated and requests above $100,000 can be sent to an approval branch. The approval task can use the Step Functions callback/task-token integration, which pauses workflow execution until an external process—such as a human approval system—returns success or failure. AWS specifically identifies human approval as a callback-task use case.

D is weaker because critical retry and approval policy should not depend solely on probabilistic orchestration prompts. E and G introduce unnecessary custom operational logic. F misuses Guardrails: Bedrock Guardrails governs model input/output safety and policy filtering; it is not a general-purpose human workflow orchestrator for shipment authorization.

==========

Option A best meets the requirements because it directly implements a Retrieval Augmented Generation pattern for conversational recommendations using managed Amazon Bedrock capabilities and a scalable vector store. The company’s source data already resides in Amazon S3, which aligns naturally with Amazon Bedrock Knowledge Bases ingestion workflows. A knowledge base can ingest book text, reviews, and metadata, generate embeddings using a supported embedding model, and persist those vectors in a purpose-built vector backend such as Amazon OpenSearch Service. This enables semantic retrieval that is well suited to conversation-driven intent, where user prompts are often descriptive and do not map cleanly to keyword filters.

The requirement to suggest books based on conversations implies the system must interpret natural language context and retrieve relevant passages, reviews, and metadata to ground the recommendation. Knowledge Bases provide managed orchestration for embedding creation and retrieval, which reduces development effort compared to building custom embedding pipelines. OpenSearch Service provides scalable vector search and k-nearest neighbors style similarity retrieval, which supports low-latency responses when properly indexed and sized.

For scaling to more than 10,000 concurrent users, the API layer design in option A is a common AWS pattern: Amazon API Gateway provides a managed front door with throttling and request handling, while AWS Lambda scales horizontally with demand and can invoke the knowledge base retrieval operations. This separates compute scaling from the vector store scaling and helps keep latency predictable under load.

Option B is not the best choice because DynamoDB is not the standard native vector store target for Amazon Bedrock Knowledge Bases in this context and would introduce additional implementation complexity around vector indexing and similarity search behavior. Option C requires substantial ML lifecycle work, model hosting, tuning, and continuous iteration to achieve quality recommendations at scale. Option D provides strong enterprise search, but it focuses on retrieval and FAQs rather than a managed RAG recommendation workflow grounded in embeddings and conversational context for generative responses.

Option A is the correct solution because it uses native Amazon Bedrock governance and evaluation capabilities to meet regulatory, performance, and deployment timeline requirements with the least operational overhead.

Amazon Bedrock guardrails provide built-in safety controls that enforce responsible AI policies directly during inference. Custom content filters and toxicity detection protect customer interactions and prevent disallowed investment guidance patterns without requiring custom application logic. Guardrails operate inline and are optimized for low latency, which helps meet the strict 200 ms response-time requirement.

Hallucination detection is addressed through Amazon Bedrock Model Evaluation, which supports automated evaluation at scale using LLM-as-a-judge techniques. This enables the company to detect factual inaccuracies and policy violations systematically, without building custom evaluation pipelines or requiring extensive human review. Evaluation outputs can be surfaced as metrics.

Storing all prompt-response pairs in Amazon DynamoDB provides a low-latency, highly scalable audit store that aligns with financial regulatory requirements. Using TTL enforces data retention policies automatically, reducing compliance risk and storage overhead.

Amazon CloudWatch custom metrics integrate seamlessly with existing compliance dashboards, allowing near–real-time monitoring of safety interventions, hallucination rates, and drift indicators. CloudWatch anomaly detection can be applied to these metrics to surface behavior changes quickly.

Option B relies on custom Lambda logic and S3-based auditing, increasing latency and operational complexity. Option C introduces additional services that increase setup time and may exceed the 60-day deployment window. Option D uses non–Bedrock-native monitoring and adds unnecessary infrastructure layers.

Therefore, Option A provides the most complete, compliant, and low-overhead governance solution for a regulated GenAI financial services application.

Option C is the correct solution because it directly addresses the root cause of the problem—overly broad retrieval—while requiring minimal architectural change. Amazon Bedrock Knowledge Bases support metadata-aware filtering, which allows the system to constrain retrieval queries based on indexed metadata such as content type, publication date, source, or category.

By indexing Amazon S3 object metadata, the company can restrict vector searches to relevant subsets of the corpus, such as recent emergency reports, specific content formats, or trusted sources. This significantly reduces the number of documents evaluated during retrieval, which improves both latency and result relevance without changing embedding models or retrieval infrastructure.

This approach aligns with AWS best practices for optimizing RAG systems: when embeddings are already strong, retrieval quality is often improved by narrowing the candidate set rather than increasing model complexity. Metadata filtering reduces noise and ensures that retrieved documents are more contextually aligned with user queries.

Option A requires retraining or adapting embedding models, which the company has already determined will not provide additional benefit. Option B introduces a migration to OpenSearch, which adds operational overhead and deviates from the existing Bedrock knowledge base architecture. Option D requires moving to a different indexing service, increasing complexity and implementation effort.

Therefore, Option C provides the most effective and low-effort solution to improve retrieval accuracy and performance in the existing Amazon Bedrock RAG system.

Option B provides the strongest match among the listed alternatives because it combines managed speaker identification, multimodal generative analysis, and a native search-oriented datastore without unnecessary custom orchestration.

Amazon Transcribe speaker diarization distinguishes speakers and assigns identifiers such as spk_0 , spk_1 , and so forth. Its output includes speaker labels and timestamps, allowing individual statements to be associated with particular speakers and positions in the meeting timeline.

Anthropic Claude models on Amazon Bedrock support multimodal prompts that combine text and images. The application can therefore supply speaker-attributed transcript segments together with extracted presentation/video frames and instruct the model to generate summaries that associate spoken comments with relevant visual information. AWS ' s Claude Messages API documentation explicitly supports mixed image-and-text input.

Amazon OpenSearch Service is appropriate for storing the enriched meeting records and supporting document indexing and full-text searching. It provides substantially more natural full-text retrieval than attempting to create a custom indexing layer over DynamoDB.

A uses Transcribe and Rekognition effectively, but it states that a Lambda function itself “generates” the summaries without specifying a generative model and requires custom correlation logic. C chains BDA, Transcribe, Rekognition, DynamoDB, and Bedrock, increasing service count and operational complexity; DynamoDB also does not natively satisfy the full-text-search requirement. D similarly depends on DynamoDB plus a custom indexing mechanism.

Current AWS capabilities make Bedrock Data Automation even more capable than the wording of C suggests: BDA can produce video summaries, scene-level summaries, detected video text, full audio transcripts, and speaker identification. However, among the supplied choices , B remains the cleanest architecture satisfying multimodal GenAI analysis, diarization, scalable managed processing, and native searchable storage.

==========

The correct combination is B and C because together they address both workload diversity and hybrid deployment requirements with minimal custom engineering.

Option B provides consistent, high-throughput access by configuring provisioned throughput in Amazon Bedrock. Provisioned throughput guarantees predictable capacity and performance, which is essential for batch processing workloads that require sustained inference rates. This eliminates cold starts and throttling concerns that can occur with purely on-demand usage, making it well suited for high-volume enterprise workloads.

Option C enables hybrid deployment across cloud and on-premises environments by deploying foundation models to Amazon SageMaker AI endpoints and using Amazon SageMaker Neo for edge and on-premises optimization. SageMaker Neo compiles models for target hardware, allowing inference to run efficiently outside the AWS cloud while still using AWS-managed tooling. Orchestrating these deployments with AWS Lambda allows consistent invocation patterns across environments.

Option A uses asynchronous endpoints, which are not suitable for real-time, low-latency inference. Option D addresses scaling but does not support on-premises or hybrid deployment. Option E simplifies model onboarding but does not address hybrid execution or guaranteed throughput.

Therefore, Options B and C together provide real-time and batch support, predictable performance, and true hybrid deployment while minimizing operational overhead.

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 C is the best answer because it implements a decoupled, queue-based moderation pipeline that invokes the expensive model only when the low-latency model is not confident enough. Amazon SQS is designed to decouple distributed application components and support asynchronous processing. AWS documentation describes SQS as a fully managed message queuing service that enables decoupling and scaling of microservices, distributed systems, and serverless applications. This matches the requirement for high resiliency and sudden demand spikes because incoming requests can be buffered in a durable queue rather than overwhelming the model-processing layer.

Using AWS Fargate to process queue messages is also appropriate because Fargate provides serverless container compute for Amazon ECS or Amazon EKS workloads. It allows the company to run scalable processing workers without managing EC2 capacity directly. AWS Prescriptive Guidance includes architectures that use API Gateway, Amazon SQS, and AWS Fargate to process events asynchronously, which supports the same decoupled processing model required in this question.

The two-stage queue design also optimizes cost. The small, low-latency classifier is used first for all requests. Only requests with confidence below 0.65 are placed into the second queue and processed by the larger model. This avoids running the larger model for every moderation request. High-confidence results can be completed quickly by the first-stage processor, while uncertain results are isolated into an asynchronous second-stage workflow.

Option A is incorrect because it synchronously calls the larger model for low-confidence results, which violates the requirement to process low-confidence requests asynchronously. Option B is incorrect because it invokes both models for every request, increasing cost and eliminating the benefit of confidence-based escalation. Option D requires managing EC2 instances and uses keyword heuristics instead of model confidence, so it is less resilient and less aligned with Bedrock-based moderation. Therefore, option C is correct.

AWS Glue Data Quality is the correct core service because it directly addresses the distinctive requirements that separate this question from ordinary ETL validation. AWS describes Glue Data Quality as a managed, serverless capability for measuring and monitoring dataset quality. It uses Data Quality Definition Language (DQDL) for rules, can automatically analyze datasets and recommend rules, generates a Data Quality score after rule evaluation, supports machine-learning-based anomaly detection, and integrates with Amazon CloudWatch.

Completeness can be evaluated through DQDL rules such as IsComplete . AWS rule recommendations can automatically generate completeness, uniqueness, value-domain, and column-length rules based on observed data. Anomaly detection learns historical statistics and identifies values outside predicted bounds; AWS can additionally recommend future data-quality rules based on detected anomalies.

Glue Data Quality can publish pass/fail metrics into the Glue Data Quality CloudWatch namespace, making the results usable for monitoring, alarms, and regulatory-quality dashboards.

There is one important technical issue in the wording of option B: AWS Glue Data Quality itself does not remove PII. The complete AWS Glue implementation would pair Glue Data Quality with the AWS Glue Detect PII transform. AWS documents that this transform can identify sensitive entities and then mask, redact, hash, or otherwise process identified PII. Therefore, B is clearly the intended and strongest listed answer, but a production implementation should add the Glue PII transform to fully satisfy the question ' s PII-removal requirement.

A requires extensive custom validation. C does not provide the requested automated rule recommendations and managed quality-score capabilities. D handles PII detection but lacks automated DQDL recommendations, ML anomaly detection, and native data-quality scoring.

==========