Examkin

Question

Difficulty: MediumOptimizing Resource Costs and Sizing

A logistics company manages its IT environment using AWS Organizations with consolidated billing enabled. The environment consists of a production account and a development account. The production account runs a continuous telemetry application on Amazon ECS Fargate and a legacy database cluster on Amazon EC2 m6i instances. The development account runs dynamic, ephemeral testing environments on AWS Lambda and Amazon EC2. The company wants to optimize its compute spend across both accounts while maintaining high availability and minimizing administrative overhead. Which strategy should a solutions architect recommend to achieve these goals at the lowest cost?

  1. Purchase Compute Savings Plans in the organization's management account.Answer
  2. B
    Purchase EC2 Instance Savings Plans for the m6i instance family in the management account.
  3. C
    Purchase EC2 Instance Savings Plans in the production account and Compute Savings Plans in the development account, then share them across accounts using AWS Resource Access Manager (RAM).
  4. D
    Consolidate all outbound traffic from both accounts through a single NAT Gateway in the production account, and purchase Compute Savings Plans in the production account.

Answer

Purchase Compute Savings Plans in the organization's management account.
Purchasing Compute Savings Plans in the organization's management account provides the highest flexibility and maximum overall savings. Compute Savings Plans automatically apply to EC2 instances (regardless of family, region, or operating system), ECS Fargate tasks, and AWS Lambda functions across all accounts under consolidated billing. This requires no administrative sharing setup and covers all the specified compute services.

Step-by-Step Solution

1
Analyze the compute workload types across the AWS Organization.
The workloads consist of Amazon EC2 instances, Amazon ECS Fargate tasks, and AWS Lambda functions.
Understanding the specific compute types determines the appropriate Savings Plan category required to cover all active resources.
2
Evaluate the eligibility of Savings Plan types for the workloads.
Compute Savings Plans cover EC2, Fargate, and Lambda. EC2 Instance Savings Plans only cover EC2.
This step ensures that the selected Savings Plan type maximizes discount coverage across the heterogeneous compute fleet.
3
Determine how Savings Plan benefits are shared across a multi-account organization.
Savings Plans purchased in any account (including the management account) automatically apply to eligible usage in any member account under consolidated billing.
This confirms that purchasing in the management account will distribute the discount across production and development accounts without manual intervention or RAM sharing.
4
Verify that all architecture and high availability constraints are met.
Avoiding NAT Gateway consolidation ensures that no single point of failure is introduced into the networking path.
Cost-saving measures must not compromise the high availability requirements of the production workloads.

Key Concept

Selecting and applying the appropriate Savings Plan type across a multi-account AWS Organization containing serverless and traditional compute resources.
Estimated Time:2m 0s
Rate this question

Topics

Optimizing Resource Costs and Sizing

More questions from this topic