Answer-first summary for fast verification
Answer: Leverage Spot Instances for the EC2 data ingestion layer due to its unpredictable nature, Implement a 1-year Compute Savings Plan for the stable front-end and API layer workloads on Fargate and Lambda
For the data ingestion layer running on EC2 with sporadic and unpredictable usage, using Spot Instances (Option A) is the most cost-effective option as they are significantly cheaper than On-Demand Instances, especially for workloads that can handle interruptions. For the front end and API layer, which have predictable utilization over the next year, purchasing a 1-year Compute Savings Plan (Option C) provides significant cost savings compared to On-Demand pricing. This combination balances cost optimization while ensuring the application can handle its varying workload demands.
Author: LeetQuiz Editorial Team
Ultimate access to all questions.
As a solutions architect, how would you recommend optimizing AWS costs for an application using EC2, Fargate, and Lambda, given that EC2 handles unpredictable data ingestion which can be interrupted, while Fargate and Lambda serve predictable front-end and API layer workloads, respectively?
A
Leverage Spot Instances for the EC2 data ingestion layer due to its unpredictable nature
B
Utilize On-Demand Instances for managing the EC2 data ingestion layer
C
Implement a 1-year Compute Savings Plan for the stable front-end and API layer workloads on Fargate and Lambda
D
Adopt 1-year All Upfront Reserved instances for the EC2 data ingestion layer
E
Select a 1-year EC2 instance Savings Plan for the consistent front-end and API layer operations
No comments yet.