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 91

Question 900

A small insurer wants to distinguish a Prometheus scraping failure from a genuinely idle API. What pair of supported action and practical verification should be approved?

  1. 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.
  2. Require reviewed image provenance, admission policy checks and staged traffic validation before promoting a cloud-native application. Acceptance evidence: Insert a deliberately unsigned test image into staging and confirm the release gate blocks production promotion while logging a reason.
  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. 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.

Explanation

Correct Answer

D:

The situation is that a small insurer wants to distinguish a Prometheus scraping failure from a genuinely idle API. Expose appropriately labeled /metrics endpoints or exporters and configure Prometheus scrape targets to collect time-series measurements. Acceptance evidence: Verify a synthetic exporter is listed UP in Prometheus target status and query its request counter after generating traffic. This pairing is justified because prometheus commonly pulls numeric samples from configured targets, stores them as labeled time series and supports PromQL queries over those samples.

Incorrect Answers

A:

This action and check address the distinct objective “Instrument services with OpenTelemetry context propagation” instead of the stated acceptance requirement. The matching action is to expose appropriately labeled /metrics endpoints or exporters and configure Prometheus scrape targets to collect time-series measurements. Its confirming test is to verify a synthetic exporter is listed UP in Prometheus target status and query its request counter after generating traffic.

B:

This action and check address the distinct objective “Define secure release governance with staged approvals and policy verification” instead of the stated acceptance requirement. The matching action is to expose appropriately labeled /metrics endpoints or exporters and configure Prometheus scrape targets to collect time-series measurements. Its confirming test is to verify a synthetic exporter is listed UP in Prometheus target status and query its request counter after generating traffic.

C:

The situation is that a small insurer wants to distinguish a Prometheus scraping failure from a genuinely idle API. This action and check address the distinct objective “Explain metrics, logs and traces as complementary observability signals” instead of the stated acceptance requirement. The matching action is to expose appropriately labeled /metrics endpoints or exporters and configure Prometheus scrape targets to collect time-series measurements. Its confirming test is to verify a synthetic exporter is listed UP in Prometheus target status and query its request counter after generating traffic.

Question 901

A city service needs to page only when its checkout failure rate stays elevated for several minutes. Which Kubernetes or cloud-native implementation decision best solves the stated problem?

  1. Define symptom-based Prometheus alerting rules with sensible durations and route alerts through Alertmanager to the responsible service team.
  2. Expose appropriately labeled /metrics endpoints or exporters and configure Prometheus scrape targets to collect time-series measurements.
  3. Package workloads in standard images and declarative manifests while documenting external dependencies and provider-specific integrations before claiming portability.
  4. Use requiredDuringSchedulingIgnoredDuringExecution for mandatory constraints and preferredDuringSchedulingIgnoredDuringExecution for a soft placement preference.

Explanation

Correct Answer

A:

Define symptom-based Prometheus alerting rules with sensible durations and route alerts through Alertmanager to the responsible service team. This resolves the issue because alert rules evaluate time-series expressions while Alertmanager groups, routes and silences notifications; neither automatically fixes the underlying workload. To verify, trigger a controlled error-rate alert, verify its pending/firing transition and confirm the correct team receives a grouped notification.

Incorrect Answers

B:

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, alert rules evaluate time-series expressions while Alertmanager groups, routes and silences notifications; neither automatically fixes the underlying workload.

C:

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, alert rules evaluate time-series expressions while Alertmanager groups, routes and silences notifications; neither automatically fixes the underlying workload.

D:

This option addresses the distinct objective “Distinguish preferred node affinity from required scheduling rules”, not the immediate requirement. A required affinity expression blocks scheduling onto nonmatching nodes; a preferred expression influences scoring but permits fallback when necessary. For the stated case, alert rules evaluate time-series expressions while Alertmanager groups, routes and silences notifications; neither automatically fixes the underlying workload.

Question 902

