CKAD Application Deployment Practice Test 3 — 15 Questions

Question 1

You have an existing Deployment 'web' created with 'kubectl create deployment web --image=nginx --replicas=3'. You need to change the image to 'nginx:1.19' and record the change. Which command should you use?

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

Accepted Answer

kubectl set image deployment/web web=nginx:1.19 --record. `kubectl set image deployment/web web=nginx:1.19 --record` directly updates the container image for the 'web' container in the 'web' Deployment and the `--record` flag annotates the change with the command used, which is visible in the rollout history. This is the most straightforward and idiomatic way to update an image and record the change for audit or rollback purposes.

Answer

kubectl replace -f deployment.yaml --record

Answer

kubectl edit deployment web --record

Answer

kubectl patch deployment web -p '{"spec":{"template":{"spec":{"containers":[{"name":"web","image":"nginx:1.19"}]}}}}}' --record

Question 2

You are using Kustomize to manage configurations. Your project structure is: 'base/kustomization.yaml', 'overlays/prod/kustomization.yaml'. The base defines a Deployment with image 'nginx:1.18'. The overlay wants to patch the image to 'nginx:1.19'. Which is the correct way to define the patch in the overlay?

Accepted Answer

Use 'patches: [path: deployment-patch.yaml]'. Kustomize supports both `patchesStrategicMerge` and the more general `patches` field. The `patches` field with a `path` entry is valid for strategic merge patches. For example, `patches: [path: deployment-patch.yaml]` is correct in current Kustomize versions. Thus both A and C are correct ways to override the image.

Answer

Use 'resources: [../base]' and then define a new Deployment with the same name to override.

Answer

Use 'patchesJson6902: [target: ..., patch: ...]'

Question 3

Which command is used to undo the most recent rollout of a Deployment named 'myapp'?

Accepted Answer

kubectl rollout undo deployment myapp. `kubectl rollout undo deployment myapp` reverts the Deployment to the previous revision by default, effectively undoing the most recent rollout. This command uses the rollout history stored in the Deployment's annotations (e.g., `deployment.kubernetes.io/revision`) to identify and apply the prior ReplicaSet.

Answer

kubectl rollout undo deployment myapp --to-revision=2

Answer

kubectl rollout status deployment myapp

Answer

kubectl rollback deployment myapp

Question 4

You have a HorizontalPodAutoscaler (HPA) targeting a Deployment. The HPA is configured with 'targetCPUUtilizationPercentage: 50'. The current CPU utilization is 60% across the pods. What action does the HPA take?

Accepted Answer

Scale up the Deployment to reduce per-pod CPU utilization.. The HPA is configured with a targetCPUUtilizationPercentage of 50%, and the current CPU utilization is 60%, which exceeds the target. The HPA will scale up the Deployment by increasing the number of replicas to distribute the load, thereby reducing per-pod CPU utilization toward the target. This is the core behavior of the Kubernetes Horizontal Pod Autoscaler: it adjusts replica count based on observed metrics to meet the target.

Answer

Scale down the Deployment because the target is 50%.

Answer

Mark the HPA as unable to calculate metrics and stop scaling.

Answer

Take no action because the deviation is within tolerance.

Question 5

You are performing a blue-green deployment for an application. You have two Deployments: 'app-blue' (current production) and 'app-green' (new version). Both have label 'app: myapp' and are exposed by a Service 'myapp-svc'. How do you switch traffic from blue to green?

Accepted Answer

Update the Service's selector to match the labels of the green Deployment's pods (e.g., 'version: green').. Updating the Service's selector to match the green Deployment's pod label routes traffic to green. Option A is incorrect because the Service cannot be deleted and recreated without downtime if done incorrectly. Option C is incorrect because deleting the blue Deployment before ensuring the green is serving traffic would cause downtime. Option D is incorrect because changing the image in the same Deployment would perform a rolling update, not a blue-green switch.

Answer

Delete the Service and recreate it with the selector pointing to app-green.

Answer

Delete the blue Deployment after ensuring green is ready.

Answer

Update the blue Deployment's image to the new version.

Question 6

You have a YAML file 'deploy.yaml' that defines a Deployment. Which command creates the Deployment if it does not exist, or updates it if it already exists?

Accepted Answer

kubectl apply -f deploy.yaml. `kubectl apply -f deploy.yaml` uses declarative object configuration: it creates the Deployment if it doesn't exist, or performs a strategic merge patch to update it if it already exists. This is the standard command for managing Kubernetes resources with a desired-state file.

Answer

kubectl replace -f deploy.yaml

Answer

kubectl patch -f deploy.yaml

Answer

kubectl create -f deploy.yaml

Question 7

A Helm chart has the following template snippet: '{{ .Values.replicaCount }}'. You want to set replicaCount to 5 during installation. Which command should you use?

Accepted Answer

helm install my-release mychart --set replicaCount=5. The `--set` flag in Helm allows you to directly override a single value in a chart's `values.yaml` file from the command line. This is the standard way to set `replicaCount` to 5 during installation without modifying the chart or using a separate values file.

Answer

helm install my-release mychart --name replicaCount=5

Answer

helm install my-release mychart --values replicaCount=5

Answer

helm install my-release mychart --set-string replicaCount=5

Question 8

Which TWO of the following are valid methods to achieve a blue-green deployment in Kubernetes? (Select two.)

Accepted Answer

