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 93

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?

  1. Require verified API server certificates, properly scoped identities and audit policy rather than turning off certificate checks for convenience. Acceptance evidence: With synthetic users verify a trusted API connection, denied privilege escalation and appropriate audit entries for failed requests.
  2. Prefer documented Kubernetes APIs and interoperable telemetry formats when possible while identifying any platform-specific extensions needed for the real deployment. Acceptance evidence: Test a synthetic standard API manifest and OpenTelemetry trace export across two platforms, documenting any unsupported extensions.
  3. Define a user-centered service level indicator and objective, such as percentage of successful requests within a latency threshold over a stated window. Acceptance evidence: Calculate a synthetic seven-day success ratio from request metrics and compare it to the agreed target before a risky rollout.
  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

D:

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

A:

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.

B:

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.

C:

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.

Question 921

A public permit portal has an agreed 99.9 percent successful request objective. Which engineering approach is the most appropriate for this cloud-native case?

  1. Use metrics for measurable trends, logs for event detail and distributed traces for individual transaction paths while sharing correlation identifiers.
  2. Give each workload an appropriate Kubernetes ServiceAccount and narrow RBAC permissions rather than embedding an administrator kubeconfig in its image.
  3. Define a user-centered service level indicator and objective, such as percentage of successful requests within a latency threshold over a stated window.
  4. Choose service boundaries around business capabilities and operational needs, documenting communication cost, ownership and fault tolerance.

Explanation

Correct Answer

C:

Define a user-centered service level indicator and objective, such as percentage of successful requests within a latency threshold over a stated window. This resolves the issue because a service level objective is a target for measured user-facing behavior; error budgets quantify allowed misses and help prioritize release risk. To verify, calculate a synthetic seven-day success ratio from request metrics and compare it to the agreed target before a risky rollout.

Incorrect Answers

A:

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, a service level objective is a target for measured user-facing behavior; error budgets quantify allowed misses and help prioritize release risk.

B:

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, a service level objective is a target for measured user-facing behavior; error budgets quantify allowed misses and help prioritize release risk.

D:

This option addresses the distinct objective “Contrast cloud-native microservices with a monolith without treating either as inherently superior”, not the immediate requirement. Microservices permit independent deployment and scaling but introduce network dependencies and data consistency challenges; a monolith can remain appropriate for smaller teams. For the stated case, a service level objective is a target for measured user-facing behavior; error budgets quantify allowed misses and help prioritize release risk.

Question 922

A public permit portal has an agreed 99.9 percent successful request objective. What infrastructure principle makes the correct treatment effective?

  1. Alert rules evaluate time-series expressions while Alertmanager groups, routes and silences notifications; neither automatically fixes the underlying workload.
  2. Prometheus commonly pulls numeric samples from configured targets, stores them as labeled time series and supports PromQL queries over those samples.
  3. Containers in a Pod share a network namespace and IP address and can coordinate on localhost, while the Pod is scheduled as one unit.
  4. A service level objective is a target for measured user-facing behavior; error budgets quantify allowed misses and help prioritize release risk.

Explanation

Correct Answer

D:

A service level objective is a target for measured user-facing behavior; error budgets quantify allowed misses and help prioritize release risk. It supports this action: Define a user-centered service level indicator and objective, such as percentage of successful requests within a latency threshold over a stated window. To confirm, calculate a synthetic seven-day success ratio from request metrics and compare it to the agreed target before a risky rollout.

Incorrect Answers

A:

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 a service level objective is a target for measured user-facing behavior; error budgets quantify allowed misses and help prioritize release risk.

B:

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 a service level objective is a target for measured user-facing behavior; error budgets quantify allowed misses and help prioritize release risk.

C:

That statement explains the distinct objective “Use Pods as the shared network and storage execution unit” rather than the cause in this case. The deciding mechanism here is that a service level objective is a target for measured user-facing behavior; error budgets quantify allowed misses and help prioritize release risk.

Question 923

A public permit portal has an agreed 99.9 percent successful request objective. What verification result would most convincingly distinguish a working solution from a claim?

  1. Test that one synthetic tenant cannot list another namespace's Secrets, send blocked traffic or exceed quota.
  2. Calculate a synthetic seven-day success ratio from request metrics and compare it to the agreed target before a risky rollout.
  3. Send a synthetic request with a correlation ID and confirm it appears in the trace and relevant logs while latency metrics change.
  4. Model a synthetic two-service checkout dependency and compare rollout independence with failure and latency overhead against a single service.

