CKAD Application Deployment Practice Test 3 — 15 Questions

Question 1

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}. Option B is correct: maxSurge=1 ensures at most one extra pod above the desired count, and maxUnavailable=0 ensures no pods are unavailable during the update. Option A allows up to 25% surge and 25% unavailable. Option C allows up to 2 extra pods. Option D uses Recreate strategy which is not rolling.

Answer

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

Answer

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

Answer

strategy: type: Recreate

Question 2

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). Option C is correct: use a common label 'app: api' in the selector, then manage traffic proportion by adjusting replica counts (e.g., 9 replicas stable, 1 replica canary). Option A uses a single label selector targeting a specific version, which would not select both. Option B uses separate services, not a single service. Option D uses an annotation that does not affect traffic routing.

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 3

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. Option B is correct: 'helm list' lists all releases in the current namespace. Option A only shows the status of a specific release. Option C shows revision history of a release. Option D is not a valid Helm command.

Answer

helm status my-wordpress

Answer

helm history my-wordpress

Answer

helm show status

Question 4

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.. Option A is correct: the command scales the Deployment to 5 replicas. Option B is incorrect because the command is valid. Option C is incorrect because ReplicaSet is managed by Deployment. Option D is incorrect; no new Deployment is created.

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 5

You have an existing Deployment 'web' created with 'kubectl create deployment web --image=nginx --replicas=3'. You need to change the image to 'nginx:1.19' and record the change. Which command should you use?

Accepted Answer

kubectl set image deployment/web web=nginx:1.19 --record. Option B is correct: 'kubectl set image deployment/web web=nginx:1.19 --record' updates the image and records the command in the rollout history. Option A uses 'kubectl edit' which does not record changes by default unless '--record' is added. Option C uses 'kubectl replace' which requires a file. Option D applies a patch but '--record' is not a valid flag for patch.

Answer

kubectl replace -f deployment.yaml --record

Answer

kubectl edit deployment web --record

Answer

kubectl patch deployment web -p '{"spec":{"template":{"spec":{"containers":[{"name":"web","image":"nginx:1.19"}]}}}}' --record

Question 6

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.. Option A is correct: maxSurge=0 means no extra pods above the desired count; maxUnavailable=1 means one pod can be unavailable at a time. So one old pod is terminated before a new one is created. Option B describes Recreate. Option C is incorrect because maxSurge=0 prevents creating new pods first. Option D is incorrect because only one pod is unavailable.

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 7

You are using Kustomize to manage configurations. Your project structure is: 'base/kustomization.yaml', 'overlays/prod/kustomization.yaml'. The base defines a Deployment with image 'nginx:1.18'. The overlay wants to patch the image to 'nginx:1.19'. Which is the correct way to define the patch in the overlay?

Accepted Answer

Use 'patchesStrategicMerge: [deployment-patch.yaml]' where deployment-patch.yaml contains the image override.. Option B is correct: patchesStrategicMerge is used for strategic merge patches. Option A is a valid field but for JSON patches, not for this simple image change. Option C is incorrect because patchesJson6902 is for JSON patches. Option D is a valid field but not the standard way; patchesStrategicMerge is more common for such patches.

Answer

Use 'patches: [path: deployment-patch.yaml]'

Answer

Use 'resources: [../base]' and then define a new Deployment with the same name to override.

Answer

Use 'patchesJson6902: [target: ..., patch: ...]'

Question 8

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

Accepted Answer

kubectl rollout undo deployment myapp. Option A is correct: 'kubectl rollout undo deployment myapp' rolls back to the previous revision. Option B rolls back to a specific revision. Option C shows the status, not undo. Option D is not a valid command.

Answer

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

Answer

kubectl rollout status deployment myapp

Answer

kubectl rollback deployment myapp

Question 9

You have a HorizontalPodAutoscaler (HPA) targeting a Deployment. The HPA is configured with 'targetCPUUtilizationPercentage: 50'. The current CPU utilization is 60% across the pods. What action does the HPA take?