A city service needs to page only when its checkout failure rate stays elevated for several minutes. Which platform mechanism explains why the suitable approach works?

  1. Prometheus commonly pulls numeric samples from configured targets, stores them as labeled time series and supports PromQL queries over those samples.
  2. Alert rules evaluate time-series expressions while Alertmanager groups, routes and silences notifications; neither automatically fixes the underlying workload.
  3. kube-proxy can maintain node networking rules for Services, but supported network implementations may replace this function.
  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

B:

Alert rules evaluate time-series expressions while Alertmanager groups, routes and silences notifications; neither automatically fixes the underlying workload. It supports this action: Define symptom-based Prometheus alerting rules with sensible durations and route alerts through Alertmanager to the responsible service team. To confirm, trigger a controlled error-rate alert, verify its pending/firing transition and confirm the correct team receives a grouped notification.

Incorrect Answers

A:

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 alert rules evaluate time-series expressions while Alertmanager groups, routes and silences notifications; neither automatically fixes the underlying workload.

C:

That statement explains the distinct objective “Understand service proxy implementations without assuming kube-proxy is mandatory” rather than the cause in this case. The deciding mechanism here is that alert rules evaluate time-series expressions while Alertmanager groups, routes and silences notifications; neither automatically fixes the underlying workload.

D:

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 alert rules evaluate time-series expressions while Alertmanager groups, routes and silences notifications; neither automatically fixes the underlying workload.

Question 903

A city service needs to page only when its checkout failure rate stays elevated for several minutes. Which controlled observation would best validate the intended improvement?

  1. With restricted identities, check get pods succeeds while delete secrets and create clusterroles are denied.
  2. Verify a synthetic exporter is listed UP in Prometheus target status and query its request counter after generating traffic.
  3. Compare the governance and release activity of two projects and document which operational support and security tests are still required.
  4. Trigger a controlled error-rate alert, verify its pending/firing transition and confirm the correct team receives a grouped notification.

Explanation

Correct Answer

D:

Trigger a controlled error-rate alert, verify its pending/firing transition and confirm the correct team receives a grouped notification. This is the relevant test because alert rules evaluate time-series expressions while Alertmanager groups, routes and silences notifications; neither automatically fixes the underlying workload.

Incorrect Answers

A:

This check would help evaluate the distinct objective “Use least-privilege kubectl authentication and authorization during routine administration”, but not the required result. For this case, trigger a controlled error-rate alert, verify its pending/firing transition and confirm the correct team receives a grouped notification.

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, trigger a controlled error-rate alert, verify its pending/firing transition and confirm the correct team receives a grouped notification.

C:

This check would help evaluate the distinct objective “Understand CNCF project maturity stages without equating them to security approval”, but not the required result. For this case, trigger a controlled error-rate alert, verify its pending/firing transition and confirm the correct team receives a grouped notification.

Question 904

A city service needs to page only when its checkout failure rate stays elevated for several minutes. An engineer proposes: “Create an immediate alert on every small CPU fluctuation and send it separately to all staff without ownership.” What adverse outcome would be most direct?

  1. Alert fatigue hides significant incidents while normal autoscaling bursts generate excessive pages.
  2. Monitoring dashboards show empty or stale series because the expected metrics were never exposed or scraped.
  3. Secrets can be exposed to broadly authorized readers and source-control users despite apparently valid deployments.
  4. Cross-service latency remains difficult to diagnose because spans cannot be tied to one request path.

Explanation

Correct Answer

A:

Alert fatigue hides significant incidents while normal autoscaling bursts generate excessive pages. The shortcut creates this risk because alert rules evaluate time-series expressions while Alertmanager groups, routes and silences notifications; neither automatically fixes the underlying workload.

Incorrect Answers

B:

That outcome concerns the distinct objective “Understand Prometheus pull-based metrics collection and exporters”; it is not the most direct consequence of this shortcut. The relevant consequence is that alert fatigue hides significant incidents while normal autoscaling bursts generate excessive pages.

C:

