Q92 — AWS SAA-C03 Ch.13

Question 92 of 100 | ← Chapter 13

Q992. A company has developed a non-production application that is composed of multiple microservices for each of the company's business units. A single development team maintains all the microservices. The current architecture uses a static web frontend and a Java-based backend that contains the application logic. The architecture also uses a MySQL database that the company hosts on an Amazon EC2 instance.The company needs to ensure that the application is secure and available globally.Which solution will meet these requirements with the LEAST operational overhead?

Correct Answer: B. Use Amazon CloudFront and Amazon S3 to host the static web frontend. Refactor the microservices to use AWS Lambda functions that the microservices access by using Amazon API Gateway. Migrate the MySQL database to Amazon RDS for MySQL.

Explanation

To ensure that the application is secure, available globally, and requires the least operational overhead, the best solution is:B. Use Amazon CloudFront and Amazon S3 to host the static web frontend. Refactor the microservices to use AWS Lambda functions that the microservices access by using Amazon API Gateway. Migrate the MySQL database to Amazon RDS for MySQL.Explanation:Amazon CloudFront: This content delivery network (CDN) improves the availability and performance of the static web frontend by caching content at edge locations around the world, ensuring fast delivery to users globally.Amazon S3: Hosting the static web frontend in S3 is cost-effective and requires minimal management. S3 provides high availability and durability for static content.AWS Lambda and Amazon API Gateway: Refactoring the microservices to use AWS Lambda allows for a serverless architecture, which reduces operational overhead since there is no need to manage servers or scaling. Amazon API Gateway provides a secure and scalable way to expose these Lambda functions as APIs.Amazon RDS for MySQL: Migrating the MySQL database to Amazon RDS simplifies database management tasks like backups, patching, and scaling, while also providing high availability with features like Multi-AZ deployments.Evaluation of Other Options:A. Use Amazon CloudFront and AWS Amplify: While AWS Amplify is great for front-end applications, it may not be necessary for a static web frontend hosted in S3. The option also suggests using EC2 Reserved Instances for the MySQL database, which adds operational overhead compared to RDS.C. Use Amazon CloudFront and Amazon S3... with a Network Load Balancer: This option introduces unnecessary complexity by using a Network Load Balancer for Lambda functions, which is not a typical use case for serverless architectures.D. Use Amazon S3 to host the static web frontend... with an Application Load Balancer: This option does not utilize CloudFront for global availability and performance improvements, and using an Application Load Balancer adds more operational overhead compared to API Gateway.In summary, Option B provides a robust, scalable, and cost-effective solution that meets the company's needs while minimizing operational overhead.