CKAD Application Deployment Practice Test 13 — 15 Questions

Question 1

A developer wants to perform a canary deployment where 10% of traffic goes to a new version (v2) of an application. They create two Deployments (app-v1 and app-v2) and a Service. The Service selector is configured to match labels: 'app: myapp, version: v1'. How can they route 10% of traffic to v2 with minimal changes?

Choose an answer to begin — your selection is scored in the full session.

Accepted Answer

Change the Service selector to 'app: myapp' (remove version label) and set v1 replicas to 9 and v2 replicas to 1.. To achieve a canary deployment with 10% traffic to v2, the Service selector must match pods from both versions. By changing the selector to 'app: myapp' (removing the version label), the Service will load-balance across all pods with that label. Then, by setting v1 replicas to 9 and v2 replicas to 1, the total pods are 10, so v2 receives approximately 10% of traffic. This requires minimal changes: one selector update and replica adjustments.

Answer

Use kubectl rollout pause on the v2 Deployment.

Answer

Set the v2 Deployment's spec.replicas to 10% of the total replicas and keep the Service selector unchanged.

Answer

Add a NetworkPolicy to limit traffic to v2 pods to 10%.

Question 2

What is the purpose of the 'maxUnavailable' field in a Deployment's rolling update configuration?

Accepted Answer

The maximum number of Pods that can be unavailable during the update.. The 'maxUnavailable' field in a Deployment's rolling update configuration specifies the maximum number of Pods that can be unavailable during the update process, relative to the desired replica count. This ensures that a controlled number of Pods are taken down at a time, maintaining application availability while the update progresses. It is defined as either an absolute number or a percentage of the desired replicas, and it works in conjunction with 'maxSurge' to control the update pace.

Answer

The maximum number of Pods that can be created above the desired replicas.

Answer

The maximum time allowed for the update to complete.

Answer

The maximum number of Pods to be terminated simultaneously.

Question 3

Which command shows the rollout history of a Deployment named 'web'?

Accepted Answer

kubectl rollout history deployment web. `kubectl rollout history deployment web` is the dedicated command to display the revision history of a Deployment, including revision numbers and change-cause annotations. This command directly queries the Deployment's rollout state from the Kubernetes API server, showing each revision's metadata.

Answer

kubectl rollout status deployment web

Answer

kubectl get deployment web -o yaml

Answer

kubectl describe deployment web

Question 4

A Deployment is configured with strategy type 'Recreate'. Which statement about this strategy is true?

Accepted Answer

It terminates all existing Pods before creating new Pods.. The Recreate strategy in a Kubernetes Deployment terminates all existing Pods before creating new ones, resulting in a brief period of downtime. This is the defining behavior of the Recreate strategy as documented in the Kubernetes Deployment spec. It is the opposite of RollingUpdate, which maintains availability by incrementally replacing Pods.

Answer

It creates a new ReplicaSet but does not scale down the old one.

Answer

It updates Pods by gradually terminating old Pods and creating new ones.

Answer

It first creates new Pods and then terminates old Pods.

Question 5

What is the effect of running 'kubectl rollout pause deployment web'?

Accepted Answer

It marks the deployment as paused, and no changes are applied until 'kubectl rollout resume' is run.. Running 'kubectl rollout pause deployment web' marks the deployment as paused, which means that any subsequent changes to the deployment's spec (e.g., updating the container image) will not trigger a rollout or create new ReplicaSets. The current state of the Pods remains unchanged until 'kubectl rollout resume' is executed, which resumes the rollout and applies any pending changes. This is a Kubernetes-native mechanism to control the timing of rollouts, often used for canary deployments or manual verification.

Answer

It stops all Pods in the deployment.

Answer

It deletes the deployment and recreates it.

Answer

It prevents new Pods from being created.

Question 6

An administrator runs 'kubectl apply -f deployment.yaml' and later wants to revert to the previous configuration. Which approach is correct?

Accepted Answer

Run 'kubectl rollout undo deployment '.. 'kubectl rollout undo deployment ' reverts a Deployment to its previous ReplicaSet revision by rolling back the Deployment's pod template, which is the built-in mechanism Kubernetes provides for undoing a rollout. It uses the revision history stored in the Deployment's ReplicaSets, so it restores the prior configuration cleanly without manual editing.

Answer

Run 'kubectl edit deployment <name>' and manually revert changes.

Answer

Run 'kubectl delete -f deployment.yaml' and reapply the old YAML.

Answer

Run 'kubectl replace -f deployment.yaml' with the old YAML.

Question 7

Which TWO statements about Kustomize are true?

Accepted Answer

Kustomize supports overlays that allow different configurations for different environments.. Kustomize supports overlays, which are layered patches applied on top of a base configuration. This allows you to define a common base set of Kubernetes resources and then use different overlay directories (e.g., dev, staging, prod) to customize settings like replicas, image tags, or namespaces for each environment without duplicating the entire manifest.

Answer

Kustomize can be used to perform canary deployments.

Answer

Kustomize requires Helm to manage dependencies.

Answer

Kustomize can only be used with kubectl apply -k.

Question 8

Which THREE of the following are valid ways to update a Deployment's container image in Kubernetes?

