Soru

Zorluk: OrtaAWS Pricing Models

A retail company plans to deploy its core customer database on Amazon EC2. The database must run continuously 24/7 and requires stable, predictable compute capacity. The company is prepared to commit to a 1-year term to reduce costs. Additionally, the company expects sudden, short-term traffic spikes during promotional events when they will need to launch additional temporary instances. Which combination of EC2 pricing models provides the most cost-effective solution while ensuring database stability?

  1. A
    Spot Instances for the baseline database and Savings Plans for the temporary spikes
  2. B
    On-Demand Instances for the baseline database and Spot Instances for the temporary spikes
  3. C
    Spot Instances for the baseline database and On-Demand Instances for the temporary spikes
  4. Reserved Instances for the baseline database and On-Demand Instances for the temporary spikesCevap

Cevap

Reserved Instances for the baseline database and On-Demand Instances for the temporary spikes
The correct answer is the combination of Reserved Instances for the baseline database and On-Demand Instances for the temporary traffic spikes. Reserved Instances offer a significant discount compared to On-Demand pricing in exchange for a 1-year or 3-year commitment, which fits the stable 24/7 baseline requirement of the database. On-Demand Instances are billed by the second or hour with no long-term commitment, making them perfect for handling short-term, unpredictable spikes without the risk of interruption.

Adım Adım Çözüm

1
Identify the requirements of the baseline workload.
The baseline database runs continuously (24/7), requires stability (no interruptions), and the company is willing to make a 1-year commitment.
Analyzing baseline needs allows us to select the most cost-effective committed pricing model (Reserved Instances or Savings Plans) rather than paying full price.
2
Identify the requirements of the temporary scaling workload.
The traffic spikes are sudden, short-term, and temporary.
Analyzing spike characteristics prevents committing to long-term pricing models for resources that are only needed briefly, and rules out Spot Instances due to the potential for interruption during critical customer activity.
3
Combine the optimal pricing models to form the final solution.
Use Reserved Instances for the baseline database to secure discounts, and On-Demand Instances for the temporary traffic spikes to ensure reliability without long-term commitments.
This combination minimizes costs for predictable usage while maintaining stability and flexibility for unpredictable spikes.

Anahtar Kavram

AWS EC2 Pricing Models
Bu soruyu puanla