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 94

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.

Question 931

A startup with three developers considers splitting its simple web app into dozens of services. What technical action should the platform team take in this situation?

  1. Recognize Kubernetes for orchestration, Prometheus for metrics, Envoy for data-plane proxying and Fluentd for log collection in the cloud-native landscape.
  2. Use OpenTelemetry SDKs and a collector to export appropriately sampled traces and metrics with stable service identities and trace context.
  3. Identify whether the cluster uses kube-proxy or an alternative Service dataplane before diagnosing virtual Service IP forwarding behavior.
  4. Choose service boundaries around business capabilities and operational needs, documenting communication cost, ownership and fault tolerance.

Explanation

Correct Answer

D:

Choose service boundaries around business capabilities and operational needs, documenting communication cost, ownership and fault tolerance. This resolves the issue because microservices permit independent deployment and scaling but introduce network dependencies and data consistency challenges; a monolith can remain appropriate for smaller teams. To verify, model a synthetic two-service checkout dependency and compare rollout independence with failure and latency overhead against a single service.

Incorrect Answers

A:

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, microservices permit independent deployment and scaling but introduce network dependencies and data consistency challenges; a monolith can remain appropriate for smaller teams.

B:

This option addresses the distinct objective “Instrument services with OpenTelemetry context propagation”, not the immediate requirement. Trace context allows spans from different services to join one transaction view, while collectors receive and forward telemetry without automatically storing all data. For the stated case, microservices permit independent deployment and scaling but introduce network dependencies and data consistency challenges; a monolith can remain appropriate for smaller teams.

C:

This option addresses the distinct objective “Understand service proxy implementations without assuming kube-proxy is mandatory”, not the immediate requirement. Kube-proxy can maintain node networking rules for Services, but supported network implementations may replace this function. For the stated case, microservices permit independent deployment and scaling but introduce network dependencies and data consistency challenges; a monolith can remain appropriate for smaller teams.

Question 932

A startup with three developers considers splitting its simple web app into dozens of services. What underlying Kubernetes behavior is most relevant to this technical decision?

  1. Microservices permit independent deployment and scaling but introduce network dependencies and data consistency challenges; a monolith can remain appropriate for smaller teams.
  2. Ingress and Gateway API express routing intent, while an actual controller/dataplane implements TLS termination, listeners and backend forwarding.
  3. Containers and Kubernetes APIs reduce some environment differences, but network load balancers, storage drivers and IAM integrations remain provider-specific.
  4. CNCF projects address different layers of a cloud-native platform and interoperability does not turn them into interchangeable cluster control-plane components.

Explanation

Correct Answer

A:

Microservices permit independent deployment and scaling but introduce network dependencies and data consistency challenges; a monolith can remain appropriate for smaller teams. It supports this action: Choose service boundaries around business capabilities and operational needs, documenting communication cost, ownership and fault tolerance. To confirm, model a synthetic two-service checkout dependency and compare rollout independence with failure and latency overhead against a single service.

Incorrect Answers

B:

That statement explains the distinct objective “Choose Ingress or Gateway API with an implementing controller for HTTP exposure” rather than the cause in this case. The deciding mechanism here is that microservices permit independent deployment and scaling but introduce network dependencies and data consistency challenges; a monolith can remain appropriate for smaller teams.

C:

That statement explains the distinct objective “Apply cloud-native portability and immutable infrastructure principles pragmatically” rather than the cause in this case. The deciding mechanism here is that microservices permit independent deployment and scaling but introduce network dependencies and data consistency challenges; a monolith can remain appropriate for smaller teams.

D:

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 microservices permit independent deployment and scaling but introduce network dependencies and data consistency challenges; a monolith can remain appropriate for smaller teams.

Question 933

