1Z0-1067-25 Question 48
Select 2You support a multi-tier application running on Oracle Cloud Infrastructure (OCI) that experiences unpredictable traffic spikes. Your overall monthly cost is steadily increasing due to resources being over-provisioned to handle peak loads. Which two actions should you implement to optimize cost without sacrificing performance?
- A
Enable compute autoscaling policies to dynamically adjust instance capacity based on CPU or memory usage thresholds.
- B
Use flexible compute shapes so you can right-size the instances closer to the typical workload demands.
- C
Configure a single, large compute instance that can handle peak loads without scaling in or out.
- D
Enable the highest performance setting on your Oracle Autonomous Database to address all potential spikes in demand 24/7.
Show answer and explanation
Correct answers: A, B
Explanation
By combining flexible compute shapes with autoscaling policies, you ensure that instances are sized efficiently for normal operating conditions and expanded only when demand increases. This approach reduces unnecessary spending while maintaining performance during peak periods. Consult the OCI documentation on 'Configuring Autoscaling Policies' and 'Using Flexible Compute Shapes' for specific configuration details and best practices.
- A. Correct.
Correct. Autoscaling automatically increases or decreases resources based on real-time metrics, ensuring you�re not overpaying during low demand while still meeting performance needs during spikes.
- B. Correct.
Correct. Flexible shapes allow you to closely match the CPU and memory configuration to your typical workload profile, reducing unnecessary resource costs while providing enough capacity for your usual demand.
- C. Incorrect.
Incorrect. Provisioning a large instance that exceeds typical requirements leads to constant over-provisioning. While it might handle peak loads, it fails the goal of cost optimization since it continues to run at full cost even during low usage.
- D. Incorrect.
Incorrect. Permanently enabling the highest performance setting on the database does not scale resources up or down dynamically. It can address spikes, but will also incur high costs continuously, negating the cost optimization objective.