1Z0-997-25 Question 12
Select 2Your organization is deploying a microservices-based e-commerce application on Oracle Cloud Infrastructure (OCI). Each microservice runs in its own container on OCI Container Engine for Kubernetes (OKE). The development team wants to implement a CI/CD pipeline using Oracle DevOps for automated builds and rolling deployments, ensuring minimal downtime and rapid feature releases. Which TWO design choices will help you achieve a resilient and streamlined microservices deployment?
- A
Use OCI DevOps Build Pipelines to create separate container images per microservice and OCI DevOps Deployment Pipelines to perform rolling updates on your OKE cluster.
- B
Store credentials and configuration data directly in container images to reduce application startup complexity and avoid using external secret management services.
- C
Define resource requests and limits for each microservice in the Kubernetes manifests to prevent resource contention and ensure proper autoscaling.
- D
Use a single Persistent Volume for all microservices so that each microservice can share the same application data and configuration files.
- E
Combine all microservices into a single container to streamline orchestration and reduce cluster complexity.
Show answer and explanation
Correct answers: A, C
Explanation
A robust microservices architecture on OCI typically involves using OCI DevOps Build and Deployment Pipelines to handle container image builds and rolling deployments on OCI Container Engine for Kubernetes (OKE). Each microservice should have its own resource constraints defined, ensuring high availability and efficient autoscaling. For additional guidance, consult the Oracle Cloud Infrastructure documentation regarding OCI DevOps (https://docs.oracle.com/en-us/iaas/Content/devops/using/home.htm) and OKE best practices (https://docs.oracle.com/en-us/iaas/Content/ContEng/Concepts/contengoverview.htm).
- A. Correct.
Option 1 is correct. Using OCI DevOps Build Pipelines to build separate container images for each microservice aligns with good microservices design. Rolling updates with OCI DevOps Deployment Pipelines in an OKE cluster ensure minimal downtime.
- B. Incorrect.
Option 2 is incorrect. Storing credentials in container images is an insecure practice and violates OCI security best practices. It is better to use secrets or configuration maps in Kubernetes, or a service like OCI Vault.
- C. Correct.
Option 3 is correct. Specifying resource requests and limits for each microservice is a Kubernetes best practice. This ensures that microservices are allocated the right amount of CPU and memory resources, preventing conflicts and promoting stable autoscaling.
- D. Incorrect.
Option 4 is incorrect. A single Persistent Volume shared by all microservices can create data conflicts and complicate scaling or updating individual microservices. Typically, each microservice should manage its own storage requirements.
- E. Incorrect.
Option 5 is incorrect. Combining all microservices into a single container negates the benefits of a microservices architecture. It would reduce flexibility, make scaling less efficient, and reintroduce a monolithic design.