A startup with three developers considers splitting its simple web app into dozens of services. What acceptance check most directly confirms this requirement is met?

  1. Observe a controlled drain with replica owners and a PDB, then verify workloads move and uncordon restores eligibility.
  2. Model a synthetic two-service checkout dependency and compare rollout independence with failure and latency overhead against a single service.
  3. Build a study architecture diagram that connects each tool to its documented function and verify the expected data flow in a sample environment.
  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

B:

Model a synthetic two-service checkout dependency and compare rollout independence with failure and latency overhead against a single service. This is the relevant test because microservices permit independent deployment and scaling but introduce network dependencies and data consistency challenges; a monolith can remain appropriate for smaller teams.

Incorrect Answers

A:

This check would help evaluate the distinct objective “Use cordon and drain with disruption considerations for planned node maintenance”, but not the required result. For this case, model a synthetic two-service checkout dependency and compare rollout independence with failure and latency overhead against a single service.

C:

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, model a synthetic two-service checkout dependency and compare rollout independence with failure and latency overhead against a single service.

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, model a synthetic two-service checkout dependency and compare rollout independence with failure and latency overhead against a single service.

Question 934

A startup with three developers considers splitting its simple web app into dozens of services. The team suggests: “Split every short function into a network service and assume more microservices automatically mean higher reliability.” Which failure should the reviewer anticipate?

  1. Network calls and coordination complexity grow without a business reason, creating new failure modes.
  2. External routing remains absent or policy is misunderstood, and internal identity controls may be incomplete.
  3. A project can exhaust shared cluster capacity when declarative metadata is mistaken for enforced admission policy.
  4. Cluster workload placement breaks because monitoring software cannot perform scheduler decisions.

Explanation

Correct Answer

A:

Network calls and coordination complexity grow without a business reason, creating new failure modes. The shortcut creates this risk because microservices permit independent deployment and scaling but introduce network dependencies and data consistency challenges; a monolith can remain appropriate for smaller teams.

Incorrect Answers

B:

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 network calls and coordination complexity grow without a business reason, creating new failure modes.

C:

That outcome concerns the distinct objective “Understand resource quotas and LimitRanges for namespace capacity governance”; it is not the most direct consequence of this shortcut. The relevant consequence is that network calls and coordination complexity grow without a business reason, creating new failure modes.

D:

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 network calls and coordination complexity grow without a business reason, creating new failure modes.

Question 935

A startup with three developers considers splitting its simple web app into dozens of services. Which engineering change and test jointly addresses the scenario?

  1. 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.
  2. Use kubectl get for concise resource lists and kubectl describe for detailed status, conditions and Events when triaging a workload. Acceptance evidence: Compare kubectl get pods -o wide with kubectl describe pod for a test image-pull failure and note which output shows recent Events.
  3. 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.
  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

D:

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. This pairing is justified because microservices permit independent deployment and scaling but introduce network dependencies and data consistency challenges; a monolith can remain appropriate for smaller teams.

Incorrect Answers

A:

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 choose service boundaries around business capabilities and operational needs, documenting communication cost, ownership and fault tolerance. Its confirming test is to model a synthetic two-service checkout dependency and compare rollout independence with failure and latency overhead against a single service.

B:

This action and check address the distinct objective “Use kubectl get and describe for distinct inspection needs” instead of the stated acceptance requirement. The matching action is to choose service boundaries around business capabilities and operational needs, documenting communication cost, ownership and fault tolerance. Its confirming test is to model a synthetic two-service checkout dependency and compare rollout independence with failure and latency overhead against a single service.

C:

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 choose service boundaries around business capabilities and operational needs, documenting communication cost, ownership and fault tolerance. Its confirming test is to model a synthetic two-service checkout dependency and compare rollout independence with failure and latency overhead against a single service.

Question 936

