Examkin

Question

Difficulty: MediumOptimizing Resource Costs and Sizing

A media streaming platform hosts its content delivery, transcoding, and recommendation engine on AWS. The environment is organized under an AWS Organizations structure with consolidated billing. The transcoding tasks run on Amazon ECS using AWS Fargate, the recommendation engine is built on AWS Lambda, and the main web platform runs on an Auto Scaling group of Amazon EC2 instances. A Solutions Architect is tasked with optimizing the compute costs for these workloads without impacting application availability or introducing management overhead.

Which of the following actions should the Solutions Architect recommend to optimize resource costs? (Select TWO.)

  1. Commit to Compute Savings Plans at the organization's management account level, which applies cost reductions to the EC2, Fargate, and Lambda compute workloads across the member accounts.Answer
  2. Activate AWS Compute Optimizer in the organization management account to analyze utilization metrics for EC2 and Fargate, allowing right-sizing of resources prior to purchasing any savings commitments.Answer
  3. C
    Commit to EC2 Instance Savings Plans at the management account level to cover the combined compute usage of the EC2 instances, Fargate tasks, and Lambda functions across the organization.
  4. D
    Utilize AWS Resource Access Manager (RAM) to share the savings commitments from the management account to the member accounts, ensuring that target workloads receive the discounts first.
  5. E
    Route all egress traffic from member VPCs through a single NAT Gateway located in a shared transit VPC to eliminate hourly fees for multiple NAT Gateways.

Answer

Commit to Compute Savings Plans at the organization's management account level, and activate AWS Compute Optimizer in the organization management account to analyze utilization metrics for EC2 and Fargate to right-size resources before purchasing savings commitments.
Committing to Compute Savings Plans at the organization's management account level is correct because Compute Savings Plans automatically apply to EC2 instances, ECS Fargate tasks, and Lambda functions across all member accounts in the organization. Activating AWS Compute Optimizer allows the organization to right-size these resources before committing to a Savings Plan, which ensures that the savings plan is sized to actual needs, avoiding waste.

Step-by-Step Solution

1
Enable resource analysis and optimization recommendations.
AWS Compute Optimizer is activated at the AWS Organizations level, providing recommendations to right-size the EC2 instances and ECS Fargate tasks based on historical performance metrics.
Right-sizing resources first prevents purchasing excess savings commitments for over-provisioned infrastructure.
2
Assess the requirements of the mixed compute environment.
Identify that the workloads run across different compute services: EC2 instances, ECS Fargate tasks, and Lambda functions.
The choice of Savings Plan must cover all three compute types to maximize cost efficiency.
3
Select and purchase the appropriate Savings Plan type at the management account level.
Compute Savings Plans are purchased in the management account, which automatically applies discount rates to EC2, Fargate, and Lambda across all member accounts within the consolidated billing structure.
Compute Savings Plans offer the highest flexibility and are the only type that applies to EC2, Fargate, and Lambda simultaneously.

Key Concept

Compute cost optimization requires a combination of resource right-sizing to eliminate waste and selecting flexible Savings Plans (Compute Savings Plans) to cover heterogeneous compute resources (EC2, Fargate, Lambda) across an AWS Organization.
Rate this question

Topics

Optimizing Resource Costs and Sizing

More questions from this topic