CKAD Application Deployment Practice Test 4 — 15 Questions

Question 1

You want to scale a Deployment named 'frontend' to 5 replicas. Which command should you use?

Accepted Answer

kubectl scale deployment frontend --replicas=5. `kubectl scale` is the dedicated Kubernetes command to adjust the number of replicas for a Deployment (or other scalable resources). The syntax `kubectl scale deployment frontend --replicas=5` directly instructs the API server to update the Deployment's `spec.replicas` field to 5, triggering the ReplicaSet controller to create or remove Pods to match the desired count.

Answer

kubectl set replicas deployment frontend=5

Answer

kubectl update deployment frontend --replicas=5

Answer

kubectl scale --replicas=5 frontend

Question 2

Which field in a Deployment's rolling update strategy controls the maximum number of pods that can be created above the desired replicas during a rolling update?

Accepted Answer

maxSurge. In a Deployment's rolling update strategy, `maxSurge` controls the maximum number of pods that can be created above the desired replica count during the update. This allows the system to spin up new pods before terminating old ones, ensuring zero downtime. The value can be an absolute number or a percentage of the desired replicas.

Answer

maxUnavailable

Answer

revisionHistoryLimit

Answer

minReadySeconds

Question 3

You have a Deployment that uses the 'Recreate' strategy. What happens when you update the pod template (e.g., change the image)?

Accepted Answer

All existing pods are terminated before new pods are created. The 'Recreate' strategy in a Kubernetes Deployment terminates all existing pods before creating new ones when the pod template is updated. This ensures zero overlapping pods during the update, which is useful for applications that cannot handle multiple versions running simultaneously.

Answer

The update is not allowed; you must delete the Deployment first

Answer

New pods are created gradually while old pods are terminated

Answer

Pods are updated in-place without restart

Question 4

You want to use Kustomize to apply a patch that adds a sidecar container to all pods in a Deployment. Which Kustomize feature should you use?

Accepted Answer

patchesStrategicMerge. `patchesStrategicMerge`, is correct because it allows you to apply a strategic merge patch to a Kubernetes resource, such as adding a sidecar container to all pods in a Deployment. This feature merges the patch into the base resource definition, enabling modifications like appending containers to the pod spec without overwriting the entire resource.

Answer

namePrefix

Answer

replicas

Answer

images

Question 5

Which command lists all Helm releases in the current namespace?

Accepted Answer

helm list. The `helm list` command is the correct way to list all Helm releases in the current namespace. It queries the Helm release storage (typically Secrets in the cluster) and returns the release names, status, chart versions, and other metadata for the namespace set in the current kubeconfig context.

Answer

helm get all

Answer

helm status

Answer

helm show

Question 6

You have created a HorizontalPodAutoscaler (HPA) for a Deployment. The HPA is configured with targetCPUUtilizationPercentage: 50. The current CPU utilization is 80%. What will the HPA do?

Accepted Answer

It will increase the number of replicas. The HPA will increase the number of replicas to bring average CPU utilization down to the target.

Answer

It will restart the pods

Answer

It will do nothing because HPA only scales based on memory

Answer

It will decrease the number of replicas

Question 7

You want to perform a rolling update of a Deployment. The Deployment has a maxSurge=1 and maxUnavailable=0. How many extra pods can be created above the desired count during the update?

Accepted Answer

1. In a rolling update with `maxSurge=1` and `maxUnavailable=0`, Kubernetes ensures that at most one extra pod can be created above the desired replica count during the update. This is controlled by the `maxSurge` field, which defines the maximum number of pods that can be created over the desired number, and here it is set to 1 (either an absolute number or a percentage, defaulting to 25%). Since `maxUnavailable=0`, no pods can be taken down before new ones are ready, so the surge allows exactly one additional pod to be created temporarily.

Answer

Unlimited

Answer

0

Answer

Desired replicas

Question 8

Which TWO of the following are correct ways to pause a rollout of a Deployment named 'myapp'? (Select TWO)

Accepted Answer

kubectl rollout pause deployment/myapp. `kubectl rollout pause deployment/myapp` is the dedicated command to pause a rollout. Option C is also correct because the Deployment spec includes a `paused` field; setting `spec.paused: true` via `kubectl edit` or `kubectl patch` achieves the same effect. Option B (`kubectl rollout undo`) rolls back a rollout, not pauses it. Option D (`kubectl rollout resume`) resumes a paused rollout. Option E triggers a new rollout with `set image` before pausing, which does not simply pause the current rollout.

