Examkin

Soru

Zorluk: ZorCost-Optimized Compute Selection and Purchasing Strategies

A financial company runs a risk modeling application on AWS. The application consists of two main workloads:

1. A continuous, steady-state transaction-processing service running on AWS Fargate.
2. A daily batch-processing job running on AWS Fargate that can tolerate interruptions and does not have a strict completion time.

The company also hosts a stateful PostgreSQL database on Amazon RDS that runs continuously to support the transaction-processing service.

Which two purchasing strategies should the solutions architect recommend to minimize overall compute and database costs?

  1. Purchase a Compute Savings Plan to cover the continuous transaction-processing service running on AWS Fargate.Cevap
  2. Use Fargate Spot to run the daily batch-processing job.Cevap
  3. C
    Purchase a Compute Savings Plan to cover the costs of both the continuous transaction-processing service on Fargate and the Amazon RDS PostgreSQL database.
  4. D
    Purchase an EC2 Instance Savings Plan to cover the continuous transaction-processing service running on AWS Fargate.
  5. E
    Migrate the continuous transaction-processing service to run continuously on AWS Lambda using On-Demand pricing to eliminate Fargate compute costs.

Cevap

The correct strategies are purchasing a Compute Savings Plan to cover the continuous transaction-processing service running on AWS Fargate, and using Fargate Spot to run the daily batch-processing job.
The continuous, steady-state transaction-processing service runs on AWS Fargate, which is covered by Compute Savings Plans. Purchasing a Compute Savings Plan provides significant discounts for Fargate. The daily batch-processing job is interruptible and has flexible completion times, making Fargate Spot the most cost-effective choice, providing up to a 70% discount compared to Fargate On-Demand.

Adım Adım Çözüm

1
Analyze the workload characteristics of each compute component.
The transaction-processing service runs continuously (steady-state), while the batch-processing job is daily, interruptible, and has no strict completion time.
Understanding workload patterns is necessary to choose between commitment-based discounts and spot pricing.
2
Select the cost-optimized purchasing option for the steady-state Fargate service.
Compute Savings Plans apply discounts of up to 66% to EC2, AWS Fargate, and AWS Lambda usage, making them ideal for the continuous transaction-processing service.
Fargate compute is covered by Compute Savings Plans, but not by EC2 Instance Savings Plans.
3
Select the cost-optimized purchasing option for the interruptible batch service.
Fargate Spot offers up to a 70% discount compared to On-Demand Fargate prices for workloads that can tolerate interruptions.
Since the batch job can tolerate interruptions and has no strict completion time, Fargate Spot provides the highest savings.
4
Evaluate database costing and rule out incorrect purchasing plan coverages.
Compute Savings Plans and EC2 Instance Savings Plans do not cover Amazon RDS, and AWS Lambda is not cost-effective for continuous long-running workloads.
Savings Plans scope must not be misapplied to non-compute services like Amazon RDS.

Anahtar Kavram

Matching compute workloads to the correct AWS purchasing models (Compute Savings Plans, Fargate Spot) while understanding the scope boundaries of Savings Plans.
Tahmini Süre:2m 30s
Bu soruyu puanla

Konular

Cost-Optimized Compute Selection and Purchasing Strategies