AIP-C01 Certification Exam Guide + Practice Questions Updated 2026

Explanation:
Option C is the correct solution because it uses Amazon Bedrock cross-Region inference profiles , which are explicitly designed to support regional data residency, private connectivity, and resilience with minimal operational overhead.
By using a Europe-scoped inference profile, the application ensures that all inference requests are routed only within European Regions where the FM is deployed, such as eu-central-1 and eu-west-3. This satisfies data residency requirements while still providing resilience and load distribution across Regions.
Configuring an Amazon Bedrock VPC endpoint ensures that all traffic remains on the AWS private network. No public endpoints are used, which aligns with the company’s private networking requirements.
Extending existing SCPs to allow inference profile usage ensures that employees can access the FM only in approved Regions, maintaining governance across the Control Tower environment.
Options A and B introduce unnecessary custom routing layers and EC2 management.
Option D moves away from Amazon Bedrock entirely and increases operational complexity.
Therefore, Option C is the only solution that satisfies private access, regional confinement, governance controls, and low operational overhead.

Explanation:
Option B is the correct solution because it aligns with AWS guidance for building high-throughput, ultra-low-latency GenAI applications while maintaining predictable costs and automatic scaling. Amazon Bedrock provides access to foundation models that are specifically optimized for real-time inference use cases, including conversational and recommendation-style workloads that require responses within milliseconds.
Low-latency models in Amazon Bedrock are designed to handle very high request rates with minimal per-request overhead. Purchasing provisioned throughput ensures that sufficient model capacity is reserved to handle peak loads, eliminating cold starts and reducing request queuing during traffic surges. This is critical when supporting up to 500,000 concurrent calls with strict latency requirements.
Automatic scaling policies allow the application to dynamically adjust capacity based on demand, ensuring cost efficiency during off-peak hours while maintaining performance during peak usage. This directly supports the requirement to stay within a predefined monthly compute budget.
Option A fails because batch processing and complex reasoning models introduce higher latency and are not suitable for real-time suggestions.
Option C introduces significantly higher operational and cost overhead due to dedicated GPU instances and manual scaling responsibilities.
Option D is optimized for batch workloads and cannot meet the sub-200 ms latency requirement.
Therefore, Option B provides the best balance of performance, scalability, cost control, and operational simplicity using AWS-native GenAI services.

Explanation:
Option B best satisfies the requirements because it directly applies Retrieval Augmented Generation principles using managed Amazon Bedrock Knowledge Bases, which are designed to handle large, complex documents while preserving contextual relationships. Financial reports often interleave tables with explanatory narrative, and accurate analysis depends on keeping those elements logically connected. By segmenting documents based on their structural layout―for example, sections, subsections, tables, and surrounding commentary―the knowledge base can retrieve semantically relevant chunks that maintain this relationship during inference.
Amazon Bedrock Knowledge Bases support contextual chunking strategies that go beyond simple fixed-size segmentation. This is critical for financial documents, where a metric in a table may be explained in adjacent paragraphs or footnotes. Context-aware chunking ensures that retrieved content includes both the numeric data and its interpretation, enabling the foundation model to generate accurate, grounded responses. Including citations further improves analyst trust and auditability by allowing users to trace answers back to specific source sections, which is a common requirement in financial environments.
Scalability is another key requirement. Knowledge Bases manage embedding generation, indexing, and retrieval orchestration as a managed service, which allows the solution to scale across large document collections without requiring custom infrastructure or model hosting. This approach also supports efficient updates as new quarterly reports are added, ensuring the retrieval layer remains current.
Option A does not scale well because processing entire 5C100 page documents in a single prompt increases token usage, latency, and cost while risking context truncation.
Option C relies on fixed-size chunking triggered at query time, which often breaks semantic relationships in structured financial content.
Option D introduces unnecessary architectural complexity by splitting structured and unstructured data into separate applications, increasing operational overhead without providing better contextual retrieval than a unified RAG approach.

Explanation:
The correct combination is C and D because together they enforce centralized governance over both model access and prompt content controls, which are the two core requirements of the scenario.
To ensure employees can use only approved Amazon Bedrock models, governance must be enforced at the organization level and not rely on individual application logic. Service Control Policies (SCPs) are the strongest control mechanism available in AWS Organizations because they define the maximum permissions an account or principal can have. In option C, the SCP prevents any Amazon Bedrock model invocation unless a centrally approved guardrail identifier is specified. This ensures that guardrails are always enforced, regardless of how or where the invocation originates. The additional use of IAM permissions boundaries ensures that even within allowed accounts, employees are restricted to invoking only explicitly approved foundation models.
To prevent specific topics and proprietary information from being included in prompts, Amazon Bedrock Guardrails must be used. Guardrails operate inline during model invocation and can block disallowed content before it is processed by the model.
Option D correctly specifies a block filtering policy, which is appropriate when content must be prevented entirely rather than partially redacted. Deploying the guardrail using AWS CloudFormation StackSets allows the company to centrally manage and consistently deploy the same guardrail configuration across all accounts in the organization, ensuring uniform enforcement.
Option E uses mask filtering, which is better suited for redacting sensitive output rather than preventing prohibited content from being submitted in prompts.
Option B attempts to use SCPs alone but does not enforce guardrail deployment or content filtering.
Option A incorrectly places guardrail enforcement in permissions boundaries, which are not designed to validate request parameters such as guardrail identifiers.
By combining SCP-based enforcement with centrally deployed Bedrock guardrails, options C and D together provide strong, scalable, and centrally managed controls for both content safety and model governance across the organization.

Explanation:
Amazon Bedrock AgentCore Observability is the best fit because the requirement is specifically for built-in Amazon Bedrock visibility into agent interactions, tool behavior, and failures without custom instrumentation. AWS documentation states that AgentCore provides built-in metrics, logs, and traces for AgentCore modular services, and that this data can be viewed in Amazon CloudWatch. AgentCore observability also supports sessions, traces, and spans, where traces represent full request-response cycles and spans represent operations inside a trace. This directly matches the need to analyze multi-agent interactions, tool invocations, latency, throttling, and error behavior during peak traffic.
Option A is also correct because Amazon Bedrock AgentCore integrates with AWS X-Ray for distributed tracing of AI agents and tools. AWS X-Ray support helps follow requests across service boundaries and identify performance bottlenecks in agent and tool execution. CloudWatch provides curated GenAI observability views for AgentCore and can show operational health, metrics, traces, sessions, and error breakdowns. This gives the developer end-to-end visibility with minimal additional overhead because the core telemetry is service-provided rather than extracted through a custom pipeline.
Option B is incorrect because Container Insights focuses on container infrastructure and would not provide native visibility into Bedrock AgentCore agent reasoning paths or tool-level traces. Polling
APIs with Lambda adds custom logic and operational overhead.
Option C is incorrect because a custom ETL pipeline, DynamoDB storage, and QuickSight reporting do not satisfy the “built-in Amazon Bedrock capabilities” and “minimal overhead” requirements.
Option D starts correctly with AgentCore Observability, but then adds custom Lambda processing and Grafana, which introduces unnecessary custom instrumentation and processing.
Therefore, option A is the most AWS-aligned solution.