1Z0-997-25 Question 5
Select 2Your team is building an e-commerce analytics pipeline on Oracle Cloud Infrastructure (OCI) to handle user interactions in near real time. They want to use an event-driven, serverless approach to reduce operational overhead and scale seamlessly. Which two design approaches should you adopt to build this microservices solution on OCI?
- A
Use Oracle Functions with OCI Events Service triggers to invoke serverless functions whenever new data is placed in OCI Streaming.
- B
Deploy fixed-shape nodes on Oracle Container Engine for Kubernetes and handle scaling manually by resizing compute instances.
- C
Utilize OCI Streaming to decouple high-throughput data ingestion from downstream microservices, triggering functions for on-demand processing.
- D
Set up a custom VM for Oracle Functions so you can manually configure the underlying OS for each microservice workload.
- E
Implement Oracle Functions behind an API Gateway, ensuring microservices are stateless and scale automatically based on demand.
Show answer and explanation
Correct answers: A, C
Explanation
In this scenario, the primary goal is to build a cloud-native, event-driven, and serverless solution on OCI. Leveraging OCI Streaming for high-throughput data ingestion and Oracle Functions with OCI Events Service for on-demand execution is a recommended pattern. It minimizes operational overhead, scales automatically with incoming traffic, and ensures a loosely coupled microservices architecture. For further information, consult OCI documentation on Functions (https://docs.oracle.com/en-us/iaas/Content/functions.htm) and Streaming (https://docs.oracle.com/en-us/iaas/Content/Streaming/Concepts/streamingoverview.htm).
- A. Correct.
Option 1 is correct. Oracle Functions can leverage OCI Events Service to automatically invoke serverless functions when new messages arrive in OCI Streaming. This design pattern is essential for event-driven architectures, allowing functions to run code only when needed and scale seamlessly with incoming events.
- B. Incorrect.
Option 2 is incorrect. Manually resizing fixed-shape nodes on Oracle Container Engine for Kubernetes provides scalability but increases operational overhead and does not fully leverage OCI's serverless offerings. This approach can be used but does not align with a purely event-driven, serverless design.
- C. Correct.
Option 3 is correct. OCI Streaming provides a scalable and durable messaging backbone, enabling microservices to process data asynchronously. By triggering serverless functions for on-demand transformations, you achieve both elasticity and loose coupling among services.
- D. Incorrect.
Option 4 is incorrect. Oracle Functions is a fully managed service running on OCI infrastructure�you do not deploy a custom VM for it. This choice does not reflect the serverless nature of Oracle Functions, which abstracts away the operating system management.
- E. Incorrect.
Option 5 is incorrect. While integrating Oracle Functions with an API Gateway is a common pattern for microservices, standalone usage behind an API Gateway does not inherently address high-throughput event ingestion or real-time data processing. The key requirement in the scenario is near real-time event-driven architecture, which is best met by pairing functions with OCI Streaming and Events.