Explanation

Correct Answer

B:

Calculate a synthetic seven-day success ratio from request metrics and compare it to the agreed target before a risky rollout. This is the relevant test because a service level objective is a target for measured user-facing behavior; error budgets quantify allowed misses and help prioritize release risk.

Incorrect Answers

A:

This check would help evaluate the distinct objective “Separate multi-tenant namespace governance from actual isolation guarantees”, but not the required result. For this case, calculate a synthetic seven-day success ratio from request metrics and compare it to the agreed target before a risky rollout.

C:

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, calculate a synthetic seven-day success ratio from request metrics and compare it to the agreed target before a risky rollout.

D:

This check would help evaluate the distinct objective “Contrast cloud-native microservices with a monolith without treating either as inherently superior”, but not the required result. For this case, calculate a synthetic seven-day success ratio from request metrics and compare it to the agreed target before a risky rollout.

Question 924

A public permit portal has an agreed 99.9 percent successful request objective. The change review contains this proposal: “Declare an uptime target achieved from the number of Running Pods while ignoring failed user requests.” What risk matters most?

  1. The reported reliability can look excellent while customer transactions routinely fail or exceed acceptable latency.
  2. Alert fatigue hides significant incidents while normal autoscaling bursts generate excessive pages.
  3. The application never becomes operational because packaging metadata is confused with cluster reconciliation.
  4. Applications fail on migration when plugin behavior or provider-specific components were never evaluated.

Explanation

Correct Answer

A:

The reported reliability can look excellent while customer transactions routinely fail or exceed acceptable latency. The shortcut creates this risk because a service level objective is a target for measured user-facing behavior; error budgets quantify allowed misses and help prioritize release risk.

Incorrect Answers

B:

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 the reported reliability can look excellent while customer transactions routinely fail or exceed acceptable latency.

C:

That outcome concerns the distinct objective “Use Helm charts for parameterized application packages without equating them to cluster controllers”; it is not the most direct consequence of this shortcut. The relevant consequence is that the reported reliability can look excellent while customer transactions routinely fail or exceed acceptable latency.

D:

That outcome concerns the distinct objective “Understand open standards and vendor-neutral community collaboration”; it is not the most direct consequence of this shortcut. The relevant consequence is that the reported reliability can look excellent while customer transactions routinely fail or exceed acceptable latency.

Question 925

A public permit portal has an agreed 99.9 percent successful request objective. Which implementation together with matching acceptance evidence best meets this case?

  1. Inspect probe configuration, Pod Ready conditions and restart events to identify whether traffic eligibility or container execution is failing. Acceptance evidence: Induce a temporary readiness failure in staging and verify traffic stops without a restart; then separately test controlled liveness failure.
  2. Define a user-centered service level indicator and objective, such as percentage of successful requests within a latency threshold over a stated window. Acceptance evidence: Calculate a synthetic seven-day success ratio from request metrics and compare it to the agreed target before a risky rollout.
  3. 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.
  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

B:

Define a user-centered service level indicator and objective, such as percentage of successful requests within a latency threshold over a stated window. Acceptance evidence: Calculate a synthetic seven-day success ratio from request metrics and compare it to the agreed target before a risky rollout. This pairing is justified because a service level objective is a target for measured user-facing behavior; error budgets quantify allowed misses and help prioritize release risk.

Incorrect Answers

A:

This action and check address the distinct objective “Investigate readiness failures separately from liveness-related restarts” instead of the stated acceptance requirement. The matching action is to define a user-centered service level indicator and objective, such as percentage of successful requests within a latency threshold over a stated window. Its confirming test is to calculate a synthetic seven-day success ratio from request metrics and compare it to the agreed target before a risky rollout.

C:

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 define a user-centered service level indicator and objective, such as percentage of successful requests within a latency threshold over a stated window. Its confirming test is to calculate a synthetic seven-day success ratio from request metrics and compare it to the agreed target before a risky rollout.

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 define a user-centered service level indicator and objective, such as percentage of successful requests within a latency threshold over a stated window. Its confirming test is to calculate a synthetic seven-day success ratio from request metrics and compare it to the agreed target before a risky rollout.

Question 926

