CKAD Application Deployment Practice Test 5 — 15 Questions

Question 1

You have a Deployment with the following strategy: rollingUpdate: maxSurge: 25%, maxUnavailable: 25%. The Deployment has 4 replicas. During an update, what is the minimum number of pods guaranteed to be available?

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

Accepted Answer

3. With 4 replicas and a rolling update strategy of maxSurge: 25% and maxUnavailable: 25%, the maximum number of pods that can be unavailable during the update is 25% of 4, which is 1. Therefore, the minimum number of pods guaranteed to be available is 4 - 1 = 3. This is calculated by rounding down the maxUnavailable value (1) and ensuring the desired replica count minus unavailable pods equals the minimum available.

Answer

2

Answer

4

Answer

1

Question 2

What is the purpose of the 'values.yaml' file in a Helm chart?

Accepted Answer

It contains default configuration values for the chart.. The `values.yaml` file in a Helm chart provides default configuration values that can be overridden at install or upgrade time using the `--values` or `--set` flags. These values are injected into the chart's templates via Go template syntax, enabling parameterized deployments without modifying the chart itself.

Answer

It stores the release history.

Answer

It defines the Kubernetes resources to be created.

Answer

It lists dependencies of the chart.

Question 3

Which commands list all Helm releases in the current namespace? (Select all that apply)

Accepted Answer

helm list. Both `helm list` and its alias `helm ls` are valid commands to list all Helm releases in the current namespace. `helm get all` retrieves all information about a specific release, and `helm status` shows the status of a single release.

Answer

helm get all

Answer

helm status

Question 4

You want to undo a rollout to the previous revision. Which command should you use?

Accepted Answer

kubectl rollout undo deployment/myapp. `kubectl rollout undo deployment/myapp` reverts the deployment to the previous revision by default, using the rollout history stored in the deployment's ReplicaSet annotations. This command directly triggers a new rollout that matches the pod template of the prior revision, effectively undoing the last change.

Answer

kubectl delete deployment/myapp --cascade=orphan

Answer

kubectl set image deployment/myapp app=myapp:previous

Answer

kubectl rollout history deployment/myapp --revision=2

Question 5

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 6

Which TWO are valid fields in a Deployment's rollingUpdate configuration? (Select 2)

Accepted Answer

maxSurge. In a Deployment's rolling update configuration, the `maxSurge` field defines the maximum number of Pods that can be created above the desired replica count during the update, while `maxUnavailable` defines the maximum number of Pods that can be unavailable during the update. Both are valid fields within the `spec.strategy.rollingUpdate` object in a Kubernetes Deployment.

Answer

minReadySeconds

Answer

progressDeadlineSeconds

Answer

revisionHistoryLimit

Question 7

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 8

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 9

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 10

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 11

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 12

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 13

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 14

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 15

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