That outcome concerns the distinct objective “Distinguish ConfigMaps from Secrets and avoid storing credentials in public configuration”; it is not the most direct consequence of this shortcut. The relevant consequence is that alert fatigue hides significant incidents while normal autoscaling bursts generate excessive pages.

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 alert fatigue hides significant incidents while normal autoscaling bursts generate excessive pages.

Question 905

A city service needs to page only when its checkout failure rate stays elevated for several minutes. What pair of supported action and practical verification should be approved?

  1. Follow a project's published governance, issue templates, contributor guides and code of conduct when reporting bugs or proposing changes. Acceptance evidence: Submit a reproducible synthetic issue and examine how maintainers triage, review and test a proposed patch before release.
  2. Run automated source tests, dependency checks and artifact signing during CI, then promote the vetted immutable artifact through a controlled delivery stage. Acceptance evidence: Trace a test commit through build-test-image-digest and compare that digest between staging and production promotion records.
  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 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

C:

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

A:

This action and check address the distinct objective “Use open community governance and contribution processes for sustainable cloud-native projects” 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.

B:

This action and check address the distinct objective “Separate CI build verification from CD environment promotion” 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.

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 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 906

A college lab sends every transient CPU spike to the whole operations channel and wants actionable alerts. Which engineering approach is the most appropriate for this cloud-native case?

  1. Prefer documented Kubernetes APIs and interoperable telemetry formats when possible while identifying any platform-specific extensions needed for the real deployment.
  2. Define symptom-based Prometheus alerting rules with sensible durations and route alerts through Alertmanager to the responsible service team.
  3. Apply suitable Pod Security Admission labels such as baseline or restricted and test whether noncompliant synthetic Pod specs are rejected.
  4. Define a user-centered service level indicator and objective, such as percentage of successful requests within a latency threshold over a stated window.

Explanation

Correct Answer

B:

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. This resolves the issue because alert rules evaluate time-series expressions while Alertmanager groups, routes and silences notifications; neither automatically fixes the underlying workload. To verify, trigger a controlled error-rate alert, verify its pending/firing transition and confirm the correct team receives a grouped notification.

Incorrect Answers

A:

This option addresses the distinct objective “Understand open standards and vendor-neutral community collaboration”, not the immediate requirement. Open standards and vendor-neutral governance reduce lock-in and support collaboration, but products can still differ in versions, implementations and operational capabilities. For the stated case, alert rules evaluate time-series expressions while Alertmanager groups, routes and silences notifications; neither automatically fixes the underlying workload.

C:

This option addresses the distinct objective “Use Pod Security Standards to deny overly privileged Pod configurations”, not the immediate requirement. Pod Security Standards establish common workload hardening profiles, and admission checks can enforce restricted capabilities and privilege use at API creation. For the stated case, alert rules evaluate time-series expressions while Alertmanager groups, routes and silences notifications; neither automatically fixes the underlying workload.

D:

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, alert rules evaluate time-series expressions while Alertmanager groups, routes and silences notifications; neither automatically fixes the underlying workload.

Question 907

A college lab sends every transient CPU spike to the whole operations channel and wants actionable alerts. 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. Authentication establishes who calls the API; RBAC authorization checks requested verb, resource and namespace before the API permits it.
  3. Service meshes commonly use proxies or ambient dataplanes to control east-west traffic; ingress/gateway handling addresses entry routes and can integrate with the mesh.
  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

A:

The situation is that a college lab sends every transient CPU spike to the whole operations channel and wants actionable alerts. Alert rules evaluate time-series expressions while Alertmanager groups, routes and silences notifications; neither automatically fixes the underlying workload. It supports this action: Define symptom-based Prometheus alerting rules with sensible durations and route alerts through Alertmanager to the responsible service team. To confirm, trigger a controlled error-rate alert, verify its pending/firing transition and confirm the correct team receives a grouped notification.

Incorrect Answers

B:

That statement explains the distinct objective “Use least-privilege kubectl authentication and authorization during routine administration” rather than the cause in this case. The deciding mechanism here is that alert rules evaluate time-series expressions while Alertmanager groups, routes and silences notifications; neither automatically fixes the underlying workload.

