A payroll application sees a sharp, repeatable load increase every weekday at 09:00 as staff log in, and demand drops again by 18:00. Reactive scaling reacts only after CPU has already climbed, causing slow responses for the first few minutes. Which Auto Scaling approach best ensures capacity is already in place before the morning surge?
- AIncrease the cooldown period on the existing simple scaling policy so the group reacts more decisively when the morning CPU spike begins.
- BLower the target value on the target tracking policy so the group keeps far more spare instances running throughout the day.
- CSwitch to a step scaling policy with larger step sizes so the group adds many instances at once when CPU first rises.
- DAdd a scheduled scaling action that raises the desired and minimum capacity shortly before 09:00 and lowers it after 18:00. Correct
Why A is wrong: A longer cooldown only delays further scaling actions; it does nothing to add capacity ahead of 09:00 and would actually slow the group's reaction to the surge.
Why B is wrong: A lower target keeps extra capacity around the clock, which can cover the surge but wastes money during the long off-peak hours and still reacts rather than pre-provisioning for a known time.
Why C is wrong: Bigger step sizes speed the catch-up after CPU rises, but the group still launches only once the spike has begun, so the first minutes of the 09:00 surge stay underserved.
Why D is correct: Scheduled scaling changes capacity on a known clock pattern, so raising desired capacity just before 09:00 means instances are warm and registered before the predictable surge, then scaling back after 18:00.