Create two Deployments (blue and green) with different labels, and a Service that selects one of them. Update the Service's selector to switch traffic.. It directly implements blue-green deployment by creating two separate Deployments (blue and green) with different labels, then using a single Service whose selector is updated to point to the new version's pods. This allows instant traffic switching without downtime, as the Service's label selector is a live Kubernetes resource that immediately routes traffic to matching pods.

Answer

Use a single Deployment and change the image, then use kubectl rollout pause/resume to control traffic.

Answer

Set maxSurge=100% and maxUnavailable=0% in the Deployment strategy.

Answer

Create multiple Deployments with different images and use Ingress with weight-based routing.

Question 9

Which TWO of the following are valid ways to view the rollout history of a Deployment named 'myapp'? (Select two.)

Accepted Answer

kubectl get replicasets -l app=myapp. `kubectl get replicasets -l app=myapp` lists all ReplicaSets associated with the Deployment via the label selector. Each ReplicaSet corresponds to a revision in the rollout history, so viewing them effectively shows the history of revisions.

Option B is correct because `kubectl rollout history deployment myapp` directly displays the rollout history with revision numbers and change causes.

Option C is incorrect because `kubectl describe deployment myapp` only shows the current state of the Deployment, including the current revision annotation, but does not list past revisions or the full history.

Option D is incorrect because `kubectl rollout status deployment myapp` monitors the progress of a single rollout (e.g., during an update) and does not show historical rollouts.

Option E is incorrect because `kubectl get deployment myapp -o yaml` outputs the current Deployment manifest, which contains only the desired state and current status, not the revision history.

Answer

kubectl describe deployment myapp

Answer

kubectl rollout status deployment myapp

Answer

kubectl get deployment myapp -o yaml

Question 10

Which TWO of the following are valid uses of Kubernetes Annotations? (Select two.)

Accepted Answer

Configuring ingress controllers with specific settings like rewrite rules.. Kubernetes annotations are key-value pairs used to attach arbitrary non-identifying metadata to objects, and Ingress controllers commonly use specific annotations (e.g., nginx.ingress.kubernetes.io/rewrite-target) to configure behavior like URL rewriting. This allows operators to customize controller functionality without altering the core resource definition.

Answer

Defining the name of a Kubernetes resource.

Answer

Identifying which pods a Service should route traffic to.

Answer

Enabling service discovery between microservices.

Question 11

Which kubectl command is used to view the rollout status of a Deployment named 'web-app'?

Accepted Answer

kubectl rollout status deployment web-app. `kubectl rollout status deployment web-app` is the dedicated command to monitor the progress of a rollout for a Deployment named 'web-app'. It blocks until the rollout completes successfully or reports a failure, providing real-time status updates such as 'Waiting for rollout to finish' or 'deployment "web-app" successfully rolled out'.

Answer

kubectl rollout history deployment web-app

Answer

kubectl describe deployment web-app

Answer

kubectl status deployment web-app

Question 12

A Deployment has been updated with a new image. After running 'kubectl rollout status deployment/myapp', you see that the rollout has stalled. You want to undo the rollout to the previous revision. What command do you run?

Accepted Answer

kubectl rollout undo deployment/myapp. 'kubectl rollout undo deployment/myapp' reverts the Deployment to the previous revision, which is the standard Kubernetes command for rolling back a stalled or failed rollout. This command uses the Deployment's revision history stored in its annotations to restore the prior pod template specification.

Answer

kubectl rollout restart deployment/myapp

Answer

kubectl delete deployment/myapp --cascade=orphan

Answer

kubectl set image deployment/myapp app=old-image

Question 13

You are implementing a blue-green deployment using Kubernetes Deployments and Services. The 'blue' Deployment runs version 1.0, and the 'green' Deployment runs version 2.0. What is the key mechanism to switch traffic from blue to green?

Accepted Answer

Update the Service's label selector to match the green Deployment's pod labels. By updating the Service's label selector to match the green Deployment's pod labels, the Service routes traffic to the new version.

Answer

Scale down the blue Deployment to 0 replicas

Answer

Delete the blue Deployment

Answer

Change the Service type from ClusterIP to NodePort

Question 14

You want to perform a canary deployment where 10% of traffic goes to the new version. You have a Deployment 'app-v1' with 10 replicas. You create a second Deployment 'app-v2' with 1 replica and a new Service. What Kubernetes resource is typically used to split traffic between the two Services?

Accepted Answer

Ingress resource with a canary annotation. An Ingress resource with a canary annotation (e.g., `nginx.ingress.kubernetes.io/canary-weight: "10"`) allows you to split traffic between two Services by weight. This is the standard Kubernetes approach for canary deployments, where the Ingress controller (like NGINX) routes a specified percentage of traffic to the canary Service (app-v2) and the rest to the primary Service (app-v1).

Answer

A single Service with multiple selectors

Answer

NetworkPolicy

Answer

HorizontalPodAutoscaler

Question 15

When using 'kubectl apply' vs 'kubectl create', which statement is correct?

Accepted Answer

'kubectl apply' can create or update resources; 'kubectl create' only creates and fails if resource exists. 'kubectl apply' uses a declarative approach that creates a resource if it does not exist and updates it if it does, while 'kubectl create' is imperative and will fail with an error if the resource already exists. This distinction is fundamental to Kubernetes resource management, where 'apply' manages the full object state via last-applied-configuration annotations, and 'create' only handles initial creation.

Answer

'kubectl create' will update a resource if it already exists

Answer

'kubectl apply' and 'kubectl create' are interchangeable

Answer

'kubectl apply' can only create resources, not update them