Refer to the exhibit. A DevOps engineer must deploy two microservices. The deployment must be installed in a new Kubernetes cluster. The microservices currently run in Docker and are managed by using

Question

services:
 database:
 image: postgres:latest
 volumes:
 - db_data:/var/lib/postgresql/data
 microservice1:
 image: microservice1:latest
 depends_on:
 - database
 microservice2:
 image: microservice2:latest
 depends_on:
 - microservice1

Explanation

This question tests the ability to translate a Docker Compose multi-service definition into an ordered Kubernetes deployment workflow, covering cluster setup, manifest creation, and dependency-aware rollout.

Approach. The correct sequence follows a dependency-first, infrastructure-before-application order: (1) Provision the new Kubernetes cluster and configure kubectl access (kubeconfig). (2) Ensure container images (microservice1, microservice2, postgres) are pushed to a registry accessible by the cluster. (3) Create Kubernetes manifests - a PersistentVolumeClaim for the db_data volume, Deployments and Services for each workload - translating docker-compose constructs into native K8s objects. (4) Apply manifests in dependency order using kubectl apply -f: PVC and database first, then microservice1 (which depends_on database), then microservice2 (which depends_on microservice1), verifying pod readiness at each stage with kubectl get pods or readiness probes.

Concept tested. Translating Docker Compose service definitions (images, volumes, depends_on) into Kubernetes resources (Deployments, Services, PersistentVolumeClaims) and applying them in correct dependency order within a new cluster.

Reference. Kubernetes Documentation - 'Translate a Docker Compose File to Kubernetes Resources' (kompose.io); CKA/CKAD exam objectives on workload deployment and storage.

No community discussion yet for this question.