1Z0-1067-25 Question 76
Select 2You run a high-traffic e-commerce application on Oracle Cloud Infrastructure, where an Instance Pool sits behind a Load Balancer. Traffic patterns are highly unpredictable, with sudden spikes followed by periods of low activity. You want to automatically scale out compute capacity during peak loads and scale in to save costs when demand subsides. Which two of the following approaches can you set up in OCI to achieve dynamic elasticity and cost optimization for your Instance Pool?
- A
Configure an OCI Autoscaling policy to add or remove instances in the Instance Pool based on average CPU utilization thresholds.
- B
Over-provision the Instance Pool with the maximum number of instances you expect at peak load so your capacity is always ready.
- C
Implement a scheduled scaling policy to add instances during known peak periods and remove them when traffic is typically lower.
- D
Rely solely on manual scaling through the console when traffic increases beyond the current capacity of the Instance Pool.
- E
Use an Autoscaling policy to dynamically change the shape of running Compute instances after CPU usage exceeds a set threshold.
Show answer and explanation
Correct answers: A, C
Explanation
In OCI, best practice for implementing scalability and elasticity in compute environments involves combining threshold-based Autoscaling for real-time response and scheduled scaling for predictable traffic variations. For more details, refer to Oracle documentation on Instance Pools and Autoscaling (https://docs.oracle.com/en-us/iaas/Content/Compute/Tasks/autoscalinginstancepools.htm) which outlines how to configure and tune autoscaling policies for cost-effective, elastic computing.
- A. Correct.
Correct. OCI Autoscaling policies let you define scaling triggers based on metrics such as CPU or memory utilization. This ensures instances are added or removed automatically based on real-time demand, providing both elasticity and cost-efficiency.
- B. Incorrect.
Incorrect. Simply over-provisioning ensures capacity during peak times but wastes resources and increases costs during low-demand periods. This approach lacks true elasticity and cost optimization.
- C. Correct.
Correct. Scheduled scaling is useful for predictable traffic surges. By adding instances during known peak periods and removing them later, you automate capacity changes and reduce costs once peak demand subsides.
- D. Incorrect.
Incorrect. Manual scaling relies on human intervention and may lead to delayed response to spikes or unnecessary costs if you forget to scale down. It is neither fully elastic nor cost-optimized.
- E. Incorrect.
Incorrect. While OCI Autoscaling can add or remove instances, you cannot automatically change the instance shape within an existing pool through Autoscaling. Shape changes typically require re-creating or modifying the instance configurations outside of the Autoscaling policy.