CKAD Application Deployment Practice Test 10 — 15 Questions

Question 1

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?

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

Accepted Answer

Between 5 and 6. With maxUnavailable=0, no pods can be unavailable during the update. With maxSurge=1, one extra pod can be created above the desired 5, so total running pods can be 6. The new pod is created first, then the old pod is terminated, ensuring 5 pods are always available.

Answer

Between 4 and 5

Answer

Between 5 and 10

Answer

Exactly 5

Question 2

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 3

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 4

A canary deployment is being implemented using two Deployments (stable and canary) and a Service. The Service's label selector has two entries: 'app: myapp' and 'version: stable'. Initially, the canary Deployment's pods have label 'version: canary'. To route a small percentage of traffic to the canary, what should you do?

Accepted Answer

Change the canary Deployment's pod template labels to also include 'version: stable' so that the Service selects them. A Service selector matches pods based on AND logic for the specified key-value pairs. Since the Service requires 'version: stable', canary pods with 'version: canary' do not match. You cannot add a second 'version' label because label keys must be unique within a pod. Therefore, Option B is invalid. A proper canary setup would use a selector with a shared label (e.g., just 'app: myapp') and control traffic via replica counts.

Answer

Update the Service's selector to include both 'version: stable' and 'version: canary'

Answer

Use a NetworkPolicy to allow traffic to the canary

Answer

Create a new Service that points to both Deployments

Question 5

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 6

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 7

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 8

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. In Helm, to upgrade an existing release with new values, you use 'helm upgrade' with the release name and chart. You can pass new values via --set or --values.

Answer

helm update myapp ./mychart

Answer

helm install myapp ./mychart --replace

Answer

kubectl edit deployment myapp

Question 9

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 10

You are using Kustomize with the following structure: a base with a Deployment YAML, and an overlay that patches the image tag. The overlay's kustomization.yaml contains: 'patches: - target: kind: Deployment, name: myapp, patch: |- ...'. After running 'kubectl apply -k ./overlay', the Deployment is created but the image tag is not updated. What is the most likely cause?

Accepted Answer

The base Deployment has a different name than 'myapp'. The most common issue is that the patch is not matching the Deployment's name or kind correctly. The target's name must match exactly, or the patch may not be applied. Also, the patch format (strategic merge or JSON patch) must be correct. But the most likely cause is that the patch is not being applied because the patch target does not match the resource.

Answer

The image tag is defined in the base and cannot be overridden

Answer

You need to run 'kustomize build' first

Answer

The overlay is not referencing the base correctly

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. Both 'kubectl replace -f deployment.yaml' (where the YAML includes the updated image) and 'kubectl set image deployment/myapp mycontainer=nginx:1.21' are valid non-interactive methods to update a Deployment's image. 'kubectl edit' is interactive and not considered a direct command-line method for batch operations or automation, so it is not a valid answer here.

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