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 95

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.

Question 941

A university curriculum introduces Kubernetes, Prometheus and Envoy as different tools within one platform. Which engineering approach is the most appropriate for this cloud-native case?

  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. 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.
  4. Observe rollout progression and use a reviewed rollback to a previous ReplicaSet revision when a new application build fails health checks.

Explanation

Correct Answer

A:

Recognize Kubernetes for orchestration, Prometheus for metrics, Envoy for data-plane proxying and Fluentd for log collection in the cloud-native landscape. This resolves the issue because CNCF projects address different layers of a cloud-native platform and interoperability does not turn them into interchangeable cluster control-plane components. To verify, build a study architecture diagram that connects each tool to its documented function and verify the expected data flow in a sample environment.

Incorrect Answers

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, CNCF projects address different layers of a cloud-native platform and interoperability does not turn them into interchangeable cluster control-plane components.

C:

This option addresses the distinct objective “Distinguish service mesh traffic management from external ingress routing”, not the immediate requirement. 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. For the stated case, CNCF projects address different layers of a cloud-native platform and interoperability does not turn them into interchangeable cluster control-plane components.

D:

This option addresses the distinct objective “Use rollout status and undo to validate and recover a Deployment release”, not the immediate requirement. Deployment rollout strategy gradually replaces Pods and preserves revision history, but success depends on availability and revision retention settings. For the stated case, CNCF projects address different layers of a cloud-native platform and interoperability does not turn them into interchangeable cluster control-plane components.

Question 942

A university curriculum introduces Kubernetes, Prometheus and Envoy as different tools within one platform. What infrastructure principle makes the correct treatment effective?

  1. etcd persists Kubernetes API objects and cluster configuration, while application records ordinarily live in workload-specific storage outside etcd.
  2. 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.
  3. CNCF projects address different layers of a cloud-native platform and interoperability does not turn them into interchangeable cluster control-plane components.
  4. Trace context allows spans from different services to join one transaction view, while collectors receive and forward telemetry without automatically storing all data.

Explanation

Correct Answer

C:

CNCF projects address different layers of a cloud-native platform and interoperability does not turn them into interchangeable cluster control-plane components. It supports this action: Recognize Kubernetes for orchestration, Prometheus for metrics, Envoy for data-plane proxying and Fluentd for log collection in the cloud-native landscape. To confirm, build a study architecture diagram that connects each tool to its documented function and verify the expected data flow in a sample environment.

Incorrect Answers

A:

That statement explains the distinct objective “Distinguish etcd persistence from running workload data” rather than the cause in this case. The deciding mechanism here is that CNCF projects address different layers of a cloud-native platform and interoperability does not turn them into interchangeable cluster control-plane components.

B:

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 CNCF projects address different layers of a cloud-native platform and interoperability does not turn them into interchangeable cluster control-plane components.

D:

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 CNCF projects address different layers of a cloud-native platform and interoperability does not turn them into interchangeable cluster control-plane components.

Question 943

A university curriculum introduces Kubernetes, Prometheus and Envoy as different tools within one platform. 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. Upgrade a synthetic four-replica app, monitor old/new ReplicaSets and ready endpoints, then compare observed minimum availability.
  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. Deploy a synthetic stateless workload to two conformant clusters and record which storage, ingress and identity settings require changes.

Explanation

Correct Answer

C:

Build a study architecture diagram that connects each tool to its documented function and verify the expected data flow in a sample environment. This is the relevant test because CNCF projects address different layers of a cloud-native platform and interoperability does not turn them into interchangeable cluster control-plane components.

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, build a study architecture diagram that connects each tool to its documented function and verify the expected data flow in a sample environment.

B:

This check would help evaluate the distinct objective “Configure Deployment rolling updates with availability safeguards”, but not the required result. For this case, build a study architecture diagram that connects each tool to its documented function and verify the expected data flow in a sample environment.

D:

This check would help evaluate the distinct objective “Apply cloud-native portability and immutable infrastructure principles pragmatically”, but not the required result. For this case, build a study architecture diagram that connects each tool to its documented function and verify the expected data flow in a sample environment.

