Examkin

Soru

Zorluk: ZorCost-Optimized Compute Selection and Purchasing Strategies

An analytics company runs a real-time data processing application on AWS. The application consists of three main components:

* A front-end ingestion API hosted on Amazon ECS with AWS Fargate that experiences stable, continuous traffic 24/7.
* A legacy stateful data validation service that runs on Amazon EC2 instances and requires constant, continuous compute capacity.
* A business intelligence database running on Amazon RDS for MySQL that is operational 24/7.

The company wants to make a 3-year commitment to minimize their overall costs with minimal administrative overhead. Which purchasing strategy provides the lowest overall cost while meeting all architectural requirements?

  1. Purchase a 3-year Compute Savings Plan to cover the Amazon ECS Fargate tasks and the Amazon EC2 instances, and purchase 3-year Amazon RDS DB Instance Reserved Instances for the database.Cevap
  2. B
    Purchase a 3-year Compute Savings Plan to cover the Amazon ECS Fargate tasks, the Amazon EC2 instances, and the Amazon RDS database.
  3. C
    Purchase a 3-year EC2 Instance Savings Plan to cover the Amazon EC2 instances, use Amazon ECS Fargate Spot for the front-end ingestion API, and purchase a Compute Savings Plan to cover the Amazon RDS database.
  4. D
    Migrate the legacy stateful data validation service to run continuously on AWS Lambda to utilize Compute Savings Plans, and purchase Amazon RDS DB Instance Reserved Instances for the database.

Cevap

Purchase a 3-year Compute Savings Plan to cover the Amazon ECS Fargate tasks and the Amazon EC2 instances, and purchase 3-year Amazon RDS DB Instance Reserved Instances for the database.
The correct strategy combines a 3-year Compute Savings Plan for the ECS Fargate and EC2 validation service workloads with 3-year RDS DB Instance Reserved Instances for the database. Compute Savings Plans automatically apply discounts to compute usage across EC2 and Fargate, regardless of region or family. Because Amazon RDS is excluded from Compute Savings Plans, it must be covered by its own Reserved Instances to achieve maximum cost savings for the 24/7 database workload.

Adım Adım Çözüm

1
Analyze the compute requirements for the ingestion API and validation service.
The ingestion API (ECS Fargate) and legacy validation service (EC2) are both steady-state compute workloads running 24/7.
Identifying the patterns of the compute workloads allows for selecting the most appropriate purchasing model.
2
Select the optimal purchasing strategy for the Fargate and EC2 workloads.
A 3-year Compute Savings Plan is selected to cover both Fargate and EC2 instances.
Compute Savings Plans provide the highest flexibility (covering EC2, Fargate, and Lambda across any instance family and region) with up to 66% savings over a 3-year term.
3
Evaluate the database workload and determine its purchasing option.
Amazon RDS for MySQL is running 24/7 and is not covered by Compute Savings Plans. Select Amazon RDS DB Instance Reserved Instances.
Since Compute Savings Plans do not apply to Amazon RDS, RDS DB Instance Reserved Instances must be purchased separately to cover the database.

Anahtar Kavram

Compute purchasing strategies on AWS require matching specific services with their corresponding savings models, such as using Compute Savings Plans for EC2 and ECS Fargate while utilizing Reserved Instances for Amazon RDS databases.
Bu soruyu puanla

Konular

Cost-Optimized Compute Selection and Purchasing Strategies