1Z0-1067-25 Question 73
Select 2You manage an e-commerce application running on a single Compute instance in Oracle Cloud Infrastructure (OCI). Traffic often spikes unpredictably during flash sales, causing high CPU usage and slow response times. You have decided to implement a scalable, elastic solution that automatically adds new Compute resources when utilization is high and removes them when usage drops. Which two steps should you take to achieve this in OCI?
- A
Create an Instance Pool from an Instance Configuration and set up auto scaling rules in the Scaling Configuration to trigger based on CPU utilization thresholds.
- B
Monitor CPU usage using OCI Monitoring and configure an Autoscaling Configuration on the Load Balancer to automatically provision new instances when thresholds are reached.
- C
Enable Bring Your Own IP (BYOIP) so that any newly launched instances automatically assume the same public IP address when scaling out or in.
- D
Attach the Instance Pool to a Load Balancer to automatically distribute traffic across all instances in the pool.
- E
Set up manual provisioning scripts to deploy new Compute instances whenever Cloud Guard detects an anomaly in utilization rates.
Show answer and explanation
Correct answers: A, D
Explanation
To implement elasticity in Oracle Cloud Infrastructure, you typically create an Instance Configuration and then an Instance Pool. You set CPU utilization thresholds or other metrics in the auto scaling rules (Scaling Configuration) so that new instances are added when traffic spikes and removed when it decreases. Attaching the Instance Pool to a Load Balancer allows traffic to be routed efficiently across all active instances. Refer to OCI documentation on 'Using Instance Configurations and Pools' and 'Monitoring and Autoscaling' for additional details.
- A. Correct.
Correct. Creating an Instance Pool with a corresponding Instance Configuration is essential for automatically scaling out or in. In the Scaling Configuration section, you can define rules based on CPU usage thresholds to launch or terminate instances automatically.
- B. Incorrect.
Incorrect. Autoscaling in OCI is typically configured on Instance Pools, not directly on the Load Balancer. While OCI Monitoring can help detect utilization issues, you still need an Instance Pool and auto scaling rules on that pool rather than on the Load Balancer itself.
- C. Incorrect.
Incorrect. BYOIP allows you to bring your own IP addresses to OCI but does not automatically handle scaling. It is not required for instance auto scaling and does not help with elastic scaling behavior.
- D. Correct.
Correct. Attaching your Instance Pool to a Load Balancer ensures that traffic is evenly distributed among all active instances. As new instances are added or removed, the Load Balancer adjusts to route traffic appropriately, providing a seamless scaling experience.
- E. Incorrect.
Incorrect. Manual provisioning scripts are not an effective approach to auto scaling. While you can automate certain tasks with scripts, fully automated instance scaling in OCI typically relies on configured rules within an Instance Pool rather than Cloud Guard anomaly detections.