SAP-C02 · Question #271
A company is running a three-tier web application in an on-premises data center. The frontend is served by an Apache web server, the middle tier is a monolithic Java application, and the storage…
The correct answer is A. Refactor the frontend so that static assets can be hosted on Amazon S3. C. Rehost the Java application in an AWS Elastic Beanstalk environment that includes auto scaling. E. Use AWS Database Migration Service (AWS DMS) to replatform the PostgreSQL database to an. To address overload issues, maximize scalability, and minimize operational effort for the three-tier application, the company should host static frontend assets on Amazon S3, rehost the Java application on AWS Elastic Beanstalk with auto scaling, and replatform the PostgreSQL…
Question
A company is running a three-tier web application in an on-premises data center. The frontend is served by an Apache web server, the middle tier is a monolithic Java application, and the storage tier is a PostgreSOL database. During a recent marketing promotion, customers could not place orders through the application because the application crashed An analysis showed that all three tiers were overloaded. The application became unresponsive, and the database reached its capacity limit because of read operations. The company already has several similar promotions scheduled in the near future. A solutions architect must develop a plan for migration to AWS to resolve these issues. The solution must maximize scalability and must minimize operational effort. Which combination of steps will meet these requirements? (Choose three.)
Options
- ARefactor the frontend so that static assets can be hosted on Amazon S3.
- BRehost the Apache web server of the frontend on Amazon EC2 instances that are in an Auto
- CRehost the Java application in an AWS Elastic Beanstalk environment that includes auto scaling.
- DRefactor the Java application.
- EUse AWS Database Migration Service (AWS DMS) to replatform the PostgreSQL database to an
- FRehost the PostgreSQL database on an Amazon EC2 instance that has twice as much memory
How the community answered
(15 responses)- A60% (9)
- B7% (1)
- D27% (4)
- F7% (1)
Why each option
To address overload issues, maximize scalability, and minimize operational effort for the three-tier application, the company should host static frontend assets on Amazon S3, rehost the Java application on AWS Elastic Beanstalk with auto scaling, and replatform the PostgreSQL database to Amazon RDS using AWS DMS.
Hosting static assets on Amazon S3 greatly improves frontend scalability by offloading the web server and leveraging S3's high availability and performance, with minimal operational effort.
While rehosting Apache on EC2 with Auto Scaling provides scalability, offloading static assets to S3 (Choice A) is a more effective and lower-effort first step for frontend optimization.
Rehosting the Java application in AWS Elastic Beanstalk, which includes auto scaling, maximizes scalability for the middle tier and minimizes operational effort due to its managed service capabilities.
Refactoring the Java application, though beneficial for long-term scalability, contradicts the requirement to minimize operational effort, as it involves significant development work.
Replatforming the PostgreSQL database to Amazon RDS using AWS DMS allows for easy vertical and horizontal scaling (e.g., read replicas) to handle read operations, while significantly reducing operational overhead through a fully managed database service.
Rehosting the PostgreSQL database on a larger EC2 instance only scales vertically and does not provide the managed service benefits, operational efficiency, or read-replica scalability of Amazon RDS.
Concept tested: Three-tier migration, scalability, managed services, operational efficiency
Source: https://docs.aws.amazon.com/AmazonS3/latest/userguide/WebsiteHosting.html
Community Discussion
No community discussion yet for this question.