1Z0-1072-25 Question 21
Single answerYour e-commerce application runs on an OCI Instance Pool behind an OCI Load Balancer. You have configured a threshold-based autoscaling policy to add instances when CPU utilization remains above 70% for at least 5 minutes. Despite observing metrics showing CPU usage frequently exceeding 75% for over 10 minutes, the autoscaling feature never spins up new instances. Which step below best addresses this issue?
- A
A. Lower the CPU threshold from 70% to 50% so that autoscaling triggers more frequently.
- B
B. Increase the shape of existing instances in the pool to handle higher load without adding more instances.
- C
C. Ensure the autoscaling configuration is attached to the correct instance pool and references the appropriate CPU metric namespace.
- D
D. Restart the Load Balancer to refresh its connections and force a new autoscaling event.
Show answer and explanation
Correct answer: C
Explanation
In Oracle Cloud Infrastructure, threshold-based autoscaling for an Instance Pool depends on correctly attaching the autoscaling policy to the specific instance pool and selecting the accurate metric namespace (e.g., oci_computeagent for CPU utilization). If the policy is attached to the wrong resource or references a non-existent metric namespace, autoscaling will not trigger despite high CPU usage. Following OCI best practices, always verify that the correct instance pool is defined in the policy, and confirm you are using the right metrics compartment and namespace before fine-tuning thresholds. For more detail, consult Oracle documentation on 'Configuring Autoscaling for Instance Pools.'
- A. Incorrect.
A. Incorrect. Reducing the CPU threshold may trigger scaling earlier, but it does not address underlying implementation issues if the autoscaling configuration is not properly attached or referencing the correct metrics.
- B. Incorrect.
B. Incorrect. While using a larger instance shape can handle more load, it bypasses the root cause if the autoscaling policy is misconfigured. Autoscaling won't work correctly if not properly set up, regardless of the instance shape.
- C. Correct.
C. Correct. A common misconfiguration is failing to attach autoscaling to the intended resource or referencing a wrong metric namespace. Verifying the correct instance pool and CPU utilization metric are used ensures autoscaling triggers properly.
- D. Incorrect.
D. Incorrect. Restarting the Load Balancer does not directly resolve misconfiguration problems. Autoscaling is driven by metrics on the instance pool, not by Load Balancer restarts.