An App Service plan hosts a web API that experiences unpredictable traffic spikes during business hours. You need to minimize cost overnight while ensuring the API scales out quickly when either CPU exceeds 70% or memory exceeds 75% for 10 minutes. During business hours (8 AM–6 PM), maintain a minimum of 3 instances; off-hours maintain 1 instance; and never exceed 10 instances. What configurations should you implement?

The correct options collectively address all requirements. Creating an autoscale setting with two scheduled profiles (business hours and off-hours) allows for different minimum instance counts based on time, fulfilling the cost minimization and minimum instance requirements. The business hours profile sets a minimum of 3 instances and a default of 3, while off-hours sets a minimum of 1 and a default of 1. Both profiles enforce a maximum of 10 instances. Adding scale-out rules for CPU exceeding 70% and Memory exceeding 75% for 10 minutes ensures the API scales quickly based on performance metrics. Corresponding scale-in rules are necessary to reduce instances when demand decreases, optimizing cost. Manually scaling or scaling up the SKU would not provide the dynamic, cost-effective scaling required.