Amazon Web Services Updated SAP-C02 Exam Questions and Answers by zayne

This is a data residency and preventive governance problem. EU customer uploads must be routed to EU endpoints, processed by EU workloads, and stored only in EU Regions. Separate EU and non-EU stacks avoid commingling workloads and make residency controls enforceable. Route 53 geolocation routing is appropriate because the routing decision is based on user location, not latency. The critical control is an Organizations SCP that denies resource creation outside approved Regions. AWS documents region-deny patterns using the aws:RequestedRegion condition and AWS Control Tower Region deny controls to prevent actions outside governed Regions. AWS Config is detective, not preventive, so option C is too late. Latency-based routing can send EU users outside the EU, and a single global API design weakens the sovereignty boundary.

Deploying the shared libraries and custom classes to a Docker image and uploading the image to Amazon Elastic Container Registry (Amazon ECR) and creating a Lambda layer that uses the Docker image as the source. Then, deploying the API ' s Lambda functions as Zip packages and configuring the packages to use the Lambda layer would meet the requirements for simplifying the deployment and optimizing for code reuse.

A Lambda layer is a distribution mechanism for libraries, custom runtimes, and other function dependencies. It allows you to manage your in-development function code separately from your dependencies, this way you can easily update your dependencies without having to update your entire function code.

By deploying the shared libraries and custom classes to a Docker image and uploading the image to Amazon Elastic Container Registry (ECR), it makes it easy to manage and version the dependencies. This way, the company can use the same version of the dependencies across different Lambda functions.

By creating a Lambda layer that uses the Docker image as the source, the company can configure the API ' s Lambda functions to use the layer, reducing the need to include the dependencies in each function package, and making it easy to update the dependencies across all functions at once.

Dis the right choice:EFS with Max I/O modeis designed formassively parallel workloadslike big data. It supports high throughput and concurrent access from many EC2 nodes across AZs.

A(Storage Gateway) is not optimized for high-performance, low-latency compute clusters.

Bis limited in performance (latency optimized for single-threaded workloads).

C(EBS) cannot be shared across AZs and is not POSIX-compatible for concurrent multi-node access.

The performance symptom is classic Lambda cold-start variability. The API is used sporadically, so Lambda execution environments may be recycled between requests. The first request takes longer because Lambda must initialize an execution environment; subsequent identical requests are faster because the environment is already warm. Provisioned concurrency keeps execution environments initialized and ready to respond, producing more consistent latency. AWS Application Auto Scaling can manage provisioned concurrency with target tracking, which helps align provisioned capacity with usage patterns. DynamoDB on-demand mode already scales automatically for table throughput, and DAX would mainly help read-heavy caching scenarios, not Lambda initialization delay. CloudFront may reduce network latency for cacheable content, but it does not remove Lambda cold starts for dynamic API calls. (AWS Documentation)

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