CKAD Application Observability and Maintenance Practice Test 8 — 15 Questions

Question 1

Which command outputs the pod's full YAML specification including status?

Accepted Answer

kubectl get pod -o yaml. `kubectl get pod -o yaml` outputs the full YAML specification of the pod, including its status (e.g., conditions, container statuses, phase). The `-o yaml` flag retrieves the complete Kubernetes resource object from the API server, which includes both the desired spec and the current status, as stored in etcd.

Answer

kubectl describe pod <pod-name>

Answer

kubectl get pod <pod-name> --export

Answer

kubectl get pod <pod-name> -o json

Question 2

Which THREE of the following are valid types of probes in Kubernetes? (Select 3)

Accepted Answer

Liveness probe. Liveness, Readiness, and Startup probes are all valid probe types in Kubernetes. Liveness probes check if a container is still running and can restart it if needed. Readiness probes determine if a container is ready to serve traffic. Startup probes delay liveness and readiness checks until the container has started successfully. Options B (Survival) and D (Health) are not valid Kubernetes probe types.

Answer

Survival probe

Answer

Health probe

Question 3

Which THREE of the following are valid parameters for configuring probes? (Select 3)

Accepted Answer

timeoutSeconds. In Kubernetes, probe configuration parameters are defined in the container spec within a Pod. `timeoutSeconds` is a valid parameter that specifies the number of seconds after which the probe times out, defaulting to 1 second if not set. It is used in liveness, readiness, and startup probes to control how long kubelet waits for a probe response before considering it failed.

Answer

retryIntervalSeconds

Answer

cooldownSeconds

Question 4

Which THREE of the following are true about the 'kubectl describe pod' output? (Select 3)

Accepted Answer

It shows the exact resource requests and limits of each container. kubectl describe pod provides static configuration details and recent events. It shows resource requests and limits per container (A), recent pod events (C), and the node name where the pod is scheduled (E). It does not show container logs (B) or current CPU/memory usage (D).

Answer

It shows the last few lines of the container logs

Answer

It shows the current CPU and memory usage of the pod

Question 5

Which kubectl command can you use to stream the logs from a pod in real-time?

Accepted Answer

kubectl logs -f. The `-f` flag (short for `--follow`) in `kubectl logs` streams the log output in real-time, similar to `tail -f` on a Linux system. This allows you to observe new log entries as they are written by the pod's containers, which is essential for debugging live issues or monitoring application behavior.

Answer

kubectl logs --previous

Answer

kubectl logs

Answer

kubectl logs --tail=10

Question 6

You have a pod that takes 2 minutes to start its application. You want to avoid the liveness probe from killing the pod during startup, but still have it active afterward. Which probe should you add to the pod spec?

Accepted Answer

Add a startup probe with a failureThreshold high enough to cover the startup time. A startup probe is designed specifically for slow-starting containers. It runs before the liveness probe and, if it fails, the container is killed. By setting a high failureThreshold (e.g., 12 with a 10-second period gives 120 seconds), you allow the application up to 2 minutes to start without the liveness probe interfering. Once the startup probe succeeds, the liveness probe takes over normally.

Answer

Increase the timeoutSeconds on the liveness probe

Answer

Set periodSeconds on the liveness probe to 120

Answer

Set initialDelaySeconds on the liveness probe to 120

Question 7

You want to see detailed information about a node's resource usage. Which command should you run?

Accepted Answer

kubectl top node. `kubectl top node` retrieves real-time CPU and memory usage metrics for nodes from the metrics server, which is essential for monitoring resource consumption. This command directly answers the question about detailed resource usage, unlike other options that provide configuration or log data.

Answer

kubectl describe node

Answer

kubectl logs node

Answer

kubectl get nodes -o wide

Question 8

Which field in the container spec controls the time Kubernetes waits after sending SIGTERM before sending SIGKILL during pod shutdown?

Accepted Answer

terminationGracePeriodSeconds. `terminationGracePeriodSeconds` is the field in the Pod spec that defines the duration Kubernetes waits after sending SIGTERM to the main process in each container before forcefully sending SIGKILL. This grace period allows the application to perform clean shutdown tasks, such as closing connections or flushing data. The default value is 30 seconds if not specified.

