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

AWS Systems Manager State Manager is the correct service because it maintains a desired configuration state across managed nodes. An association can define that specific software, such as antivirus or monitoring agents, must be installed and running with the required configuration. This directly satisfies the requirement to ensure all 10,000 EC2 instances consistently run the latest SaaS agent configuration with the least administrative overhead. A custom Lambda that logs in to every machine is fragile, hard to secure, and operationally expensive. AWS Config is useful for evaluating resource configuration, but it is not the most direct tool for recurring software installation and configuration enforcement inside EC2 instances. Session Manager and user data are also poor choices because user data normally runs at launch and does not continuously enforce state. (AWS Documentation)

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

Dis the AWS best practice forsession storage: UseElastiCache for Redis— a fast, in-memory data store that handles high throughput with microsecond latency.

It ' s highly scalable, fault-tolerant, and optimized for temporary, fast-access session data.

Incorrect:

A: S3 is slow and object-based — not for session I/O.

B: FSx is Windows-only and not ideal for this use case.

C: EBS Multi-Attach has limitations, complexity, and is not suitable for high-performance shared memory.

Configure AWS Budgets in the organization ג €™s master account and configure budget alerts that are grouped by application, environment, and owner. Add each business unit to an Amazon SNS topic for each alert. Use Cost Explorer in the organization ג €™s master account to create monthly reports for each business unit.

https://aws.amazon.com/about-aws/whats-new/2019/07/introducing-aws-budgets-reports/#:~:text=AWS%20Budgets%20gives%20you%20the,below%20the%20threshold%20you%20define

The requirement is to reduce application latency for a globally distributed user base, with users primarily in the United States but increasing usage in Europe and the Middle East. The application is read-heavy and uses Amazon DynamoDB as its data store. Reducing latency for global users requires placing both the application compute and the data closer to users in each Region.

Option D uses the correct multi-Region architecture. Deploying the application to multiple AWS Regions places Amazon EKS workloads closer to end users. Converting the DynamoDB table to a global table creates fully managed, multi-Region replicas of the data with low-latency replication. This allows reads to be served locally from the nearest DynamoDB replica, significantly reducing read latency for users outside the primary Region. Because the workload is read-heavy, this design is particularly effective.

Route 53 geolocation routing directs users to the Region closest to them based on their geographic location. Combined with health checks and Evaluate Target Health, this ensures users are routed to the nearest healthy Region, improving both latency and availability.

Option A is incorrect because global secondary indexes do not replicate data across Regions. GSIs operate within a single Region and are used to support alternative query patterns, not global data distribution. Additionally, Route 53 failover routing is designed for disaster recovery, not for performance optimization or global load balancing.

Option B uses DynamoDB Accelerator (DAX), which improves read latency by caching data in memory, but DAX is Region-specific and does not reduce cross-Region network latency for users in Europe and the Middle East accessing a US-based application. It also does not address application-level latency caused by distance to the EKS cluster.

Option C is not valid because DynamoDB does not support read replicas in the same way relational databases do. DynamoDB replication for latency and global access is achieved through global tables, not through read replicas in a single Region. CloudFront can reduce latency for static or cacheable HTTP content, but it does not solve backend application latency or DynamoDB access latency for dynamic, read-heavy requests.

Therefore, deploying the application and DynamoDB as global tables across Regions and using Route 53 geolocation routing is the correct solution to minimize latency for all global users.