Soru

Zorluk: OrtaCost-Optimized Compute Selection and Purchasing Strategies

A media company hosts a containerized video transcoding application on AWS Fargate. The transcoding tasks require a steady-state baseline of 12 tasks running 24/7, and scale up to 50 tasks during peak evening hours. The application's metadata database runs on Amazon RDS for MySQL and requires continuous 24/7 operation. Which combination of purchasing strategies will minimize compute costs while ensuring the application meets its availability requirements? (Select TWO.)

  1. Purchase a Compute Savings Plan to cover the baseline capacity of the AWS Fargate tasks.Cevap
  2. Purchase Amazon RDS Reserved Instances for the MySQL database.Cevap
  3. C
    Purchase a single Compute Savings Plan to cover both the AWS Fargate tasks and the Amazon RDS MySQL database.
  4. D
    Migrate the 24/7 video transcoding service from AWS Fargate to AWS Lambda to eliminate baseline compute costs.
  5. E
    Use On-Demand capacity for the baseline AWS Fargate tasks and purchase a Compute Savings Plan to cover the Amazon RDS MySQL database.

Cevap

Purchase a Compute Savings Plan to cover the baseline capacity of the AWS Fargate tasks, and purchase Amazon RDS Reserved Instances for the MySQL database.
To minimize compute costs for a 24/7 baseline containerized workload on AWS Fargate, purchasing a Compute Savings Plan is the most effective approach. For the database tier running on Amazon RDS that also operates 24/7, purchasing Amazon RDS Reserved Instances provides the necessary discount. Together, these two strategies minimize the steady-state baseline costs of both compute components.

Adım Adım Çözüm

1
Analyze the compute requirements for the containerized transcoding tier.
The Fargate tasks have a 24/7 baseline of 12 tasks and a dynamic scaling component up to 50 tasks.
Identifying the baseline allows for commitment-based discounts, while the scaling portion requires flexible models like On-Demand or Spot.
2
Select the appropriate purchasing strategy for the Fargate baseline.
A Compute Savings Plan is selected to cover the baseline of 12 tasks.
Compute Savings Plans offer up to 66% savings on Fargate workloads in exchange for a 1- or 3-year commitment, matching the continuous baseline requirement.
3
Analyze the database tier requirements and choose the right purchasing strategy.
Amazon RDS Reserved Instances are selected for the MySQL database.
The database operates 24/7 continuously, making it ideal for RDS Reserved Instances. Compute Savings Plans do not apply to RDS.

Anahtar Kavram

Selecting cost-optimized purchasing options (Savings Plans and Reserved Instances) for heterogeneous AWS workloads.
Bu soruyu puanla