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 96

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.

Question 951

A regional bank needs mutual TLS between payment microservices but only one public API entry point. 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 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.
  3. Configure anti-affinity against other Pods with a specific label so replicas prefer or require separate failure domains as appropriate.
  4. Choose service boundaries around business capabilities and operational needs, documenting communication cost, ownership and fault tolerance.

Explanation

Correct Answer

B:

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. This resolves the issue because 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. To verify, test a synthetic internal service call with mutual TLS policy and separately inspect the public Gateway listener and route status.

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

C:

This option addresses the distinct objective “Use Pod anti-affinity to reduce correlated replica failure”, not the immediate requirement. Pod anti-affinity considers labels on existing Pods and topology keys such as hostname; it does not directly guarantee unlimited nodes. For the stated case, 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.

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

Question 952

A regional bank needs mutual TLS between payment microservices but only one public API entry point. What underlying Kubernetes behavior is most relevant to this technical decision?

  1. A StorageClass defines how storage is provisioned and may use WaitForFirstConsumer to delay provisioning until scheduling requirements are known.
  2. CNCF maturity describes aspects of adoption and governance, not a blanket guarantee that every deployment or version is free of defects.
  3. Containers and Kubernetes APIs reduce some environment differences, but network load balancers, storage drivers and IAM integrations remain provider-specific.
  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

D:

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. It supports this action: 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. To confirm, test a synthetic internal service call with mutual TLS policy and separately inspect the public Gateway listener and route status.

Incorrect Answers

A:

That statement explains the distinct objective “Use StorageClass for dynamic volume provisioning rather than handcrafting every disk” rather than the cause in this case. The deciding mechanism here is that 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.

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

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

Question 953

A regional bank needs mutual TLS between payment microservices but only one public API entry point. What acceptance check most directly confirms this requirement is met?

  1. Read the cluster networking configuration, find a test Service and verify backend connectivity using the installed dataplane.
  2. Test a synthetic internal service call with mutual TLS policy and separately inspect the public Gateway listener and route status.
  3. Submit a reproducible synthetic issue and examine how maintainers triage, review and test a proposed patch before release.
  4. Model a synthetic two-service checkout dependency and compare rollout independence with failure and latency overhead against a single service.

Explanation

Correct Answer

B:

Test a synthetic internal service call with mutual TLS policy and separately inspect the public Gateway listener and route status. This is the relevant test because 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.

Incorrect Answers

A:

This check would help evaluate the distinct objective “Understand service proxy implementations without assuming kube-proxy is mandatory”, but not the required result. For this case, test a synthetic internal service call with mutual TLS policy and separately inspect the public Gateway listener and route status.

C:

This check would help evaluate the distinct objective “Use open community governance and contribution processes for sustainable cloud-native projects”, but not the required result. For this case, test a synthetic internal service call with mutual TLS policy and separately inspect the public Gateway listener and route status.

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, test a synthetic internal service call with mutual TLS policy and separately inspect the public Gateway listener and route status.

Question 954

A regional bank needs mutual TLS between payment microservices but only one public API entry point. The team suggests: “Assume installing Envoy sidecars alone makes every private service securely accessible from the public internet.” Which failure should the reviewer anticipate?

  1. An urgent fix is applied to only one environment and configuration drift grows difficult to audit.
  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. Cluster workload placement breaks because monitoring software cannot perform scheduler decisions.

Explanation

Correct Answer

C:

External routing remains absent or policy is misunderstood, and internal identity controls may be incomplete. The shortcut creates this risk because 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.

Incorrect Answers

A:

That outcome concerns the distinct objective “Use Kustomize overlays to adapt manifests without copying whole deployments”; it is not the most direct consequence of this shortcut. The relevant consequence is that external routing remains absent or policy is misunderstood, and internal identity controls may be incomplete.

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 external routing remains absent or policy is misunderstood, and internal identity controls may be incomplete.

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 external routing remains absent or policy is misunderstood, and internal identity controls may be incomplete.

Question 955

