CKAD Application Deployment Practice Test 13 — 15 Questions

Question 1

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. The kubectl rollout status command tracks the progress of a deployment rollout.

Answer

kubectl describe deployment/web-app

Answer

kubectl rollout history deployment/web-app

Answer

kubectl get events --watch

Question 2

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. With maxSurge=2, up to 2 extra pods can be created above the desired 5. With maxUnavailable=1, at most 1 pod can be unavailable. So the total running can be up to 5 + 2 = 7.

Answer

6

Answer

10

Answer

5

Question 3

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 4

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"}}}'. To switch traffic, update the Service's selector to point to the green deployment's pods, which have label 'version: green'. kubectl patch is a direct way to update the selector.

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 5

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.. Recreate strategy first scales down all existing pods, then scales up new ones. This causes a brief downtime.

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 6

Which command is used to scale a Deployment named 'frontend' to 10 replicas?

Accepted Answer

kubectl scale deployment/frontend --replicas=10. kubectl scale can change the replica count of a Deployment.

Answer

kubectl scale deploy frontend --replicas 10

Answer

kubectl set replicas deployment/frontend 10

Answer

kubectl edit deployment frontend and change replicas to 10

Question 7

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 stabilization window is the time the HPA waits before considering a scale-down decision. It will wait 300 seconds after the utilization drops below the target.

Answer

Immediately

Answer

After 60 seconds

Answer

After 360 seconds

Question 8

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.. Option C is correct because 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.

Question 9

You want to perform a canary deployment. You have a Deployment 'app-v1' with 10 replicas. You create a new Deployment 'app-v2' with 1 replica. Both have the label 'app: myapp'. The Service 'myapp-svc' uses selector 'app: myapp'. How do you gradually increase traffic to v2?

Accepted Answer

Gradually increase the replicas of app-v2 and decrease those of app-v1.. By increasing the number of replicas in the v2 Deployment, more pods will be available to receive traffic from the Service, as both versions share the same label.

Answer

Create a second Service for v2 and use DNS weighting.

Answer

Update the Service selector to include version labels.

Answer

Use 'kubectl set image' on the existing Deployment.

Question 10

You have a Deployment that is failing after a rollout. You want to revert to the previous revision. Which command accomplishes this?

Accepted Answer

kubectl rollout undo deployment/myapp. kubectl rollout undo reverts to the previous revision by default.

Answer

kubectl rollout history deployment/myapp --revision=previous

Answer

kubectl rollout resume deployment/myapp

Answer

kubectl delete deployment/myapp --cascade=orphan && kubectl apply -f old-deployment.yaml

Question 11

In a Deployment, what is the purpose of the 'maxUnavailable' field in the rolling update strategy?

Accepted Answer

The maximum number of pods that can be unavailable during the update.. In a Deployment's rolling update strategy, the 'maxUnavailable' field specifies the maximum number of Pods that can be unavailable during the update process. This ensures that the Deployment maintains a certain level of availability by controlling how many Pods can be taken down at any given time, relative to the desired replica count. It is defined as either an absolute number or a percentage of the desired Pods, and it works alongside 'maxSurge' to manage the update's pace and safety.

Answer

The maximum number of pods that can be terminated at once.

Answer

The maximum time allowed for the rollout to complete.

Answer

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

Question 12

Which TWO statements are true about Helm releases? (Select two)

Accepted Answer

Helm stores release information in the same namespace as the chart's resources.. Helm releases are tracked in the cluster, and each install creates a new release.

Answer

Helm automatically deletes the previous release when upgrading.

Answer

Helm rollback only works if the current release was created with Helm.

Answer

A Helm release is immutable once installed.

Answer

Helm rollback only works on the most recent release revision.

Question 13

Which THREE are valid ways to expose a canary deployment for testing? (Select three)

Accepted Answer

Create a separate Service for the canary with a different selector and provide its endpoint to testers.. Canary deployments can be exposed via different Services, ingress routing, or mesh traffic splitting. Using a single Service with same labels also works but gives proportional traffic.

Answer

Use a DaemonSet instead of Deployment for canary.

Answer

Use a NetworkPolicy to restrict canary pods from receiving traffic.

Question 14

Which TWO statements about kubectl apply vs kubectl create are correct? (Select two)

Accepted Answer

kubectl apply can update existing resources; kubectl create cannot.. kubectl apply manages resources declaratively using last-applied-configuration. kubectl create is imperative and will error if resource exists.

Answer

Both commands support the --dry-run=client flag.

Answer

Both commands require a full YAML manifest file.

Answer

kubectl create is the recommended way to manage production resources.

Answer

Both commands can only be used to create resources, not update.

Question 15

Which TWO are valid reasons to use a HorizontalPodAutoscaler (HPA) with a custom metric? (Select two)

Accepted Answer

To scale based on the length of a message queue.. HPA can scale based on custom metrics like requests per second or queue length, not just CPU/memory.

Answer

To scale based on the number of pods in a different Deployment.

Answer

To scale based on disk I/O utilization.

Answer

To scale based on the node's CPU temperature.