Question 944

A university curriculum introduces Kubernetes, Prometheus and Envoy as different tools within one platform. The change review contains this proposal: “Replace kube-scheduler with a Prometheus exporter because both are popular CNCF ecosystem projects.” What risk matters most?

  1. Cluster workload placement breaks because monitoring software cannot perform scheduler decisions.
  2. Network calls and coordination complexity grow without a business reason, creating new failure modes.
  3. The workload may be placed nearby but access-control enforcement remains unchanged or incorrectly configured.
  4. External routing remains absent or policy is misunderstood, and internal identity controls may be incomplete.

Explanation

Correct Answer

A:

Cluster workload placement breaks because monitoring software cannot perform scheduler decisions. The shortcut creates this risk because CNCF projects address different layers of a cloud-native platform and interoperability does not turn them into interchangeable cluster control-plane components.

Incorrect Answers

B:

That outcome concerns the distinct objective “Contrast cloud-native microservices with a monolith without treating either as inherently superior”; it is not the most direct consequence of this shortcut. The relevant consequence is that cluster workload placement breaks because monitoring software cannot perform scheduler decisions.

C:

That outcome concerns the distinct objective “Use Pod affinity for co-location without assuming it creates networking permissions”; it is not the most direct consequence of this shortcut. The relevant consequence is that cluster workload placement breaks because monitoring software cannot perform scheduler decisions.

D:

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 cluster workload placement breaks because monitoring software cannot perform scheduler decisions.

Question 945

A university curriculum introduces Kubernetes, Prometheus and Envoy as different tools within one platform. Which implementation together with matching acceptance evidence best meets this case?

  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. Inject environment-specific nonsecret values through ConfigMaps and secrets through guarded Secret references without rebuilding a different application image. Acceptance evidence: Promote the same image digest into two test namespaces with different safe endpoints, verifying Secret values are not in image layers.
  3. 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.
  4. Recognize Kubernetes for orchestration, Prometheus for metrics, Envoy for data-plane proxying and Fluentd for log collection in the cloud-native landscape. Acceptance evidence: Build a study architecture diagram that connects each tool to its documented function and verify the expected data flow in a sample environment.

Explanation

Correct Answer

D:

Recognize Kubernetes for orchestration, Prometheus for metrics, Envoy for data-plane proxying and Fluentd for log collection in the cloud-native landscape. Acceptance evidence: Build a study architecture diagram that connects each tool to its documented function and verify the expected data flow in a sample environment. This pairing is justified because CNCF projects address different layers of a cloud-native platform and interoperability does not turn them into interchangeable cluster control-plane components.

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 recognize Kubernetes for orchestration, Prometheus for metrics, Envoy for data-plane proxying and Fluentd for log collection in the cloud-native landscape. Its confirming test is to build a study architecture diagram that connects each tool to its documented function and verify the expected data flow in a sample environment.

B:

This action and check address the distinct objective “Externalize application configuration from an image while protecting secrets” instead of the stated acceptance requirement. The matching action is to recognize Kubernetes for orchestration, Prometheus for metrics, Envoy for data-plane proxying and Fluentd for log collection in the cloud-native landscape. Its confirming test is to build a study architecture diagram that connects each tool to its documented function and verify the expected data flow in a sample environment.

C:

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 recognize Kubernetes for orchestration, Prometheus for metrics, Envoy for data-plane proxying and Fluentd for log collection in the cloud-native landscape. Its confirming test is to build a study architecture diagram that connects each tool to its documented function and verify the expected data flow in a sample environment.

Question 946

A retailer asks which CNCF tooling should collect logs versus place Pods onto nodes. 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. Change a workload's declared replicas and observe controllers update actual Pod count, understanding that status may lag behind spec during reconciliation.
  4. Choose service boundaries around business capabilities and operational needs, documenting communication cost, ownership and fault tolerance.

Explanation

Correct Answer

A:

The situation is that a retailer asks which CNCF tooling should collect logs versus place Pods onto nodes. Recognize Kubernetes for orchestration, Prometheus for metrics, Envoy for data-plane proxying and Fluentd for log collection in the cloud-native landscape. This resolves the issue because CNCF projects address different layers of a cloud-native platform and interoperability does not turn them into interchangeable cluster control-plane components. To verify, build a study architecture diagram that connects each tool to its documented function and verify the expected data flow in a sample environment.

Incorrect Answers

B:

The situation is that a retailer asks which CNCF tooling should collect logs versus place Pods onto nodes. 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, CNCF projects address different layers of a cloud-native platform and interoperability does not turn them into interchangeable cluster control-plane components.

C:

This option addresses the distinct objective “Explain desired state versus observed status in Kubernetes objects”, not the immediate requirement. The API stores a desired spec while controllers asynchronously react to observations; status describes progress, not a guarantee of immediate convergence. For the stated case, CNCF projects address different layers of a cloud-native platform and interoperability does not turn them into interchangeable cluster control-plane components.

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, CNCF projects address different layers of a cloud-native platform and interoperability does not turn them into interchangeable cluster control-plane components.

Question 947

A retailer asks which CNCF tooling should collect logs versus place Pods onto nodes. What underlying Kubernetes behavior is most relevant to this technical decision?

  1. Containers and Kubernetes APIs reduce some environment differences, but network load balancers, storage drivers and IAM integrations remain provider-specific.
  2. CNCF projects address different layers of a cloud-native platform and interoperability does not turn them into interchangeable cluster control-plane components.
  3. The controller manager runs controllers that observe API resources and make changes so current state moves toward desired state.
  4. 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.

Explanation

Correct Answer

B:

The situation is that a retailer asks which CNCF tooling should collect logs versus place Pods onto nodes. CNCF projects address different layers of a cloud-native platform and interoperability does not turn them into interchangeable cluster control-plane components. It supports this action: Recognize Kubernetes for orchestration, Prometheus for metrics, Envoy for data-plane proxying and Fluentd for log collection in the cloud-native landscape. To confirm, build a study architecture diagram that connects each tool to its documented function and verify the expected data flow in a sample environment.

Incorrect Answers

A:

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 CNCF projects address different layers of a cloud-native platform and interoperability does not turn them into interchangeable cluster control-plane components.

C:

That statement explains the distinct objective “Identify reconciliation work performed by kube-controller-manager” rather than the cause in this case. The deciding mechanism here is that CNCF projects address different layers of a cloud-native platform and interoperability does not turn them into interchangeable cluster control-plane components.

D:

The situation is that a retailer asks which CNCF tooling should collect logs versus place Pods onto nodes. 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 CNCF projects address different layers of a cloud-native platform and interoperability does not turn them into interchangeable cluster control-plane components.

Question 948

A retailer asks which CNCF tooling should collect logs versus place Pods onto nodes. What acceptance check most directly confirms this requirement is met?

  1. Build a study architecture diagram that connects each tool to its documented function and verify the expected data flow in a sample environment.
  2. Run a request across two synthetic services and verify traceparent propagation and two linked spans in the configured backend.
  3. Inspect node runtime information and compare a Pod's scheduling success with a runtime-reported image or sandbox failure.
  4. Model a synthetic two-service checkout dependency and compare rollout independence with failure and latency overhead against a single service.

Explanation

Correct Answer

A:

The situation is that a retailer asks which CNCF tooling should collect logs versus place Pods onto nodes. Build a study architecture diagram that connects each tool to its documented function and verify the expected data flow in a sample environment. This is the relevant test because CNCF projects address different layers of a cloud-native platform and interoperability does not turn them into interchangeable cluster control-plane components.

Incorrect Answers

B:

This check would help evaluate the distinct objective “Instrument services with OpenTelemetry context propagation”, but not the required result. For this case, build a study architecture diagram that connects each tool to its documented function and verify the expected data flow in a sample environment.

C:

