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 90

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.

Question 891

A museum runs a metric exporter for the number of requests handled by its public catalog. Which engineering approach is the most appropriate for this cloud-native case?

  1. Expose appropriately labeled /metrics endpoints or exporters and configure Prometheus scrape targets to collect time-series measurements.
  2. Use metrics for measurable trends, logs for event detail and distributed traces for individual transaction paths while sharing correlation identifiers.
  3. Use container runtime namespaces to isolate views of processes and networks while using cgroups to account for and constrain resources.
  4. Recognize Kubernetes for orchestration, Prometheus for metrics, Envoy for data-plane proxying and Fluentd for log collection in the cloud-native landscape.

Explanation

Correct Answer

A:

Expose appropriately labeled /metrics endpoints or exporters and configure Prometheus scrape targets to collect time-series measurements. This resolves the issue because prometheus commonly pulls numeric samples from configured targets, stores them as labeled time series and supports PromQL queries over those samples. To verify, verify a synthetic exporter is listed UP in Prometheus target status and query its request counter after generating traffic.

Incorrect Answers

B:

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, prometheus commonly pulls numeric samples from configured targets, stores them as labeled time series and supports PromQL queries over those samples.

C:

This option addresses the distinct objective “Explain Linux namespaces and cgroups as distinct container isolation mechanisms”, not the immediate requirement. Linux namespaces affect visibility and isolation boundaries, while cgroups organize and limit resource usage; neither automatically supplies a full virtual machine. For the stated case, prometheus commonly pulls numeric samples from configured targets, stores them as labeled time series and supports PromQL queries over those samples.

D:

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, prometheus commonly pulls numeric samples from configured targets, stores them as labeled time series and supports PromQL queries over those samples.

Question 892

A museum runs a metric exporter for the number of requests handled by its public catalog. What infrastructure principle makes the correct treatment effective?

  1. A deployment pipeline is a trust boundary; signed artifacts and automated policy tests reduce the risk of unreviewed configurations reaching production.
  2. Trace context allows spans from different services to join one transaction view, while collectors receive and forward telemetry without automatically storing all data.
  3. Each telemetry type represents a different view of runtime state and links through context can connect a symptom to a specific service hop.
  4. Prometheus commonly pulls numeric samples from configured targets, stores them as labeled time series and supports PromQL queries over those samples.

Explanation

Correct Answer

D:

Prometheus commonly pulls numeric samples from configured targets, stores them as labeled time series and supports PromQL queries over those samples. It supports this action: Expose appropriately labeled /metrics endpoints or exporters and configure Prometheus scrape targets to collect time-series measurements. To confirm, verify a synthetic exporter is listed UP in Prometheus target status and query its request counter after generating traffic.

Incorrect Answers

A:

That statement explains the distinct objective “Define secure release governance with staged approvals and policy verification” rather than the cause in this case. The deciding mechanism here is that prometheus commonly pulls numeric samples from configured targets, stores them as labeled time series and supports PromQL queries over those samples.

B:

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 prometheus commonly pulls numeric samples from configured targets, stores them as labeled time series and supports PromQL queries over those samples.

C:

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 prometheus commonly pulls numeric samples from configured targets, stores them as labeled time series and supports PromQL queries over those samples.

Question 893

A museum runs a metric exporter for the number of requests handled by its public catalog. What verification result would most convincingly distinguish a working solution from a claim?

  1. Test a synthetic standard API manifest and OpenTelemetry trace export across two platforms, documenting any unsupported extensions.
  2. Run a request across two synthetic services and verify traceparent propagation and two linked spans in the configured backend.
  3. Run nslookup for a Service using short and namespace-qualified names from test Pods in two different namespaces.
  4. Verify a synthetic exporter is listed UP in Prometheus target status and query its request counter after generating traffic.

Explanation

Correct Answer

D:

Verify a synthetic exporter is listed UP in Prometheus target status and query its request counter after generating traffic. This is the relevant test 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 check would help evaluate the distinct objective “Understand open standards and vendor-neutral community collaboration”, but not the required result. For this case, verify a synthetic exporter is listed UP in Prometheus target status and query its request counter after generating traffic.

