1Z0-1067-25 Question 75
Select 2Your online media streaming application experiences unpredictable spikes in user traffic. The application is hosted on an OCI instance pool, fronted by a public load balancer. You want to implement elasticity so that the server capacity automatically scales up when traffic peaks and scales down when traffic subsides, all without manual intervention. Which two configurations should you implement in Oracle Cloud Infrastructure to effectively achieve this goal while optimizing operational costs?
- A
Create a scaling configuration for the instance pool using CPU utilization metrics to trigger automatic scale-out and scale-in.
- B
Set up an OCI Alarm to trigger a serverless function that updates the instance pool size whenever CPU usage crosses specified thresholds.
- C
Manually assign additional ephemeral public IP addresses to each new instance as traffic increases.
- D
Configure the instance pool to run ten instances at all times to avoid any chance of under-provisioning.
Show answer and explanation
Correct answers: A, B
Explanation
Using OCI Instance Pool autoscaling and OCI Alarms to trigger scaling events are essential for implementing elasticity. Scalability in OCI relies on monitoring metrics (like CPU usage) to determine when to add or remove instances, combined with automation (for example, serverless functions or direct autoscaling rules) that updates the instance pool size. This approach aligns with OCI best practices by ensuring you can handle peak demands on your application while keeping operational costs controlled when traffic is low. For more details, refer to Oracle Cloud Infrastructure Autoscaling documentation.
- A. Correct.
Correct. Creating a scaling configuration on the instance pool using CPU utilization (or similar metrics) is a primary method in OCI for enabling automatic scale-up and scale-down, ensuring that application capacity adjusts to traffic while optimizing costs.
- B. Correct.
Correct. Setting up an OCI Alarm to trigger a serverless function (or other automated workflow) to update the instance pool when CPU usage exceeds or falls below specific thresholds is a practical approach that complements the built-in autoscaling capabilities. It ensures your application remains responsive to dynamic traffic patterns.
- C. Incorrect.
Incorrect. Assigning additional ephemeral public IP addresses does not address horizontal scaling. IP addresses alone do not automatically add or remove compute resources; they merely provide access points, and would not help with computational load.
- D. Incorrect.
Incorrect. Maintaining a fixed count of ten instances does guarantee capacity but is not cost-effective or truly elastic. It does not leverage on-demand scaling and leads to potentially unnecessary resource usage outside peak times.