Linux Foundation KCNA Dumps
Linux Foundation KCNA Practice Test 89
Question 880
A university's course search depends on three services and needs to identify which hop adds most latency. What pair of supported action and practical verification should be approved?
Explanation
Correct Answer
The situation is that a university's course search depends on three services and needs to identify which hop adds most latency. Measure request latency and error rates, inspect application logs and correlate trace spans for the affected request before guessing which Pod is slow. Acceptance evidence: Generate a synthetic slow downstream call and verify a trace links frontend and backend spans while metrics show the latency change. This pairing is justified because metrics reveal aggregate trends, logs record events and traces connect operations across services, so each signal answers a different debugging question.
Incorrect Answers
This action and check address the distinct objective “Use ephemeral debugging containers only with appropriate permission and safeguards” instead of the stated acceptance requirement. The matching action is to measure request latency and error rates, inspect application logs and correlate trace spans for the affected request before guessing which Pod is slow. Its confirming test is to generate a synthetic slow downstream call and verify a trace links frontend and backend spans while metrics show the latency change.
This action and check address the distinct objective “Design a release rollback trigger from measurable service signals” instead of the stated acceptance requirement. The matching action is to measure request latency and error rates, inspect application logs and correlate trace spans for the affected request before guessing which Pod is slow. Its confirming test is to generate a synthetic slow downstream call and verify a trace links frontend and backend spans while metrics show the latency change.
This action and check address the distinct objective “Verify CoreDNS resolution and namespace-qualified Service names” instead of the stated acceptance requirement. The matching action is to measure request latency and error rates, inspect application logs and correlate trace spans for the affected request before guessing which Pod is slow. Its confirming test is to generate a synthetic slow downstream call and verify a trace links frontend and backend spans while metrics show the latency change.
Question 881
A regional bank adds observability to a payment flow involving several internal services. What technical action should the platform team take in this situation?
Explanation
Correct Answer
Use metrics for measurable trends, logs for event detail and distributed traces for individual transaction paths while sharing correlation identifiers. This resolves the issue because each telemetry type represents a different view of runtime state and links through context can connect a symptom to a specific service hop. To verify, send a synthetic request with a correlation ID and confirm it appears in the trace and relevant logs while latency metrics change.
Incorrect Answers
This option addresses the distinct objective “Build meaningful alert rules and route notifications through Alertmanager”, not the immediate requirement. Alert rules evaluate time-series expressions while Alertmanager groups, routes and silences notifications; neither automatically fixes the underlying workload. For the stated case, each telemetry type represents a different view of runtime state and links through context can connect a symptom to a specific service hop.
This option addresses the distinct objective “Use open community governance and contribution processes for sustainable cloud-native projects”, not the immediate requirement. Open-source community processes provide transparent review and shared maintenance, but do not imply unreviewed external code should be merged into production. For the stated case, each telemetry type represents a different view of runtime state and links through context can connect a symptom to a specific service hop.
This option addresses the distinct objective “Differentiate ServiceAccounts from human kubeconfig identities”, not the immediate requirement. ServiceAccounts provide workload identities for Kubernetes API access; human authentication and authorization are separately configured and should not be shared as static image secrets. For the stated case, each telemetry type represents a different view of runtime state and links through context can connect a symptom to a specific service hop.
Question 882
A regional bank adds observability to a payment flow involving several internal services. What underlying Kubernetes behavior is most relevant to this technical decision?
Explanation
Correct Answer
Each telemetry type represents a different view of runtime state and links through context can connect a symptom to a specific service hop. It supports this action: Use metrics for measurable trends, logs for event detail and distributed traces for individual transaction paths while sharing correlation identifiers. To confirm, send a synthetic request with a correlation ID and confirm it appears in the trace and relevant logs while latency metrics change.
Incorrect Answers
That statement explains the distinct objective “Separate multi-tenant namespace governance from actual isolation guarantees” rather than the cause in this case. The deciding mechanism here is that each telemetry type represents a different view of runtime state and links through context can connect a symptom to a specific service hop.
That statement explains the distinct objective “Build meaningful alert rules and route notifications through Alertmanager” rather than the cause in this case. The deciding mechanism here is that each telemetry type represents a different view of runtime state and links through context can connect a symptom to a specific service hop.
That statement explains the distinct objective “Identify CNCF ecosystem projects by their role rather than assuming all are Kubernetes core” rather than the cause in this case. The deciding mechanism here is that each telemetry type represents a different view of runtime state and links through context can connect a symptom to a specific service hop.
Question 883
A regional bank adds observability to a payment flow involving several internal services. What acceptance check most directly confirms this requirement is met?
Explanation
Correct Answer
Send a synthetic request with a correlation ID and confirm it appears in the trace and relevant logs while latency metrics change. This is the relevant test 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 check would help evaluate the distinct objective “Use ephemeral debugging containers only with appropriate permission and safeguards”, but not the required result. For this case, send a synthetic request with a correlation ID and confirm it appears in the trace and relevant logs while latency metrics change.
This check would help evaluate the distinct objective “Apply cloud-native portability and immutable infrastructure principles pragmatically”, but not the required result. For this case, send a synthetic request with a correlation ID and confirm it appears in the trace and relevant logs while latency metrics change.
This check would help evaluate the distinct objective “Build meaningful alert rules and route notifications through Alertmanager”, but not the required result. For this case, send a synthetic request with a correlation ID and confirm it appears in the trace and relevant logs while latency metrics change.
Question 884
A regional bank adds observability to a payment flow involving several internal services. The team suggests: “Treat a single CPU gauge as sufficient evidence to explain every failed customer transaction across microservices.” Which failure should the reviewer anticipate?
Explanation
Correct Answer
A backend exception can remain hidden even when CPU load looks normal. The shortcut creates this risk 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
That outcome concerns the distinct objective “Explain Linux namespaces and cgroups as distinct container isolation mechanisms”; it is not the most direct consequence of this shortcut. The relevant consequence is that a backend exception can remain hidden even when CPU load looks normal.
That outcome concerns the distinct objective “Understand CNCF project maturity stages without equating them to security approval”; it is not the most direct consequence of this shortcut. The relevant consequence is that a backend exception can remain hidden even when CPU load looks normal.
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 a backend exception can remain hidden even when CPU load looks normal.
Question 885
A regional bank adds observability to a payment flow involving several internal services. Which engineering change and test jointly addresses the scenario?
Explanation
Correct Answer
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 “Distinguish ConfigMaps from Secrets and avoid storing credentials in public configuration” 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 “Build meaningful alert rules and route notifications through Alertmanager” 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 “Distinguish service mesh traffic management from external ingress routing” 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 886
A school app records metrics but cannot explain which request to a partner service failed. Which engineering approach is the most appropriate for this cloud-native 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. This resolves the issue because each telemetry type represents a different view of runtime state and links through context can connect a symptom to a specific service hop. To verify, send a synthetic request with a correlation ID and confirm it appears in the trace and relevant logs while latency metrics change.
Incorrect Answers
The situation is that a school app records metrics but cannot explain which request to a partner service failed. This option addresses the distinct objective “Build meaningful alert rules and route notifications through Alertmanager”, not the immediate requirement. Alert rules evaluate time-series expressions while Alertmanager groups, routes and silences notifications; neither automatically fixes the underlying workload. For the stated case, each telemetry type represents a different view of runtime state and links through context can connect a symptom to a specific service hop.
This option addresses the distinct objective “Investigate readiness failures separately from liveness-related restarts”, not the immediate requirement. A failed readiness probe removes a Pod from ready Service endpoints, while failed liveness checks can restart a process; their operational consequences differ. For the stated case, each telemetry type represents a different view of runtime state and links through context can connect a symptom to a specific service hop.
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, each telemetry type represents a different view of runtime state and links through context can connect a symptom to a specific service hop.
Question 887
A school app records metrics but cannot explain which request to a partner service failed. What infrastructure principle makes the correct treatment effective?
Explanation
Correct Answer
The situation is that a school app records metrics but cannot explain which request to a partner service failed. Each telemetry type represents a different view of runtime state and links through context can connect a symptom to a specific service hop. It supports this action: Use metrics for measurable trends, logs for event detail and distributed traces for individual transaction paths while sharing correlation identifiers. To confirm, send a synthetic request with a correlation ID and confirm it appears in the trace and relevant logs while latency metrics change.
Incorrect Answers
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 each telemetry type represents a different view of runtime state and links through context can connect a symptom to a specific service hop.
That statement explains the distinct objective “Understand open standards and vendor-neutral community collaboration” rather than the cause in this case. The deciding mechanism here is that each telemetry type represents a different view of runtime state and links through context can connect a symptom to a specific service hop.
That statement explains the distinct objective “Implement namespaced RBAC Roles for least-privilege resource permissions” rather than the cause in this case. The deciding mechanism here is that each telemetry type represents a different view of runtime state and links through context can connect a symptom to a specific service hop.
Question 888
A school app records metrics but cannot explain which request to a partner service failed. What verification result would most convincingly distinguish a working solution from a claim?
Explanation
Correct Answer
The situation is that a school app records metrics but cannot explain which request to a partner service failed. Send a synthetic request with a correlation ID and confirm it appears in the trace and relevant logs while latency metrics change. This is the relevant test 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 check would help evaluate the distinct objective “Identify CNCF ecosystem projects by their role rather than assuming all are Kubernetes core”, but not the required result. For this case, send a synthetic request with a correlation ID and confirm it appears in the trace and relevant logs while latency metrics change.
This check would help evaluate the distinct objective “Distinguish a container image from a running container and its writable layer”, but not the required result. For this case, send a synthetic request with a correlation ID and confirm it appears in the trace and relevant logs while latency metrics change.
This check would help evaluate the distinct objective “Instrument services with OpenTelemetry context propagation”, but not the required result. For this case, send a synthetic request with a correlation ID and confirm it appears in the trace and relevant logs while latency metrics change.
Question 889
A school app records metrics but cannot explain which request to a partner service failed. The change review contains this proposal: “Treat a single CPU gauge as sufficient evidence to explain every failed customer transaction across microservices.” What risk matters most?
Explanation
Correct Answer
The situation is that a school app records metrics but cannot explain which request to a partner service failed. A backend exception can remain hidden even when CPU load looks normal. The shortcut creates this risk 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
That outcome concerns the distinct objective “Apply cloud-native portability and immutable infrastructure principles pragmatically”; it is not the most direct consequence of this shortcut. The relevant consequence is that a backend exception can remain hidden even when CPU load looks normal.
That outcome concerns the distinct objective “Recognize NetworkPolicy isolation only when the CNI enforces it”; it is not the most direct consequence of this shortcut. The relevant consequence is that a backend exception can remain hidden even when CPU load looks normal.
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 a backend exception can remain hidden even when CPU load looks normal.
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.
Kubernetes and Cloud Native Associate (KCNA) Practice Tests
- Linux Foundation KCNA Practice Test 87 - 10 Questions (Last Reviewed 22-Oct-2026)
- 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)