B:

This check would help evaluate the distinct objective “Instrument services with OpenTelemetry context propagation”, but not the required result. For this case, verify a synthetic exporter is listed UP in Prometheus target status and query its request counter after generating traffic.

C:

This check would help evaluate the distinct objective “Verify CoreDNS resolution and namespace-qualified Service names”, but not the required result. For this case, verify a synthetic exporter is listed UP in Prometheus target status and query its request counter after generating traffic.

Question 894

A museum runs a metric exporter for the number of requests handled by its public catalog. The change review contains this proposal: “Install Prometheus without configuring any scrape target and assume it automatically records every application request.” What risk matters most?

  1. The reported reliability can look excellent while customer transactions routinely fail or exceed acceptable latency.
  2. The service can remain under capacity because a standalone Pod has no ReplicaSet controller to recreate it.
  3. Monitoring dashboards show empty or stale series because the expected metrics were never exposed or scraped.
  4. Alert fatigue hides significant incidents while normal autoscaling bursts generate excessive pages.

Explanation

Correct Answer

C:

Monitoring dashboards show empty or stale series because the expected metrics were never exposed or scraped. The shortcut creates this risk 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:

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 monitoring dashboards show empty or stale series because the expected metrics were never exposed or scraped.

B:

That outcome concerns the distinct objective “Identify reconciliation work performed by kube-controller-manager”; it is not the most direct consequence of this shortcut. The relevant consequence is that monitoring dashboards show empty or stale series because the expected metrics were never exposed or scraped.

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 monitoring dashboards show empty or stale series because the expected metrics were never exposed or scraped.

Question 895

A museum runs a metric exporter for the number of requests handled by its public catalog. Which implementation together with matching acceptance evidence best meets this case?

  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. 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.
  3. Give each Pod an appropriate ServiceAccount, disable automountServiceAccountToken where API access is unnecessary and test token audience and role scope. Acceptance evidence: Run a test web Pod without a token mount and verify service operation succeeds while in-cluster API calls are unavailable.
  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:

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

B:

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

This action and check address the distinct objective “Enforce workload service account token boundaries and avoid needless mounts” 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 896

A small insurer wants to distinguish a Prometheus scraping failure from a genuinely idle API. Which Kubernetes or cloud-native implementation decision best solves the stated problem?

  1. Use metrics for measurable trends, logs for event detail and distributed traces for individual transaction paths while sharing correlation identifiers.
  2. Combine RBAC, Pod security policies, NetworkPolicy and resource quotas for teams that share a Kubernetes control plane.
  3. Review Sandbox, Incubating and Graduated CNCF stages as community maturity signals while independently assessing a project's fitness, lifecycle and security.
  4. Expose appropriately labeled /metrics endpoints or exporters and configure Prometheus scrape targets to collect time-series measurements.

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. This resolves the issue because prometheus commonly pulls numeric samples from configured targets, stores them as labeled time series and supports PromQL queries over those samples. To verify, verify a synthetic exporter is listed UP in Prometheus target status and query its request counter after generating traffic.

Incorrect Answers

A:

The situation is that a small insurer wants to distinguish a Prometheus scraping failure from a genuinely idle API. 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, prometheus commonly pulls numeric samples from configured targets, stores them as labeled time series and supports PromQL queries over those samples.

B:

This option addresses the distinct objective “Separate multi-tenant namespace governance from actual isolation guarantees”, not the immediate requirement. Namespaces alone partition naming but do not provide complete security isolation, capacity governance or protection from privileged node-level workloads. For the stated case, prometheus commonly pulls numeric samples from configured targets, stores them as labeled time series and supports PromQL queries over those samples.

C:

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, prometheus commonly pulls numeric samples from configured targets, stores them as labeled time series and supports PromQL queries over those samples.

Question 897

