Practice Exams:

Linux Foundation KCNA Dumps

EXAM: Kubernetes and Cloud Native Associate
Verified By Experts
Premium Bundle
$40.00
$59.97 $99.97

KCNA Premium Bundle


  • Premium File 333 Questions & Answers
  • Training Course 54 Lectures
  • Study Guide 410 Pages

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?

  1. Use an authorized kubectl debug ephemeral container when an application image lacks troubleshooting tools and policy permits ephemeral containers. Acceptance evidence: In a lab add a read-only debug container, inspect network conditions and verify audit logs record the ephemeral container action.
  2. Define post-release checks for readiness, error rate and latency, and revert an unhealthy revision using an approved rollout mechanism. Acceptance evidence: Deploy a synthetic faulty image, monitor request errors and confirm the release controller or operator restores the last known healthy revision.
  3. Use cluster DNS records such as service.namespace.svc.cluster.local when a Pod connects to Services in other namespaces. Acceptance evidence: Run nslookup for a Service using short and namespace-qualified names from test Pods in two different namespaces.
  4. 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.

Explanation

Correct Answer

D:

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

A:

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.

B:

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.

C:

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?

  1. Define symptom-based Prometheus alerting rules with sensible durations and route alerts through Alertmanager to the responsible service team.
  2. Follow a project's published governance, issue templates, contributor guides and code of conduct when reporting bugs or proposing changes.
  3. Give each workload an appropriate Kubernetes ServiceAccount and narrow RBAC permissions rather than embedding an administrator kubeconfig in its image.
  4. Use metrics for measurable trends, logs for event detail and distributed traces for individual transaction paths while sharing correlation identifiers.

Explanation

Correct Answer

D:

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

A:

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.

B:

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.

C:

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?

  1. Namespaces alone partition naming but do not provide complete security isolation, capacity governance or protection from privileged node-level workloads.
  2. Alert rules evaluate time-series expressions while Alertmanager groups, routes and silences notifications; neither automatically fixes the underlying workload.
  3. CNCF projects address different layers of a cloud-native platform and interoperability does not turn them into interchangeable cluster control-plane components.
  4. Each telemetry type represents a different view of runtime state and links through context can connect a symptom to a specific service hop.

Explanation

Correct Answer

D:

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

A:

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.

B:

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.

C:

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?

  1. In a lab add a read-only debug container, inspect network conditions and verify audit logs record the ephemeral container action.
  2. Deploy a synthetic stateless workload to two conformant clusters and record which storage, ingress and identity settings require changes.
  3. Trigger a controlled error-rate alert, verify its pending/firing transition and confirm the correct team receives a grouped notification.
  4. Send a synthetic request with a correlation ID and confirm it appears in the trace and relevant logs while latency metrics change.

Explanation

Correct Answer

D:

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

A:

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.

B:

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.

C:

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?

  1. A backend exception can remain hidden even when CPU load looks normal.
  2. Security decisions overlook shared-kernel attack surfaces and workload-specific resource contention.
  3. A trusted community label is misused as a substitute for secure configuration and maintenance.
  4. Cross-service latency remains difficult to diagnose because spans cannot be tied to one request path.

Explanation

Correct Answer

A:

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

B:

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.

C:

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.

D:

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?

  1. 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.
  2. Put non-sensitive application settings in ConfigMaps and put credentials in Secret objects with RBAC, encryption and external secret-management safeguards where appropriate. Acceptance evidence: Inspect synthetic ConfigMap and Secret manifests, then test that an unprivileged ServiceAccount cannot read the private Secret.
  3. 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.
  4. Use a supported service mesh when fine-grained internal service-to-service security and telemetry are needed, while separately configuring north-south ingress or gateway exposure. Acceptance evidence: Test a synthetic internal service call with mutual TLS policy and separately inspect the public Gateway listener and route status.

Explanation

Correct Answer

A:

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

B:

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.

C:

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.

D:

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?

  1. Define symptom-based Prometheus alerting rules with sensible durations and route alerts through Alertmanager to the responsible service team.
  2. Inspect probe configuration, Pod Ready conditions and restart events to identify whether traffic eligibility or container execution is failing.
  3. Use metrics for measurable trends, logs for event detail and distributed traces for individual transaction paths while sharing correlation identifiers.
  4. Expose appropriately labeled /metrics endpoints or exporters and configure Prometheus scrape targets to collect time-series measurements.

Explanation

Correct Answer

C:

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

A:

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.

B:

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.

D:

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?

  1. Trace context allows spans from different services to join one transaction view, while collectors receive and forward telemetry without automatically storing all data.
  2. Open standards and vendor-neutral governance reduce lock-in and support collaboration, but products can still differ in versions, implementations and operational capabilities.
  3. RBAC evaluates API verbs, resources and scope; a Role is namespaced and does not grant cluster-wide access merely because the subject can authenticate.
  4. Each telemetry type represents a different view of runtime state and links through context can connect a symptom to a specific service hop.

Explanation

Correct Answer

D:

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

A:

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.

B:

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.

C:

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?

  1. Build a study architecture diagram that connects each tool to its documented function and verify the expected data flow in a sample environment.
  2. Send a synthetic request with a correlation ID and confirm it appears in the trace and relevant logs while latency metrics change.
  3. Build a test image, run a Pod and recreate it, verifying packaged files remain while an unmounted temporary file disappears.
  4. Run a request across two synthetic services and verify traceparent propagation and two linked spans in the configured backend.

Explanation

Correct Answer

B:

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

A:

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.

C:

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.

D:

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?

  1. A backend exception can remain hidden even when CPU load looks normal.
  2. A migration fails because backend volume classes and cloud authentication semantics differ.
  3. Sensitive traffic may remain allowed because the networking implementation does not enforce the declared policy.
  4. Alert fatigue hides significant incidents while normal autoscaling bursts generate excessive pages.

Explanation

Correct Answer

A:

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

B:

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.

C:

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.

D:

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?

  1. Identify whether the cluster uses kube-proxy or an alternative Service dataplane before diagnosing virtual Service IP forwarding behavior. Acceptance evidence: Read the cluster networking configuration, find a test Service and verify backend connectivity using the installed dataplane.
  2. 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.
  3. Package workloads in standard images and declarative manifests while documenting external dependencies and provider-specific integrations before claiming portability. Acceptance evidence: Deploy a synthetic stateless workload to two conformant clusters and record which storage, ingress and identity settings require changes.
  4. 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.

Explanation

Correct Answer

B:

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

A:

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.

C:

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.

D:

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