A SysOps administrator is reviewing the AWS Trusted Advisor Cost Optimization reports for a production account and notes that several Amazon RDS DB instances have been flagged by the 'Amazon RDS Idle DB Instances' check for having zero connections over the past 14 days. The administrator must decommission these DB instances to optimize costs while ensuring that the databases can be restored in the future if required. Which two actions should the administrator take to clean up these underutilized resources in the most cost-effective and safe manner? (Select TWO.)
- Create a final DB snapshot of each idle DB instance.Cevap
- Delete the idle DB instances.Cevap
- CStop the DB instances to permanently eliminate both compute and storage charges.
- DDelete the DB instances directly without a snapshot, relying on CloudWatch log groups with indefinite retention to reconstruct the database data.
- EEnable detailed monitoring on the DB instances and configure a static budget alert in AWS Budgets to auto-terminate the instances when charges occur.
Cevap
To safely and cost-effectively clean up the idle RDS DB instances, the administrator should create a final DB snapshot of each instance to ensure data durability, and then delete the DB instances to stop all associated compute and storage charges.
To decommission underutilized RDS DB instances safely and cost-effectively, the administrator must stop ongoing charges while preserving the data for potential future use. Creating a final DB snapshot ensures that a backup exists, and deleting the DB instances stops all compute and storage charges.
Adım Adım Çözüm
Anahtar Kavram
Safely decommissioning underutilized RDS instances involves capturing a final DB snapshot to preserve data before deleting the instance to stop all compute and storage costs.