1Z0-1072-25 Question 24
Single answerYou manage an instance pool running a web application that experiences a predictable surge in traffic every weekday from 8 AM to 11 AM. During this time, CPU utilization increases significantly, and you need more compute instances to handle the load. At other times, the traffic is relatively low. Which strategy most effectively ensures you have enough capacity during peak hours and optimizes costs outside the surge window?
- A
Implement a threshold-based autoscaling policy that scales out when average CPU usage exceeds 70%
- B
Implement a schedule-based autoscaling policy that adds more instances at 8 AM and removes them at 11 AM on weekdays
- C
Use an existing alarm that triggers Instance Pool scaling whenever latency metrics spike
- D
Disable autoscaling and manually add or remove instances based on observed traffic patterns
Show answer and explanation
Correct answer: B
Explanation
For predictable traffic surges, Oracle Cloud Infrastructure (OCI) recommends using schedule-based autoscaling. By creating a schedule that automatically scales your instance pool up during the known peak time and scales it down when traffic subsides, you can provide the necessary capacity while controlling costs. Refer to the OCI documentation for best practices on configuring schedule-based autoscaling policies.
- A. Incorrect.
Option 1: While threshold-based autoscaling can handle variable workloads, it may not be optimal for predictable, time-based surges. You can still use CPU utilization metrics in combination with schedules, but if the traffic pattern is truly predictable, a pure threshold-based approach may react slower or scale too late.
- B. Correct.
Option 2 (Correct): Schedule-based autoscaling aligns perfectly with a known, repeatable surge window. You configure start and end times for scaling on weekdays, ensuring you have additional instances when needed and reducing costs outside of peak hours.
- C. Incorrect.
Option 3: Relying on latency spikes could work but might be reactive rather than proactive. If you already know your busiest times, schedule-based scaling is more cost-effective and ensures instances are pre-provisioned by 8 AM and removed at 11 AM.
- D. Incorrect.
Option 4: Manually scaling is prone to human error and not efficient for a traffic pattern that repeats daily. Leveraging OCI autoscaling ensures changes happen consistently without manual intervention.