A cooperative wants to decide whether to freeze new deployments after repeated payment API incidents. Which supported Kubernetes practice directly addresses the stated requirement?

  1. Define a user-centered service level indicator and objective, such as percentage of successful requests within a latency threshold over a stated window.
  2. Define symptom-based Prometheus alerting rules with sensible durations and route alerts through Alertmanager to the responsible service team.
  3. Use a Deployment for a replicated stateless application requiring rolling updates and replacement of failed Pods.
  4. Review Sandbox, Incubating and Graduated CNCF stages as community maturity signals while independently assessing a project's fitness, lifecycle and security.

Explanation

Correct Answer

A:

The situation is that a cooperative wants to decide whether to freeze new deployments after repeated payment API incidents. Define a user-centered service level indicator and objective, such as percentage of successful requests within a latency threshold over a stated window. This resolves the issue because a service level objective is a target for measured user-facing behavior; error budgets quantify allowed misses and help prioritize release risk. To verify, calculate a synthetic seven-day success ratio from request metrics and compare it to the agreed target before a risky rollout.

Incorrect Answers

B:

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, a service level objective is a target for measured user-facing behavior; error budgets quantify allowed misses and help prioritize release risk.

C:

This option addresses the distinct objective “Distinguish Deployment desired state from a manually created Pod”, not the immediate requirement. A Deployment owns ReplicaSets that manage matching Pods and supports declarative rollout history, unlike an independent Pod object. For the stated case, a service level objective is a target for measured user-facing behavior; error budgets quantify allowed misses and help prioritize release risk.

D:

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, a service level objective is a target for measured user-facing behavior; error budgets quantify allowed misses and help prioritize release risk.

Question 927

A cooperative wants to decide whether to freeze new deployments after repeated payment API incidents. Which causal explanation supports the intended design choice?

  1. Open-source community processes provide transparent review and shared maintenance, but do not imply unreviewed external code should be merged into production.
  2. A service level objective is a target for measured user-facing behavior; error budgets quantify allowed misses and help prioritize release risk.
  3. Prometheus commonly pulls numeric samples from configured targets, stores them as labeled time series and supports PromQL queries over those samples.
  4. The container runtime starts the configured process, and a crash or early exit can terminate the container regardless of Kubernetes placement.

Explanation

Correct Answer

B:

The situation is that a cooperative wants to decide whether to freeze new deployments after repeated payment API incidents. A service level objective is a target for measured user-facing behavior; error budgets quantify allowed misses and help prioritize release risk. It supports this action: Define a user-centered service level indicator and objective, such as percentage of successful requests within a latency threshold over a stated window. To confirm, calculate a synthetic seven-day success ratio from request metrics and compare it to the agreed target before a risky rollout.

Incorrect Answers

A:

That statement explains the distinct objective “Use open community governance and contribution processes for sustainable cloud-native projects” rather than the cause in this case. The deciding mechanism here is that a service level objective is a target for measured user-facing behavior; error budgets quantify allowed misses and help prioritize release risk.

C:

The situation is that a cooperative wants to decide whether to freeze new deployments after repeated payment API incidents. 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 a service level objective is a target for measured user-facing behavior; error budgets quantify allowed misses and help prioritize release risk.

D:

That statement explains the distinct objective “Understand ENTRYPOINT and command overrides when a container exits immediately” rather than the cause in this case. The deciding mechanism here is that a service level objective is a target for measured user-facing behavior; error budgets quantify allowed misses and help prioritize release risk.

Question 928

A cooperative wants to decide whether to freeze new deployments after repeated payment API incidents. Which test provides the strongest evidence of a correct implementation?

  1. Run a request across two synthetic services and verify traceparent propagation and two linked spans in the configured backend.
  2. Verify a synthetic exporter is listed UP in Prometheus target status and query its request counter after generating traffic.
  3. Calculate a synthetic seven-day success ratio from request metrics and compare it to the agreed target before a risky rollout.
  4. Compare kubectl get pods -o wide with kubectl describe pod for a test image-pull failure and note which output shows recent Events.

Explanation

Correct Answer

C:

The situation is that a cooperative wants to decide whether to freeze new deployments after repeated payment API incidents. Calculate a synthetic seven-day success ratio from request metrics and compare it to the agreed target before a risky rollout. This is the relevant test because a service level objective is a target for measured user-facing behavior; error budgets quantify allowed misses and help prioritize release risk.

Incorrect Answers

A:

This check would help evaluate the distinct objective “Instrument services with OpenTelemetry context propagation”, but not the required result. For this case, calculate a synthetic seven-day success ratio from request metrics and compare it to the agreed target before a risky rollout.

B:

This check would help evaluate the distinct objective “Understand Prometheus pull-based metrics collection and exporters”, but not the required result. For this case, calculate a synthetic seven-day success ratio from request metrics and compare it to the agreed target before a risky rollout.

D:

This check would help evaluate the distinct objective “Use kubectl get and describe for distinct inspection needs”, but not the required result. For this case, calculate a synthetic seven-day success ratio from request metrics and compare it to the agreed target before a risky rollout.

Question 929

A cooperative wants to decide whether to freeze new deployments after repeated payment API incidents. A shortcut is proposed: “Declare an uptime target achieved from the number of Running Pods while ignoring failed user requests.” Which technical consequence follows most closely?

  1. Cluster workload placement breaks because monitoring software cannot perform scheduler decisions.
  2. Unnecessary networking changes can disrupt unrelated services while the original name lookup error persists.
  3. The reported reliability can look excellent while customer transactions routinely fail or exceed acceptable latency.
  4. Alert fatigue hides significant incidents while normal autoscaling bursts generate excessive pages.

Explanation

Correct Answer

C:

The situation is that a cooperative wants to decide whether to freeze new deployments after repeated payment API incidents. The reported reliability can look excellent while customer transactions routinely fail or exceed acceptable latency. The shortcut creates this risk because a service level objective is a target for measured user-facing behavior; error budgets quantify allowed misses and help prioritize release risk.

Incorrect Answers

A:

That outcome concerns the distinct objective “Identify CNCF ecosystem projects by their role rather than assuming all are Kubernetes core”; it is not the most direct consequence of this shortcut. The relevant consequence is that the reported reliability can look excellent while customer transactions routinely fail or exceed acceptable latency.

B:

That outcome concerns the distinct objective “Diagnose cluster DNS separately from Pod network reachability”; it is not the most direct consequence of this shortcut. The relevant consequence is that the reported reliability can look excellent while customer transactions routinely fail or exceed acceptable latency.

D:

The situation is that a cooperative wants to decide whether to freeze new deployments after repeated payment API incidents. 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 the reported reliability can look excellent while customer transactions routinely fail or exceed acceptable latency.

Question 930

A cooperative wants to decide whether to freeze new deployments after repeated payment API incidents. Which combined solution and independent check are most directly justified?

  1. 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.
  2. Define a user-centered service level indicator and objective, such as percentage of successful requests within a latency threshold over a stated window. Acceptance evidence: Calculate a synthetic seven-day success ratio from request metrics and compare it to the agreed target before a risky rollout.
  3. Review Sandbox, Incubating and Graduated CNCF stages as community maturity signals while independently assessing a project's fitness, lifecycle and security. Acceptance evidence: Compare the governance and release activity of two projects and document which operational support and security tests are still required.
  4. Configure anti-affinity against other Pods with a specific label so replicas prefer or require separate failure domains as appropriate. Acceptance evidence: Deploy replicas with hostname anti-affinity and inspect their node placements in a cluster with enough eligible workers.

Explanation

Correct Answer

B:

The situation is that a cooperative wants to decide whether to freeze new deployments after repeated payment API incidents. Define a user-centered service level indicator and objective, such as percentage of successful requests within a latency threshold over a stated window. Acceptance evidence: Calculate a synthetic seven-day success ratio from request metrics and compare it to the agreed target before a risky rollout. This pairing is justified because a service level objective is a target for measured user-facing behavior; error budgets quantify allowed misses and help prioritize release risk.

Incorrect Answers

A:

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 a user-centered service level indicator and objective, such as percentage of successful requests within a latency threshold over a stated window. Its confirming test is to calculate a synthetic seven-day success ratio from request metrics and compare it to the agreed target before a risky rollout.

C:

This action and check address the distinct objective “Understand CNCF project maturity stages without equating them to security approval” instead of the stated acceptance requirement. The matching action is to define a user-centered service level indicator and objective, such as percentage of successful requests within a latency threshold over a stated window. Its confirming test is to calculate a synthetic seven-day success ratio from request metrics and compare it to the agreed target before a risky rollout.

D:

This action and check address the distinct objective “Use Pod anti-affinity to reduce correlated replica failure” instead of the stated acceptance requirement. The matching action is to define a user-centered service level indicator and objective, such as percentage of successful requests within a latency threshold over a stated window. Its confirming test is to calculate a synthetic seven-day success ratio from request metrics and compare it to the agreed target before a risky rollout.

Kubernetes and Cloud Native Associate (KCNA) Practice Tests