1Z0-997-25 Question 14
Select 2You are designing a microservices-based ordering and inventory system on Oracle Cloud Infrastructure (OCI) for a global retailer. Your DevOps team uses Oracle DevOps to build container images and store them in Oracle Container Registry (OCIR), then deploy these images on Oracle Container Engine for Kubernetes (OKE). The team wants to deploy each microservice with minimal downtime, allow quick rollbacks if necessary, and also implement canary releases to test new versions in a controlled manner. Which TWO design considerations should be implemented to meet these requirements?
- A
Use rolling updates in OKE so each microservice gradually updates its Pods without requiring downtime.
- B
Configure a canary deployment pipeline in Oracle DevOps to initially route a limited percentage of traffic to the new version of a service before rolling out fully.
- C
Host container images in an external Docker registry to reduce reliance on OCI services.
- D
Package all microservices as a single monolithic container to simplify environment management.
Show answer and explanation
Correct answers: A, B
Explanation
By combining rolling updates in OKE with a canary pipeline in Oracle DevOps, you ensure minimal downtime, controlled testing of new releases, and quick rollback if needed. Storing images in OCI Container Registry is a recommended practice for smoother integration and security within OCI. More details can be found in Oracle's official documentation for Container Engine for Kubernetes and OCI DevOps: https://docs.oracle.com/en/oci/
- A. Correct.
Correct. Rolling updates in OKE allow Pods to be replaced incrementally, minimizing downtime while updating microservices in production.
- B. Correct.
Correct. A canary deployment pipeline in Oracle DevOps provides granular traffic control, verifying new versions with a subset of users before full deployment.
- C. Incorrect.
Incorrect. While you can use external registries, using OCI� native Container Registry ensures closer integration with OKE and OCI DevOps, simplifying configuration and security.
- D. Incorrect.
Incorrect. Combining all services into a single container defeats the purpose of a microservices architecture and makes it harder to scale, test, and rollback individual services.