CKAD Application Deployment Practice Test 5 — 15 Questions

Question 1

A developer is creating a Deployment with 4 replicas. The application requires a rolling update with zero downtime. Which TWO strategies ensure zero downtime during an update?

Accepted Answer

Set maxSurge=1. Setting maxSurge=1 allows Kubernetes to spin up one new Pod before terminating any old Pod during a rolling update. This ensures that the total number of available Pods never drops below the desired replica count, maintaining service capacity and achieving zero downtime.

Answer

Set maxUnavailable=1

Answer

Use Recreate strategy

Answer

Set maxSurge=0

Question 2

A team is deploying a multi-container pod with a main application container and a sidecar container for logging. Which THREE statements about pod design are correct?

Accepted Answer

Containers in a pod share the same network namespace.. Containers within the same Kubernetes pod share the same network namespace, including the same IP address and port space. This allows them to communicate via localhost and share network resources, which is essential for sidecar patterns like logging agents that need to intercept or monitor the main container's traffic.

Answer

Containers in a pod share the same filesystem root.

Answer

The sidecar container must use the same image as the main container.

Question 3

A developer is deploying a web application that requires 2 GiB of memory and 0.5 CPU cores. The cluster nodes have 4 GiB of memory and 2 CPU cores each. The developer wants to ensure the pod gets guaranteed QoS class. Which resource specification should be used?

Accepted Answer

requests: memory: 2Gi, cpu: 500m; limits: memory: 2Gi, cpu: 500m. For a pod to receive the Guaranteed QoS class, every container in the pod must have both resource requests and limits set, and the requests must equal the limits for each resource (memory and CPU). This configuration ensures the pod is not overcommitted and gets the highest priority under resource pressure.

Answer

requests: memory: 2Gi, cpu: 500m; no limits

Answer

requests: memory: 2Gi, cpu: 500m; limits: memory: 4Gi, cpu: 1

Answer

requests: memory: 1Gi, cpu: 250m; limits: memory: 2Gi, cpu: 500m

Question 4

A company wants to ensure zero-downtime deployments for a stateless web application running in Kubernetes. They have a single Deployment with 3 replicas and a Service of type LoadBalancer. Which strategy should they use to achieve this?

Accepted Answer

Use RollingUpdate with maxSurge=25% and maxUnavailable=0. A RollingUpdate strategy with maxSurge=25% and maxUnavailable=0 ensures that during a deployment, the desired number of replicas is always available (no downtime). maxUnavailable=0 means no old Pods are terminated until new ones are ready, and maxSurge=25% allows one extra Pod (25% of 3 replicas = 0.75, rounded up to 1) to be created before terminating old ones, maintaining capacity for zero-downtime updates.

Answer

Use Recreate strategy

Answer

Use RollingUpdate with maxSurge=100% and maxUnavailable=100%

Answer

Use RollingUpdate with maxSurge=0 and maxUnavailable=25%

Question 5

The exhibit shows a Deployment manifest. When applied, the pods are created but show 'CrashLoopBackOff'. What is the most likely cause?

Accepted Answer

The liveness probe targets port 8080, but the container only listens on port 80. The liveness probe is configured to check port 8080, but the container (nginx) only listens on port 80 by default. Since the probe never receives a successful HTTP response, Kubernetes restarts the container repeatedly, causing the CrashLoopBackOff state. The probe must target the same port the application is serving on.

Answer

The selector does not match the pod labels

Answer

The initialDelaySeconds is too short, starting probes before the app is ready

Answer

The container image nginx:1.21 does not exist

Question 6

Order the steps to expose a Kubernetes Deployment as a ClusterIP Service.

Accepted Answer

Step 1: Ensure Deployment exists and is running. Step 2: Create a ClusterIP Service YAML manifest. Step 3: Apply the Service manifest using kubectl apply. Step 4: Verify the Service endpoints are populated. Step 5: Test DNS resolution of the Service name from a pod.. A Service requires a running Deployment. Define and apply the Service, then verify endpoints and test DNS resolution.

Answer

Step 1: Create a ClusterIP Service YAML manifest. Step 2: Apply the Service manifest. Step 3: Ensure Deployment exists and is running. Step 4: Test DNS resolution. Step 5: Verify endpoints.

Answer

Step 1: Ensure Deployment exists and is running. Step 2: Test DNS resolution. Step 3: Create the Service YAML. Step 4: Apply the Service. Step 5: Verify endpoints.

Answer

Step 1: Apply the Service manifest. Step 2: Create the Service YAML. Step 3: Ensure Deployment exists. Step 4: Verify endpoints. Step 5: Test DNS.

Question 7

You have a Deployment named 'frontend' with 4 replicas. You want to perform a rolling update with the following constraints: the number of pods above the desired count should never exceed 1, and the number of unavailable pods should never exceed 0. Which deployment strategy configuration achieves this?

Accepted Answer

strategy: rollingUpdate: {maxSurge: 1, maxUnavailable: 0}. Setting `maxSurge: 1` ensures that during a rolling update, at most one additional pod is created above the desired replica count of 4, and `maxUnavailable: 0` guarantees that no pods are taken down until the new ones are ready. This satisfies the constraints of never exceeding one extra pod and never having unavailable pods.

Answer

strategy: rollingUpdate: {maxSurge: 2, maxUnavailable: 0}

Answer

strategy: rollingUpdate: {maxSurge: 25%, maxUnavailable: 25%}

Answer

strategy: type: Recreate

Question 8