A regional bank needs mutual TLS between payment microservices but only one public API entry point. Which engineering change and test jointly addresses the scenario?

  1. 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.
  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. Review Retain versus Delete behavior for data-bearing PVs and test cleanup policy using synthetic non-sensitive data. Acceptance evidence: Create a disposable PVC with test content, delete its consuming Pod and then the claim, observing actual PV and backing volume behavior.
  4. Use a supported service mesh when fine-grained internal service-to-service security and telemetry are needed, while separately configuring north-south ingress or gateway exposure. Acceptance evidence: Test a synthetic internal service call with mutual TLS policy and separately inspect the public Gateway listener and route status.

Explanation

Correct Answer

D:

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. This pairing is justified because 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.

Incorrect Answers

A:

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 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. Its confirming test is to test a synthetic internal service call with mutual TLS policy and separately inspect the public Gateway listener and route status.

B:

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 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. Its confirming test is to test a synthetic internal service call with mutual TLS policy and separately inspect the public Gateway listener and route status.

C:

This action and check address the distinct objective “Compare PV reclaim policies and explain data retention on PVC deletion” instead of the stated acceptance requirement. The matching action is to 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. Its confirming test is to test a synthetic internal service call with mutual TLS policy and separately inspect the public Gateway listener and route status.

Question 956

A travel site deploys a mesh and wants to know why no external hostname was automatically created. What technical action should the platform team take in this situation?

  1. Follow a project's published governance, issue templates, contributor guides and code of conduct when reporting bugs or proposing changes.
  2. Choose service boundaries around business capabilities and operational needs, documenting communication cost, ownership and fault tolerance.
  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. Choose an appropriate RollingUpdate strategy with maxSurge and maxUnavailable, and verify readiness and service traffic during replacement.

Explanation

Correct Answer

C:

The situation is that a travel site deploys a mesh and wants to know why no external hostname was automatically created. 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. This resolves the issue because 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. To verify, test a synthetic internal service call with mutual TLS policy and separately inspect the public Gateway listener and route status.

Incorrect Answers

A:

This option addresses the distinct objective “Use open community governance and contribution processes for sustainable cloud-native projects”, not the immediate requirement. Open-source community processes provide transparent review and shared maintenance, but do not imply unreviewed external code should be merged into production. For the stated case, 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.

B:

The situation is that a travel site deploys a mesh and wants to know why no external hostname was automatically created. 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, 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.

D:

This option addresses the distinct objective “Configure Deployment rolling updates with availability safeguards”, not the immediate requirement. A rolling Deployment temporarily creates and removes Pods within its surge and unavailable budgets, but readiness is required for new replicas to count as available. For the stated case, 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.

Question 957

A travel site deploys a mesh and wants to know why no external hostname was automatically created. What underlying Kubernetes behavior is most relevant to this technical decision?

  1. A Deployment owns ReplicaSets that manage matching Pods and supports declarative rollout history, unlike an independent Pod object.
  2. Microservices permit independent deployment and scaling but introduce network dependencies and data consistency challenges; a monolith can remain appropriate for smaller teams.
  3. A service level objective is a target for measured user-facing behavior; error budgets quantify allowed misses and help prioritize release risk.
  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

D:

The situation is that a travel site deploys a mesh and wants to know why no external hostname was automatically created. 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. It supports this action: 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. To confirm, test a synthetic internal service call with mutual TLS policy and separately inspect the public Gateway listener and route status.

Incorrect Answers

A:

That statement explains the distinct objective “Distinguish Deployment desired state from a manually created Pod” rather than the cause in this case. The deciding mechanism here is that 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.

B:

That statement explains the distinct objective “Contrast cloud-native microservices with a monolith without treating either as inherently superior” rather than the cause in this case. The deciding mechanism here is that 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.

C:

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

Question 958

A travel site deploys a mesh and wants to know why no external hostname was automatically created. What acceptance check most directly confirms this requirement is met?

  1. Model a synthetic two-service checkout dependency and compare rollout independence with failure and latency overhead against a single service.
  2. Submit a reproducible synthetic issue and examine how maintainers triage, review and test a proposed patch before release.
  3. Test a synthetic internal service call with mutual TLS policy and separately inspect the public Gateway listener and route status.
  4. Apply a test manifest with impossible node constraints, then inspect the accepted spec and Pending status/Events.

