EC2 instance Savings Plan saves 72% while Compute Savings Plans saves 66%. But according to link, it says "Compute Savings Plans provide the most flexibility and help to reduce your costs by up to 66%. These plans automatically apply to EC2 instance usage regardless of instance family, size, AZ, region, OS or tenancy, and also apply to Fargate and Lambda usage." EC2 instance Savings Plans are not applied to Fargate or Lambda

Compute Savings Plans can be used for EC2 instances and Fargate. Whereas EC2 Savings Plans support EC2 only.

Compute Savings Plans can also apply to Fargate and Lambda Usage.

BC is the answer data ingestion = Spot Instance but Keyword "Usage Unpredictable" : On-Demand and for APi its Compute Savings Plan

The two most cost-effective purchasing options for this architecture are: A) Use Spot Instances for the data ingestion layer C) Purchase a 1-year Compute Savings Plan for the front end and API layer The reasons are: Spot Instances provide the greatest savings for flexible, interruptible EC2 workloads like data ingestion. Savings Plans offer significant discounts for predictable usage like the front end and API layer. All Upfront and partial/no Upfront RI's don't align well with the sporadic EC2 usage. On-Demand is more expensive than Spot for flexible EC2 workloads. By matching purchasing options to the workload patterns, Spot for unpredictable EC2 and Savings Plans for steady-state usage, the solutions architect optimizes cost efficiency.

Using Spot Instances for the data ingestion layer will provide the most cost-effective option for sporadic and unpredictable workloads, as Spot Instances offer significant cost savings compared to On-Demand Instances (Option A). Purchasing a 1-year Compute Savings Plan for the front end and API layer will provide cost savings for predictable utilization over the course of a year (Option C). Option B is less cost-effective as it suggests using On-Demand Instances for the data ingestion layer, which does not take advantage of cost-saving opportunities. Option D suggests purchasing 1-year All Upfront Reserved instances for the data ingestion layer, which may not be optimal for sporadic and unpredictable workloads. Option E suggests purchasing a 1-year EC2 instance Savings Plan for the front end and API layer, but Compute Savings Plans are typically more suitable for predictable workloads.

Spot instances for data injection because the task can be terminated at anytime and tolerate disruption. Compute Saving Plan is cheaper than EC2 instance Savings plan.

EC2 instance Savings Plans are not applied to Fargate or Lambda

Why not B?

To optimize the cost of running this application on AWS, you should consider the following options: A. Use Spot Instances for the data ingestion layer C. Purchase a 1-year Compute Savings Plan for the front-end and API layer Therefore, the most cost-effective solution for hosting this application would be to use Spot Instances for the data ingestion layer and to purchase either a 1-year Compute Savings Plan or a 1-year EC2 instance Savings Plan for the front-end and API layer.

Too obvious answer.

AC can be interrupted at any time => spot

A,E:: Savings Plan — EC2 Savings Plan offers almost the same savings from a cost as RIs and adds additional Automation around how the savings are being applied. One way to understand is to say that EC2 Savings Plan are Standard Reserved Instances with automatic switching depending on Instance types being used within the same instance family and additionally applied to ECS Fargate and Lambda. Savings Plan — Compute Savings Plan offers almost the same savings from a cost as RIs and adds additional Automation around how the savings are being applied. For example, they provide flexibility around instance types and regions so that you don’t have to monitor new instance types that are being launched. It is also applied to Lambda and ECS Fargate workloads. One way to understand is to say that Compute Savings Plan are Convertible Reserved Instances with automatic switching depending on Instance types being used.

A and C

its A and C . https://www.densify.com/finops/aws-savings-plan

api is not EC2.need to use compute savings plan

E makes more sense than C. See https://aws.amazon.com/savingsplans/faq/, EC2 instance Savings Plan (up to 72% saving) costs less than Compute Savings Plan (up to 66% saving)