20+ practice questions focused on Application Observability and Maintenance — one of the most tested topics on the Certified Kubernetes Application Developer CKAD exam. Each question includes a detailed explanation so you learn why the right answer is correct.
Start Application Observability and Maintenance PracticeAn application pod is logging sensitive data (e.g., passwords) to stdout. The security team requires that these logs be redacted before they are stored. Which approach should you recommend?
Explanation: The most reliable way to ensure sensitive data is never stored is to prevent it from being logged in the first place. Option D directly achieves the security requirement without introducing complex infrastructure or relying on a sidecar that cannot intercept stdout logs as described. The sidecar pattern is indeed useful for log processing, but it requires the main container to write logs to a file that is shared via a volume; it cannot read the stdout of another container. Node-level filtering (C) may introduce latency or leave brief on-disk exposure.
You are designing a health check strategy for a web application. Which TWO probe types should you configure to ensure that traffic is only sent to pods that are ready to serve?
Explanation: The Readiness probe (A) is correct because Kubernetes uses it to determine whether a pod is ready to receive traffic; when the readiness probe fails, the pod is removed from the Service's endpoints, so traffic is only sent to pods that can serve requests. The Startup probe (C) is correct because it protects slow-starting containers by disabling liveness and readiness checks until the application has successfully initialized, ensuring that traffic is not routed to pods that are still starting up and not yet ready. The TCP socket probe (B) and HTTP GET probe (D) are not correct as answers here because they are merely probe mechanisms (handlers) that can be used by readiness, liveness, or startup probes, not distinct probe types that by themselves guarantee traffic is only sent to ready pods. The Liveness probe (E) is incorrect because it only determines whether a container should be restarted, not whether the pod should receive traffic.
You want to collect logs from a pod that has multiple containers. Which TWO approaches allow you to view logs from a specific container?
Explanation: To view logs from a specific container in a multi-container pod, use `kubectl logs` with the container name. Option A uses the shorthand `-c` flag, and Option B uses the long form `--container`; both are equivalent and valid. Option D is a duplicate of Option B, so it is not a distinct approach. Option C (`--all-containers`) streams logs from all containers, not a specific one. Option E (no flags) returns logs from all containers by default, which is not what the question asks.
Which TWO of the following are valid ways to expose application metrics for scraping by Prometheus in a Kubernetes environment?
Explanation: Prometheus supports automatic service discovery in Kubernetes via pod annotations. Adding 'prometheus.io/scrape: "true"' to the pod template tells Prometheus to scrape metrics from that pod, provided Prometheus is configured to use the Kubernetes service discovery mechanism. This is a standard, widely adopted pattern for exposing application metrics. Option C is correct because a ServiceMonitor is a custom resource defined by the Prometheus Operator. It allows declarative configuration of which Services (or pods) to scrape, including the metrics path and interval. The ServiceMonitor is created in the same namespace as the target service, and Prometheus discovers it via label selectors. This is the recommended approach when using the Prometheus Operator.
Which THREE of the following are valid methods to view logs of a container that has already terminated?
Explanation: `kubectl logs <pod> --tail=50` retrieves the last 50 lines of logs from the specified pod's container. Even if the container has terminated, the logs are still available from the pod's log history, and `--tail` limits the output to the most recent entries, which is useful for debugging recent failures.
+15 more Application Observability and Maintenance questions available
Practice all Application Observability and Maintenance questions1. Baseline your knowledge
Start with 10 questions to gauge your current understanding of Application Observability and Maintenance. This tells you whether you need a concept refresher or just practice.
2. Review every explanation
For each question — right or wrong — read the full explanation. Understanding why an answer is correct is more valuable than knowing the answer itself.
3. Focus on exam traps
Application Observability and Maintenance questions on the CKAD frequently use trap wording. Look for subtle differences in answers that test your precision, not just general knowledge.
4. Reach 80% consistently
Do repeated sessions until you score 80%+ three times in a row. Then move to mixed-mode practice to test cross-topic recall under realistic conditions.
The exact number varies per candidate. Application Observability and Maintenance is tested as part of the Certified Kubernetes Application Developer CKAD blueprint. Practicing with targeted Application Observability and Maintenance questions ensures you can handle any format or difficulty that appears.
Yes. Courseiva provides free CKAD practice questions across all exam topics and domains. The platform includes topic-based practice, mock exams, missed-question review, bookmarked questions, and readiness tracking — no account required.
Difficulty is subjective, but Application Observability and Maintenance is a high-priority exam concept tested in multiple ways — direct recall, scenario analysis, and command-output interpretation. Consistent practice is the best way to build confidence.
Launch a full Application Observability and Maintenance practice session with instant scoring and detailed explanations.
Start Application Observability and Maintenance Practice →