1Z0-1067-25 Question 77
Single answerYou are managing an e-commerce platform on Oracle Cloud Infrastructure that experiences large traffic spikes during seasonal sales. To handle these surges, you want to automatically adjust compute resources based on real-time workload and optimize costs by scaling back during off-peak periods. Which approach should you implement to meet these requirements?
- A
Manually switch to a larger compute shape during high traffic, then revert back when usage decreases
- B
Use an Instance Pool with an autoscaling policy triggered by CPU utilization and memory metrics
- C
Deploy multiple fixed-size compute instances without a load balancer to simplify scaling
- D
Rely solely on vertical scaling by increasing the OCPU count on a single compute instance
Show answer and explanation
Correct answer: B
Explanation
To implement elasticity and scalability in Oracle Cloud Infrastructure, the best practice involves deploying an Instance Pool and configuring an autoscaling policy that reacts to key metrics (like CPU or memory). This setup automatically adds or removes compute instances based on demand, handling traffic spikes seamlessly while minimizing costs in off-peak periods. Refer to OCI documentation on Instance Pools and autoscaling policies for detailed configuration guidance.
- A. Incorrect.
Option 1: Manually increasing or decreasing the shape is error-prone and does not automatically react to real-time usage changes. This would lead to delayed response to spikes and potentially higher costs if you forget to revert the larger shape.
- B. Correct.
Option 2: An Instance Pool with an autoscaling policy allows you to automatically add or remove compute instances based on metrics such as CPU or memory usage. This is the recommended approach to achieve true elasticity and optimize costs in OCI.
- C. Incorrect.
Option 3: Multiple fixed-size compute instances without a load balancer and autoscaling would not allow dynamic resource adjustments. You would still face potential downtime or suboptimal performance during very high or very low traffic periods.
- D. Incorrect.
Option 4: Vertical scaling alone involves resizing a single instance. This approach can be slow and may cause downtime during shape changes. It also does not accommodate sudden traffic spikes as effectively as scalable pools.