Answer

kubectl rollout undo deployment/myapp

Answer

kubectl rollout resume deployment/myapp

Answer

kubectl set image deployment/myapp app=nginx && kubectl rollout pause deployment/myapp

Question 9

Which THREE of the following are valid Kustomize features? (Select THREE)

Accepted Answer

resources. `resources` is a core Kustomize field used to list the YAML files (or directories) that form the base set of Kubernetes resources to be customized. Without `resources`, Kustomize has no manifests to process, making it essential for defining the input to the kustomization build.

Answer

serviceAccount

Answer

ingress

Question 10

You have a Deployment named 'web-app' with 5 replicas. You run 'kubectl set image deployment/web-app app=nginx:1.21'. What is the effect of this command?

Accepted Answer

It updates the image of the container named 'app' to nginx:1.21, triggering a rolling update.. The `kubectl set image` command updates the container image in the Deployment's pod template. This triggers a rolling update, where the Deployment's ReplicaSet creates new pods with the new image and gradually terminates old pods, ensuring zero downtime. The container name 'app' matches the container in the pod spec, so the image is updated to nginx:1.21.

Answer

It scales the Deployment to 0 replicas and then scales back up.

Answer

It immediately terminates all running pods and creates new ones with the new image.

Answer

It creates a new Deployment with the updated image.

Question 11

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

Accepted Answer

kubectl rollout history deployment app. `kubectl rollout history deployment app` is the specific command designed to display the revision history of a Deployment, including revision numbers and, if configured, the change-cause annotation. This command retrieves the stored rollout history from the Deployment's annotation `deployment.kubernetes.io/revision` and lists all previous ReplicaSets that were created during rollouts.

Answer

kubectl rollout status deployment app

Answer

kubectl describe deployment app

Answer

kubectl get events --field-selector involvedObject.kind=Deployment

Question 12

You have a Helm chart for an application. You want to upgrade the release but only if the upgrade does not introduce breaking changes. Which command should you use?

Accepted Answer

helm upgrade --dry-run my-release ./mychart. `helm upgrade --dry-run` simulates the upgrade process and validates the chart against the cluster without actually applying changes. The `--dry-run` flag allows you to detect breaking changes (e.g., missing required values, API deprecations, or incompatible resource definitions) before committing to the upgrade, ensuring the release remains stable.

Answer

helm install --dry-run my-release ./mychart

Answer

helm rollback my-release 0

Answer

helm diff upgrade my-release ./mychart

Question 13

A Deployment has a rolling update strategy with maxSurge: 1 and maxUnavailable: 0. The Deployment has 4 replicas. During a rollout, what is the maximum number of pods that can exist at any point?

Accepted Answer

5. With maxSurge: 1 and maxUnavailable: 0, the Deployment controller ensures that during a rolling update, at most one additional pod (beyond the desired 4 replicas) is created before terminating old pods. Since no pods can be unavailable, the maximum number of pods at any point is 4 (desired) + 1 (surge) = 5.

Answer

6

Answer

8

Answer

4

Question 14

You need to scale a Deployment named 'frontend' to 10 replicas. Which command correctly accomplishes this?

Accepted Answer

kubectl scale deployment/frontend --replicas=10. It uses the standard imperative syntax 'kubectl scale / --replicas=N' with the resource specified as 'deployment/frontend' and the flag after the resource. Option D places the flag before the resource and uses space-separated type and name, which is not the expected form in the CKAD exam, making it incorrect despite being functionally valid in some kubectl versions.

Answer

kubectl patch deployment frontend -p '{"spec":{"replicas":10}}'

Answer

kubectl set replicas deployment/frontend 10

Answer

kubectl scale --replicas=10 deployment frontend

Question 15

Which of the following is a valid method to perform a blue-green deployment in Kubernetes?

Accepted Answer

Create two Deployments and a Service, then change the Service's selector to point to the new version.. A blue-green deployment in Kubernetes is achieved by running two separate Deployments (blue and green) and using a Service to route traffic to the active version. By updating the Service's selector to match the labels of the new Deployment (green), traffic is instantly switched without downtime. This method does not rely on any built-in Deployment strategy, as Kubernetes does not have a native 'BlueGreen' strategy type.

Answer

Use kubectl rollout undo to switch between revisions.

Answer

Set spec.strategy.type: BlueGreen in the Deployment.

Answer

Use a DaemonSet to run both versions.