A national logistics platform needs one billing component released independently from its shipment tracker. Which supported Kubernetes practice directly addresses the stated requirement?

  1. Package workloads in standard images and declarative manifests while documenting external dependencies and provider-specific integrations before claiming portability.
  2. Choose service boundaries around business capabilities and operational needs, documenting communication cost, ownership and fault tolerance.
  3. Inspect the relevant object's conditions and timestamped Events to place the failure at API admission, scheduling, image pulling or runtime startup.
  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 national logistics platform needs one billing component released independently from its shipment tracker. Choose service boundaries around business capabilities and operational needs, documenting communication cost, ownership and fault tolerance. This resolves the issue because microservices permit independent deployment and scaling but introduce network dependencies and data consistency challenges; a monolith can remain appropriate for smaller teams. To verify, model a synthetic two-service checkout dependency and compare rollout independence with failure and latency overhead against a single service.

Incorrect Answers

A:

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, microservices permit independent deployment and scaling but introduce network dependencies and data consistency challenges; a monolith can remain appropriate for smaller teams.

C:

This option addresses the distinct objective “Use describe and Events to distinguish admission, scheduling and execution errors”, not the immediate requirement. Different Kubernetes components emit distinct Events; identifying the stage prevents changing unrelated network or application settings. For the stated case, microservices permit independent deployment and scaling but introduce network dependencies and data consistency challenges; a monolith can remain appropriate for smaller teams.

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, microservices permit independent deployment and scaling but introduce network dependencies and data consistency challenges; a monolith can remain appropriate for smaller teams.

Question 937

A national logistics platform needs one billing component released independently from its shipment tracker. Which causal explanation supports the intended design choice?

  1. StatefulSet manages stable ordinal identities and preserves PVC-associated storage per replica across routine Pod replacement, subject to retention policy.
  2. Microservices permit independent deployment and scaling but introduce network dependencies and data consistency challenges; a monolith can remain appropriate for smaller teams.
  3. Containers and Kubernetes APIs reduce some environment differences, but network load balancers, storage drivers and IAM integrations remain provider-specific.
  4. CNCF maturity describes aspects of adoption and governance, not a blanket guarantee that every deployment or version is free of defects.

Explanation

Correct Answer

B:

The situation is that a national logistics platform needs one billing component released independently from its shipment tracker. Microservices permit independent deployment and scaling but introduce network dependencies and data consistency challenges; a monolith can remain appropriate for smaller teams. It supports this action: Choose service boundaries around business capabilities and operational needs, documenting communication cost, ownership and fault tolerance. To confirm, model a synthetic two-service checkout dependency and compare rollout independence with failure and latency overhead against a single service.

Incorrect Answers

A:

That statement explains the distinct objective “Use StatefulSet for stable ordinal identity and persistent per-replica claims” rather than the cause in this case. The deciding mechanism here is that microservices permit independent deployment and scaling but introduce network dependencies and data consistency challenges; a monolith can remain appropriate for smaller teams.

C:

The situation is that a national logistics platform needs one billing component released independently from its shipment tracker. That statement explains the distinct objective “Apply cloud-native portability and immutable infrastructure principles pragmatically” rather than the cause in this case. The deciding mechanism here is that microservices permit independent deployment and scaling but introduce network dependencies and data consistency challenges; a monolith can remain appropriate for smaller teams.

D:

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 microservices permit independent deployment and scaling but introduce network dependencies and data consistency challenges; a monolith can remain appropriate for smaller teams.

Question 938

A national logistics platform needs one billing component released independently from its shipment tracker. Which test provides the strongest evidence of a correct implementation?

  1. Compare the governance and release activity of two projects and document which operational support and security tests are still required.
  2. Test a synthetic internal service call with mutual TLS policy and separately inspect the public Gateway listener and route status.
  3. Check CNI capabilities, establish a default-deny test policy and verify one allowed and one denied connection.
  4. Model a synthetic two-service checkout dependency and compare rollout independence with failure and latency overhead against a single service.

Explanation

Correct Answer

D:

