SAA-C03 Question #556: Real Exam Question with Answer & Explanation

Question

A company runs its application by using Amazon EC2 instances and AWS Lambda functions. The EC2 instances run in private subnets of a VPC. The Lambda functions need direct network access to the EC2 instances for the application to work. The application will run for 1 year. The number of Lambda functions that the application uses will increase during the 1-year period. The company must minimize costs on all application resources. Which solution will meet these requirements?

Options

• APurchase an EC2 Instance Savings Plan. Connect the Lambda functions to the private sub-nets
• BPurchase an EC2 Instance Savings Plan. Connect the Lambda functions to new public sub-nets
• CPurchase a Compute Savings Plan. Connect the Lambda functions to the private subnets that
• DPurchase a Compute Savings Plan. Keep the Lambda functions in the Lambda service VPC.

Explanation

Compute Savings Plans apply to EC2, AWS Fargate, and AWS Lambda usage, maximizing coverage for mixed architectures while retaining flexibility across instance families, regions, OS, and tenancy. For private connectivity, Lambda functions must be configured with VPC access to attach ENIs in the target subnets, enabling direct network access to EC2 in private subnets (no public subnets are required for intra-VPC communication). EC2 Instance Savings Plans only discount EC2 usage and are tied to a specific instance family in a region, reducing flexibility and leaving Lambda costs undiscounted. Keeping Lambda in the service VPC prevents direct access to private EC2 without VPC configuration. Thus, a 1-year Compute Savings Plan plus connecting Lambda to the private subnets minimizes total cost and meets connectivity needs.

No community discussion yet for this question.