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

Compute Savings Plan: This plan offers significant discounts on Lambda functions compared to on-demand pricing. Since the application will run for a year, a sustained use discount like Compute Savings Plan is ideal. Private Subnets: Lambda functions in private subnets can directly access EC2 instances within the VPC without needing internet access, reducing security risks and potential egress costs.

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 or Lambda usage. For example, with Compute Savings Plans, you can change from C4 to M5 instances, shift a workload from EU (Ireland) to EU (London), or move a workload from EC2 to Fargate or Lambda at any time and automatically continue to pay the Savings Plans price.

Why Compute Savings Plan: Covers both EC2 and Lambda, providing flexibility as Lambda usage increases. Why Private Subnets: Ensures network access between Lambda and EC2 instances. !! An EC2 Instance Savings Plan doesn't cover Lambda. Also, Lambda functions in public subnets cannot directly communicate with EC2 instances in private subnets.

A and B is not because it is talkign about EC2, but the question is asking for Lambda

Compute savings include lamdba and EC2, Ec2 savings only EC2 instances. https://aws.amazon.com/savingsplans/compute-pricing/

I confuse this Question. Instance saving plan is cheaper than compute saving plan. https://aws.amazon.com/savingsplans/compute-pricing/

In this question has point out "access EC2 instances" within VPC,=> Lambda VPC to an ENI (Elastic network interface) in your account VPC.=>No charge. Therefore I stick with A, Not D.

AnswerD https://docs.aws.amazon.com/lambda/latest/dg/foundation-networking.html