CKAD Application Deployment Practice Test 12 — 15 Questions

Question 1

Which kubectl command is used to view the rollout status of a Deployment?

Accepted Answer

kubectl rollout status deployment mydeployment. The 'kubectl rollout status' command is specifically designed to show the status of a rollout for a Deployment, DaemonSet, or StatefulSet.

Answer

kubectl status deployment mydeployment

Answer

kubectl get rollout deployment mydeployment

Answer

kubectl describe rollout mydeployment

Question 2

A Deployment named 'app' has the following strategy: type: RollingUpdate with maxSurge=1 and maxUnavailable=0. You have 5 replicas. During a rolling update, how many pods will be running at any given time?

Accepted Answer

Between 5 and 6. With maxSurge=1 and maxUnavailable=0 on a 5-replica Deployment, Kubernetes must keep all 5 original pods available at all times while it may temporarily add 1 extra pod above the desired count. Therefore the total number of running pods ranges from 5 (when no surge pod exists yet) up to 6 (when one surge pod is created before an old one is terminated). The rollout proceeds by creating one new pod, waiting for it to become Ready, then terminating one old pod, keeping the count between 5 and 6.

Answer

Between 4 and 5

Answer

Between 5 and 10

Answer

Exactly 5

Question 3

You need to perform a blue-green deployment using Deployments and Services. What is the most common approach to switch traffic from the old version (blue) to the new version (green)?

Accepted Answer

Change the Service's label selector to point to the green Deployment's pod labels. In a blue-green deployment, the Service acts as the traffic router by using a label selector to match pods. By updating the Service's selector to match the green Deployment's pod labels (e.g., `version: green`), traffic is instantly switched from blue pods to green pods without any downtime, as Kubernetes Services use label selectors to dynamically route traffic to matching pods.

Answer

Update the Deployment's image field in the blue Deployment to the new version

Answer

Delete the blue Deployment and create the green Deployment

Answer

Scale the blue Deployment to 0 and the green Deployment to desired replicas

Question 4

What is the purpose of a HorizontalPodAutoscaler (HPA)?

Accepted Answer

To automatically adjust the number of pods based on resource metrics. A HorizontalPodAutoscaler automatically scales the number of pods in a Deployment, ReplicaSet, or StatefulSet based on observed CPU utilization (or other custom metrics).

Answer

To update the application version without downtime

Answer

To restart pods automatically when they fail

Answer

To distribute incoming traffic across multiple pods

Question 5

You run 'kubectl rollout undo deployment/app'. What happens?

Accepted Answer

It rolls back the Deployment to the previous revision. The 'kubectl rollout undo' command rolls back a Deployment to the previous revision. By default, it reverts to the immediate prior revision (revision 1 less than current).

Answer

It pauses the rollout

Answer

It shows the rollout history

Answer

It deletes the Deployment

Question 6

Which command is used to scale a Deployment named 'web' to 5 replicas?

Accepted Answer

kubectl scale deployment web --replicas=5. `kubectl scale deployment web --replicas=5` directly updates the `spec.replicas` field of the Deployment to 5, instructing the ReplicaSet controller to adjust the number of Pods to match the desired count. This is the standard imperative command for scaling workloads in Kubernetes.

Answer

kubectl autoscale deployment web --min=5 --max=5

Answer

kubectl set replicas deployment/web 5

Answer

kubectl edit deployment web --replicas=5

Question 7

A Deployment is configured with strategy type 'Recreate'. What happens during an update to the pod template?

Accepted Answer

Old pods are terminated and then new pods are created. The Recreate strategy first terminates all existing pods, then creates new pods. This ensures that only one version is running at a time, but causes downtime.

Answer

New pods are created before old ones are terminated

Answer

Pods are updated in place

Answer

The update is paused until manual approval

Question 8

You have a Deployment with 3 replicas. You run 'kubectl rollout pause deployment/app'. Which command would you use to resume the rollout?

Accepted Answer

kubectl rollout resume deployment/app. `kubectl rollout resume deployment/app` is the specific command to resume a paused rollout, allowing the Deployment controller to continue processing updates to the Pod template. When a rollout is paused with `kubectl rollout pause`, the controller stops applying changes to the ReplicaSet; `resume` re-enables that reconciliation loop.

Answer

