1Z0-997-25 Question 6
Select 2You are designing a new microservices-based application on Oracle Cloud Infrastructure. Real-time requests are handled by one set of services, while another set of services performs short-lived asynchronous tasks triggered by application events. You plan to use Oracle Container Engine for Kubernetes (OKE) for containerized workloads and an Autonomous Database for persistent storage. To minimize operational complexity while remaining cost-effective, which two design strategies should you implement?
- A
Deploy all microservices on OKE, configuring Horizontal Pod Autoscaling (HPA) to handle variable traffic.
- B
Use Oracle Functions for short-lived event-driven tasks, invoked through OCI Events.
- C
Maintain persistent state in container file systems for faster local reads.
- D
Rely solely on manual node scaling in OKE to manage cost and concurrency spikes.
Show answer and explanation
Correct answers: A, B
Explanation
Using HPA on OKE for real-time services and Oracle Functions for short-lived, event-driven tasks leverages the core strengths of cloud-native design on OCI. Horizontal scaling ensures that container-based microservices can handle fluctuating loads, while serverless Oracle Functions offloads asynchronous work without you managing any infrastructure. This pattern follows OCI best practices for modern, distributed architectures.
- A. Correct.
Option 1 is correct. Horizontal Pod Autoscaling (HPA) in OKE allows automatically scaling up and down based on workload demand. This ensures real-time services can handle dynamic traffic levels without manual intervention. This is a recommended OCI best practice for cloud-native architectures seeking to minimize operational overhead.
- B. Correct.
Option 2 is correct. Oracle Functions is a serverless platform ideal for short-running, event-driven tasks. Using OCI Events to trigger Functions offloads asynchronous workflows from containerized environments, reducing overhead and ensuring cost efficiency. Reference: 'Using Oracle Functions with Events' in the OCI documentation.
- C. Incorrect.
Option 3 is incorrect. Storing persistent state in container file systems creates complexity for scaling and reliability. In Kubernetes, container file systems are ephemeral and not meant to hold stateful data. Instead, using Autonomous Database or persistent storage volumes is the recommended approach.
- D. Incorrect.
Option 4 is incorrect. Manual node scaling adds unnecessary operational burden. Although it can temporarily reduce cost if workloads are predictable, it fails to handle sudden traffic spikes effectively and is not aligned with cloud-native best practices.