Bedrock Geographic Inference Profiles for EU Data Sovereignty
Short answer
D Route European applications through a Europe-specific geographic inference profile for data sovereignty, provisioned throughput with auto scaling for U.S. traffic, and EventBridge plus Lambda cross-Region failover.
Question
The company must ensure that data for European customers is processed only in AWS Regions that are based in Europe.
Which solution will meet these requirements?
Key Takeaways
The tested concept is routing inference through a geography-prefixed inference profile (eu.*) to guarantee EU-only processing, and the trap is assuming a 'global' inference profile or regional IAM tricks alone satisfy data sovereignty.
This Amazon Bedrock question tests how to satisfy EU data residency while sustaining 1,000 transactions per second with sub-500 ms latency and cross-Region resilience. The solution that works combines provisioned throughput for U.S. traffic, a Europe-specific (eu.) geographic inference profile for EU traffic, auto scaling, and EventBridge/Lambda-based failover.
Common mistake: Option A is the tempting trap: it mentions a dedicated European profile but routes Lambda and EKS traffic through a global inference profile, which can send EU customer data to non-EU Regions such as US East — a direct sovereignty violation.
Expert Analysis
Why the Answer Is Correct
Option D cleanly separates the workloads by geography, which is exactly what AWS designed geographic inference profiles for. EU applications call a Europe-prefixed geographic inference profile, so Bedrock routes and processes every inference request only inside EU-based Regions, satisfying the stated sovereignty mandate. U.S. applications use provisioned throughput with the InvokeModel API, which is the correct lever for a sustained 1,000 TPS / sub-500 ms fraud-detection workload that on-demand capacity cannot reliably guarantee. Automatic scaling of the provisioned capacity handles demand spikes, and EventBridge plus Lambda implement the cross-Region failover needed for high availability during connectivity disruptions.
Why the Other Options Are Wrong
Option A fails the sovereignty requirement because the InvokeModel calls go through a global inference profile, which can place European customer data in non-EU Regions; the Route 53 and CloudWatch components address availability and monitoring but do not repair that residency breach. Option B provisions throughput in each Region separately, which is expensive and rigid, and it relies on an Application Load Balancer plus EventBridge rules as a failover mechanism — an ALB does not route to Bedrock inference profiles and EventBridge is not a connectivity-disruption failover tool, so the design is architecturally mismatched. Option C uses on-demand throughput with InvokeModelWithResponseStream, which offers no capacity guarantee for 1,000 TPS at sub-500 ms, and the separate IAM roles with Region-scoped permissions restrict callers but do not themselves prevent a misconfigured client from targeting a non-EU endpoint, nor do they provide any failover path.
Community Comment Notes
TNT87 selected D and correctly explained that a profile "prefixed with eu." ensures inference requests are "routed and processed only within AWS Regions located in Europe," matching AWS guidance on geographic cross-Region inference. seoyeon_01 asked for clarification of the reasoning in context, which this analysis addresses: the decisive factor is that only a geography-scoped profile, not a global one, enforces residency.
Official Reference
https://docs.aws.amazon.com/bedrock/latest/userguide/cross-region-inference.html
This link opens the official vendor documentation in a new tab.
Exam Strategy
When a question names a data-residency jurisdiction, immediately reject any option whose traffic passes through a 'global' inference profile or a cross-geography endpoint. Then confirm the throughput claim is backed by provisioned capacity rather than on-demand, and that a real failover mechanism (EventBridge/Lambda, not just DNS or an ALB) is present.
Frequently Asked Questions
Why is a global inference profile wrong for European customer data?
What is an AWS Bedrock geographic inference profile?
Discussion 3 contributions
Compiled from public community threads and reader submissions, lightly edited for clarity. Handles and vote tallies are shown as recorded, and comments reflect the views of individual contributors.
From public community threads 3
-
953bf6d 👍 1 Answered AOption A is the correct solution. Why Option A Works • Data Sovereignty: Using a dedicated European inference profile with Geographic cross-Region inference ensures that requests and data for European customers stay strictly within AWS Regions located in Europe. • Performance & Throughput: The InvokeModel API combined with inference profiles handles high-volume traffic (1,000 transactions/sec) while keeping response times under 500 ms. • High Availability & Failover: Amazon Route 53 health checks and Amazon CloudWatch alarms provide automated monitoring and failover capabilities during connectivity disruptions.
-
TNT87 👍 1 Answered DData Sovereignty/Residency Compliance: Using a Europe-specific geographic inference profile (prefixed with eu.) ensures that any inference requests initiated by European applications are routed and processed only within AWS Regions located in Europe. This perfectly satisfies the data sovereignty requirement https://aws.amazon.com/blogs/machine-learning/global-cross-region-inference-for-latest-anthropic-claude-opus-sonnet-and-haiku-models-on-amazon-bedrock-in-thailand-malaysia-singapore-indonesia-and-taiwan/
-
seoyeon_01 👍 1Could someone explain why this answer makes sense in this context?
Reader comments & corrections
No reader corrections yet — spotted an error or have a note? Share it below.
Related Analysis
Practice All AIP-C01 Questions
Access 110 questions with complete answers and detailed explanations.
View Full AIP-C01 Practice Test →