1Z0-997-25 Question 8
Single answerYour development team is creating a microservices-based eCommerce application on Oracle Cloud Infrastructure (OCI). Each service is containerized and hosted in Oracle Container Engine for Kubernetes (OKE). You need to frequently deploy new features with minimal disruption, store container images securely, and have the option to quickly roll back if issues arise. Which design approach best addresses these requirements?
- A
Create an OCI DevOps pipeline that builds container images, pushes them to Oracle Container Registry, and uses a rolling update strategy in OKE.
- B
Host all microservice container images in a privately managed on-premises Docker registry and manually update OKE deployments using custom shell scripts.
- C
Perform blue-green deployments by spinning up additional clusters on-demand for each release and migrating traffic with a DNS switch operation.
- D
Use a single large monolithic container image to simplify updates, and manually restart all pods in OKE when releasing a new version.
Show answer and explanation
Correct answer: A
Explanation
OCI DevOps provides a fully managed pipeline solution designed to work seamlessly with OKE and Oracle Container Registry. By automating builds, tests, and deployments, you can minimize downtime via rolling updates and have a fast recovery path with rollbacks. This approach aligns with Oracle's recommended DevOps best practices for microservices. Refer to Oracle documentation (https://docs.oracle.com/en-us/iaas/Content/devops/overview.htm) for detailed guidance on configuring OCI DevOps, container registries, and deployment strategies in OKE.
- A. Correct.
Correct. Using OCI DevOps for your build pipeline ensures integrated builds, tests, and deployments. The pipeline can automatically push container images to Oracle Container Registry, and OKE supports rolling deployment strategies for minimal downtime. This approach also facilitates quick rollbacks if a deployment fails.
- B. Incorrect.
Incorrect. While a private on-premises registry can be used, manually updating OKE deployments with scripts increases operational overhead and risk of errors. This approach doesn't leverage OCI DevOps features that automate and streamline the CI/CD process.
- C. Incorrect.
Incorrect. Blue-green deployments are a valid strategy in some scenarios, but spinning up entirely new clusters on-demand for every release is often more costly and operationally complex than rolling updates within a single OKE cluster.
- D. Incorrect.
Incorrect. Combining all microservices into one large container goes against microservices best practices, making updates more disruptive. Manually restarting all pods also increases downtime and operational errors.