Amazon Web Services AIP-C01 - AWS Certified Generative AI Developer - Professional

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 D is the intended Bedrock prompt-engineering solution. AWS guidance recommends using output indicators to explicitly describe constraints and characteristics that the model should follow when constructing its response. The prompt should clearly state that the promotional message is mandatory, where it should appear, and how it should be integrated with the surrounding recommendation. This gives the model a stronger output constraint than an indirect instruction embedded elsewhere in a dynamically assembled prompt. Option A uses Guardrails, which are designed to evaluate and constrain unsafe or disallowed content rather than require insertion of specific marketing text. Option B adds unnecessary model calls and still does not enforce the desired response structure. Option C introduces additional AgentCore and reranking processing for a requirement that should be addressed directly through explicit output instructions in the prompt. AWS Documentation

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

Option C is correct because Amazon Bedrock agent tracing exposes the internal execution path needed to identify precisely where a multi-step workflow fails. When tracing is enabled for InvokeAgent, the response can include structured trace events. AWS documents OrchestrationTrace for orchestration activity and FailureTrace for the reason a particular step failed. Those records can be aggregated to calculate per-step attempts, successes, failures, and completion rates. Option A monitors broad client/server error metrics; even with custom metrics, it does not inherently provide the same structured execution context. Option B uses CloudTrail, which is primarily an API audit trail rather than a step-by-step agent reasoning trace. Option D requires custom EventBridge instrumentation and storage. Native agent trace data therefore provides the most direct evidence for exact failure-point analysis and detailed workflow completion analytics. AWS Documentation

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

Option B is the correct solution because it provides a scalable, durable, and secure architecture for conversational GenAI workloads that require multi-step clarification workflows and persistent memory.

AWS Step Functions Standard workflows are designed for long-running, stateful workflows with high reliability, which is ideal for clarification loops that may require multiple back-and-forth interactions. The Wait for a Callback pattern allows the workflow to pause while awaiting additional user input, making it well-suited for handling ambiguous queries without losing execution state.

Storing conversation history in Amazon DynamoDB enables millisecond-latency reads and writes at massive scale, supporting thousands of concurrent users. DynamoDB’s on-demand capacity mode automatically scales with traffic, eliminating capacity planning. Server-side encryption ensures that stored conversation data is encrypted at rest, meeting security and compliance requirements for personalized data.

Option A uses Step Functions Express and Amazon RDS, which is not ideal for long-lived conversational workflows and introduces scaling and connection management challenges. Option C stores conversations as individual S3 objects, which increases latency and complicates context retrieval. Option D relies on Amazon ElastiCache, which is optimized for ephemeral caching rather than durable, auditable conversation history.

Therefore, Option B best balances scalability, performance, durability, and security for a conversational Amazon Bedrock–based customer support application.

The correct combination is A, B, and D because these three options collectively satisfy the mandatory requirements for structured extraction, PII redaction before inference, regional human review, data residency, auditability, and high-scale availability with managed AWS services.

Option A is essential because Amazon Textract is the AWS-managed service designed to extract structured data from scanned documents such as forms, tables, and financial statements. Textract provides confidence scores, and Amazon Augmented AI (A2I) is purpose-built to route low-confidence extractions to human reviewers. Deploying Textract and A2I within the same Region ensures that the human review loop remains regionally constrained, meeting strict data residency requirements for applicants.

Option B satisfies the requirement to redact PII before inference by using AWS Lambda preprocessing. It also adds Amazon Bedrock guardrails to enforce safety controls on model outputs. Region-specific IAM roles ensure that only authorized principals in the correct Region can access the extracted data and invoke downstream services, strengthening residency enforcement and auditability.

Option D ensures that source documents are stored in Amazon S3 in the same Region as the applicant. Object metadata and tagging provide an auditable trail, supporting compliance reporting and traceability. S3 also provides the durability and availability needed to support 99.9% application availability as part of a well-architected pipeline.

Option C is not the correct approach for structured extraction from scans. Option E adds useful quality validation but is not strictly required to meet the stated requirements compared to A, B, and D. Option F is unrelated to the extraction/redaction/residency workflow requirements.

Therefore, A, B, and D are the best three choices to meet all stated requirements with minimal operational overhead.

Option A provides the most complete, AWS-native defense-in-depth solution for protecting against prompt injection attacks while meeting audit and resiliency requirements. Amazon Bedrock guardrails are designed specifically to enforce safety policies on both user inputs and model outputs, including protections against prompt injection and jailbreak attempts.

Setting content filters to high increases sensitivity to malicious or manipulative inputs. Guardrail profiles allow the same guardrail configuration to be applied consistently across multiple Regions, enabling cross-Region inference and failover without configuration drift. This directly satisfies the requirement for regional resilience.

Amazon CloudWatch Logs captures detailed guardrail intervention events, including when content is blocked, modified, or flagged. Custom metrics derived from these logs enable fine-grained auditing, alerting, and reporting on safety enforcement actions. This provides a more detailed audit trail of safety interventions than API-level logs alone.

Option B adds WAF protection but lacks detailed guardrail intervention logging. Option C introduces additional services and custom logic that increase complexity and may miss model-specific injection patterns. Option D references replication concepts that are not aligned with Bedrock guardrail operational models and relies on word filters, which are insufficient against sophisticated prompt injection techniques.

Therefore, Option A best meets the requirements for layered protection, auditability, and cross-Region resilience using managed Amazon Bedrock safety controls.

Option B is the correct solution because it directly addresses both throughput bottlenecks and latency requirements using native Amazon Bedrock performance optimization features that are designed for real-time, high-volume generative AI workloads.

Amazon Bedrock supports cross-Region inference profiles, which allow applications to transparently route inference requests across multiple AWS Regions. During peak usage periods, traffic is automatically distributed to Regions with available capacity, reducing throttling, request queuing, and timeout risks. This approach aligns with AWS guidance for building highly available, low-latency GenAI applications that must scale elastically across geographic boundaries.

Token batching further improves efficiency by combining multiple inference requests into a single model invocation where applicable. AWS Generative AI documentation highlights batching as a key optimization technique to reduce per-request overhead, improve throughput, and better utilize model capacity. This is especially effective for lightweight, low-latency models such as Claude 3 Haiku, which are designed for fast responses and high request volumes.

Option A does not meet the requirement because purchasing provisioned throughput in a single Region creates a regional bottleneck and does not address multi-Region availability or traffic spikes beyond reserved capacity. Retries increase load and latency rather than resolving the root cause.

Option C improves application-layer scaling but does not solve model-side throughput limits. Client-side round-robin routing lacks awareness of real-time model capacity and can still send traffic to saturated Regions.

Option D is unsuitable because batch inference with asynchronous retrieval is designed for offline or non-interactive workloads. It cannot meet a strict 2-second response time requirement for an interactive AI assistant.

Therefore, Option B provides the most effective and AWS-aligned solution to achieve low latency, global scalability, and high throughput during peak usage periods.

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.

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.

==========