Soru

Zorluk: Çok zorAWS Trusted Advisor Cost Optimization Checks

A SysOps administrator is reviewing the weekly AWS Trusted Advisor Cost Optimization report for a production workload. The report contains the following findings:
- An Amazon Elastic Block Store (Amazon EBS) volume has had less than 11 IOPS of write activity for the past 14 days.
- An Application Load Balancer (ALB) has had an ActiveConnectionCount of 00 over the past 7 days.
- An Amazon RDS PostgreSQL DB instance has had no active database connections (DatabaseConnections is 00) for the past 8 days.
- An Elastic IP address (EIP) is listed under the Unassociated Elastic IP Addresses check.
- A group of Amazon EC2 instances running under an Auto Scaling group is flagged under the Low Utilization Amazon EC2 Instances check, showing consistent 3%3\% average CPU utilization.

Which two actions should the SysOps administrator take to resolve these findings and optimize costs? (Select TWO.)

  1. Release the unassociated Elastic IP address, and delete the Application Load Balancer after verifying no traffic is routed to its DNS name.Cevap
  2. Create a final snapshot of the idle RDS PostgreSQL DB instance, and then delete the DB instance.Cevap
  3. C
    Disassociate the unassociated Elastic IP address from its Virtual Private Cloud (VPC) public subnet to stop the hourly charges.
  4. D
    Manually terminate the low-utilization EC2 instances within the Auto Scaling group to reduce active compute capacity.
  5. E
    Stop the idle RDS PostgreSQL DB instance, and configure an Amazon EventBridge rule to start the database only when connection activity is detected by Amazon RDS Performance Insights.

Cevap

The correct actions are to release the unassociated Elastic IP address and delete the idle Application Load Balancer, and to take a final snapshot of the idle RDS PostgreSQL DB instance before deleting it.
Releasing the unassociated Elastic IP address stops the hourly charge for unassigned EIPs. Deleting the Application Load Balancer with zero active connections removes the hourly base charges for the idle load balancer. Creating a final snapshot of the idle RDS PostgreSQL DB instance and deleting it eliminates all DB instance charges while preserving the data for potential future recovery.

Adım Adım Çözüm

1
Address the unallocated Elastic IP and idle Application Load Balancer findings.
Identify that disassociation does not stop EIP charges; the EIP must be released. Deleting the idle Application Load Balancer removes hourly base charges.
AWS charges for unassociated Elastic IPs to encourage efficient address space usage. ALBs incur hourly charges regardless of traffic volume.
2
Address the idle Amazon RDS PostgreSQL DB instance finding.
Determine that stopping the instance is not a permanent solution, as stopped RDS instances automatically restart after 7 days. Deleting the instance with a final snapshot is correct.
Deleting the instance stops all compute charges, while the snapshot preserves historical data without incurring active database engine costs.
3
Evaluate the Auto Scaling group and EIP disassociation distractors.
Rule out manual EC2 termination because the Auto Scaling group will automatically replace terminated instances. Rule out disassociation as it keeps the EIP allocated.
Auto Scaling monitors instance health and count relative to its desired capacity setting. Manual intervention at the instance level fails to change this capacity setting.

Anahtar Kavram

AWS Trusted Advisor Cost Optimization checks flag idle and underutilized resources. Remediating these requires understanding specific resource lifecycles: Elastic IPs must be released, idle load balancers should be deleted, and idle RDS DB instances must be snapshotted and deleted to prevent auto-restart charges.
Bu soruyu puanla