A small insurer wants to distinguish a Prometheus scraping failure from a genuinely idle API. 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. CNCF maturity describes aspects of adoption and governance, not a blanket guarantee that every deployment or version is free of defects.
  3. Cordon marks a node unschedulable for new ordinary Pods; drain evicts managed workloads when policies and availability permit.
  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

A:

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

Incorrect Answers

B:

That statement explains the distinct objective “Understand CNCF project maturity stages without equating them to security approval” rather than the cause in this case. The deciding mechanism here is that prometheus commonly pulls numeric samples from configured targets, stores them as labeled time series and supports PromQL queries over those samples.

C:

That statement explains the distinct objective “Use cordon and drain with disruption considerations for planned node maintenance” rather than the cause in this case. The deciding mechanism here is that prometheus commonly pulls numeric samples from configured targets, stores them as labeled time series and supports PromQL queries over those samples.

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 prometheus commonly pulls numeric samples from configured targets, stores them as labeled time series and supports PromQL queries over those samples.

Question 898

A small insurer wants to distinguish a Prometheus scraping failure from a genuinely idle API. Which controlled observation would best validate the intended improvement?

  1. Verify a synthetic exporter is listed UP in Prometheus target status and query its request counter after generating traffic.
  2. Run a request across two synthetic services and verify traceparent propagation and two linked spans in the configured backend.
  3. Deploy replicas with hostname anti-affinity and inspect their node placements in a cluster with enough eligible workers.
  4. Calculate a synthetic seven-day success ratio from request metrics and compare it to the agreed target before a risky rollout.

Explanation

Correct Answer

A:

The situation is that a small insurer wants to distinguish a Prometheus scraping failure from a genuinely idle API. Verify a synthetic exporter is listed UP in Prometheus target status and query its request counter after generating traffic. This is the relevant test because prometheus commonly pulls numeric samples from configured targets, stores them as labeled time series and supports PromQL queries over those samples.

Incorrect Answers

B:

The situation is that a small insurer wants to distinguish a Prometheus scraping failure from a genuinely idle API. This check would help evaluate the distinct objective “Instrument services with OpenTelemetry context propagation”, but not the required result. For this case, verify a synthetic exporter is listed UP in Prometheus target status and query its request counter after generating traffic.

C:

This check would help evaluate the distinct objective “Use Pod anti-affinity to reduce correlated replica failure”, but not the required result. For this case, verify a synthetic exporter is listed UP in Prometheus target status and query its request counter after generating traffic.

D:

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, verify a synthetic exporter is listed UP in Prometheus target status and query its request counter after generating traffic.

Question 899

A small insurer wants to distinguish a Prometheus scraping failure from a genuinely idle API. An engineer proposes: “Install Prometheus without configuring any scrape target and assume it automatically records every application request.” What adverse outcome would be most direct?

  1. External routing remains absent or policy is misunderstood, and internal identity controls may be incomplete.
  2. Cross-service latency remains difficult to diagnose because spans cannot be tied to one request path.
  3. New Pods can remain Pending even when the controller increases desired replica count.
  4. Monitoring dashboards show empty or stale series because the expected metrics were never exposed or scraped.

Explanation

Correct Answer

D:

The situation is that a small insurer wants to distinguish a Prometheus scraping failure from a genuinely idle API. Monitoring dashboards show empty or stale series because the expected metrics were never exposed or scraped. The shortcut creates this risk 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:

That outcome concerns the distinct objective “Distinguish service mesh traffic management from external ingress routing”; it is not the most direct consequence of this shortcut. The relevant consequence is that monitoring dashboards show empty or stale series because the expected metrics were never exposed or scraped.

B:

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 monitoring dashboards show empty or stale series because the expected metrics were never exposed or scraped.

C:

That outcome concerns the distinct objective “Use HorizontalPodAutoscaler metrics rather than ad hoc instance scripts”; it is not the most direct consequence of this shortcut. The relevant consequence is that monitoring dashboards show empty or stale series because the expected metrics were never exposed or scraped.

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.

Kubernetes and Cloud Native Associate (KCNA) Practice Tests