CKAD Application Deployment Practice Test 7 — 15 Questions

Question 1

Which of the following are valid kubectl commands for managing rollouts? (Select all that apply)

Accepted Answer

kubectl rollout status deployment/myapp. The valid kubectl rollout subcommands among the options are A (kubectl rollout status), C (kubectl rollout history), D (kubectl rollout restart), and E (kubectl rollout pause). Option B (kubectl rollout diff) is not a valid subcommand. All of these are valid commands for managing rollouts.

Answer

kubectl rollout diff deployment/myapp

Question 2

When performing a rolling update of a Deployment with 'maxSurge: 1' and 'maxUnavailable: 0', how many additional pods can be created above the desired replicas during the update?

Accepted Answer

1. maxSurge defines the maximum number of pods that can be created above the desired replicas. With maxSurge=1, exactly one extra pod can exist during the update.

Answer

0

Answer

Unlimited

Answer

100%

Question 3

You want to update a Deployment's image from nginx:1.20 to nginx:1.21. Which command will perform a rolling update?

Accepted Answer

kubectl set image deployment/my-deployment nginx=nginx:1.21. `kubectl set image` directly updates the container image of a Deployment, which triggers a rolling update by default. The Deployment controller creates a new ReplicaSet with the updated image and gradually scales it up while scaling down the old ReplicaSet, ensuring zero downtime.

Answer

kubectl create deployment my-deployment --image=nginx:1.21

Answer

kubectl apply -f deployment.yaml

Answer

kubectl edit deployment my-deployment

Question 4

A Deployment named 'web' has replicas: 3 and update strategy type: Recreate. You run 'kubectl set image deployment/web web=nginx:1.22'. What immediate effect will this have on the existing pods?

Accepted Answer

All existing pods are terminated simultaneously, then new pods are created.. The Deployment's update strategy type is set to 'Recreate', which means all existing pods are terminated simultaneously before any new pods are created. When you run 'kubectl set image deployment/web web=nginx:1.22', it triggers a rollout that follows the Recreate strategy: first, all current pods are deleted, then the new pods are created with the updated image. This is in contrast to the RollingUpdate strategy, which updates pods gradually.

Answer

One pod is terminated, then a new pod is created, repeating until all are updated.

Answer

The command fails because Recreate does not support image updates.

Answer

The pods are updated in place without termination.

Question 5

Which Helm command installs a chart from a repository?

Accepted Answer

helm install . The correct command to deploy a chart from a repository is `helm install `. This command tells Helm to create a release (a running instance of a chart) using the specified chart name or chart reference, which can be a chart from a configured repository, a local path, or a packaged chart archive.

Answer

helm deploy

Answer

helm create

Answer

helm run <release-name> <chart>

Question 6

You have a Helm release named 'my-app' that you want to revert to revision 3. Which command accomplishes this?

Accepted Answer

helm rollback my-app 3. The correct command to revert a Helm release to a previous revision is `helm rollback `. In this case, `helm rollback my-app 3` will roll back the 'my-app' release to revision 3, restoring the Kubernetes resources to the state defined in that revision's chart and values.

Answer

helm undo my-app --revision 3

Answer

helm revert my-app 3

Answer

helm upgrade my-app --revision 3

Question 7

Which kubectl command can you use to pause a rolling update of a Deployment?

Accepted Answer

kubectl rollout pause deployment/my-deployment. The correct command to pause a rolling update of a Deployment is `kubectl rollout pause deployment/my-deployment`. This command temporarily halts the rollout process, allowing you to make changes or investigate issues without triggering a new revision. The `kubectl rollout` subcommand is specifically designed for managing Deployment rollouts, and `pause` is the correct verb to suspend the update.

Answer

kubectl rollout suspend deployment/my-deployment

Answer

kubectl rollout stop deployment/my-deployment

Answer

kubectl rollout halt deployment/my-deployment

Question 8

What is the purpose of the 'kubectl rollout status' command?

Accepted Answer

To check the current status of a rollout. The command 'kubectl rollout status' tracks the progress of a rollout until it completes or fails.

Answer

To roll back a deployment

Answer

To view the rollout history

Answer

To pause a rollout

Question 9

You have a Deployment with replicas: 5 and update strategy type: RollingUpdate with maxSurge: 25% and maxUnavailable: 25%. During a rolling update, what is the maximum number of pods that can be unavailable at any given time?

Accepted Answer

