Soru

Zorluk: Çok zorAWS Pricing Models

A company is designing a cost-optimization strategy for three distinct workloads running on Amazon EC2:

1. A continuous, predictable baseline of containerized microservices that runs 24/7.
2. A nightly batch data processing job that is highly parallelizable, runs for 3 hours, and can resume from checkpoints if interrupted.
3. A critical, monthly database reconciliation process that runs for 6 hours on the first day of each month and must not be interrupted.

Which combination of Amazon EC2 pricing models provides the most cost-effective solution while ensuring all performance requirements are met?

  1. Savings Plans for the continuous baseline, Spot Instances for the nightly batch processing, and On-Demand Instances for the monthly database reconciliation.Cevap
  2. B
    On-Demand Instances for the continuous baseline, Savings Plans for the nightly batch processing, and Spot Instances for the monthly database reconciliation.
  3. C
    Savings Plans for both the continuous baseline and the nightly batch processing, and Spot Instances for the monthly database reconciliation.
  4. D
    Dedicated Hosts for the continuous baseline, Reserved Instances for the nightly batch processing, and Savings Plans for the monthly database reconciliation.

Cevap

Savings Plans for the continuous baseline, Spot Instances for the nightly batch processing, and On-Demand Instances for the monthly database reconciliation.
The strategy of using Savings Plans for the continuous baseline, Spot Instances for the nightly batch processing, and On-Demand Instances for the monthly database reconciliation represents the absolute cost-optimum. The continuous baseline receives commitment discounts, the fault-tolerant batch job leverages the deep discounts of Spot Instances, and the short-duration, critical database reconciliation is run on On-Demand to guarantee execution without paying for idle capacity during the rest of the month.

Adım Adım Çözüm

1
Analyze the continuous baseline workload (24/7).
Identified Savings Plans or Reserved Instances as the most cost-effective option due to predictable, continuous utilization over 1 or 3 years.
Stable and predictable 24/7 workloads benefit from commitment-based discounts of up to 72% compared to On-Demand rates.
2
Analyze the nightly batch processing workload (3 hours, fault-tolerant).
Identified Spot Instances as the optimal choice.
Since the job is parallelizable and can resume from checkpoints, it can take advantage of Spot Instances, which offer up to a 90% discount with the trade-off of potential interruptions.
3
Analyze the monthly database reconciliation workload (6 hours once a month, critical and non-interruptible).
Identified On-Demand Instances as the best choice.
The workload cannot tolerate interruption, making Spot Instances unsuitable. Because it only runs for 6 hours a month, committing to a Savings Plan or Reserved Instance for this period would lead to massive waste (paying for idle capacity for the rest of the month), making On-Demand the most cost-effective option.
4
Combine the optimal pricing models for all three workloads.
Determined that the combination of Savings Plans, Spot Instances, and On-Demand Instances maximizes cost efficiency while fulfilling all operational requirements.
This strategy aligns the pricing model features to the specific predictability, duration, and fault tolerance of each workload.

Anahtar Kavram

Selecting the optimal Amazon EC2 pricing model based on workload predictability, duration, and fault tolerance.
Bu soruyu puanla