Examkin

Soru

Zorluk: OrtaCost-Optimized Database Design and Capacity Planning

A company runs a critical web application on AWS with a relational workload using an Amazon RDS for MySQL database. The database is currently deployed as a Multi-AZ DB instance to meet high availability requirements. During business hours, the database experiences predictable, high-volume read queries that cause CPU utilization on the primary instance to spike to 90%90\%. The database storage size is relatively small, but the workload requires high throughput and IOPS. The company wants to minimize overall operational costs while maintaining performance and high availability.

Which TWO configurations should the solutions architect implement to meet these requirements? (Select TWO)

  1. Create Amazon RDS Read Replicas to offload read queries, allowing the primary database instance to be scaled down to a smaller size.Cevap
  2. Configure the database storage using General Purpose SSD (gp3) volumes instead of Provisioned IOPS SSD (io1) volumes to provision the required IOPS and throughput independently of storage capacity.Cevap
  3. C
    Deploy a Read Replica in a separate Availability Zone, configure it as the primary automatic failover target, and disable the Multi-AZ DB instance configuration.
  4. D
    Purchase a Compute Savings Plan to cover the hourly instance costs of the primary RDS instance and the Read Replicas.
  5. E
    Migrate the read-heavy tables to Amazon DynamoDB configured in Provisioned Capacity Mode with static write and read capacity units scaled to the peak read volume.

Cevap

Create Amazon RDS Read Replicas to offload read queries and configure the database storage using General Purpose SSD (gp3) volumes.
Creating Amazon RDS Read Replicas is the most cost-effective way to handle high volumes of read queries, as it allows the read traffic to be offloaded from the primary database instance. This enables the primary instance to be scaled down to a smaller, less expensive instance size. Configuring General Purpose SSD (gp3) volumes is cost-effective because gp3 allows provisioning IOPS and throughput independently of storage capacity. This prevents the need to overprovision storage capacity or use expensive Provisioned IOPS SSD (io1) volumes just to achieve high IOPS.

Adım Adım Çözüm

1
Analyze the read query workload performance bottleneck.
The primary Multi-AZ database instance is experiencing CPU spikes to 90%90\% due to read traffic, which can be offloaded by deploying Read Replicas, allowing the primary instance to be downsized to save compute costs.
Offloading read traffic reduces compute requirements on the primary instance, optimizing the database capacity plan.
2
Evaluate the storage volume type for high IOPS and throughput requirements.
Using General Purpose SSD (gp3) volumes allows provisioning the required IOPS and throughput independently of storage size, avoiding the high cost of Provisioned IOPS SSD (io1) volumes or overprovisioning gp2 storage size.
This achieves cost-effective storage configuration without paying for unused storage space.
3
Assess high availability and automatic failover options.
Multi-AZ must be kept active for automatic failover. RDS Read Replicas cannot serve as automatic failover targets in place of Multi-AZ.
This ensures the SLA is met while avoiding configuration mistakes that compromise availability.

Anahtar Kavram

To cost-optimize relational database capacity on AWS, offload read-heavy traffic to Read Replicas to downscale the primary instance, and utilize gp3 storage to provision IOPS and throughput independently without overprovisioning storage space or using expensive Provisioned IOPS (io1) volumes.
Tahmini Süre:2m 0s
Bu soruyu puanla

Konular

Cost-Optimized Database Design and Capacity Planning