1. With maxUnavailable: 25% on a Deployment of 5 replicas, the maximum number of unavailable pods is 25% of 5 = 1.25, and Kubernetes rounds down for maxUnavailable, resulting in 1. Therefore, at most 1 pod can be unavailable at any given time during the rolling update.

Answer

2

Answer

5

Answer

0

Question 10

Which of the following is a correct Kustomize kustomization.yaml configuration for setting an image tag to 'v2'?

Accepted Answer

images:
- name: my-app
  newTag: v2. In Kustomize, the `images` field in `kustomization.yaml` uses the `newTag` key to override the tag of an existing container image. This allows you to change the image tag to 'v2' without modifying the original YAML manifests, aligning with Kustomize's declarative patching approach.

Answer

images:
- name: my-app
  newName: v2

Answer

patches:
- target:
    kind: Deployment
  patch: |-
    - op: replace
      path: /spec/template/spec/containers/0/image
      value: my-app:v2

Answer

imageTag:
- name: my-app
  tag: v2

Question 11

Which command scales a Deployment named 'web' to 5 replicas?

Accepted Answer

kubectl scale deployment web --replicas=5. The correct command to scale a Deployment to a specific number of replicas is `kubectl scale deployment web --replicas=5`. This command directly modifies the `spec.replicas` field of the Deployment object, instructing the Kubernetes controller manager to adjust the number of running Pods to match the desired count.

Answer

kubectl set replicas deployment web 5

Answer

kubectl resize deployment web --replicas=5

Answer

kubectl autoscale deployment web --replicas=5

Question 12

You have an HPA that scales a Deployment based on CPU utilization. You want to prevent the Deployment from scaling down for at least 5 minutes. Which HPA behavior field should you configure?

Accepted Answer

behavior.scaleDown.stabilizationWindowSeconds. To prevent scaling down, you can set a stabilization window on the scaleDown policy. Option B correctly sets a stabilizationWindowSeconds in the scaleDown behavior.

Answer

behavior.scaleUp.policies[0].periodSeconds

Answer

behavior.scaleUp.stabilizationWindowSeconds

Answer

behavior.scaleDown.policies[0].periodSeconds

Question 13

Which TWO of the following are valid methods to perform a blue-green deployment in Kubernetes?

Accepted Answer

Create a new Deployment for the new version, then update the Service's selector to point to the new pods.. A blue-green deployment requires two separate environments (blue = current, green = new) and a mechanism to switch traffic between them. Option B is valid because it uses a new Deployment for the green version and updates the Service selector to point to the new pods, effectively switching traffic. Option C is also valid: it deploys the new version in a separate namespace and uses a Service to route traffic to the new namespace, achieving the same isolation and switch. Option A is incorrect because it modifies the existing Deployment's image and uses Recreate strategy, which is a single-version update with downtime, not a blue-green switch. Option D is incorrect because `kubectl rollout undo` reverts to a previous revision of the same Deployment, not a parallel green environment. Option E uses the RollingUpdate strategy with extreme surge, which is a rolling update, not a blue-green deployment.

Answer

Use kubectl patch to modify the Deployment's image and rely on the Recreate strategy.

Answer

Use kubectl rollout undo to revert to the previous version.

Answer

Use the RollingUpdate strategy with maxSurge=100% and maxUnavailable=0%.

Question 14

Which THREE of the following are valid fields in a Helm chart's values.yaml file that can be used in templates?

Accepted Answer

replicaCount: 3. `replicaCount: 3` is a standard top-level key in a Helm chart's `values.yaml` file. This file contains plain YAML key-value pairs that are injected into templates via the `.Values` object (e.g., `{{ .Values.replicaCount }}`). It is not a template directive itself, but a data source for templates.

Answer

Answer

Question 15

Which TWO of the following commands are used to inspect the rollout history of a Deployment?

Accepted Answer

kubectl rollout history deployment/my-deployment. The correct commands to inspect rollout history are 'kubectl rollout history deployment/' (option B) and 'kubectl get replicasets -l app=' (option C). 'kubectl rollout history' directly shows the revision history of a deployment, while 'kubectl get replicasets' indirectly shows the ReplicaSets created for each revision, which correspond to the rollout history. 'kubectl rollout status' (option A) shows current rollout progress, not history. 'kubectl get events' (option D) shows events, not history. 'kubectl describe deployment' (option E) shows some details but not the complete history of revisions.

Answer

kubectl rollout status deployment/my-deployment

Answer

kubectl get events --field-selector involvedObject.name=my-deployment

Answer

kubectl describe deployment my-deployment