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

Option A is the correct answer because Amazon Bedrock Flows is purpose-built to orchestrate generative AI workflows that combine data access, deterministic transformations, and model invocation with minimal operational overhead. The requirements explicitly state that the workflow must retrieve content from Amazon S3, extract a specific portion of a predefined template, send that portion to an Amazon Bedrock model, and store the model’s response back into the same S3 bucket. Amazon Bedrock Flows natively supports all of these steps.

By configuring S3 action nodes at the beginning and end of the flow, the workflow can retrieve the original communications and persist the reviewed output without custom code. The expression step allows deterministic parsing of a specific portion of the template, which is essential when only part of the message should be reviewed. This avoids relying on generative logic for parsing, which would be less predictable and harder to audit. The agent step is then used specifically for the review task, where the foundation model evaluates or modifies the extracted content.

Option B uses AWS Step Functions, which can achieve similar outcomes but requires more explicit orchestration logic and does not provide GenAI-native constructs such as expressions and agent steps in a single managed experience. Options C and D rely on Amazon Bedrock agents and AWS Lambda functions to handle parsing and data movement, which increases complexity, operational overhead, and maintenance burden.

Because Amazon Bedrock Flows directly integrates S3 actions, parsing expressions, and model review steps in a single managed workflow, Option A best meets the requirements with the least development and operational effort.

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.

The correct answers are A and D because they collectively satisfy the requirements for structured inputs, consistent output formatting, and non-blocking detection of bullying language.

Option A is required because Amazon Bedrock Prompt Management enables prompt templates with explicit input variables and defined output formats. By defining the four required inputs as variables, the company ensures that every invocation of the Amazon Nova Pro FM receives the correct structured inputs. Specifying the output format ensures consistent responses, which is essential for a grants application workflow. Adding the managed prompt to the prompts node of the flow allows Bedrock Flows to invoke the model using this standardized configuration.

Option D addresses the requirement to receive notifications when bullying language is detected without blocking responses. Amazon Bedrock guardrails support content filters with configurable actions. By applying the insults content filter and setting the response action to detect, the system flags responses containing bullying or insulting language while still allowing the response to be returned. This enables monitoring, alerting, and auditing without interrupting application functionality.

Option B is incorrect because setting the filter response to block contradicts the requirement not to block all flagged responses. Option C introduces a prompt router, which is unnecessary because the application uses a single Amazon Nova Pro FM. Option E incorrectly attempts to enforce input variables and output formatting through an inference profile, which does not provide prompt-level variable enforcement or formatting guarantees.

Therefore, A and D together provide structured prompt management and non-blocking safety detection with minimal operational complexity.

Option C best meets the requirements by combining native Amazon Bedrock logging with adaptive monitoring and minimal operational overhead. Amazon Bedrock model invocation logging can be sent directly to CloudWatch Logs, where detailed fields such as InputTokenCount, OutputTokenCount, and tool invocation metadata are captured for each request.

CloudWatch metric filters allow extraction of structured metrics from logs, including tool-specific token consumption patterns. By defining filters per tool integration, the company can isolate which tools are responsible for increased token usage without building custom log-processing pipelines.

CloudWatch anomaly detection provides automatic baseline modeling and dynamic thresholds based on historical traffic patterns. Unlike static alarms, anomaly detection adapts as usage evolves, making it ideal for applications with changing workloads or seasonal usage patterns. This directly satisfies the requirement to automatically adjust thresholds as traffic patterns change.

When abnormal token consumption occurs, anomaly detection alarms trigger immediately, enabling rapid investigation and remediation. Because this solution uses fully managed AWS services without custom analytics jobs or manual threshold tuning, it significantly reduces operational effort.

Option A fails to adapt to changing patterns. Option B introduces batch analysis and delayed insights. Option D requires manual intervention and custom code, increasing maintenance burden.

Therefore, Option C provides the most scalable, adaptive, and low-maintenance solution for monitoring and controlling token consumption in Amazon Bedrock–based applications.

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.

==========

Option C is the correct solution because it provides near real-time monitoring, hallucination detection, and cost anomaly awareness using built-in Amazon Bedrock and Amazon CloudWatch capabilities, with minimal custom development.

By configuring Amazon Bedrock invocation logging with text output logging, the company captures detailed prompt and response data for auditing and analysis without building custom logging pipelines. This data is stored in Amazon S3, providing durable storage for compliance and retrospective investigation.

Using Amazon Bedrock guardrails with contextual grounding checks allows the application to automatically detect hallucinations by verifying whether generated summaries are grounded in the provided clinical documents. This is the AWS-recommended approach for hallucination detection in RAG and summarization workloads and avoids the need to maintain custom evaluation models or pipelines.