Explanation

Correct Answer

C:

The situation is that a travel site deploys a mesh and wants to know why no external hostname was automatically created. Test a synthetic internal service call with mutual TLS policy and separately inspect the public Gateway listener and route status. This is the relevant test because 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.

Incorrect Answers

A:

The situation is that a travel site deploys a mesh and wants to know why no external hostname was automatically created. 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, test a synthetic internal service call with mutual TLS policy and separately inspect the public Gateway listener and route status.

B:

The situation is that a travel site deploys a mesh and wants to know why no external hostname was automatically created. This check would help evaluate the distinct objective “Use open community governance and contribution processes for sustainable cloud-native projects”, but not the required result. For this case, test a synthetic internal service call with mutual TLS policy and separately inspect the public Gateway listener and route status.

D:

This check would help evaluate the distinct objective “Interpret Kubernetes spec and status fields without confusing intent with condition”, but not the required result. For this case, test a synthetic internal service call with mutual TLS policy and separately inspect the public Gateway listener and route status.

Question 959

A travel site deploys a mesh and wants to know why no external hostname was automatically created. The team suggests: “Assume installing Envoy sidecars alone makes every private service securely accessible from the public internet.” Which failure should the reviewer anticipate?

  1. A migration fails because backend volume classes and cloud authentication semantics differ.
  2. DNS disruption may affect the whole cluster while the actual routing mismatch remains unchanged.
  3. Monitoring dashboards show empty or stale series because the expected metrics were never exposed or scraped.
  4. External routing remains absent or policy is misunderstood, and internal identity controls may be incomplete.

Explanation

Correct Answer

D:

The situation is that a travel site deploys a mesh and wants to know why no external hostname was automatically created. External routing remains absent or policy is misunderstood, and internal identity controls may be incomplete. The shortcut creates this risk because 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.

Incorrect Answers

A:

That outcome concerns the distinct objective “Apply cloud-native portability and immutable infrastructure principles pragmatically”; it is not the most direct consequence of this shortcut. The relevant consequence is that external routing remains absent or policy is misunderstood, and internal identity controls may be incomplete.

B:

That outcome concerns the distinct objective “Distinguish a failed Service selector from broken DNS or a failing backend”; it is not the most direct consequence of this shortcut. The relevant consequence is that external routing remains absent or policy is misunderstood, and internal identity controls may be incomplete.

C:

That outcome concerns the distinct objective “Understand Prometheus pull-based metrics collection and exporters”; it is not the most direct consequence of this shortcut. The relevant consequence is that external routing remains absent or policy is misunderstood, and internal identity controls may be incomplete.

Question 960

A travel site deploys a mesh and wants to know why no external hostname was automatically created. Which engineering change and test jointly addresses the scenario?

  1. 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.
  2. 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.
  3. Define symptom-based Prometheus alerting rules with sensible durations and route alerts through Alertmanager to the responsible service team. Acceptance evidence: Trigger a controlled error-rate alert, verify its pending/firing transition and confirm the correct team receives a grouped notification.
  4. Inspect Deployment, ReplicaSet and Pod owner references when verifying which controller maintains replica count. Acceptance evidence: Run kubectl get rs and kubectl describe deployment for a test rollout and verify the expected owner chain.

Explanation

Correct Answer

A:

The situation is that a travel site deploys a mesh and wants to know why no external hostname was automatically created. 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. This pairing is justified because 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.

Incorrect Answers

B:

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 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. Its confirming test is to test a synthetic internal service call with mutual TLS policy and separately inspect the public Gateway listener and route status.

C:

This action and check address the distinct objective “Build meaningful alert rules and route notifications through Alertmanager” instead of the stated acceptance requirement. The matching action is to 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. Its confirming test is to test a synthetic internal service call with mutual TLS policy and separately inspect the public Gateway listener and route status.

D:

This action and check address the distinct objective “Interpret ReplicaSet ownership and selectors in a Deployment” instead of the stated acceptance requirement. The matching action is to 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. Its confirming test is to test a synthetic internal service call with mutual TLS policy and separately inspect the public Gateway listener and route status.

Kubernetes and Cloud Native Associate (KCNA) Practice Tests