1Z0-1067-25 Question 74
Select 2You manage a microservices-based e-commerce application on Oracle Cloud Infrastructure. The front-end service is deployed using an Instance Pool to handle fluctuating traffic loads. The back-end service runs on Oracle Container Engine for Kubernetes (OKE), where pods perform inventory and checkout processes. Traffic spikes unpredictably throughout the day, and you want to ensure both front-end and back-end services can scale automatically without manual intervention. Which two configurations should you implement to achieve this goal?
- A
Configure an OCI Auto Scaling policy on the Instance Pool to increase or decrease the number of instances based on CPU utilization thresholds.
- B
Use a Load Balancer attached to the front-end Instance Pool to automatically replicate the entire environment when traffic increases.
- C
Implement a Horizontal Pod Autoscaler (HPA) for the OKE back-end pods, setting appropriate CPU or memory utilization thresholds for scaling out or in.
- D
Schedule a nightly Terraform run to recreate the entire infrastructure based on predicted usage models.
- E
Assign multiple ephemeral public IP addresses to the same Instance Pool to handle sudden bursts of traffic.
Show answer and explanation
Correct answers: A, C
Explanation
To implement elasticity in Oracle Cloud Infrastructure, you configure Auto Scaling for your Instance Pools (front-end) and use Horizontal Pod Autoscalers in your OKE clusters (back-end). These real-time autoscaling solutions respond to metrics such as CPU or memory usage without manual intervention. For more details, refer to the OCI documentation on Auto Scaling (docs.oracle.com/en/solutions/learn-autoscaling) and Kubernetes Horizontal Pod Autoscaler (kubernetes.io/docs/tasks/run-application/horizontal-pod-autoscale).
- A. Correct.
Correct. Configuring an Auto Scaling policy on the Instance Pool allows you to dynamically add or remove compute instances based on metrics like CPU utilization. This ensures the front-end can scale in response to real-time demand without manual intervention.
- B. Incorrect.
Incorrect. While a Load Balancer can help distribute traffic across multiple instances, it cannot replicate the entire environment on its own. Auto-scaling is configured at the Instance Pool level, not directly through the Load Balancer.
- C. Correct.
Correct. A Horizontal Pod Autoscaler (HPA) in OKE monitors resource utilization (CPU or memory) in pods and automatically adjusts the number of pod replicas. This is a recommended approach for elastic scaling of back-end services in Kubernetes on OCI.
- D. Incorrect.
Incorrect. Scheduling a nightly Terraform run doesn't provide real-time elasticity. Auto-scaling requires continuous monitoring of resource metrics, not just periodic infrastructure recreation.
- E. Incorrect.
Incorrect. Assigning multiple ephemeral public IP addresses to the same Instance Pool does not inherently provide elasticity or scaling. It only increases IP availability, which does not address fluctuating compute or container resource needs.