Linux Foundation KCNA Dumps
Linux Foundation KCNA Practice Test 90
Question 890
A school app records metrics but cannot explain which request to a partner service failed. Which implementation together with matching acceptance evidence best meets this case?
Explanation
Correct Answer
The situation is that a school app records metrics but cannot explain which request to a partner service failed. Use metrics for measurable trends, logs for event detail and distributed traces for individual transaction paths while sharing correlation identifiers. Acceptance evidence: Send a synthetic request with a correlation ID and confirm it appears in the trace and relevant logs while latency metrics change. This pairing is justified because each telemetry type represents a different view of runtime state and links through context can connect a symptom to a specific service hop.
Incorrect Answers
This action and check address the distinct objective “Understand service proxy implementations without assuming kube-proxy is mandatory” instead of the stated acceptance requirement. The matching action is to use metrics for measurable trends, logs for event detail and distributed traces for individual transaction paths while sharing correlation identifiers. Its confirming test is to send a synthetic request with a correlation ID and confirm it appears in the trace and relevant logs while latency metrics change.
This action and check address the distinct objective “Apply cloud-native portability and immutable infrastructure principles pragmatically” instead of the stated acceptance requirement. The matching action is to use metrics for measurable trends, logs for event detail and distributed traces for individual transaction paths while sharing correlation identifiers. Its confirming test is to send a synthetic request with a correlation ID and confirm it appears in the trace and relevant logs while latency metrics change.
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 use metrics for measurable trends, logs for event detail and distributed traces for individual transaction paths while sharing correlation identifiers. Its confirming test is to send a synthetic request with a correlation ID and confirm it appears in the trace and relevant logs while latency metrics change.
Question 891
A museum runs a metric exporter for the number of requests handled by its public catalog. Which engineering approach is the most appropriate for this cloud-native case?
Explanation
Correct Answer
Expose appropriately labeled /metrics endpoints or exporters and configure Prometheus scrape targets to collect time-series measurements. This resolves the issue because prometheus commonly pulls numeric samples from configured targets, stores them as labeled time series and supports PromQL queries over those samples. To verify, verify a synthetic exporter is listed UP in Prometheus target status and query its request counter after generating traffic.
Incorrect Answers
This option addresses the distinct objective “Explain metrics, logs and traces as complementary observability signals”, not the immediate requirement. Each telemetry type represents a different view of runtime state and links through context can connect a symptom to a specific service hop. For the stated case, prometheus commonly pulls numeric samples from configured targets, stores them as labeled time series and supports PromQL queries over those samples.
This option addresses the distinct objective “Explain Linux namespaces and cgroups as distinct container isolation mechanisms”, not the immediate requirement. Linux namespaces affect visibility and isolation boundaries, while cgroups organize and limit resource usage; neither automatically supplies a full virtual machine. For the stated case, prometheus commonly pulls numeric samples from configured targets, stores them as labeled time series and supports PromQL queries over those samples.
This option addresses the distinct objective “Identify CNCF ecosystem projects by their role rather than assuming all are Kubernetes core”, not the immediate requirement. CNCF projects address different layers of a cloud-native platform and interoperability does not turn them into interchangeable cluster control-plane components. For the stated case, prometheus commonly pulls numeric samples from configured targets, stores them as labeled time series and supports PromQL queries over those samples.
Question 892
A museum runs a metric exporter for the number of requests handled by its public catalog. What infrastructure principle makes the correct treatment effective?
Explanation
Correct Answer
Prometheus commonly pulls numeric samples from configured targets, stores them as labeled time series and supports PromQL queries over those samples. It supports this action: Expose appropriately labeled /metrics endpoints or exporters and configure Prometheus scrape targets to collect time-series measurements. To confirm, verify a synthetic exporter is listed UP in Prometheus target status and query its request counter after generating traffic.
Incorrect Answers
That statement explains the distinct objective “Define secure release governance with staged approvals and policy verification” rather than the cause in this case. The deciding mechanism here is that prometheus commonly pulls numeric samples from configured targets, stores them as labeled time series and supports PromQL queries over those samples.
That statement explains the distinct objective “Instrument services with OpenTelemetry context propagation” rather than the cause in this case. The deciding mechanism here is that prometheus commonly pulls numeric samples from configured targets, stores them as labeled time series and supports PromQL queries over those samples.
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 prometheus commonly pulls numeric samples from configured targets, stores them as labeled time series and supports PromQL queries over those samples.
Question 893
A museum runs a metric exporter for the number of requests handled by its public catalog. What verification result would most convincingly distinguish a working solution from a claim?
Explanation
Correct Answer
Verify a synthetic exporter is listed UP in Prometheus target status and query its request counter after generating traffic. This is the relevant test 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 check would help evaluate the distinct objective “Understand open standards and vendor-neutral community collaboration”, but not the required result. For this case, verify a synthetic exporter is listed UP in Prometheus target status and query its request counter after generating traffic.
This check would help evaluate the distinct objective “Instrument services with OpenTelemetry context propagation”, but not the required result. For this case, verify a synthetic exporter is listed UP in Prometheus target status and query its request counter after generating traffic.
This check would help evaluate the distinct objective “Verify CoreDNS resolution and namespace-qualified Service names”, but not the required result. For this case, verify a synthetic exporter is listed UP in Prometheus target status and query its request counter after generating traffic.
Question 894
A museum runs a metric exporter for the number of requests handled by its public catalog. The change review contains this proposal: “Install Prometheus without configuring any scrape target and assume it automatically records every application request.” What risk matters most?
Explanation
Correct Answer
Monitoring dashboards show empty or stale series because the expected metrics were never exposed or scraped. The shortcut creates this risk because prometheus commonly pulls numeric samples from configured targets, stores them as labeled time series and supports PromQL queries over those samples.
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 monitoring dashboards show empty or stale series because the expected metrics were never exposed or scraped.
That outcome concerns the distinct objective “Identify reconciliation work performed by kube-controller-manager”; it is not the most direct consequence of this shortcut. The relevant consequence is that monitoring dashboards show empty or stale series because the expected metrics were never exposed or scraped.
That outcome concerns the distinct objective “Build meaningful alert rules and route notifications through Alertmanager”; it is not the most direct consequence of this shortcut. The relevant consequence is that monitoring dashboards show empty or stale series because the expected metrics were never exposed or scraped.
Question 895
A museum runs a metric exporter for the number of requests handled by its public catalog. Which implementation together with matching acceptance evidence best meets this case?
Explanation
Correct Answer
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 “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.
This action and check address the distinct objective “Distinguish service mesh traffic management from external ingress routing” 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 “Enforce workload service account token boundaries and avoid needless mounts” 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 896
A small insurer wants to distinguish a Prometheus scraping failure from a genuinely idle API. Which Kubernetes or cloud-native implementation decision best solves the stated problem?
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. This resolves the issue because prometheus commonly pulls numeric samples from configured targets, stores them as labeled time series and supports PromQL queries over those samples. To verify, verify a synthetic exporter is listed UP in Prometheus target status and query its request counter after generating traffic.
Incorrect Answers
The situation is that a small insurer wants to distinguish a Prometheus scraping failure from a genuinely idle API. This option addresses the distinct objective “Explain metrics, logs and traces as complementary observability signals”, not the immediate requirement. Each telemetry type represents a different view of runtime state and links through context can connect a symptom to a specific service hop. For the stated case, prometheus commonly pulls numeric samples from configured targets, stores them as labeled time series and supports PromQL queries over those samples.
This option addresses the distinct objective “Separate multi-tenant namespace governance from actual isolation guarantees”, not the immediate requirement. Namespaces alone partition naming but do not provide complete security isolation, capacity governance or protection from privileged node-level workloads. For the stated case, prometheus commonly pulls numeric samples from configured targets, stores them as labeled time series and supports PromQL queries over those samples.
This option addresses the distinct objective “Understand CNCF project maturity stages without equating them to security approval”, not the immediate requirement. CNCF maturity describes aspects of adoption and governance, not a blanket guarantee that every deployment or version is free of defects. For the stated case, prometheus commonly pulls numeric samples from configured targets, stores them as labeled time series and supports PromQL queries over those samples.
Question 897
A small insurer wants to distinguish a Prometheus scraping failure from a genuinely idle API. Which platform mechanism explains why the suitable approach works?
Explanation
Correct Answer
The situation is that a small insurer wants to distinguish a Prometheus scraping failure from a genuinely idle API. Prometheus commonly pulls numeric samples from configured targets, stores them as labeled time series and supports PromQL queries over those samples. It supports this action: Expose appropriately labeled /metrics endpoints or exporters and configure Prometheus scrape targets to collect time-series measurements. To confirm, verify a synthetic exporter is listed UP in Prometheus target status and query its request counter after generating traffic.
Incorrect Answers
That statement explains the distinct objective “Understand CNCF project maturity stages without equating them to security approval” rather than the cause in this case. The deciding mechanism here is that prometheus commonly pulls numeric samples from configured targets, stores them as labeled time series and supports PromQL queries over those samples.
That statement explains the distinct objective “Use cordon and drain with disruption considerations for planned node maintenance” rather than the cause in this case. The deciding mechanism here is that prometheus commonly pulls numeric samples from configured targets, stores them as labeled time series and supports PromQL queries over those samples.
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 prometheus commonly pulls numeric samples from configured targets, stores them as labeled time series and supports PromQL queries over those samples.
Question 898
A small insurer wants to distinguish a Prometheus scraping failure from a genuinely idle API. Which controlled observation would best validate the intended improvement?
Explanation
Correct Answer
The situation is that a small insurer wants to distinguish a Prometheus scraping failure from a genuinely idle API. Verify a synthetic exporter is listed UP in Prometheus target status and query its request counter after generating traffic. This is the relevant test because prometheus commonly pulls numeric samples from configured targets, stores them as labeled time series and supports PromQL queries over those samples.
Incorrect Answers
The situation is that a small insurer wants to distinguish a Prometheus scraping failure from a genuinely idle API. This check would help evaluate the distinct objective “Instrument services with OpenTelemetry context propagation”, but not the required result. For this case, verify a synthetic exporter is listed UP in Prometheus target status and query its request counter after generating traffic.
This check would help evaluate the distinct objective “Use Pod anti-affinity to reduce correlated replica failure”, but not the required result. For this case, verify a synthetic exporter is listed UP in Prometheus target status and query its request counter after generating traffic.
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, verify a synthetic exporter is listed UP in Prometheus target status and query its request counter after generating traffic.
Question 899
A small insurer wants to distinguish a Prometheus scraping failure from a genuinely idle API. An engineer proposes: “Install Prometheus without configuring any scrape target and assume it automatically records every application request.” What adverse outcome would be most direct?
Explanation
Correct Answer
The situation is that a small insurer wants to distinguish a Prometheus scraping failure from a genuinely idle API. Monitoring dashboards show empty or stale series because the expected metrics were never exposed or scraped. The shortcut creates this risk because prometheus commonly pulls numeric samples from configured targets, stores them as labeled time series and supports PromQL queries over those samples.
Incorrect Answers
That outcome concerns the distinct objective “Distinguish service mesh traffic management from external ingress routing”; it is not the most direct consequence of this shortcut. The relevant consequence is that monitoring dashboards show empty or stale series because the expected metrics were never exposed or scraped.
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 monitoring dashboards show empty or stale series because the expected metrics were never exposed or scraped.
That outcome concerns the distinct objective “Use HorizontalPodAutoscaler metrics rather than ad hoc instance scripts”; it is not the most direct consequence of this shortcut. The relevant consequence is that monitoring dashboards show empty or stale series because the expected metrics were never exposed or scraped.
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.
Kubernetes and Cloud Native Associate (KCNA) Practice Tests
- Linux Foundation KCNA Practice Test 88 - 10 Questions (Last Reviewed 21-Oct-2026)
- 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)