A company's website runs on EC2 instances in an Auto Scaling group. Users report slower performance every weekend from 6 PM to 11 PM. The SysOps administrator needs the simplest, most operationally efficient way to improve capacity during those peak windows. What is the best solution?

The correct answer is to set up a scheduled scaling action with a recurrence. This is the most straightforward and operationally efficient method for handling predictable, recurring traffic patterns like weekend peaks. Scheduled scaling allows you to define specific times to increase or decrease the Auto Scaling group's desired capacity, ensuring resources are available when needed and scaled down afterward to save costs. Creating an EventBridge rule to trigger a Lambda function is overly complex for this common use case. While technically possible, it introduces unnecessary operational overhead compared to a built-in Auto Scaling feature. Using a target tracking policy based on memory utilization is reactive, not proactive, and might not scale instances quickly enough to prevent performance degradation during a sudden, predictable surge. Adjusting the cooldown period primarily affects how quickly an Auto Scaling group scales after a scaling event, not how it proactively prepares for predictable peaks.