CKAD Application Deployment Practice Test 9 — 15 Questions

Question 1

Which TWO statements about kubectl apply vs kubectl create are correct? (Select two)

Accepted Answer

kubectl apply can update existing resources; kubectl create will error if resource exists. C is correct because `kubectl apply` uses a declarative approach: it creates a resource if it does not exist and updates it if it already exists, merging changes based on the last-applied-configuration annotation. In contrast, `kubectl create` is imperative and will return an error if the resource already exists, as it expects to create a new resource from scratch.

Answer

kubectl create can update existing resources if the --force flag is used

Answer

kubectl apply only works with Deployments

Answer

kubectl create can be used to update resources by providing the full YAML

Question 2

A Deployment named 'web-app' has 4 replicas. You need to perform a rolling update with a maxSurge of 50% and maxUnavailable of 25%. Which YAML snippet configures this correctly?

Accepted Answer

strategy:
  rollingUpdate:
    maxSurge: 50%
    maxUnavailable: 25%. Ly uses the fields maxSurge and maxUnavailable with the required percentages (50% and 25%). Option A uses incorrect field names (surge, unavailable). Option C uses absolute numbers instead of percentages. Option D swaps the values (maxSurge: 25%, maxUnavailable: 50%). Therefore, option B is the correct configuration for the rolling update.

Answer

strategy:
  rollingUpdate:
    surge: 50%
    unavailable: 25%

Answer

strategy:
  rollingUpdate:
    maxSurge: 2
    maxUnavailable: 1

Answer

strategy:
  rollingUpdate:
    maxSurge: 25%
    maxUnavailable: 50%

Question 3

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

Accepted Answer

kubectl rollout history deployment my-deployment. `kubectl rollout history` is the dedicated command to view the revision history of a Deployment, including the list of revisions and, optionally, details of a specific revision when combined with `--revision`. This command directly queries the Deployment's rollout history stored in its annotations (e.g., `deployment.kubernetes.io/revision`).

Answer

kubectl rollout history deployment my-deployment --revision=2

Answer

kubectl rollout list deployment my-deployment

Answer

kubectl rollout status deployment my-deployment

Question 4

You are performing a blue-green deployment. You have two Deployments: 'app-blue' (current) and 'app-green' (new). Both have labels 'app: myapp' and 'version: blue' or 'version: green' respectively. The Service 'myapp-svc' selects pods with 'app: myapp, version: blue'. How do you switch traffic to the green deployment?

Accepted Answer

Update the Service selector to 'app: myapp, version: green'. Updating the Service's selector to 'app: myapp, version: green' directs traffic to the green pods. Option B uses a semicolon instead of a comma, which is invalid syntax. Option A adds a label mismatch and does not change the Service selector. Option C would change the green deployment's label to 'blue', causing both deployments to have the same version label, which is not a proper blue-green switch.

Answer

Add an additional label 'traffic: enabled' to the 'app-green' pods and update the Service to select 'traffic: enabled'

Answer

Update the Service selector to 'app: myapp; version: green'

Answer

Update the 'app-green' Deployment to have label 'version: blue'

Question 5

You have a Helm chart that deploys a web application. You want to conditionally include a ConfigMap in the release based on a value 'config.enabled'. Which template syntax correctly implements this?

Accepted Answer

{{- if .Values.config.enabled }}
  (ConfigMap YAML)
{{- end }}. Uses the correct Helm template syntax: '{{- if .Values.config.enabled }}' to conditionally include content. The '{{- ... }}' syntax trims whitespace and the 'if' directive checks the value. Option A uses Python/Django-style syntax which is invalid in Helm. Option C uses an invalid 'when' statement. Option D uses Handlebars-style block helpers ('{{#if}}...{{/if}}'), which is not valid Helm template syntax.

Answer

{% if .Values.config.enabled %}
  (ConfigMap YAML)
{% endif %}

Answer

{{- when .Values.config.enabled }}
  (ConfigMap YAML)
{{- end }}

Answer

