Exam AWS Certified Solutions Architect - Associate SAA-C03 topic 1 question 140 discussion

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.

One other follow-up item on splitting hairs for whether C or D is the best answer... you can pull of a combination of reserved instances that would be more ideal for answering the question as D, but again in the real world, C would be more correct. "Yes, you can leverage Reserved Instances with Amazon ECS (Elastic Container Service) to reduce costs for your container workloads. While ECS itself doesn't have specific "ECS Reserved Instances", you can achieve cost savings by using Reserved Instances with the underlying EC2 instances that support your ECS cluster, especially when using EC2 launch types. "

Ah, I see, the highest responses are sent to the top. Got it, well that may be the best possible, though not always accurate.

I'm guessing the responses to my answers are running through an AI generated lookup and reply as they are instantaneous and not completely addressing my comments... interesting. Well, so much for posting discussions))

Yes, that is correct, for the real world

Follow-up, the better answer is still D. but in the real world, the answer is C, not D. In the real world there is no such thing as a predictable, I would not rely on a reserved instance for such but have the 6% cost difference vs the risk as a factor for using a compute savings plan. For the test, A, D; for the real world A, C.

A is obvious. D takes some real understanding of the cost of a known reserved instance overhead vs the flexibility of compute savings plan. Since the performance of the next year is known, a reserved savings plan is actually cheaper than a compute savings plan. "Reserved Instances (RIs), especially Standard RIs, traditionally offered the highest potential discounts (up to 72% for EC2 instances) but came with rigid terms. You had to commit to specific instance types, regions, operating systems, and tenancies for a 1 or 3-year term." You have to assume that the question is stating correctly the performance of the next year is known, "The front-end utilization and API layer utilization will be predictable over the course of the next year." C is a good answer, but D is actually better.

Ans A, C - A: Spot obvious for unpredictable, 'don't care' usage C: Not so obvious... but its more than just EC2 - its about Compute power using Fargate, Lambda, API call processing so it has to be C (as opposed to E)

Be mindful that the question is asking about API. So it should be Compute Savings Plans. If it is for EC2, the Reserved Instance will be correct.

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?