Q7 — AWS SAA-C03 Ch.16

Question 7 of 100 | ← Chapter 16

Q1207. A company needs to accommodate traffic for a web application that the company hosts on AWS,especially during peak usage hours.The application uses Amazon EC2 instances as web servers,an Amazon RDS DB instance for database operations, and an Amazon S3 bucket to store transaction documents.The application struggles to scale effectively and experiences performance issues.The company wants to improve the scalability of the application and prevent future performance issues. The company also wants to improve global access speeds to the transaction documents for the company's global users.Which solution will meet these requirements?

• A. Place the EC2 instances in Auto Scaling groups to scale appropriately during peak usage hours. Use Amazon RDS read replicas to improve database read performance. Deploy an Amazon CloudFront distribution that uses Amazon S3 as the origin. ✓
• B. Increase the size of the EC2 instances to provide more compute capacity. Use Amazon ElastiCache to reduce database read loads. Use AWS Global Accelerator to optimize the delivery of the transaction documents that are in the S3 bucket.
• C. Transition workloads from the EC2 instances to AWS Lambda functions to scale in response to the usage peaks. Migrate the database to an Amazon Aurora global database to provide cross-Region reads. Use AWS Global Accelerator to deliver the transaction documents that are in the S3 bucket.
• D. Convert the application architecture to use Amazon Elastic Container Service (Amazon ECS) containers. Configure a Multi-AZ deployment of Amazon RDS to support database operations.Replicate the transaction documents that are in the S3 bucket across multiple AWS Regions.

Correct Answer: A. Place the EC2 instances in Auto Scaling groups to scale appropriately during peak usage hours. Use Amazon RDS read replicas to improve database read performance. Deploy an Amazon CloudFront distribution that uses Amazon S3 as the origin.

Explanation

To meet the company's requirements of improving the scalability of the web application, preventing future performance issues, and enhancing global access speeds to transaction documents, the most suitable solution is:A. Place the EC2 instances in Auto Scaling groups to scale appropriately during peak usage hours. Use Amazon RDS read replicas to improve database read performance. Deploy an Amazon CloudFront distribution that uses Amazon S3 as the origin.Analysis:Auto Scaling Groups for EC2 Instances:Scalability: By placing the EC2 instances in Auto Scaling groups, the application can automatically adjust the number of instances based on demand. This ensures that the application can handle increased traffic during peak usage hours without manual intervention, improving scalability and preventing performance issues.Amazon RDS Read Replicas:Database Performance: Read replicas can be used to offload read traffic from the primary RDS instance, improving database read performance. This is particularly useful for applications that have a high read-to- write ratio, as it reduces the load on the primary database and helps prevent performance bottlenecks.Amazon CloudFront Distribution with S3 Origin:Global Access Speeds: CloudFront is a content delivery network (CDN) that can cache content at edge locations around the world. By deploying a CloudFront distribution that uses the Amazon S3 bucket as the origin, the transaction documents can be delivered to global users with lower latency and higher throughput, improving access speeds and user experience.Why Other Options Are Not Suitable:B. Increase the size of the EC2 instances, use Amazon ElastiCache, and AWS Global Accelerator:Increasing Instance Size: While increasing the size of the EC2 instances can provide more compute capacity, it does not address the scalability issue during peak usage hours. Auto Scaling groups are a more flexible and scalable solution.Amazon ElastiCache: While ElastiCache can reduce database read loads, it does not directly address the scalability of the web application or the global access speeds to transaction documents. AWS Global Accelerator: While Global Accelerator can optimize the delivery of content, it is not as effective as CloudFront for caching and delivering static content from S3 buckets. C. Transition workloads to AWS Lambda, migrate to Amazon Aurora global database, and use AWS Global Accelerator:AWS Lambda: Transitioning workloads to Lambda functions may not be feasible for all parts of the application, especially if the application has long-running processes or requires persistent state. Amazon Aurora Global Database: While Aurora global database provides cross-Region reads, it is more complex and expensive than using read replicas for improving database read performance. AWS Global Accelerator: As mentioned earlier, Global Accelerator is not as effective as CloudFront for caching and delivering static content from S3 buckets.D. Convert to Amazon ECS containers, configure Multi-AZ deployment of Amazon RDS, and replicate S3 documents across multiple Regions:Amazon ECS Containers: While containers can improve scalability and deployment flexibility, they do not directly address the need for improved global access speeds to transaction documents. Multi-AZ Deployment of Amazon RDS: While Multi-AZ deployment provides high availability and durability for the database, it does not directly improve database read performance or scalability during peak usage hours.Replicating S3 Documents Across Multiple Regions: While this can improve global access speeds, it is more complex and costly than using CloudFront to cache and deliver content from a single S3 bucket.