Examkin

Question

Difficulty: EasyOptimizing Resource Costs and Sizing

A company manages a multi-account environment using AWS Organizations. The application architecture spans several member accounts, utilizing Amazon EC2 instances in an Auto Scaling group, containerized microservices on AWS Fargate, and serverless background tasks running on AWS Lambda. To reduce compute costs, the solutions architect needs to recommend a Savings Plan to be purchased in the organization's management account. The plan must offer maximum flexibility to automatically apply to EC2, Fargate, and Lambda across all member accounts without requiring manual allocation. Which Savings Plan should the solutions architect recommend?

  1. Compute Savings Plans, because they automatically apply to EC2 instances, AWS Fargate, and AWS Lambda usage across all accounts in the organization, regardless of instance family, region, or operating system.Answer
  2. B
    EC2 Instance Savings Plans, because they offer the deepest discounts and automatically apply to EC2, Fargate, and Lambda usage across the entire organization.
  3. C
    Compute Savings Plans, but the plans must be shared manually with each member account using AWS Resource Access Manager (RAM) to allow sharing across the organization.
  4. D
    EC2 Instance Savings Plans, combined with deploying a centralized NAT Gateway in a single Availability Zone to route all outbound Fargate and Lambda traffic through it to consolidate network costs.

Answer

Compute Savings Plans, because they automatically apply to EC2 instances, AWS Fargate, and AWS Lambda usage across all accounts in the organization, regardless of instance family, region, or operating system.
Compute Savings Plans offer the greatest flexibility by automatically applying to EC2, Fargate, and Lambda usage across all accounts in an AWS Organization, regardless of instance family, size, region, or operating system, with no manual allocation required.

Step-by-Step Solution

1
Analyze the compute services utilized in the multi-account architecture.
The architecture utilizes a combination of Amazon EC2, AWS Fargate, and AWS Lambda.
Identifying all compute services is critical to selecting a Savings Plan type that covers all of them.
2
Evaluate the coverage of the different Savings Plan types.
Compute Savings Plans cover EC2, Fargate, and Lambda, whereas EC2 Instance Savings Plans only cover EC2.
This comparison determines which plan can cover the diverse compute resources in the environment.
3
Determine how Savings Plans are shared and managed in a multi-account environment.
Savings Plans purchased at the management account automatically apply across all member accounts in the AWS Organization without using AWS Resource Access Manager.
Understanding organizational sharing ensures the proposed solution requires minimal administrative overhead.

Key Concept

Compute Savings Plans provide the flexibility needed to cover heterogeneous compute resources (EC2, Fargate, Lambda) automatically across all accounts in an AWS Organization.
Rate this question

Topics

Optimizing Resource Costs and Sizing

More questions from this topic