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

Option B provides the strongest modular architecture for an integration-heavy agentic workload. Strands supports hierarchical agents-as-tools patterns in which a coordinating agent delegates specialized work to independent agents, allowing integrations and domain logic to be added or modified without creating one increasingly complex agent. AgentCore Gateway exposes tools through standardized MCP interfaces so agents can discover and invoke internal or external capabilities through a unified connectivity layer. AWS Step Functions supports callback tasks that pause execution until a human or external process returns a task token, making it suitable for the required human approval checkpoint. Option A requires custom model hosting and approval UI development. Option C is primarily a batch data-processing architecture rather than real-time agent orchestration. Option D can function initially, but a single agent becomes less modular and maintainable as the number of tools and business domains expands. Strands Agents

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

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 B is correct because the requirement is agentic, dynamic orchestration rather than a predefined workflow. AgentCore Memory can preserve conversational context, while AgentCore Gateway provides a unified MCP interface through which an agent can discover and invoke many tools and backend APIs. AWS documents support multiple Gateway targets and consolidated tool discovery, so adding or selecting enterprise capabilities does not require hard-coding every workflow path. AgentCore observability also exposes detailed traces covering processing steps, tool invocations, decision points, errors, and outputs, which supports compliance review and explainability. Option A is fundamentally static orchestration. Option C substitutes retrieval for API execution and still requires custom Lambda orchestration. Option D uses guardrails for a purpose they are not designed to perform; guardrails constrain content but are not a dynamic enterprise-tool orchestration engine. AWS Documentation

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

Option B best meets the combined resiliency and observability requirements because it applies AWS-recommended retry behavior for transient throttling and enables true distributed tracing across service boundaries. During peak traffic, intermittent failures are commonly caused by throttling and other transient conditions. The AWS SDK standard retry mode provides exponential backoff with jitter, which reduces synchronized retry storms, prevents cascading failures, and improves overall system stability. Jitter is important because it spreads retry attempts over time, reducing load amplification during throttling events.

For observability, AWS X-Ray provides distributed tracing that follows a request across components such as API Gateway or load balancers, application services, and downstream calls to Amazon Bedrock. X-Ray can identify where latency is being introduced and which downstream call is contributing most to end-to-end response time. This is required to “identify latency contributors” and isolate performance issues under load.

The requirement also states that the company must correlate performance issues with specific FM characteristics. X-Ray annotations are designed for this purpose: the application can annotate traces with the model ID, inference parameters, region, or inference profile used. This enables filtering and analysis (for example, comparing latency or error patterns by model, parameter set, or endpoint configuration) without building a separate telemetry system.

Option A’s fixed-delay retries increase synchronized retry behavior and do not provide distributed tracing. Option C does not prevent cascading failures and cannot provide cross-service tracing. Option D is incorrect because CloudTrail is an audit logging service and does not provide distributed tracing for request latency analysis.

Therefore, Option B provides the correct combination of resilient retries and deep, model-correlated distributed observability for Amazon Bedrock workloads.