Linux Foundation KCNA Dumps
Linux Foundation KCNA Practice Test 91
Question 900
A small insurer wants to distinguish a Prometheus scraping failure from a genuinely idle API. What pair of supported action and practical verification should be approved?
Explanation
Correct Answer
The situation is that a small insurer wants to distinguish a Prometheus scraping failure from a genuinely idle API. Expose appropriately labeled /metrics endpoints or exporters and configure Prometheus scrape targets to collect time-series measurements. Acceptance evidence: Verify a synthetic exporter is listed UP in Prometheus target status and query its request counter after generating traffic. This pairing is justified because prometheus commonly pulls numeric samples from configured targets, stores them as labeled time series and supports PromQL queries over those samples.
Incorrect Answers
This action and check address the distinct objective “Instrument services with OpenTelemetry context propagation” instead of the stated acceptance requirement. The matching action is to expose appropriately labeled /metrics endpoints or exporters and configure Prometheus scrape targets to collect time-series measurements. Its confirming test is to verify a synthetic exporter is listed UP in Prometheus target status and query its request counter after generating traffic.
This action and check address the distinct objective “Define secure release governance with staged approvals and policy verification” instead of the stated acceptance requirement. The matching action is to expose appropriately labeled /metrics endpoints or exporters and configure Prometheus scrape targets to collect time-series measurements. Its confirming test is to verify a synthetic exporter is listed UP in Prometheus target status and query its request counter after generating traffic.
The situation is that a small insurer wants to distinguish a Prometheus scraping failure from a genuinely idle API. This action and check address the distinct objective “Explain metrics, logs and traces as complementary observability signals” instead of the stated acceptance requirement. The matching action is to expose appropriately labeled /metrics endpoints or exporters and configure Prometheus scrape targets to collect time-series measurements. Its confirming test is to verify a synthetic exporter is listed UP in Prometheus target status and query its request counter after generating traffic.
Question 901
A city service needs to page only when its checkout failure rate stays elevated for several minutes. Which Kubernetes or cloud-native implementation decision best solves the stated problem?
Explanation
Correct Answer
Define symptom-based Prometheus alerting rules with sensible durations and route alerts through Alertmanager to the responsible service team. This resolves the issue because alert rules evaluate time-series expressions while Alertmanager groups, routes and silences notifications; neither automatically fixes the underlying workload. To verify, trigger a controlled error-rate alert, verify its pending/firing transition and confirm the correct team receives a grouped notification.
Incorrect Answers
This option addresses the distinct objective “Understand Prometheus pull-based metrics collection and exporters”, not the immediate requirement. Prometheus commonly pulls numeric samples from configured targets, stores them as labeled time series and supports PromQL queries over those samples. For the stated case, alert rules evaluate time-series expressions while Alertmanager groups, routes and silences notifications; neither automatically fixes the underlying workload.
This option addresses the distinct objective “Apply cloud-native portability and immutable infrastructure principles pragmatically”, not the immediate requirement. Containers and Kubernetes APIs reduce some environment differences, but network load balancers, storage drivers and IAM integrations remain provider-specific. For the stated case, alert rules evaluate time-series expressions while Alertmanager groups, routes and silences notifications; neither automatically fixes the underlying workload.
This option addresses the distinct objective “Distinguish preferred node affinity from required scheduling rules”, not the immediate requirement. A required affinity expression blocks scheduling onto nonmatching nodes; a preferred expression influences scoring but permits fallback when necessary. For the stated case, alert rules evaluate time-series expressions while Alertmanager groups, routes and silences notifications; neither automatically fixes the underlying workload.
Question 902
A city service needs to page only when its checkout failure rate stays elevated for several minutes. Which platform mechanism explains why the suitable approach works?
Explanation
Correct Answer
Alert rules evaluate time-series expressions while Alertmanager groups, routes and silences notifications; neither automatically fixes the underlying workload. It supports this action: Define symptom-based Prometheus alerting rules with sensible durations and route alerts through Alertmanager to the responsible service team. To confirm, trigger a controlled error-rate alert, verify its pending/firing transition and confirm the correct team receives a grouped notification.
Incorrect Answers
That statement explains the distinct objective “Understand Prometheus pull-based metrics collection and exporters” rather than the cause in this case. The deciding mechanism here is that alert rules evaluate time-series expressions while Alertmanager groups, routes and silences notifications; neither automatically fixes the underlying workload.
That statement explains the distinct objective “Understand service proxy implementations without assuming kube-proxy is mandatory” rather than the cause in this case. The deciding mechanism here is that alert rules evaluate time-series expressions while Alertmanager groups, routes and silences notifications; neither automatically fixes the underlying workload.
That statement explains the distinct objective “Use SLI and SLO measures to focus reliability objectives” rather than the cause in this case. The deciding mechanism here is that alert rules evaluate time-series expressions while Alertmanager groups, routes and silences notifications; neither automatically fixes the underlying workload.
Question 903
A city service needs to page only when its checkout failure rate stays elevated for several minutes. Which controlled observation would best validate the intended improvement?
Explanation
Correct Answer
Trigger a controlled error-rate alert, verify its pending/firing transition and confirm the correct team receives a grouped notification. This is the relevant test because alert rules evaluate time-series expressions while Alertmanager groups, routes and silences notifications; neither automatically fixes the underlying workload.
Incorrect Answers
This check would help evaluate the distinct objective “Use least-privilege kubectl authentication and authorization during routine administration”, but not the required result. For this case, trigger a controlled error-rate alert, verify its pending/firing transition and confirm the correct team receives a grouped notification.
This check would help evaluate the distinct objective “Understand Prometheus pull-based metrics collection and exporters”, but not the required result. For this case, trigger a controlled error-rate alert, verify its pending/firing transition and confirm the correct team receives a grouped notification.
This check would help evaluate the distinct objective “Understand CNCF project maturity stages without equating them to security approval”, but not the required result. For this case, trigger a controlled error-rate alert, verify its pending/firing transition and confirm the correct team receives a grouped notification.
Question 904
A city service needs to page only when its checkout failure rate stays elevated for several minutes. An engineer proposes: “Create an immediate alert on every small CPU fluctuation and send it separately to all staff without ownership.” What adverse outcome would be most direct?
Explanation
Correct Answer
Alert fatigue hides significant incidents while normal autoscaling bursts generate excessive pages. The shortcut creates this risk because alert rules evaluate time-series expressions while Alertmanager groups, routes and silences notifications; neither automatically fixes the underlying workload.
Incorrect Answers
That outcome concerns the distinct objective “Understand Prometheus pull-based metrics collection and exporters”; it is not the most direct consequence of this shortcut. The relevant consequence is that alert fatigue hides significant incidents while normal autoscaling bursts generate excessive pages.
That outcome concerns the distinct objective “Distinguish ConfigMaps from Secrets and avoid storing credentials in public configuration”; it is not the most direct consequence of this shortcut. The relevant consequence is that alert fatigue hides significant incidents while normal autoscaling bursts generate excessive pages.
That outcome concerns the distinct objective “Instrument services with OpenTelemetry context propagation”; it is not the most direct consequence of this shortcut. The relevant consequence is that alert fatigue hides significant incidents while normal autoscaling bursts generate excessive pages.
Question 905
A city service needs to page only when its checkout failure rate stays elevated for several minutes. What pair of supported action and practical verification should be approved?
Explanation
Correct Answer
Define symptom-based Prometheus alerting rules with sensible durations and route alerts through Alertmanager to the responsible service team. Acceptance evidence: Trigger a controlled error-rate alert, verify its pending/firing transition and confirm the correct team receives a grouped notification. This pairing is justified because alert rules evaluate time-series expressions while Alertmanager groups, routes and silences notifications; neither automatically fixes the underlying workload.
Incorrect Answers
This action and check address the distinct objective “Use open community governance and contribution processes for sustainable cloud-native projects” instead of the stated acceptance requirement. The matching action is to define symptom-based Prometheus alerting rules with sensible durations and route alerts through Alertmanager to the responsible service team. Its confirming test is to trigger a controlled error-rate alert, verify its pending/firing transition and confirm the correct team receives a grouped notification.
This action and check address the distinct objective “Separate CI build verification from CD environment promotion” instead of the stated acceptance requirement. The matching action is to define symptom-based Prometheus alerting rules with sensible durations and route alerts through Alertmanager to the responsible service team. Its confirming test is to trigger a controlled error-rate alert, verify its pending/firing transition and confirm the correct team receives a grouped notification.
This action and check address the distinct objective “Instrument services with OpenTelemetry context propagation” instead of the stated acceptance requirement. The matching action is to define symptom-based Prometheus alerting rules with sensible durations and route alerts through Alertmanager to the responsible service team. Its confirming test is to trigger a controlled error-rate alert, verify its pending/firing transition and confirm the correct team receives a grouped notification.
Question 906
A college lab sends every transient CPU spike to the whole operations channel and wants actionable alerts. Which engineering approach is the most appropriate for this cloud-native case?
Explanation
Correct Answer
The situation is that a college lab sends every transient CPU spike to the whole operations channel and wants actionable alerts. Define symptom-based Prometheus alerting rules with sensible durations and route alerts through Alertmanager to the responsible service team. This resolves the issue because alert rules evaluate time-series expressions while Alertmanager groups, routes and silences notifications; neither automatically fixes the underlying workload. To verify, trigger a controlled error-rate alert, verify its pending/firing transition and confirm the correct team receives a grouped notification.
Incorrect Answers
This option addresses the distinct objective “Understand open standards and vendor-neutral community collaboration”, not the immediate requirement. Open standards and vendor-neutral governance reduce lock-in and support collaboration, but products can still differ in versions, implementations and operational capabilities. For the stated case, alert rules evaluate time-series expressions while Alertmanager groups, routes and silences notifications; neither automatically fixes the underlying workload.
This option addresses the distinct objective “Use Pod Security Standards to deny overly privileged Pod configurations”, not the immediate requirement. Pod Security Standards establish common workload hardening profiles, and admission checks can enforce restricted capabilities and privilege use at API creation. For the stated case, alert rules evaluate time-series expressions while Alertmanager groups, routes and silences notifications; neither automatically fixes the underlying workload.
This option addresses the distinct objective “Use SLI and SLO measures to focus reliability objectives”, not the immediate requirement. A service level objective is a target for measured user-facing behavior; error budgets quantify allowed misses and help prioritize release risk. For the stated case, alert rules evaluate time-series expressions while Alertmanager groups, routes and silences notifications; neither automatically fixes the underlying workload.
Question 907
A college lab sends every transient CPU spike to the whole operations channel and wants actionable alerts. What infrastructure principle makes the correct treatment effective?
Explanation
Correct Answer
The situation is that a college lab sends every transient CPU spike to the whole operations channel and wants actionable alerts. Alert rules evaluate time-series expressions while Alertmanager groups, routes and silences notifications; neither automatically fixes the underlying workload. It supports this action: Define symptom-based Prometheus alerting rules with sensible durations and route alerts through Alertmanager to the responsible service team. To confirm, trigger a controlled error-rate alert, verify its pending/firing transition and confirm the correct team receives a grouped notification.
Incorrect Answers
That statement explains the distinct objective “Use least-privilege kubectl authentication and authorization during routine administration” rather than the cause in this case. The deciding mechanism here is that alert rules evaluate time-series expressions while Alertmanager groups, routes and silences notifications; neither automatically fixes the underlying workload.
That statement explains the distinct objective “Distinguish service mesh traffic management from external ingress routing” rather than the cause in this case. The deciding mechanism here is that alert rules evaluate time-series expressions while Alertmanager groups, routes and silences notifications; neither automatically fixes the underlying workload.
That statement explains the distinct objective “Explain metrics, logs and traces as complementary observability signals” rather than the cause in this case. The deciding mechanism here is that alert rules evaluate time-series expressions while Alertmanager groups, routes and silences notifications; neither automatically fixes the underlying workload.
Question 908
A college lab sends every transient CPU spike to the whole operations channel and wants actionable alerts. What verification result would most convincingly distinguish a working solution from a claim?
Explanation
Correct Answer
The situation is that a college lab sends every transient CPU spike to the whole operations channel and wants actionable alerts. Trigger a controlled error-rate alert, verify its pending/firing transition and confirm the correct team receives a grouped notification. This is the relevant test because alert rules evaluate time-series expressions while Alertmanager groups, routes and silences notifications; neither automatically fixes the underlying workload.
Incorrect Answers
This check would help evaluate the distinct objective “Use labels and selectors to connect resources predictably”, but not the required result. For this case, trigger a controlled error-rate alert, verify its pending/firing transition and confirm the correct team receives a grouped notification.
The situation is that a college lab sends every transient CPU spike to the whole operations channel and wants actionable alerts. This check would help evaluate the distinct objective “Understand Prometheus pull-based metrics collection and exporters”, but not the required result. For this case, trigger a controlled error-rate alert, verify its pending/firing transition and confirm the correct team receives a grouped notification.
This check would help evaluate the distinct objective “Use SLI and SLO measures to focus reliability objectives”, but not the required result. For this case, trigger a controlled error-rate alert, verify its pending/firing transition and confirm the correct team receives a grouped notification.
Question 909
A college lab sends every transient CPU spike to the whole operations channel and wants actionable alerts. The change review contains this proposal: “Create an immediate alert on every small CPU fluctuation and send it separately to all staff without ownership.” What risk matters most?
Explanation
Correct Answer
The situation is that a college lab sends every transient CPU spike to the whole operations channel and wants actionable alerts. Alert fatigue hides significant incidents while normal autoscaling bursts generate excessive pages. The shortcut creates this risk because alert rules evaluate time-series expressions while Alertmanager groups, routes and silences notifications; neither automatically fixes the underlying workload.
Incorrect Answers
That outcome concerns the distinct objective “Use SLI and SLO measures to focus reliability objectives”; it is not the most direct consequence of this shortcut. The relevant consequence is that alert fatigue hides significant incidents while normal autoscaling bursts generate excessive pages.
That outcome concerns the distinct objective “Understand open standards and vendor-neutral community collaboration”; it is not the most direct consequence of this shortcut. The relevant consequence is that alert fatigue hides significant incidents while normal autoscaling bursts generate excessive pages.
That outcome concerns the distinct objective “Use cordon and drain with disruption considerations for planned node maintenance”; it is not the most direct consequence of this shortcut. The relevant consequence is that alert fatigue hides significant incidents while normal autoscaling bursts generate excessive pages.
Question 910
A college lab sends every transient CPU spike to the whole operations channel and wants actionable alerts. Which implementation together with matching acceptance evidence best meets this case?
Explanation
Correct Answer
The situation is that a college lab sends every transient CPU spike to the whole operations channel and wants actionable alerts. Define symptom-based Prometheus alerting rules with sensible durations and route alerts through Alertmanager to the responsible service team. Acceptance evidence: Trigger a controlled error-rate alert, verify its pending/firing transition and confirm the correct team receives a grouped notification. This pairing is justified because alert rules evaluate time-series expressions while Alertmanager groups, routes and silences notifications; neither automatically fixes the underlying workload.
Incorrect Answers
This action and check address the distinct objective “Understand Prometheus pull-based metrics collection and exporters” instead of the stated acceptance requirement. The matching action is to define symptom-based Prometheus alerting rules with sensible durations and route alerts through Alertmanager to the responsible service team. Its confirming test is to trigger a controlled error-rate alert, verify its pending/firing transition and confirm the correct team receives a grouped notification.
This action and check address the distinct objective “Interpret ReplicaSet ownership and selectors in a Deployment” instead of the stated acceptance requirement. The matching action is to define symptom-based Prometheus alerting rules with sensible durations and route alerts through Alertmanager to the responsible service team. Its confirming test is to trigger a controlled error-rate alert, verify its pending/firing transition and confirm the correct team receives a grouped notification.
This action and check address the distinct objective “Contrast cloud-native microservices with a monolith without treating either as inherently superior” instead of the stated acceptance requirement. The matching action is to define symptom-based Prometheus alerting rules with sensible durations and route alerts through Alertmanager to the responsible service team. Its confirming test is to trigger a controlled error-rate alert, verify its pending/firing transition and confirm the correct team receives a grouped notification.
Kubernetes and Cloud Native Associate (KCNA) Practice Tests
- Linux Foundation KCNA Practice Test 89 - 10 Questions (Last Reviewed 20-Oct-2026)
- Linux Foundation KCNA Practice Test 90 - 10 Questions (Last Reviewed 19-Oct-2026)
- Linux Foundation KCNA Practice Test 91 - 10 Questions (Last Reviewed 18-Oct-2026)
- Linux Foundation KCNA Practice Test 92 - 10 Questions (Last Reviewed 17-Oct-2026)
- Linux Foundation KCNA Practice Test 93 - 10 Questions (Last Reviewed 16-Oct-2026)