1Z0-1067-25 Question 47
Single answerYou manage an e-commerce application running on Oracle Cloud Infrastructure (OCI) that experiences varying traffic throughout the day. During peak hours, your application struggles to meet performance demands, and during off-peak hours, you end up overpaying for underutilized resources. Which single strategy most effectively optimizes cost while maintaining consistent performance for these fluctuating workloads?
- A
Enable OCI Compute Autoscaling on your instance pool to automatically increase or reduce the number of instances based on actual load
- B
Use fixed-size, high-end compute shapes around the clock to guarantee capacity for potential peak traffic
- C
Create multiple VCNs and re-route traffic manually through smaller compute instances whenever usage decreases
- D
Reserve capacity for all compute instances at a fixed rate to lock in lower prices, regardless of usage patterns
Show answer and explanation
Correct answer: A
Explanation
OCI Compute Autoscaling is a key feature for on-demand scaling in response to real-time metrics, eliminating the need to overprovision resources. It helps maintain performance standards during traffic peaks and cut costs during off-peak periods. For more details, refer to the Oracle Cloud Infrastructure documentation on autoscaling best practices: https://docs.oracle.com/en-us/iaas/Content/Compute/Tasks/autoscalinginstancepools.htm
- A. Correct.
Correct. Autoscaling dynamically adjusts the number of running instances based on CPU or memory usage thresholds, ensuring enough capacity during peak times and cost savings during low-traffic periods. This approach is a standard best practice for balancing cost and performance in OCI.
- B. Incorrect.
Incorrect. Continuously running high-end compute shapes guarantees performance but leads to a significant cost increase when traffic is low. It fails to leverage any cost savings mechanism available in OCI for off-peak times.
- C. Incorrect.
Incorrect. Manually re-routing traffic between different VCNs and smaller instances is cumbersome and error-prone. It doesn't provide an automated, real-time approach for scaling resources in response to demand.
- D. Incorrect.
Incorrect. While reserving capacity can reduce costs for steady workloads, it doesn't address sudden spikes or variability, and you might overpay for unused capacity. This strategy is more suitable for predictable, long-running workloads.