Answer

timeoutSeconds

Answer

periodSeconds

Answer

activeDeadlineSeconds

Question 9

You run 'kubectl get pods' and see that a pod is in 'Pending' state. What is the most likely cause?

Accepted Answer

The node has insufficient resources to run the pod. A pod in 'Pending' state indicates that the pod has been accepted by the Kubernetes API server but is not yet scheduled to a node. The most common cause is insufficient resources (CPU, memory, or ephemeral storage) on any available node, which prevents the scheduler from binding the pod. This is confirmed by running 'kubectl describe pod <pod-name>' and checking the 'Events' section for messages like '0/1 nodes are available: Insufficient cpu'.

Answer

The readiness probe is failing

Answer

The container command exited with an error

Answer

The pod's imagePullPolicy is set to Never

Question 10

You want to see all events in the default namespace sorted by timestamp. Which command should you use?

Accepted Answer

kubectl get events. `kubectl get events` retrieves all events in the current namespace (default) and displays them in a table sorted by the `LAST SEEN` timestamp by default. Events are Kubernetes API objects that record actions and state changes (e.g., pod scheduling, container restarts), making this command the standard way to observe cluster activity in a namespace.

Answer

kubectl logs --all-containers

Answer

kubectl top events

Answer

kubectl describe pods

Question 11

You have a pod with two containers: app and sidecar. The sidecar logs are verbose and you want to view only the app container logs. Which command should you use?

Accepted Answer

kubectl logs pod-name --container app. Both `kubectl logs pod-name --container app` and `kubectl logs pod-name -c app` correctly specify the container named 'app' in a multi-container pod. The `--container` flag is the long form of `-c`. Without a container flag, `kubectl logs` defaults to the first container in the pod spec, which may not be the app container. Option B is incorrect because it does not target a specific container, and option D incorrectly uses a label selector.

Answer

kubectl logs pod-name

Answer

kubectl logs -l app=pod-name

Question 12

Which TWO of the following are valid types of probes in Kubernetes?

Accepted Answer

Startup probe. Kubernetes defines exactly three probe types: livenessProbe, readinessProbe, and startupProbe. Therefore, options B, C, and E are all valid. Since the question asks for two, it cannot be answered unambiguously. If the question were intended to ask for two, it must include only two valid options among the choices, or ask for the invalid types instead.

Answer

Survival probe

Answer

Health probe

Question 13

Which TWO of the following are valid reasons for using a startup probe?

Accepted Answer

To prevent unnecessary restarts during initial startup. A startup probe is specifically designed to address containers that require a longer initialization time before they are ready to handle traffic or respond to health checks. By delaying the start of liveness and readiness probes until the startup probe succeeds, it prevents the kubelet from prematurely restarting the container due to failed liveness checks during its slow startup phase. This is the primary reason for using a startup probe: to avoid unnecessary restarts during initial startup.

Answer

To monitor the health of a container after it has started

Answer

To provide additional logging for the container

Answer

To replace the need for a readiness probe

Question 14

Which FOUR of the following are valid probe handlers in Kubernetes?

Accepted Answer

exec. Kubernetes supports four probe handler types: ExecAction (exec), HTTPGetAction (httpGet), TCPSocketAction (tcpSocket), and GRPCAction (gRPC). The gRPC probe handler was added in v1.24. UDP is not a supported probe handler. Since the question asks for THREE but there are four valid options, all four except udpSocket are correct in this context.

Answer

udpSocket

Question 15

You have a pod 'app-pod' that keeps restarting. You want to see the logs from the previous (crashed) container instance. Which command should you use?

Accepted Answer

kubectl logs app-pod --previous. The `--previous` flag in `kubectl logs` retrieves logs from the previous instance of a container in a pod. Option B uses `-prev` which is not a valid shorthand (the correct shorthand is `-p`, which is not listed). Options C and D are incorrect: `-f` is for following logs in real-time, and `describe` shows events and configuration, not logs.

Answer

kubectl logs app-pod -prev

Answer

kubectl logs app-pod -f

Answer

kubectl describe pod app-pod