1Z0-997-25 Question 4
Select 2Your organization is building a new e-commerce platform on Oracle Cloud Infrastructure using a microservices architecture. The platform must handle large traffic surges during promotional events yet stay cost-efficient when traffic is low. You also want minimal operational overhead for ephemeral workloads, such as order validation tasks, which only run sporadically. Which two design choices should you implement to meet these requirements?
- A
Containerize your microservices with Oracle Container Engine for Kubernetes (OKE) and configure horizontal pod autoscaling
- B
Implement Oracle Functions for stateless, event-driven tasks that scale automatically
- C
Provision Oracle Exadata Cloud Service for ephemeral workloads
- D
Host all microservices on a single always-running Oracle Compute instance with manual scaling
Show answer and explanation
Correct answers: A, B
Explanation
Leveraging Oracle Container Engine for Kubernetes (OKE) with horizontal pod autoscaling ensures that microservices can scale up or down based on real-time loads. Oracle Functions handles stateless, event-driven tasks in a serverless manner, eliminating idle costs. According to Oracle� Cloud Native Architecture best practices, combining OKE for persistent services with Functions for short-lived or ephemeral tasks is an effective way to balance performance and cost efficiency. Refer to Oracle� official OCI documentation for guidance on setting up and configuring these services.
- A. Correct.
Correct. Oracle Container Engine for Kubernetes (OKE) supports automatic horizontal pod autoscaling, enabling microservices to dynamically scale based on demand. This design minimizes idle resource costs because when traffic is low, the number of pods can decrease, and when traffic spikes, additional pods are provisioned automatically.
- B. Correct.
Correct. Oracle Functions is a serverless platform that automatically spins up execution environments only when needed. It� ideal for short-lived or event-driven tasks, such as order validation, because you pay only for the actual time your function runs, reducing overhead during idle periods.
- C. Incorrect.
Incorrect. Oracle Exadata Cloud Service is intended for high-performance database workloads, not transient microservices or event-driven tasks. Using Exadata for ephemeral workloads is both cost-inefficient and operationally complex for the scenario described.
- D. Incorrect.
Incorrect. Deploying all microservices on a single Oracle Compute instance with manual scaling can lead to excessive costs when the instance sits idle. Moreover, manual scaling is error-prone, inefficient for handling sudden traffic spikes, and does not provide the flexibility of autonomous or serverless scaling.