CKAD Practice Test 46 — 15 Questions

Question 1

You have a Deployment named 'web-app' with 5 replicas. You want to perform a rolling update with a maximum of 2 extra pods during the update and allow at most 1 pod to be unavailable. Which YAML snippet correctly configures the rolling update strategy?

Accepted Answer

strategy:
  type: RollingUpdate
  rollingUpdate:
    maxSurge: 2
    maxUnavailable: 1. Option A correctly sets maxSurge to 2 and maxUnavailable to 1. maxSurge specifies the maximum number of pods that can be created above the desired replicas (5+2=7). maxUnavailable specifies the maximum number of pods that can be unavailable during the update (1).

Answer

strategy:
  type: RollingUpdate
  rollingUpdate:
    maxSurge: 3
    maxUnavailable: 0

Answer

strategy:
  type: RollingUpdate
  rollingUpdate:
    maxSurge: 1
    maxUnavailable: 2

Answer

strategy:
  type: RollingUpdate
  rollingUpdate:
    maxSurge: "50%"
    maxUnavailable: "20%"

Question 2

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 }}. Option D uses the correct Helm template syntax: '{{- if .Values.config.enabled }}' to conditionally include content. Option A uses Python-style syntax. Option B is close but missing the if statement. Option C uses an invalid 'when' statement.

Answer

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

Answer

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

Answer

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

Question 3

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 4

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 5

Which TWO of the following are valid ways to scale a Deployment named 'my-app' to 5 replicas?

Accepted Answer

kubectl apply -f deployment.yaml where deployment.yaml has 'replicas: 5'. Option A uses kubectl scale with --replicas flag to set the count. Option C modifies the deployment YAML and applies it, which is also valid. Option B has typo 'scale' missing. Option D sets a label selector but leaves replicas unchanged if not specified. Option E uses edit but doesn't specify the change.

Answer

kubectl edit deployment my-app

Answer

kubectl deployment my-app scale --replicas=5

Answer

kubectl scale deployment my-app --selector=app=my-app

Question 6

You have installed a Helm chart for an application named 'myapp' in the namespace 'prod'. You need to upgrade the release to a new chart version, but you want to be able to revert to the current version quickly if the upgrade fails. Which command should you run?

Accepted Answer

helm upgrade myapp ./chart --namespace prod --history-max 10. The --history-max flag limits the number of revisions kept. Option D keeps 10 revisions, allowing rollback if needed. Option C also keeps history but is less explicit about the number. However, the question expects a command that preserves history for rollback; the default is 10, but explicitly setting it is good practice.

Answer

helm upgrade myapp ./chart --namespace prod --atomic

Answer

helm upgrade myapp ./chart --namespace prod --recreate-pods

Answer

helm upgrade myapp ./chart --namespace prod

Question 7

You have a Deployment 'db' that uses a ConfigMap for configuration. You want to update the ConfigMap and roll out the changes to pods without restarting them manually. Which approach should you use?

Accepted Answer

Update the ConfigMap and then update the Deployment's pod template (e.g., change an annotation) to trigger a rolling update. Mounting ConfigMaps as volumes with subPath does not automatically update pods; however, using environment variables from ConfigMaps also does not update pods. The recommended approach is to use a Deployment update with a change that triggers a rollout (e.g., updating an annotation). Option B is correct.

Answer

Delete the ConfigMap and recreate it with the same name

Answer

Edit the ConfigMap and run kubectl rollout restart deployment/db

Answer

Use kubectl replace on the ConfigMap and the pods will automatically get the new values

Question 8

A developer wants to perform a canary deployment where 10% of traffic goes to a new version (v2) of an application. They create two Deployments (app-v1 and app-v2) and a Service. The Service selector is configured to match labels: 'app: myapp, version: v1'. How can they route 10% of traffic to v2 with minimal changes?

Accepted Answer

Change the Service selector to 'app: myapp' (remove version label) and set v1 replicas to 9 and v2 replicas to 1.. By adding the label 'version: v1' to only a subset of v2 pods, the Service will include them. But the correct approach is to modify the Service selector to match both versions and then scale the Deployments accordingly. However, the simplest method is to adjust the replica counts: if v1 has 9 replicas and v2 has 1 replica, and the Service selects both, traffic will be distributed roughly 90/10.

Answer

Use kubectl rollout pause on the v2 Deployment.

Answer

Set the v2 Deployment's spec.replicas to 10% of the total replicas and keep the Service selector unchanged.

Answer

Add a NetworkPolicy to limit traffic to v2 pods to 10%.

Question 9

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 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 10

A Deployment is configured with strategy type 'Recreate'. Which statement about this strategy is true?

Accepted Answer

It terminates all existing Pods before creating new Pods.. Recreate terminates all existing Pods before creating new ones, causing downtime.

Answer

It creates a new ReplicaSet but does not scale down the old one.

Answer

It updates Pods by gradually terminating old Pods and creating new ones.

Answer

It first creates new Pods and then terminates old Pods.

Question 11

Which field in a HorizontalPodAutoscaler spec defines the target CPU utilization percentage?

Accepted Answer

spec.targetCPUUtilizationPercentage. The targetCPUUtilizationPercentage field in the HPA spec (for autoscaling/v1) or in the metric spec (for autoscaling/v2) defines the CPU target.

Answer

spec.behavior

Answer

spec.metrics[0].resource.target.averageUtilization

Answer

spec.maxReplicas

Question 12

Which TWO options are valid annotations for a Pod?

Accepted Answer

description: 'This pod runs the frontend'. Annotations are key-value pairs that can contain any non-identifying metadata. They are not used for selection.

Answer

version: v1

Answer

pod-template-hash: 12345

Answer

environment: production

Question 13

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

Accepted Answer

Create two Services, one for blue and one for green. Initially point an ingress to the blue Service. Update the ingress to point to green after validation.. Blue-green deployment involves running two versions simultaneously and switching traffic. Option A uses label selectors to route traffic to either 'version: blue' or 'version: green' pods. Option D uses a Service with a selector that matches the active version, and traffic is switched by updating the selector. Option B describes canary deployment. Option C is rolling update. Option E is not a standard method.

Answer

Use a Deployment with 'strategy.type: Recreate' and delete the old version before creating the new one.

Answer

Create a Deployment with two replicas and use a Service with session affinity to gradually shift traffic.

Answer

Use a Deployment with 'strategy.type: RollingUpdate' and set 'maxSurge: 100%' and 'maxUnavailable: 0%'.

Question 14

Which TWO of the following are correct about the difference between 'kubectl apply' and 'kubectl create'?

Accepted Answer

'kubectl apply' can be used to update existing resources, whereas 'kubectl create' will fail if the resource already exists.. Option A is correct: apply uses declarative management; create is imperative. Option B is correct: apply can create and update resources; create only creates. Option C is false: create can also create resources from files. Option D is false: both can create resources. Option E is false: apply does not delete resources by default.

Answer

'kubectl apply' can only be used to create resources, not update them.

Answer

'kubectl apply' will delete resources if they are removed from the file.

Answer

'kubectl create' can only create resources from YAML files, not from stdin.

Question 15

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'. Option B is correct: update the Service's selector to 'app: myapp, version: green'. Option A changes the Deployment, not the Service. Option C would break the Service selector syntax. Option D changes the green Deployment's labels, which would not be picked up by the Service without selector change.

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'