Accepted Answer

Scale up the Deployment to reduce per-pod CPU utilization.. Option B is correct: HPA scales up to bring actual utilization closer to the target. Option A is incorrect because scaling down when above target would increase utilization further. Option C is incorrect because HPA does not wait for sustained load; it reacts based on the metric. Option D is incorrect because HPA does not stop itself; it continues to adjust.

Answer

Scale down the Deployment because the target is 50%.

Answer

Mark the HPA as unable to calculate metrics and stop scaling.

Answer

Take no action because the deviation is within tolerance.

Question 10

You are performing a blue-green deployment for an application. You have two Deployments: 'app-blue' (current production) and 'app-green' (new version). Both have label 'app: myapp' and are exposed by a Service 'myapp-svc'. How do you switch traffic from blue to green?

Accepted Answer

Update the Service's selector to match the labels of the green Deployment's pods (e.g., 'version: green').. Option B is correct: updating the Service's selector to match the green Deployment's pod label routes traffic to green. Option A is incorrect because the Service cannot be deleted and recreated without downtime if done incorrectly. Option C is incorrect because changing the image in the same Deployment would perform a rolling update, not a blue-green switch. Option D is incorrect because deleting blue would cause downtime.

Answer

Delete the Service and recreate it with the selector pointing to app-green.

Answer

Delete the blue Deployment after ensuring green is ready.

Answer

Update the blue Deployment's image to the new version.

Question 11

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. Option B is correct: 'kubectl apply' creates or updates resources declaratively. Option A ('create') fails if the resource exists. Option C ('replace') requires the resource to exist. Option D ('patch') modifies an existing resource but is not idempotent like apply.

Answer

kubectl replace -f deploy.yaml

Answer

kubectl patch -f deploy.yaml

Answer

kubectl create -f deploy.yaml

Question 12

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. Option D is correct: '--set' overrides values directly on the command line. Option A sets the release name, not values. Option B specifies a values file, but the question asks for direct setting. Option C is not a valid flag.

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 13

Which TWO of the following are valid methods to achieve a blue-green deployment in Kubernetes? (Select two.)

Accepted Answer

Create two Deployments (blue and green) with different labels, and a Service that selects one of them. Update the Service's selector to switch traffic.. Options A and C are correct. A: Create two separate Deployments and switch a Service's selector. C: Use Kubernetes Services with label selectors to route traffic to one set of pods, then update the selector. Option B is not standard; Option D describes a canary deployment; Option E describes a rolling update.

Answer

Use a single Deployment and change the image, then use kubectl rollout pause/resume to control traffic.

Answer

Set maxSurge=100% and maxUnavailable=0% in the Deployment strategy.

Answer

Create multiple Deployments with different images and use Ingress with weight-based routing.

Question 14

Which THREE of the following are valid ways to view the rollout history of a Deployment named 'myapp'? (Select three.)

Accepted Answer

kubectl get replicasets -l app=myapp. Options A, C, and D are correct. A: 'kubectl rollout history deployment myapp' shows all revisions. C: 'kubectl describe deployment myapp' includes annotations like 'deployment.kubernetes.io/revision' showing the current revision. D: 'kubectl get replicasets -l app=myapp' shows all ReplicaSets, which correspond to revisions. Option B is not a valid command; Option E shows only the current status, not the history.

Answer

kubectl rollout status deployment myapp

Answer

kubectl get deployment myapp -o yaml

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.. Options B and D are correct. Annotations are used to attach non-identifying metadata. Option B is correct because annotations can be used by tools like Helm to track release information. Option D is correct because annotations can be used by ingress controllers for specific configurations. Option A is incorrect because selectors are used for identification. Option C is incorrect because the 'name' field is used for naming. Option E is incorrect because annotations are not used for service discovery; labels and selectors are.

Answer

Defining the name of a Kubernetes resource.

Answer

Identifying which pods a Service should route traffic to.

Answer

Enabling service discovery between microservices.