This check would help evaluate the distinct objective “Explain the container runtime interface without conflating it with the control plane”, but not the required result. For this case, build a study architecture diagram that connects each tool to its documented function and verify the expected data flow in a sample environment.

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, build a study architecture diagram that connects each tool to its documented function and verify the expected data flow in a sample environment.

Question 949

A retailer asks which CNCF tooling should collect logs versus place Pods onto nodes. The team suggests: “Replace kube-scheduler with a Prometheus exporter because both are popular CNCF ecosystem projects.” Which failure should the reviewer anticipate?

  1. Cross-service latency remains difficult to diagnose because spans cannot be tied to one request path.
  2. Name lookup may succeed but no usable endpoint exists to receive traffic.
  3. External routing remains absent or policy is misunderstood, and internal identity controls may be incomplete.
  4. Cluster workload placement breaks because monitoring software cannot perform scheduler decisions.

Explanation

Correct Answer

D:

The situation is that a retailer asks which CNCF tooling should collect logs versus place Pods onto nodes. Cluster workload placement breaks because monitoring software cannot perform scheduler decisions. The shortcut creates this risk because CNCF projects address different layers of a cloud-native platform and interoperability does not turn them into interchangeable cluster control-plane components.

Incorrect Answers

A:

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 cluster workload placement breaks because monitoring software cannot perform scheduler decisions.

B:

That outcome concerns the distinct objective “Use EndpointSlices to connect Service selectors with actual backend Pods”; it is not the most direct consequence of this shortcut. The relevant consequence is that cluster workload placement breaks because monitoring software cannot perform scheduler decisions.

C:

The situation is that a retailer asks which CNCF tooling should collect logs versus place Pods onto nodes. 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 cluster workload placement breaks because monitoring software cannot perform scheduler decisions.

Question 950

A retailer asks which CNCF tooling should collect logs versus place Pods onto nodes. 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. Package reusable Kubernetes resource templates in a Helm chart and review rendered manifests and values before installation or upgrade. Acceptance evidence: Run helm template with staging values, inspect the generated Deployment and Service, and compare a revision's upgrade history.
  3. Recognize Kubernetes for orchestration, Prometheus for metrics, Envoy for data-plane proxying and Fluentd for log collection in the cloud-native landscape. Acceptance evidence: Build a study architecture diagram that connects each tool to its documented function and verify the expected data flow in a sample environment.
  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

C:

The situation is that a retailer asks which CNCF tooling should collect logs versus place Pods onto nodes. Recognize Kubernetes for orchestration, Prometheus for metrics, Envoy for data-plane proxying and Fluentd for log collection in the cloud-native landscape. Acceptance evidence: Build a study architecture diagram that connects each tool to its documented function and verify the expected data flow in a sample environment. This pairing is justified because CNCF projects address different layers of a cloud-native platform and interoperability does not turn them into interchangeable cluster control-plane components.

Incorrect Answers

A:

The situation is that a retailer asks which CNCF tooling should collect logs versus place Pods onto nodes. 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 recognize Kubernetes for orchestration, Prometheus for metrics, Envoy for data-plane proxying and Fluentd for log collection in the cloud-native landscape. Its confirming test is to build a study architecture diagram that connects each tool to its documented function and verify the expected data flow in a sample environment.

B:

This action and check address the distinct objective “Use Helm charts for parameterized application packages without equating them to cluster controllers” instead of the stated acceptance requirement. The matching action is to recognize Kubernetes for orchestration, Prometheus for metrics, Envoy for data-plane proxying and Fluentd for log collection in the cloud-native landscape. Its confirming test is to build a study architecture diagram that connects each tool to its documented function and verify the expected data flow in a sample environment.

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 recognize Kubernetes for orchestration, Prometheus for metrics, Envoy for data-plane proxying and Fluentd for log collection in the cloud-native landscape. Its confirming test is to build a study architecture diagram that connects each tool to its documented function and verify the expected data flow in a sample environment.

Kubernetes and Cloud Native Associate (KCNA) Practice Tests