A company uses multiple Amazon RDS databases to support an application. The application receives all its traffic during weekdays and is idle during weekends. The company wants a solution to automatica

Question

Options

• AUse a cron job to automatically scale down the RDS DB instance type during weekends.
• BConfigure Instance Scheduler on AWS to stop the RDS DB instances at the beginning of each
• CPurchase Reserved Instances for the RDS DB instances.
• DUse the auto scaling feature of Amazon RDS to automatically adjust the DB instance type based

• A
  13% (3)
• B
  74% (17)
• C
  4% (1)
• D
  9% (2)

Explanation

The Instance Scheduler on AWS is an AWS-provided solution designed specifically to start and stop AWS resources such as Amazon RDS instances on a defined schedule. This directly aligns with the requirement to automatically manage RDS instances during predictable idle periods, such as weekends, to reduce costs. RDS instances incur compute charges while running, even if idle. Stopping them during weekends eliminates those charges while retaining storage and backups. Instance Scheduler supports tag-based scheduling, centralized management, and automated start/stop workflows without custom scripting. Option A introduces custom automation and ongoing maintenance overhead. Option C (Reserved Instances) is unsuitable because the databases are idle for long, predictable periods and Reserved Instances charge regardless of usage. Option D is incorrect because RDS does not support auto scaling of DB instance classes based on utilization. Instance Scheduler is the most cost-effective and operationally efficient solution for this use case.

No community discussion yet for this question.