Linux Foundation KCNA Dumps
Linux Foundation KCNA Practice Test 92
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.
Question 911
A retailer's checkout request calls an inventory and tax service and needs one correlated trace. Which supported Kubernetes practice directly addresses the stated requirement?
Explanation
Correct Answer
Use OpenTelemetry SDKs and a collector to export appropriately sampled traces and metrics with stable service identities and trace context. This resolves the issue because trace context allows spans from different services to join one transaction view, while collectors receive and forward telemetry without automatically storing all data. To verify, run a request across two synthetic services and verify traceparent propagation and two linked spans in the configured backend.
Incorrect Answers
This option addresses the distinct objective “Understand service proxy implementations without assuming kube-proxy is mandatory”, not the immediate requirement. Kube-proxy can maintain node networking rules for Services, but supported network implementations may replace this function. For the stated case, trace context allows spans from different services to join one transaction view, while collectors receive and forward telemetry without automatically storing all data.
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, trace context allows spans from different services to join one transaction view, while collectors receive and forward telemetry without automatically storing all data.
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, trace context allows spans from different services to join one transaction view, while collectors receive and forward telemetry without automatically storing all data.
Question 912
A retailer's checkout request calls an inventory and tax service and needs one correlated trace. Which causal explanation supports the intended design choice?
Explanation
Correct Answer
Trace context allows spans from different services to join one transaction view, while collectors receive and forward telemetry without automatically storing all data. It supports this action: Use OpenTelemetry SDKs and a collector to export appropriately sampled traces and metrics with stable service identities and trace context. To confirm, run a request across two synthetic services and verify traceparent propagation and two linked spans in the configured backend.
Incorrect Answers
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 trace context allows spans from different services to join one transaction view, while collectors receive and forward telemetry without automatically storing all data.
That statement explains the distinct objective “Use namespaces as organizational scopes without treating them as firewalls” rather than the cause in this case. The deciding mechanism here is that trace context allows spans from different services to join one transaction view, while collectors receive and forward telemetry without automatically storing all data.
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 trace context allows spans from different services to join one transaction view, while collectors receive and forward telemetry without automatically storing all data.
Question 913
A retailer's checkout request calls an inventory and tax service and needs one correlated trace. Which test provides the strongest evidence of a correct implementation?
Explanation
Correct Answer
Run a request across two synthetic services and verify traceparent propagation and two linked spans in the configured backend. This is the relevant test because trace context allows spans from different services to join one transaction view, while collectors receive and forward telemetry without automatically storing all data.
Incorrect Answers
This check would help evaluate the distinct objective “Use Pods as the shared network and storage execution unit”, but not the required result. For this case, run a request across two synthetic services and verify traceparent propagation and two linked spans in the configured backend.
This check would help evaluate the distinct objective “Understand open standards and vendor-neutral community collaboration”, but not the required result. For this case, run a request across two synthetic services and verify traceparent propagation and two linked spans in the configured backend.
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, run a request across two synthetic services and verify traceparent propagation and two linked spans in the configured backend.
Question 914
A retailer's checkout request calls an inventory and tax service and needs one correlated trace. A shortcut is proposed: “Create new unrelated trace identifiers at every internal call and assume the collector reconstructs the complete transaction.” Which technical consequence follows most closely?
Explanation
Correct Answer
Cross-service latency remains difficult to diagnose because spans cannot be tied to one request path. The shortcut creates this risk because trace context allows spans from different services to join one transaction view, while collectors receive and forward telemetry without automatically storing all data.
Incorrect Answers
That outcome concerns the distinct objective “Understand readiness, liveness and startup probes as different signals”; it is not the most direct consequence of this shortcut. The relevant consequence is that cross-service latency remains difficult to diagnose because spans cannot be tied to one request path.
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 cross-service latency remains difficult to diagnose because spans cannot be tied to one request path.
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 cross-service latency remains difficult to diagnose because spans cannot be tied to one request path.
Question 915
A retailer's checkout request calls an inventory and tax service and needs one correlated trace. Which combined solution and independent check are most directly justified?
Explanation
Correct Answer
Use OpenTelemetry SDKs and a collector to export appropriately sampled traces and metrics with stable service identities and trace context. Acceptance evidence: Run a request across two synthetic services and verify traceparent propagation and two linked spans in the configured backend. This pairing is justified because trace context allows spans from different services to join one transaction view, while collectors receive and forward telemetry without automatically storing all data.
Incorrect Answers
This action and check address the distinct objective “Use image provenance and policy controls without trusting mutable tags” instead of the stated acceptance requirement. The matching action is to use OpenTelemetry SDKs and a collector to export appropriately sampled traces and metrics with stable service identities and trace context. Its confirming test is to run a request across two synthetic services and verify traceparent propagation and two linked spans in the configured backend.
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 use OpenTelemetry SDKs and a collector to export appropriately sampled traces and metrics with stable service identities and trace context. Its confirming test is to run a request across two synthetic services and verify traceparent propagation and two linked spans in the configured backend.
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 OpenTelemetry SDKs and a collector to export appropriately sampled traces and metrics with stable service identities and trace context. Its confirming test is to run a request across two synthetic services and verify traceparent propagation and two linked spans in the configured backend.
Question 916
A hospital develops observability without sending private patient fields as span attributes. Which engineering approach is the most appropriate for this cloud-native case?
Explanation
Correct Answer
The situation is that a hospital develops observability without sending private patient fields as span attributes. Use OpenTelemetry SDKs and a collector to export appropriately sampled traces and metrics with stable service identities and trace context. This resolves the issue because trace context allows spans from different services to join one transaction view, while collectors receive and forward telemetry without automatically storing all data. To verify, run a request across two synthetic services and verify traceparent propagation and two linked spans in the configured backend.
Incorrect Answers
This option addresses the distinct objective “Use container resource requests to help the scheduler fit Pods on nodes”, not the immediate requirement. The scheduler evaluates requests against node allocatable capacity; limits govern runtime ceilings and do not substitute for scheduling requests. For the stated case, trace context allows spans from different services to join one transaction view, while collectors receive and forward telemetry without automatically storing all data.
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, trace context allows spans from different services to join one transaction view, while collectors receive and forward telemetry without automatically storing all data.
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, trace context allows spans from different services to join one transaction view, while collectors receive and forward telemetry without automatically storing all data.
Question 917
A hospital develops observability without sending private patient fields as span attributes. What infrastructure principle makes the correct treatment effective?
Explanation
Correct Answer
The situation is that a hospital develops observability without sending private patient fields as span attributes. Trace context allows spans from different services to join one transaction view, while collectors receive and forward telemetry without automatically storing all data. It supports this action: Use OpenTelemetry SDKs and a collector to export appropriately sampled traces and metrics with stable service identities and trace context. To confirm, run a request across two synthetic services and verify traceparent propagation and two linked spans in the configured backend.
Incorrect Answers
That statement explains the distinct objective “Contrast cloud-native microservices with a monolith without treating either as inherently superior” rather than the cause in this case. The deciding mechanism here is that trace context allows spans from different services to join one transaction view, while collectors receive and forward telemetry without automatically storing all data.
That statement explains the distinct objective “Use an immutable image digest for exact deployment provenance” rather than the cause in this case. The deciding mechanism here is that trace context allows spans from different services to join one transaction view, while collectors receive and forward telemetry without automatically storing all data.
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 trace context allows spans from different services to join one transaction view, while collectors receive and forward telemetry without automatically storing all data.
Question 918
A hospital develops observability without sending private patient fields as span attributes. What verification result would most convincingly distinguish a working solution from a claim?
Explanation
Correct Answer
The situation is that a hospital develops observability without sending private patient fields as span attributes. Run a request across two synthetic services and verify traceparent propagation and two linked spans in the configured backend. This is the relevant test because trace context allows spans from different services to join one transaction view, while collectors receive and forward telemetry without automatically storing all data.
Incorrect Answers
This check would help evaluate the distinct objective “Explain metrics, logs and traces as complementary observability signals”, but not the required result. For this case, run a request across two synthetic services and verify traceparent propagation and two linked spans in the configured backend.
This check would help evaluate the distinct objective “Differentiate ServiceAccounts from human kubeconfig identities”, but not the required result. For this case, run a request across two synthetic services and verify traceparent propagation and two linked spans in the configured backend.
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, run a request across two synthetic services and verify traceparent propagation and two linked spans in the configured backend.
Question 919
A hospital develops observability without sending private patient fields as span attributes. The change review contains this proposal: “Create new unrelated trace identifiers at every internal call and assume the collector reconstructs the complete transaction.” What risk matters most?
Explanation
Correct Answer
The situation is that a hospital develops observability without sending private patient fields as span attributes. Cross-service latency remains difficult to diagnose because spans cannot be tied to one request path. The shortcut creates this risk because trace context allows spans from different services to join one transaction view, while collectors receive and forward telemetry without automatically storing all data.
Incorrect Answers
The situation is that a hospital develops observability without sending private patient fields as span attributes. 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 cross-service latency remains difficult to diagnose because spans cannot be tied to one request path.
That outcome concerns the distinct objective “Explain metrics, logs and traces as complementary observability signals”; it is not the most direct consequence of this shortcut. The relevant consequence is that cross-service latency remains difficult to diagnose because spans cannot be tied to one request path.
That outcome concerns the distinct objective “Distinguish memory limits from CPU throttling for scheduling and runtime symptoms”; it is not the most direct consequence of this shortcut. The relevant consequence is that cross-service latency remains difficult to diagnose because spans cannot be tied to one request path.
Question 920
A hospital develops observability without sending private patient fields as span attributes. Which implementation together with matching acceptance evidence best meets this case?
Explanation
Correct Answer
The situation is that a hospital develops observability without sending private patient fields as span attributes. Use OpenTelemetry SDKs and a collector to export appropriately sampled traces and metrics with stable service identities and trace context. Acceptance evidence: Run a request across two synthetic services and verify traceparent propagation and two linked spans in the configured backend. This pairing is justified because trace context allows spans from different services to join one transaction view, while collectors receive and forward telemetry without automatically storing all data.
Incorrect Answers
This action and check address the distinct objective “Protect API server access using authenticated TLS clients and audited authorization” instead of the stated acceptance requirement. The matching action is to use OpenTelemetry SDKs and a collector to export appropriately sampled traces and metrics with stable service identities and trace context. Its confirming test is to run a request across two synthetic services and verify traceparent propagation and two linked spans in the configured backend.
This action and check address the distinct objective “Understand open standards and vendor-neutral community collaboration” instead of the stated acceptance requirement. The matching action is to use OpenTelemetry SDKs and a collector to export appropriately sampled traces and metrics with stable service identities and trace context. Its confirming test is to run a request across two synthetic services and verify traceparent propagation and two linked spans in the configured backend.
This action and check address the distinct objective “Use SLI and SLO measures to focus reliability objectives” instead of the stated acceptance requirement. The matching action is to use OpenTelemetry SDKs and a collector to export appropriately sampled traces and metrics with stable service identities and trace context. Its confirming test is to run a request across two synthetic services and verify traceparent propagation and two linked spans in the configured backend.
Kubernetes and Cloud Native Associate (KCNA) Practice Tests
- 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)
- Linux Foundation KCNA Practice Test 94 - 10 Questions (Last Reviewed 15-Oct-2026)