Make the checkout fleet come back down
Try this labAll AZ-104 practice
- Certification
- AZ-104
- Format
- Structured configuration
- Difficulty
- hard
- Estimated time
- 20 min
- Automated checks
- 10
SCENARIO
The checkout scale set grew to peak capacity and never shrank after demand fell. Short CPU spikes also caused repeated capacity changes. The approved fleet range is two to eight instances, brief spikes last four minutes, and a capacity change takes five minutes to settle.
TASK
Repair autoscale.json so sustained load grows the fleet, sustained quiet returns it to the configured minimum, and brief spikes cause no scale-out.
- Prevent immediate reversals after a capacity change and keep capacity within the approved range.
- Preserve the supplied scale set and CPU metric.