kubectl rollout continue deployment/app

Answer

kubectl rollout undo deployment/app

Answer

kubectl rollout restart deployment/app

Question 9

You are using Helm to manage an application. After running 'helm install myapp ./mychart', you notice that the application is running but you need to change a configuration value. Which command should you use to update the release?

Accepted Answer

helm upgrade myapp ./mychart --set key=value. 'helm upgrade' is the correct command to update an existing release with new chart values or a new chart version. Passing '--set key=value' overrides a specific value at upgrade time, and Helm computes a diff against the previous release, applying only the necessary Kubernetes changes. 'helm install' is only for creating new releases.

Answer

helm update myapp ./mychart

Answer

helm install myapp ./mychart --replace

Answer

kubectl edit deployment myapp

Question 10

What is the difference between 'kubectl apply' and 'kubectl create'?

Accepted Answer

'kubectl apply' can be used to create and update resources; 'kubectl create' only creates new resources. 'kubectl apply' is declarative: it creates or updates a resource to match the provided configuration. 'kubectl create' is imperative: it creates a new resource and will fail if the resource already exists.

Answer

'kubectl apply' only works with Deployments, while 'kubectl create' works with all resources

Answer

'kubectl apply' is for creating resources, 'kubectl create' is for updating

Answer

There is no difference

Question 11

Which TWO commands can be used to view the rollout history of a Deployment?

Accepted Answer

kubectl describe deployment mydeployment. `kubectl describe deployment mydeployment` includes the rollout history in its output, showing revision numbers and timestamps of changes. Option E is correct because `kubectl rollout history deployment/mydeployment` is the dedicated command to display the rollout history, listing revisions and associated change causes.

Answer

kubectl get deployment mydeployment

Answer

kubectl rollout status deployment/mydeployment

Answer

kubectl logs deployment/mydeployment

Question 12

Which FOUR of the following are valid fields in a HorizontalPodAutoscaler (HPA) v2 specification?

Accepted Answer

spec.metrics. In HPA v2 (autoscaling/v2), the spec includes 'metrics', 'behavior', 'minReplicas', and 'maxReplicas'. All four of these fields are valid in the v2 specification. 'targetCPUUtilizationPercentage' is a deprecated field from v1 and is not part of the v2 spec. Therefore, options B, C, D, and E are correct.

Answer

spec.targetCPUUtilizationPercentage

Question 13

Which TWO of the following are valid non-interactive methods to update a Deployment's image?

Accepted Answer

kubectl replace -f deployment.yaml. Option A (kubectl replace -f deployment.yaml) is correct because replace applies a full manifest non-interactively, so if the YAML file already contains the updated image, the Deployment's Pod template is replaced and a rollout is triggered without opening an editor. Option D (kubectl set image deployment/myapp mycontainer=nginx:1.21) is correct because kubectl set image is a purpose-built, non-interactive command that directly patches the named container's image in the Deployment spec, causing a new ReplicaSet rollout. Option B is not valid here because kubectl edit opens an interactive text editor, which contradicts the non-interactive requirement. Option C is not valid because kubectl rollout does not have an 'image' subcommand; the correct subcommands are status, history, undo, restart, pause, and resume. Option E is not valid because kubectl create fails when the Deployment already exists and is not an update method.

Answer

kubectl edit deployment/myapp and change the image field

Answer

kubectl rollout image deployment/myapp mycontainer=nginx:1.21

Answer

kubectl create -f deployment.yaml

Question 14

Which kubectl command sets the number of replicas for a deployment named 'nginx' to 5?

Accepted Answer

kubectl scale deployment nginx --replicas=5. kubectl scale is the correct command to change the replica count of a deployment.

Answer

kubectl update deployment nginx --replicas=5

Answer

kubectl set scale deployment nginx --replicas=5

Answer

kubectl resize deployment nginx --replicas=5

Question 15

When performing a rolling update of a Deployment, which field in the Deployment spec controls the maximum number of Pods that can be created above the desired replicas during the update?

Accepted Answer

spec.strategy.rollingUpdate.maxSurge. maxSurge defines how many Pods can be created above the desired replica count during a rolling update.

Answer

spec.strategy.type

Answer

spec.strategy.rollingUpdate.maxUnavailable

Answer

spec.replicas