Examkin

Soru

Zorluk: OrtaCost-Optimized Compute Selection and Purchasing Strategies

A company hosts a containerized application on AWS. The application consists of a backend transaction processing service hosted on Amazon ECS on AWS Fargate that runs continuously, requiring a steady-state baseline of 8 tasks and scaling up to 20 tasks during peak hours. Additionally, the company runs a daily batch processing job on Amazon EC2 instances to generate reports; this job is fault-tolerant and can be interrupted without affecting the system. The database tier uses an Amazon RDS for PostgreSQL instance that runs continuously 24/7. Which two options should a solutions architect recommend to provide the most cost-effective compute architecture? (Select TWO.)

  1. Purchase a Compute Savings Plan to cover the baseline AWS Fargate tasks.Cevap
  2. Run the daily batch processing job on Amazon EC2 Spot Instances.Cevap
  3. C
    Purchase an EC2 Instance Savings Plan to cover the baseline AWS Fargate tasks.
  4. D
    Purchase a Compute Savings Plan to cover the Amazon RDS for PostgreSQL instance.
  5. E
    Migrate the continuously running backend transaction processing service to AWS Lambda to leverage pay-per-use billing.

Cevap

Purchasing a Compute Savings Plan to cover the baseline Fargate tasks and running the daily batch processing job on Amazon EC2 Spot Instances provides the most cost-effective compute architecture.
Purchasing a Compute Savings Plan to cover the baseline Fargate tasks is correct because Compute Savings Plans apply directly to AWS Fargate and provide substantial discounts for steady-state usage. Running the daily batch processing job on Amazon EC2 Spot Instances is correct because the job is fault-tolerant and can tolerate interruptions, allowing the company to take advantage of the steep discounts offered by Spot Instances.

Adım Adım Çözüm

1
Analyze the workload characteristics of each tier in the architecture.
The Fargate-hosted backend service runs continuously (steady baseline of 8 tasks, scaling up to 20). The EC2 batch job is periodic, fault-tolerant, and interruptible. The RDS database runs continuously.
Identifying the lifecycle and tolerance of each workload is required to choose the correct billing model.
2
Determine the optimal purchasing model for the Fargate baseline tasks.
Compute Savings Plans apply to AWS Fargate and cover continuous baseline usage with significant discounts.
Baseline workloads running 24/7 are best covered by Savings Plans to reduce On-Demand costs.
3
Determine the optimal purchasing model for the periodic, interruptible batch processing job.
Spot Instances are ideal for fault-tolerant, flexible workloads because they offer up to 90% savings over On-Demand rates.
Since the batch job can be interrupted, it does not require On-Demand or committed capacity models like Savings Plans.

Anahtar Kavram

Selecting cost-optimized AWS compute models (Savings Plans vs Spot Instances) based on workload stability and fault tolerance.
Tahmini Süre:1m 30s
Bu soruyu puanla

Konular

Cost-Optimized Compute Selection and Purchasing Strategies