Creating Amazon CloudWatch anomaly detection alarms for InputTokenCount and OutputTokenCount metrics enables automatic detection of abnormal token usage patterns that often correlate with runaway prompts, inefficient summarization, or prompt injection attempts. Anomaly detection adapts dynamically to usage trends, making it more effective than static thresholds for early cost warnings.

Option A introduces batch analytics with Glue and Athena, which is not near real time and increases operational overhead. Option B requires managing evaluation jobs and Lambda-based notification logic. Option D focuses on infrastructure-level monitoring and offline dashboards rather than near real-time GenAI quality and cost signals.

Therefore, Option C best meets the requirements with the least operational effort and maintenance overhead.

This requirement explicitly calls for character-by-character streaming, long-running responses, low latency, and massive concurrency, which aligns directly with Amazon Bedrock streaming inference patterns.

Amazon Bedrock provides the InvokeModelWithResponseStream API specifically for streaming partial model outputs as tokens are generated. This enables near-instant feedback to users instead of waiting for the full response to complete, which is essential when responses last up to 45 seconds.

Amazon API Gateway WebSocket APIs are purpose-built for bidirectional, low-latency, server-initiated communication, allowing the backend to push characters or tokens to clients in real time. This eliminates inefficient polling and supports thousands of concurrent open connections.

AWS Lambda integrates natively with WebSocket APIs and scales automatically with connection volume, enabling a fully managed, serverless architecture. This approach maintains security, centralized authentication, throttling, and observability while avoiding direct client access to Bedrock APIs.

Option B introduces polling latency and unnecessary API overhead and does not provide true streaming. Option C violates AWS security best practices by exposing Bedrock directly to clients and does not scale securely. Option D only serves completed responses and cannot meet the real-time streaming requirement.

Therefore, Option A is the only solution that fully satisfies streaming behavior, concurrency, latency, and managed-service constraints.

Option D is correct because it separates the United States and European workloads and uses the correct Amazon Bedrock inference pattern for European data residency. AWS documentation states that geographic cross-Region inference keeps data processing within specified geographic boundaries such as US, EU, and APAC, and is intended for organizations with data residency and compliance requirements. The regional availability documentation further explains that a geographic profile routes within a defined geography and that prompts and outputs may move within that geography but not outside it. This directly satisfies the requirement that European customer data must be processed only in Europe-based AWS Regions.

Provisioned throughput is appropriate for the US workload because the system has a demanding and predictable performance target: 1,000 transactions per second with sub-500 ms response times. Provisioned capacity is generally used when an application needs reserved throughput and consistent performance rather than depending only on on-demand capacity. Automatic scaling based on utilization metrics supports changing demand while maintaining performance. EventBridge and Lambda can coordinate failover workflows or routing updates when connectivity disruptions occur, supporting high availability across Regions.

Option A is not the best answer because it includes a global inference profile. AWS documentation states that global cross-Region inference can route requests across supported commercial AWS Regions worldwide and has no geographic data-residency restriction. AWS explicitly notes that organizations with data residency or compliance requirements should assess whether global cross-Region inference fits their framework because requests may be processed in other supported commercial Regions. That conflicts with the European data processing requirement.

Option B uses separate Regional provisioned throughput, but it relies on a custom Application Load Balancer approach for Bedrock routing and does not use the Bedrock geographic inference profile that is designed for EU data residency. Option C uses response streaming, which improves perceived response latency for text generation but does not guarantee sub-500 ms fraud-processing latency or European-only processing. Therefore, option D is the most complete AWS-aligned solution.

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 C is the correct solution because it enforces privacy controls at inference time, not at ingestion time, which is required when different user roles require different visibility into the same underlying data.

Using an S3 Lifecycle configuration ensures that documents older than 3 years are automatically removed, guaranteeing that the knowledge base references only compliant, recent medical reports. Scheduling Lambda-based syncs keeps the knowledge base aligned with the bucket contents without introducing complex per-upload orchestration.

The most important requirement is role-based PII exposure. Amazon Bedrock guardrails support dynamic application at inference time, allowing the system to select a guardrail configuration based on the authenticated user’s Amazon Cognito group. Surgeons can receive full responses, while engineers receive responses with PII masked—without duplicating data or maintaining multiple knowledge bases.

This approach preserves a single source of truth for medical reports while enforcing privacy through response-level controls. It also maintains full auditability of access and redaction behavior.

Option A permanently removes PII and violates surgeon access requirements. Option B redacts data inconsistently and couples privacy logic to ingestion. Option D doubles storage, increases cost, and introduces data drift risk.

Therefore, Option C best meets privacy, compliance, scalability, and operational efficiency requirements.