{{#if .Values.config.enabled}}
  (ConfigMap YAML)
{{/if}}

Question 6

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

Accepted Answer

kubectl scale deployment frontend --replicas=5. Options B, C, and D are all correct. `kubectl scale deployment frontend --replicas=5` (Option B) uses the full resource type 'deployment' and the `--replicas=5` syntax with an equals sign, which is the canonical form for numeric flags. Option C uses the short alias 'deploy' instead of 'deployment', which is also valid. Option D uses `deployment/frontend` (resource/name syntax) with the `--replicas=5` flag, which is also a valid way to specify the resource. All three commands successfully update the Deployment's `.spec.replicas` field to 5. Option A is wrong because it uses a space instead of an equals sign for the `--replicas` flag.

Answer

kubectl scale deployment frontend --replicas 5

Question 7

You have created a HorizontalPodAutoscaler (HPA) named 'web-hpa' targeting a Deployment 'web'. The HPA uses targetCPUUtilizationPercentage: 80. The current CPU usage is 60%. How many replicas will the HPA set?

Accepted Answer

1. The HPA calculates the desired number of replicas using the formula: desiredReplicas = ceil[currentReplicas * (currentMetricValue / targetMetricValue)]. With current CPU at 60% and target at 80%, the ratio is 0.75. If the current replica count is 1, the result is ceil(1 * 0.75) = 1. Since the ratio is below 1.0, the HPA does not scale up; it only scales down if the ratio falls below a configurable threshold (default 0.5) for a sustained period, which is not the case here.

Answer

The HPA would not be created if current usage is below target

Answer

2

Answer

0

Question 8

You need to perform a canary deployment where 10% of traffic goes to the new version. You have a Deployment 'app-v1' with 9 replicas and 'app-v2' with 1 replica. What must be true for the Service to distribute traffic roughly 90/10?

Accepted Answer

The Service selector must include a label that both Deployments share, e.g., 'app: myapp'. A Kubernetes Service distributes traffic across all Pods matching its label selector. For a canary deployment with 90/10 traffic split, both Deployments must share a common label (e.g., 'app: myapp') so the Service selects all 10 Pods (9 from v1, 1 from v2), achieving roughly 90% traffic to v1 and 10% to v2 based on replica count. The Service uses round-robin or random load balancing by default, so the ratio of replicas directly determines traffic distribution.

Answer

The Service must have 'sessionAffinity: ClientIP' to ensure sticky sessions

Answer

The Service must not have any selectors, and endpoints must be manually managed

Answer

The Service selector must include only 'version: v2'

Question 9

You are using Kustomize with a base and an overlay. The base sets a Deployment's replicas to 3. The overlay sets replicas to 5 using a patch. What is the final replica count after running 'kubectl apply -k overlay/'?

Accepted Answer

5. In Kustomize, overlays override base values through patches. The overlay specifies replicas: 5, so the final replica count is 5. Thus, option A is correct. Option B is incorrect because Kustomize applies patches in a defined order, not a random merge. Option C is incorrect because values are not summed. Option D is the base value, which is overridden.

Answer

The result depends on the merge order

Answer

8

Answer

3

Question 10

Which command is used to rollback a Deployment to the previous revision?

Accepted Answer

kubectl rollout undo deployment my-deployment. 'kubectl rollout undo deployment my-deployment'. Option B rolls forward? Option C is not valid. Option D is for history.

Answer

kubectl rollout redo deployment my-deployment

Answer

kubectl rollout revert deployment my-deployment

Answer

kubectl rollout history deployment my-deployment

Question 11

During a rolling update of a Deployment with 10 replicas, you set maxSurge to 3 and maxUnavailable to 2. What is the maximum number of pods that can be unavailable during the update?

Accepted Answer

2. maxUnavailable: 2 means at most 2 pods can be unavailable. Option C is correct.

Answer

5

Answer

3

Answer

10

Question 12

Your Deployment is stuck during rollout, and you want to investigate. Which command pauses the rollout and allows you to check the current state?

Accepted Answer

kubectl rollout pause deployment my-deployment. The correct command to pause a deployment rollout is `kubectl rollout pause deployment my-deployment`. While paused, you can inspect the current state with `kubectl rollout status` or other diagnostic commands. Option A (`kubectl rollout resume`) resumes a paused rollout, not pauses it. Option B (`kubectl rollout status`) shows the rollout state but does not pause it. Option D (`kubectl rollout stop`) is not a valid kubectl command; the correct command to stop a rollout is `kubectl rollout undo`. Therefore, only option C pauses the rollout as required.

Answer

kubectl rollout resume deployment my-deployment

Answer

kubectl rollout status deployment my-deployment

Answer

kubectl rollout stop deployment my-deployment

Question 13

You want to add an annotation to a pod without modifying the pod template. Which approach should you use?

Accepted Answer

kubectl annotate pod my-pod key=value. 'kubectl annotate pod my-pod key=value' adds an annotation directly to the existing pod without modifying the pod template. Option A uses 'kubectl annotate deployment', which adds an annotation to the Deployment object itself, not to the pod. Option B uses 'kubectl label', which adds labels, not annotations. Option C uses 'kubectl edit', which is not a direct annotation command and may be less efficient.

Answer

kubectl annotate deployment my-deployment key=value

Answer

kubectl label pod my-pod key=value

Answer

kubectl edit pod my-pod and add annotation manually

Question 14

You are using Helm to manage a chart. Which commands are valid to list installed releases? (Choose TWO)

Accepted Answer

helm ls. `helm ls` and `helm list` are both valid commands to list installed releases in Helm. `helm ls` is an alias for `helm list`, and both display all deployed releases in the current namespace by default. These commands are essential for managing Helm-based deployments.

Answer

helm upgrade

Answer

helm status

Answer

helm history

Question 15

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