Examkin

Question

Difficulty: MediumOptimizing Resource Costs and Sizing

An enterprise manages a multi-account environment under AWS Organizations with consolidated billing enabled. In member Account A, the production environment runs a containerized microservice on Amazon ECS on AWS Fargate that scales dynamically throughout the day, and several AWS Lambda functions that process real-time streaming data. In member Account B, a legacy application runs on Amazon EC2 m6i.largem6i.large instances 24/7 with a constant baseline CPU utilization of 80%80\%. The solutions architect needs to optimize resource costs for these workloads while maximizing the savings rate. Which two options represent the most cost-effective and architecturally sound actions to achieve this objective?

  1. Purchase Compute Savings Plans in the payer account of the organization to cover the Amazon ECS on AWS Fargate tasks and AWS Lambda functions.Answer
  2. Purchase EC2 Instance Savings Plans in Account B for the m6im6i instance family in the target AWS Region to cover the legacy application servers.Answer
  3. C
    Purchase EC2 Instance Savings Plans in the payer account to cover the dynamically scaling Amazon ECS on AWS Fargate tasks and AWS Lambda functions.
  4. D
    Use AWS Resource Access Manager (RAM) to share the Amazon EC2 instances in Account B with the payer account, and purchase EC2 Instance Savings Plans in the payer account.
  5. E
    Consolidate the outbound internet traffic from both Account A and Account B through a single NAT Gateway in Account B to minimize hourly NAT charges.

Answer

The most cost-effective and architecturally sound actions are to purchase Compute Savings Plans in the payer account to cover the AWS Fargate and AWS Lambda workloads, and to purchase EC2 Instance Savings Plans in Account B for the m6im6i instance family in the target AWS Region to cover the legacy application servers.
Purchasing Compute Savings Plans in the payer account allows the discount to automatically apply to the dynamically scaling ECS Fargate tasks and Lambda functions in Account A. Purchasing EC2 Instance Savings Plans in Account B for the m6im6i instance family provides the maximum discount for the steady-state, 24/7 legacy EC2 instances. Buying them in the specific member account ensures the local instances consume the commitment first before any excess is shared.

Step-by-Step Solution

1
Analyze the workload characteristics of Account A and Account B.
Account A contains dynamically scaling Amazon ECS on AWS Fargate tasks and AWS Lambda functions. Account B contains steady-state Amazon EC2 m6i.largem6i.large instances running 24/7.
Understanding the execution model (serverless/dynamic vs. steady-state EC2) is necessary to map them to the correct Savings Plan type.
2
Select the appropriate Savings Plan type for Account A's serverless and containerized workloads.
Compute Savings Plans must be selected because EC2 Instance Savings Plans do not cover AWS Fargate or AWS Lambda.
Compute Savings Plans offer the flexibility needed for dynamic workloads and cover EC2, Fargate, and Lambda.
3
Select the appropriate Savings Plan type for Account B's steady-state EC2 workloads.
EC2 Instance Savings Plans for the m6im6i instance family in the target AWS Region must be selected.
EC2 Instance Savings Plans offer the deepest discounts (up to 72%72\%) compared to Compute Savings Plans (up to 66%66\%) for steady-state workloads that do not change instance families or regions.

Key Concept

Optimizing compute costs by combining Compute Savings Plans for dynamic, serverless workloads with EC2 Instance Savings Plans for steady-state, family-specific EC2 instances across a multi-account organization.
Rate this question

Topics

Optimizing Resource Costs and Sizing

More questions from this topic