Domain 2: Reliability and Business Continuity
Explore key AWS operational strategies to improve reliability and business continuity, including dynamic scaling, failover optimization, backup management, and disaster recovery approaches. Understand how to implement best practices with AWS services like CloudFront, DynamoDB, Aurora, RDS, S3, ElastiCache, Auto Scaling, Route 53, and AWS Backup. This lesson equips you with practical guidance to maintain application availability and data integrity during high demand and failures.
Question 15
An e-commerce platform serves dynamic product pages globally through an Application Load Balancer-backed web tier. During flash sales, the origin is overwhelmed by repeated requests for semi-dynamic assets and API responses that change infrequently. The team wants to improve dynamic scalability without changing core application logic.
Which solution is the best fit?
A. Place a Network Load Balancer in front of the origin web tier to improve throughput for repeated requests.
B. Use Amazon CloudFront with appropriate cache behaviors and TTL settings for semi-dynamic content and API responses.
C. Disable caching because the content is dynamic and increase the size of the EC2 instances behind the Application Load Balancer.
D. Configure Route 53 latency-based routing to direct users to the nearest Region without introducing a caching layer.
Question 16
A mobile order-tracking application uses Amazon DynamoDB and experiences request throttling during sudden campaign-driven traffic surges. The operations team wants to maintain performance with minimal manual tuning. Repeated reads of the same order status are common during these events.
Which actions should the team choose? Select any three options.
A. Switch the table to on-demand capacity mode for highly variable traffic patterns.
B. Configure DynamoDB auto scaling for provisioned throughput if the team wants managed adjustment of capacity.
C. Add DAX if repeated read access patterns are a significant contributor to latency during spikes.
D. Put DynamoDB behind an Elastic Load Balancer to distribute requests across partitions.
E. Rely only on exponential backoff in the application and make no table capacity changes.
F. Add RDS read replicas so relational replicas can absorb excess DynamoDB read traffic.
Question 17
A read-heavy SaaS application uses Amazon Aurora. The writer instance remains healthy, but high read traffic saturates CPU and begins to affect write latency during peak usage. The team wants the best architecture change to improve scalability while keeping operations managed.
What should they do?
A. Add Aurora Replicas and direct read traffic to the cluster reader endpoint.
B. Enable Multi-AZ only, because ...