You are implementing a canary deployment for a microservice named 'api'. The stable version is deployed as 'api-stable' with label 'version: stable'. You create a canary Deployment 'api-canary' with label 'version: canary'. Both Deployments have the same label 'app: api'. You want a Service 'api-svc' to route 90% of traffic to stable and 10% to canary. Which Service configuration achieves this?

Accepted Answer

selector: {app: api} and adjust the number of replicas in each Deployment to achieve the desired ratio (e.g., 9 stable, 1 canary). Kubernetes Services distribute traffic based on the number of ready Pods matching the selector. By setting 9 replicas for 'api-stable' and 1 replica for 'api-canary', both with the same selector 'app: api', the Service will route approximately 90% of requests to stable and 10% to canary, achieving the desired canary deployment ratio without native traffic splitting.

Answer

Add annotation 'traffic-weight: 90' to stable and 'traffic-weight: 10' to canary

Answer

selector: {app: api, version: stable}

Answer

Create two separate Services, each targeting one version, and rely on DNS weighting

Question 9

You have installed a Helm chart for 'wordpress' using 'helm install my-wordpress bitnami/wordpress'. Later, you want to check the status of the release. Which command lists the status of all releases?

Accepted Answer

helm list. The `helm list` command is the correct way to list all releases in the current namespace, showing their status (deployed, failed, pending, etc.). It provides a summary of each release, including the name, revision, update time, and status. This directly answers the question of listing the status of all releases.

Answer

helm status my-wordpress

Answer

helm history my-wordpress

Answer

helm show status

Question 10

A Deployment has 3 replicas. You run 'kubectl scale deployment mydeploy --replicas=5'. What happens?

Accepted Answer

The Deployment is updated to have 5 replicas, and the ReplicaSet creates 2 additional pods.. `kubectl scale` updates the Deployment's `spec.replicas` field to 5, which triggers the existing ReplicaSet to adjust its pod count. The ReplicaSet controller creates 2 additional pods to match the desired state, resulting in a total of 5 pods. The Deployment itself is not replaced, and no new ReplicaSet is created unless the pod template changes.

Answer

The command fails because you must edit the YAML directly.

Answer

A new Deployment is created with 5 replicas.

Answer

The current ReplicaSet is deleted and a new one is created with 5 replicas.

Question 11

You have a Deployment 'app' with the following strategy configuration: 'type: RollingUpdate', 'rollingUpdate: {maxSurge: 0, maxUnavailable: 1}'. You update the container image. What is the behavior during the update?

Accepted Answer

One old pod is terminated, then a new pod is created, repeating until all pods are updated.. With `maxSurge: 0` and `maxUnavailable: 1`, the RollingUpdate strategy ensures that during the update, no extra pods beyond the desired replica count are created (surge is zero), and at most one pod can be unavailable at any time. The Deployment controller first terminates an old pod (making one unavailable), then creates a new pod to replace it, repeating this process until all pods are updated. This guarantees a controlled, sequential rollout with minimal disruption.

Answer

A new pod is created first, then the oldest pod is terminated.

Answer

Two old pods are terminated at a time, while new pods are created.

Answer

All old pods are terminated simultaneously, then new pods are created.

Question 12

Which command is used to undo the most recent rollout of a Deployment named 'myapp'?

Accepted Answer

kubectl rollout undo deployment myapp. `kubectl rollout undo deployment myapp` reverts the Deployment to the previous revision by default, effectively undoing the most recent rollout. This command uses the rollout history stored in the Deployment's annotations (e.g., `deployment.kubernetes.io/revision`) to identify and apply the prior ReplicaSet.

Answer

kubectl rollout undo deployment myapp --to-revision=2

Answer

kubectl rollout status deployment myapp

Answer

kubectl rollback deployment myapp

Question 13

You have a YAML file 'deploy.yaml' that defines a Deployment. Which command creates the Deployment if it does not exist, or updates it if it already exists?

Accepted Answer

kubectl apply -f deploy.yaml. `kubectl apply -f deploy.yaml` uses declarative object configuration: it creates the Deployment if it doesn't exist, or performs a strategic merge patch to update it if it already exists. This is the standard command for managing Kubernetes resources with a desired-state file.

Answer

kubectl replace -f deploy.yaml

Answer

kubectl patch -f deploy.yaml

Answer

kubectl create -f deploy.yaml

Question 14

A Helm chart has the following template snippet: '{{ .Values.replicaCount }}'. You want to set replicaCount to 5 during installation. Which command should you use?

Accepted Answer

helm install my-release mychart --set replicaCount=5. The `--set` flag in Helm allows you to directly override a single value in a chart's `values.yaml` file from the command line. This is the standard way to set `replicaCount` to 5 during installation without modifying the chart or using a separate values file.

Answer

helm install my-release mychart --name replicaCount=5

Answer

helm install my-release mychart --values replicaCount=5

Answer

helm install my-release mychart --set-string replicaCount=5

Question 15

Which TWO of the following are valid uses of Kubernetes Annotations? (Select two.)

Accepted Answer

Configuring ingress controllers with specific settings like rewrite rules.. Kubernetes annotations are key-value pairs used to attach arbitrary non-identifying metadata to objects, and Ingress controllers commonly use specific annotations (e.g., nginx.ingress.kubernetes.io/rewrite-target) to configure behavior like URL rewriting. This allows operators to customize controller functionality without altering the core resource definition.

Answer

Defining the name of a Kubernetes resource.

Answer

Identifying which pods a Service should route traffic to.

Answer

Enabling service discovery between microservices.