SAP-C02 · Question #529
A company wants to manage the costs associated with a group of 20 applications that are infrequently used, but are still business-critical, by migrating to AWS. The applications are a mix of Java…
The correct answer is B. Deploy Amazon ECS containers on Amazon EC2 with Auto Scaling configured for memory. To minimize costs and standardize deployment for diverse, infrequently used applications including a long-running report, Amazon ECS containers on Amazon EC2 with Auto Scaling should be used for the core applications, complemented by AWS Fargate for those requiring higher…
Question
A company wants to manage the costs associated with a group of 20 applications that are infrequently used, but are still business-critical, by migrating to AWS. The applications are a mix of Java and Node.js spread across different instance clusters. The company wants to minimize costs while standardizing by using a single deployment methodology. Most of the applications are part of month-end processing routines with a small number of concurrent users, but they are occasionally run at other times. Average application memory consumption is less than 1 GB. though some applications use as much as 2.5 GB of memory during peak processing. The most important application in the group is a billing report written in Java that accesses multiple data sources and often runs for several hours. Which is the MOST cost-effective solution?
Options
- ADeploy a separate AWS Lambda function for each application. Use AWS CloudTrail logs and
- BDeploy Amazon ECS containers on Amazon EC2 with Auto Scaling configured for memory
- CDeploy AWS Elastic Beanstalk for each application with Auto Scaling to ensure that all requests
- DDeploy a new Amazon EC2 instance cluster that co-hosts all applications by using EC2 Auto
How the community answered
(31 responses)- A13% (4)
- B45% (14)
- C6% (2)
- D35% (11)
Why each option
To minimize costs and standardize deployment for diverse, infrequently used applications including a long-running report, Amazon ECS containers on Amazon EC2 with Auto Scaling should be used for the core applications, complemented by AWS Fargate for those requiring higher memory or further operational simplicity.
Deploying all applications as AWS Lambda functions is unsuitable because the critical billing report often runs for several hours, exceeding Lambda's 15-minute maximum runtime.
Deploying applications as Amazon ECS containers on Amazon EC2 provides a standardized deployment methodology for mixed runtimes (Java, Node.js), allows Auto Scaling for cost efficiency on unpredictable workloads, supports long-running processes, and AWS Fargate can specifically provide serverless compute for containers with higher memory requirements, further minimizing costs for infrequent use.
Deploying AWS Elastic Beanstalk for each application might not be the most cost-effective or streamlined deployment for 20 infrequently used applications compared to a shared container orchestration platform like ECS, and it still runs underlying EC2 instances.
Co-hosting 20 diverse applications on a single Amazon EC2 instance cluster can lead to resource contention, management complexity, and is less cost-effective or flexible for varied workloads than a containerized approach.
Concept tested: Containerization, ECS, Fargate, Cost Optimization
Source: https://docs.aws.amazon.com/AmazonECS/latest/developerguide/ecs_services.html
Community Discussion
No community discussion yet for this question.