The situation is that a national logistics platform needs one billing component released independently from its shipment tracker. Model a synthetic two-service checkout dependency and compare rollout independence with failure and latency overhead against a single service. This is the relevant test because microservices permit independent deployment and scaling but introduce network dependencies and data consistency challenges; a monolith can remain appropriate for smaller teams.

Incorrect Answers

A:

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, model a synthetic two-service checkout dependency and compare rollout independence with failure and latency overhead against a single service.

B:

This check would help evaluate the distinct objective “Distinguish service mesh traffic management from external ingress routing”, but not the required result. For this case, model a synthetic two-service checkout dependency and compare rollout independence with failure and latency overhead against a single service.

C:

This check would help evaluate the distinct objective “Recognize NetworkPolicy isolation only when the CNI enforces it”, but not the required result. For this case, model a synthetic two-service checkout dependency and compare rollout independence with failure and latency overhead against a single service.

Question 939

A national logistics platform needs one billing component released independently from its shipment tracker. A shortcut is proposed: “Split every short function into a network service and assume more microservices automatically mean higher reliability.” Which technical consequence follows most closely?

  1. The Pod remains unschedulable because requested capacity and node feasibility did not change.
  2. Network calls and coordination complexity grow without a business reason, creating new failure modes.
  3. External routing remains absent or policy is misunderstood, and internal identity controls may be incomplete.
  4. The reported reliability can look excellent while customer transactions routinely fail or exceed acceptable latency.

Explanation

Correct Answer

B:

The situation is that a national logistics platform needs one billing component released independently from its shipment tracker. Network calls and coordination complexity grow without a business reason, creating new failure modes. The shortcut creates this risk because microservices permit independent deployment and scaling but introduce network dependencies and data consistency challenges; a monolith can remain appropriate for smaller teams.

Incorrect Answers

A:

That outcome concerns the distinct objective “Use container resource requests to help the scheduler fit Pods on nodes”; it is not the most direct consequence of this shortcut. The relevant consequence is that network calls and coordination complexity grow without a business reason, creating new failure modes.

C:

The situation is that a national logistics platform needs one billing component released independently from its shipment tracker. 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 network calls and coordination complexity grow without a business reason, creating new failure modes.

D:

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 network calls and coordination complexity grow without a business reason, creating new failure modes.

Question 940

A national logistics platform needs one billing component released independently from its shipment tracker. Which combined solution and independent check are most directly justified?

  1. 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.
  2. 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.
  3. Give clients a Service DNS name rather than hardcoding Pod IP addresses that can change when replicas are replaced. Acceptance evidence: Delete and replace a Deployment Pod and verify a client continues to reach its Service DNS name despite changed backend Pod addresses.
  4. 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.

Explanation

Correct Answer

B:

The situation is that a national logistics platform needs one billing component released independently from its shipment tracker. 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. This pairing is justified because microservices permit independent deployment and scaling but introduce network dependencies and data consistency challenges; a monolith can remain appropriate for smaller teams.

Incorrect Answers

A:

The situation is that a national logistics platform needs one billing component released independently from its shipment tracker. 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 choose service boundaries around business capabilities and operational needs, documenting communication cost, ownership and fault tolerance. Its confirming test is to model a synthetic two-service checkout dependency and compare rollout independence with failure and latency overhead against a single service.

C:

This action and check address the distinct objective “Distinguish Pod IPs from stable Services during rescheduling” instead of the stated acceptance requirement. The matching action is to choose service boundaries around business capabilities and operational needs, documenting communication cost, ownership and fault tolerance. Its confirming test is to model a synthetic two-service checkout dependency and compare rollout independence with failure and latency overhead against a single service.

D:

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 choose service boundaries around business capabilities and operational needs, documenting communication cost, ownership and fault tolerance. Its confirming test is to model a synthetic two-service checkout dependency and compare rollout independence with failure and latency overhead against a single service.

Kubernetes and Cloud Native Associate (KCNA) Practice Tests