C:

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 alert rules evaluate time-series expressions while Alertmanager groups, routes and silences notifications; neither automatically fixes the underlying workload.

D:

That statement explains the distinct objective “Explain metrics, logs and traces as complementary observability signals” rather than the cause in this case. The deciding mechanism here is that alert rules evaluate time-series expressions while Alertmanager groups, routes and silences notifications; neither automatically fixes the underlying workload.

Question 908

A college lab sends every transient CPU spike to the whole operations channel and wants actionable alerts. What verification result would most convincingly distinguish a working solution from a claim?

  1. Compare kubectl get pods -l app=inventory with Service selectors and EndpointSlices for a test workload.
  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. Trigger a controlled error-rate alert, verify its pending/firing transition and confirm the correct team receives a grouped notification.

Explanation

Correct Answer

D:

The situation is that a college lab sends every transient CPU spike to the whole operations channel and wants actionable alerts. Trigger a controlled error-rate alert, verify its pending/firing transition and confirm the correct team receives a grouped notification. This is the relevant test because alert rules evaluate time-series expressions while Alertmanager groups, routes and silences notifications; neither automatically fixes the underlying workload.

Incorrect Answers

A:

This check would help evaluate the distinct objective “Use labels and selectors to connect resources predictably”, but not the required result. For this case, trigger a controlled error-rate alert, verify its pending/firing transition and confirm the correct team receives a grouped notification.

B:

The situation is that a college lab sends every transient CPU spike to the whole operations channel and wants actionable alerts. This check would help evaluate the distinct objective “Understand Prometheus pull-based metrics collection and exporters”, but not the required result. For this case, trigger a controlled error-rate alert, verify its pending/firing transition and confirm the correct team receives a grouped notification.

C:

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, trigger a controlled error-rate alert, verify its pending/firing transition and confirm the correct team receives a grouped notification.

Question 909

A college lab sends every transient CPU spike to the whole operations channel and wants actionable alerts. The change review contains this proposal: “Create an immediate alert on every small CPU fluctuation and send it separately to all staff without ownership.” What risk matters most?

  1. The reported reliability can look excellent while customer transactions routinely fail or exceed acceptable latency.
  2. Applications fail on migration when plugin behavior or provider-specific components were never evaluated.
  3. The planned maintenance causes avoidable downtime because no safe application replica remains available.
  4. Alert fatigue hides significant incidents while normal autoscaling bursts generate excessive pages.

Explanation

Correct Answer

D:

The situation is that a college lab sends every transient CPU spike to the whole operations channel and wants actionable alerts. Alert fatigue hides significant incidents while normal autoscaling bursts generate excessive pages. The shortcut creates this risk because alert rules evaluate time-series expressions while Alertmanager groups, routes and silences notifications; neither automatically fixes the underlying workload.

Incorrect Answers

A:

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 alert fatigue hides significant incidents while normal autoscaling bursts generate excessive pages.

B:

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 alert fatigue hides significant incidents while normal autoscaling bursts generate excessive pages.

C:

That outcome concerns the distinct objective “Use cordon and drain with disruption considerations for planned node maintenance”; it is not the most direct consequence of this shortcut. The relevant consequence is that alert fatigue hides significant incidents while normal autoscaling bursts generate excessive pages.

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?

  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. Inspect Deployment, ReplicaSet and Pod owner references when verifying which controller maintains replica count. Acceptance evidence: Run kubectl get rs and kubectl describe deployment for a test rollout and verify the expected owner chain.
  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. Choose service boundaries around business capabilities and operational needs, documenting communication cost, ownership and fault tolerance. Acceptance evidence: Model a synthetic two-service checkout dependency and compare rollout independence with failure and latency overhead against a single service.

Explanation

Correct Answer

C:

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

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 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.

B:

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.

D:

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.

Kubernetes and Cloud Native Associate (KCNA) Practice Tests