Accepted Answer

kubectl apply -f updated-deployment.yaml with the new image.. `kubectl apply -f updated-deployment.yaml` applies a declarative configuration that includes the new container image. When the Deployment manifest is updated with the new image and reapplied, Kubernetes performs a rolling update to gradually replace pods with the new image, ensuring zero downtime if configured correctly.

Answer

kubectl update deployment myapp --image=nginx:1.20

Answer

kubectl rollout image deployment myapp nginx:1.20

Question 9

You have a Deployment named 'web-app' with 5 replicas. You run the command: kubectl set image deployment/web-app web-app=nginx:1.25. Which command can you use to monitor the progress of the rollout?

Accepted Answer

kubectl rollout status deployment/web-app. `kubectl rollout status deployment/web-app` is the dedicated command to monitor the progress of a rollout, providing real-time updates on whether the rollout is succeeding, pending, or failed. It watches the deployment's status conditions and reports when the new ReplicaSet has fully replaced the old one, making it the precise tool for tracking the progress of the `kubectl set image` change.

Answer

kubectl describe deployment/web-app

Answer

kubectl rollout history deployment/web-app

Answer

kubectl get events --watch

Question 10

You are performing a rolling update of a Deployment. You set maxSurge=2 and maxUnavailable=1. The Deployment has 5 replicas. During the update, how many pods can be running simultaneously?

Accepted Answer

7. During a rolling update, maxSurge=2 allows up to 2 extra pods beyond the desired replicas, and maxUnavailable=1 allows at most 1 pod to be unavailable. With a desired count of 5, the maximum running pods is 5 (desired) + 2 (surge) = 7, because the surge pods are created before old ones are terminated, and the unavailable limit does not cap the total running count.

Answer

6

Answer

10

Answer

5

Question 11

You have a Helm chart for an application. After running 'helm install my-release ./mychart', you realize you forgot to set a required value. Which command can you use to update the release with the correct value while keeping the same chart version?

Accepted Answer

helm upgrade my-release ./mychart --set key=value. Helm upgrade modifies a release with new values or chart changes. The --set flag overrides values inline.

Answer

kubectl edit deployment my-release

Answer

helm install my-release ./mychart --set key=value

Answer

helm rollback my-release 1

Question 12

You want to perform a blue-green deployment using Deployments and Services. You have two Deployments: 'app-blue' (current) and 'app-green' (new). The Service 'app-service' currently selects pods with label 'version: blue'. What kubectl command should you run to switch traffic to the green deployment?

Accepted Answer

kubectl patch service app-service -p '{"spec":{"selector":{"version":"green"}}}'. A Kubernetes Service routes traffic based on its label selector, so blue-green switching is achieved by changing the Service's selector to point at the new pods. The kubectl patch command with a strategic merge patch on spec.selector updates the selector in place, instantly redirecting traffic to pods labeled version: green without recreating the Service or changing its ClusterIP. This is the canonical, non-disruptive way to flip traffic between blue and green Deployments.

Answer

kubectl delete service app-service --ignore-not-found && kubectl create service app-service --selector version=green

Answer

kubectl set selector service/app-service version=green

Answer

kubectl apply -f service.yaml where service.yaml has the new selector

Question 13

You have a Deployment with strategy type: Recreate. You update the container image. What behavior will occur during the update?

Accepted Answer

Old pods are terminated, then new pods are created.. With the Recreate strategy, the Deployment controller first scales down all existing pods to zero, ensuring they are fully terminated, and then creates new pods with the updated container image. This behavior guarantees that only one version of the application runs at any time, avoiding concurrent old and new pod execution.

Answer

The update is performed in-place without pod termination.

Answer

New pods are created before old ones are terminated.

Answer

The deployment is paused automatically.

Question 14

You have a HorizontalPodAutoscaler (HPA) that targets CPU utilization at 50%. The current average CPU utilization is 80%. The HPA has a stabilization window of 300 seconds and a scale-down policy with a periodSeconds of 60. CPU utilization drops to 40%. How long will it take for the HPA to begin scaling down?

Accepted Answer

After 300 seconds. The HPA will begin scaling down after 300 seconds because the stabilization window for scale-down is set to 300 seconds. During this window, the HPA evaluates all recommended replica counts and selects the highest one, effectively delaying any scale-down action until the window expires. Even though CPU dropped to 40% (below the 50% target), the stabilization window prevents premature scale-down.

Answer

Immediately

Answer

After 60 seconds

Answer

After 360 seconds

Question 15

You are using Kustomize. Your kustomization.yaml file specifies a base and an overlay. You run: kubectl apply -k overlays/production. What happens?

Accepted Answer

It applies the merged result of base and overlay.. When you run `kubectl apply -k overlays/production`, Kustomize reads the `kustomization.yaml` in the specified directory, which references a base and an overlay. It then performs a strategic merge patch of the overlay's customizations (e.g., patches, namePrefix, commonLabels) onto the base resources, producing a single set of manifests that are applied to the cluster. This is the core purpose of Kustomize: to compose and customize resources without templating.

Answer

It errors because -k expects a directory with kustomization.yaml.

Answer

It applies the base resources only.

Answer

It applies the overlay resources only.