1Z0-997-25 Question 3
Single answerYou have been asked to design a cloud-native, microservices-based e-commerce platform on Oracle Cloud Infrastructure (OCI). The platform must handle varying traffic loads with minimal operational overhead. Key requirements include rapid scalability, high availability, and efficient management of stateless services. Which solution architecture best addresses these requirements?
- A
A) Deploy all services on a single Virtual Machine (VM) instance and manually adjust shape sizes to scale.
- B
B) Implement a microservices architecture using Oracle Container Engine for Kubernetes (OKE) with a Horizontal Pod Autoscaler (HPA), and store microservice state in an external OCI service such as Autonomous Database.
- C
C) Run the application in an on-premises Kubernetes cluster connected to OCI through a VPN to reduce cloud costs.
- D
D) Use local ephemeral storage within each container for stateful services and scale out manually whenever traffic surges.
Show answer and explanation
Correct answer: B
Explanation
A cloud-native microservices approach on OCI often involves using OKE with features like the Horizontal Pod Autoscaler and external data persistence in Autonomous Database to separate state from the microservices. This aligns with the recommended pattern of building stateless microservices that can be scaled horizontally with minimal downtime or manual intervention. Further guidance can be found in OCI's official documentation on Container Engine for Kubernetes, which includes best practices for configuring HPA and integrating with other OCI services to achieve high availability and fault tolerance.
- A. Incorrect.
A) Incorrect: Placing all services on a single VM instance and scaling by adjusting the instance shape is manually intensive and does not leverage cloud-native capabilities such as Kubernetes-based auto-scaling. This approach increases operational overhead and does not offer the high availability you typically need for production traffic spikes.
- B. Correct.
B) Correct: Using Oracle Container Engine for Kubernetes (OKE) with the Horizontal Pod Autoscaler (HPA) is a recommended cloud-native approach, allowing automatic scaling of microservices. Storing application state in an external data store such as an Autonomous Database ensures stateless service containers, making them more resilient and easier to scale up and down as traffic demands change.
- C. Incorrect.
C) Incorrect: While a hybrid or on-premises approach can sometimes be valid, hosting the Kubernetes cluster on-premises for a cloud-native solution negates many auto-scaling benefits and can introduce latency issues. Also, you lose some of OCI� fully managed capabilities that reduce operational overhead.
- D. Incorrect.
D) Incorrect: Relying solely on local ephemeral storage for stateful services is not aligned with cloud-native best practices. If containers restart, any state stored locally is lost, which can lead to data inconsistency. Furthermore, manual scaling does not efficiently handle sudden traffic surges.