A company's application is running on Amazon EC2 instances. The company is planning a partial migration to a serverless architecture in the next year and wants to pay for resources up front. Which AWS

Question

Options

• AConvertible Reserved Instances
• BSpot Instances
• CEC2 Instance Savings Plans
• DCompute Savings Plan

• A
  9% (2)
• B
  13% (3)
• C
  4% (1)
• D
  74% (17)

Explanation

Compute Savings Plans offer the most flexibility because they automatically apply discounts across EC2 instances, AWS Lambda, and AWS Fargate - making them ideal for a company transitioning to serverless while still running EC2. Since the company plans a partial migration to serverless, they need a savings plan that covers both current EC2 usage and future serverless workloads, which Compute Savings Plans uniquely provide with up to 66% savings.

Why the distractors are wrong:

• A (Convertible Reserved Instances): While these allow instance type flexibility, they are locked to EC2 only and don't extend to serverless services like Lambda or Fargate.
• B (Spot Instances): These don't involve upfront payments and are unpredictable/interruptible - unsuitable for planned, stable workloads.
• C (EC2 Instance Savings Plans): These also only apply to EC2 and don't cover serverless services, making them less flexible than Compute Savings Plans during a migration.

Memory Tip: Think "Compute = Complete Coverage" - Compute Savings Plans cover the broadest range of services (EC2 + Lambda + Fargate), while EC2 Instance Savings Plans are narrower (EC2 only). Whenever a question involves serverless migration + cost savings, Compute Savings Plans is almost always the answer.

No community discussion yet for this question.