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 97

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.

Question 961

A public university compares moving an internal web service between on-premises and hosted Kubernetes. Which supported Kubernetes practice directly addresses the stated requirement?

  1. Set runAsNonRoot, suitable user IDs and drop unneeded Linux capabilities rather than assuming every container requires root.
  2. Package workloads in standard images and declarative manifests while documenting external dependencies and provider-specific integrations before claiming portability.
  3. Use metrics for measurable trends, logs for event detail and distributed traces for individual transaction paths while sharing correlation identifiers.
  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.

Explanation

Correct Answer

B:

Package workloads in standard images and declarative manifests while documenting external dependencies and provider-specific integrations before claiming portability. This resolves the issue because containers and Kubernetes APIs reduce some environment differences, but network load balancers, storage drivers and IAM integrations remain provider-specific. To verify, deploy a synthetic stateless workload to two conformant clusters and record which storage, ingress and identity settings require changes.

Incorrect Answers

A:

This option addresses the distinct objective “Run images with least-privilege runtime security contexts”, not the immediate requirement. SecurityContext configures process identity and privilege boundaries, and unnecessary root privileges increase impact if an application is compromised. For the stated case, containers and Kubernetes APIs reduce some environment differences, but network load balancers, storage drivers and IAM integrations remain provider-specific.

C:

This option addresses the distinct objective “Explain metrics, logs and traces as complementary observability signals”, not the immediate requirement. Each telemetry type represents a different view of runtime state and links through context can connect a symptom to a specific service hop. For the stated case, containers and Kubernetes APIs reduce some environment differences, but network load balancers, storage drivers and IAM integrations remain provider-specific.

D:

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, containers and Kubernetes APIs reduce some environment differences, but network load balancers, storage drivers and IAM integrations remain provider-specific.

Question 962

A public university compares moving an internal web service between on-premises and hosted Kubernetes. Which causal explanation supports the intended design choice?

  1. Containers and Kubernetes APIs reduce some environment differences, but network load balancers, storage drivers and IAM integrations remain provider-specific.
  2. Microservices permit independent deployment and scaling but introduce network dependencies and data consistency challenges; a monolith can remain appropriate for smaller teams.
  3. Kubernetes expects a Pod network providing Pod-to-Pod connectivity; the CNI implementation configures networking while Services provide stable virtual access to changing endpoints.
  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

A:

Containers and Kubernetes APIs reduce some environment differences, but network load balancers, storage drivers and IAM integrations remain provider-specific. It supports this action: Package workloads in standard images and declarative manifests while documenting external dependencies and provider-specific integrations before claiming portability. To confirm, deploy a synthetic stateless workload to two conformant clusters and record which storage, ingress and identity settings require changes.

Incorrect Answers

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 containers and Kubernetes APIs reduce some environment differences, but network load balancers, storage drivers and IAM integrations remain provider-specific.

C:

That statement explains the distinct objective “Distinguish the CNI Pod network from Service discovery and routing” rather than the cause in this case. The deciding mechanism here is that containers and Kubernetes APIs reduce some environment differences, but network load balancers, storage drivers and IAM integrations remain provider-specific.

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 containers and Kubernetes APIs reduce some environment differences, but network load balancers, storage drivers and IAM integrations remain provider-specific.

Question 963

A public university compares moving an internal web service between on-premises and hosted Kubernetes. Which test provides the strongest evidence of a correct implementation?

  1. Test a synthetic standard API manifest and OpenTelemetry trace export across two platforms, documenting any unsupported extensions.
  2. Deploy a synthetic stateless workload to two conformant clusters and record which storage, ingress and identity settings require changes.
  3. Test a synthetic internal service call with mutual TLS policy and separately inspect the public Gateway listener and route status.
  4. Run a synthetic read-only Pod with a restricted ServiceAccount and verify one permitted API read and one forbidden Secret list.

Explanation

Correct Answer

B:

Deploy a synthetic stateless workload to two conformant clusters and record which storage, ingress and identity settings require changes. This is the relevant test because containers and Kubernetes APIs reduce some environment differences, but network load balancers, storage drivers and IAM integrations remain provider-specific.

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, deploy a synthetic stateless workload to two conformant clusters and record which storage, ingress and identity settings require changes.

C:

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, deploy a synthetic stateless workload to two conformant clusters and record which storage, ingress and identity settings require changes.

D:

This check would help evaluate the distinct objective “Differentiate ServiceAccounts from human kubeconfig identities”, but not the required result. For this case, deploy a synthetic stateless workload to two conformant clusters and record which storage, ingress and identity settings require changes.

Question 964

A public university compares moving an internal web service between on-premises and hosted Kubernetes. A shortcut is proposed: “Claim a stateful Kubernetes Deployment can move unchanged among all cloud providers without checking storage and identity assumptions.” Which technical consequence follows most closely?

  1. An urgent fix is applied to only one environment and configuration drift grows difficult to audit.
  2. External routing remains absent or policy is misunderstood, and internal identity controls may be incomplete.
  3. A migration fails because backend volume classes and cloud authentication semantics differ.
  4. The operator may deploy unsupported changes without release provenance or a responsible maintenance path.

Explanation

Correct Answer

C:

A migration fails because backend volume classes and cloud authentication semantics differ. The shortcut creates this risk because containers and Kubernetes APIs reduce some environment differences, but network load balancers, storage drivers and IAM integrations remain provider-specific.

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 a migration fails because backend volume classes and cloud authentication semantics differ.

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 a migration fails because backend volume classes and cloud authentication semantics differ.

D:

That outcome concerns the distinct objective “Use open community governance and contribution processes for sustainable cloud-native projects”; it is not the most direct consequence of this shortcut. The relevant consequence is that a migration fails because backend volume classes and cloud authentication semantics differ.

Question 965

A public university compares moving an internal web service between on-premises and hosted Kubernetes. Which combined solution and independent check are most directly justified?

  1. Resolve an object's apiVersion, kind, metadata namespace and name before applying or deleting it. Acceptance evidence: List Deployments with --all-namespaces and inspect one manifest's apiVersion and kind to target a specific test object.
  2. Use a supported service mesh when fine-grained internal service-to-service security and telemetry are needed, while separately configuring north-south ingress or gateway exposure. Acceptance evidence: Test a synthetic internal service call with mutual TLS policy and separately inspect the public Gateway listener and route status.
  3. 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.
  4. 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.

Explanation

Correct Answer

D:

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. This pairing is justified because containers and Kubernetes APIs reduce some environment differences, but network load balancers, storage drivers and IAM integrations remain provider-specific.

Incorrect Answers

A:

This action and check address the distinct objective “Read the API resource model using namespaces and names rather than guessing ownership” instead of the stated acceptance requirement. The matching action is to package workloads in standard images and declarative manifests while documenting external dependencies and provider-specific integrations before claiming portability. Its confirming test is to deploy a synthetic stateless workload to two conformant clusters and record which storage, ingress and identity settings require changes.

B:

This action and check address the distinct objective “Distinguish service mesh traffic management from external ingress routing” instead of the stated acceptance requirement. The matching action is to package workloads in standard images and declarative manifests while documenting external dependencies and provider-specific integrations before claiming portability. Its confirming test is to deploy a synthetic stateless workload to two conformant clusters and record which storage, ingress and identity settings require changes.

C:

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 package workloads in standard images and declarative manifests while documenting external dependencies and provider-specific integrations before claiming portability. Its confirming test is to deploy a synthetic stateless workload to two conformant clusters and record which storage, ingress and identity settings require changes.

Question 966

A retailer needs a portability assessment for its customer application with attached managed database services. Which Kubernetes or cloud-native implementation decision best solves the stated problem?

  1. Recognize Kubernetes for orchestration, Prometheus for metrics, Envoy for data-plane proxying and Fluentd for log collection in the cloud-native landscape.
  2. Inspect kubelet-reported Pod and container conditions when a scheduled workload fails to start, while keeping cluster resources managed through the API.
  3. Define a user-centered service level indicator and objective, such as percentage of successful requests within a latency threshold over a stated window.
  4. Package workloads in standard images and declarative manifests while documenting external dependencies and provider-specific integrations before claiming portability.

Explanation

Correct Answer

D:

The situation is that a retailer needs a portability assessment for its customer application with attached managed database services. Package workloads in standard images and declarative manifests while documenting external dependencies and provider-specific integrations before claiming portability. This resolves the issue because containers and Kubernetes APIs reduce some environment differences, but network load balancers, storage drivers and IAM integrations remain provider-specific. To verify, deploy a synthetic stateless workload to two conformant clusters and record which storage, ingress and identity settings require changes.

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, containers and Kubernetes APIs reduce some environment differences, but network load balancers, storage drivers and IAM integrations remain provider-specific.

B:

This option addresses the distinct objective “Recognize the kubelet role in local Pod lifecycle management”, not the immediate requirement. Each kubelet watches assigned Pod specifications and coordinates the container runtime, volumes and health information on its node. For the stated case, containers and Kubernetes APIs reduce some environment differences, but network load balancers, storage drivers and IAM integrations remain provider-specific.

C:

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, containers and Kubernetes APIs reduce some environment differences, but network load balancers, storage drivers and IAM integrations remain provider-specific.

Question 967

A retailer needs a portability assessment for its customer application with attached managed database services. Which platform mechanism explains why the suitable approach works?

  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. Service meshes commonly use proxies or ambient dataplanes to control east-west traffic; ingress/gateway handling addresses entry routes and can integrate with the mesh.
  4. Image provenance reduces accidental or malicious image substitution; mutable tags alone cannot prove build integrity or content identity.

Explanation

Correct Answer

A:

The situation is that a retailer needs a portability assessment for its customer application with attached managed database services. Containers and Kubernetes APIs reduce some environment differences, but network load balancers, storage drivers and IAM integrations remain provider-specific. It supports this action: Package workloads in standard images and declarative manifests while documenting external dependencies and provider-specific integrations before claiming portability. To confirm, deploy a synthetic stateless workload to two conformant clusters and record which storage, ingress and identity settings require changes.

Incorrect Answers

B:

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 containers and Kubernetes APIs reduce some environment differences, but network load balancers, storage drivers and IAM integrations remain provider-specific.

C:

That statement explains the distinct objective “Distinguish service mesh traffic management from external ingress routing” rather than the cause in this case. The deciding mechanism here is that containers and Kubernetes APIs reduce some environment differences, but network load balancers, storage drivers and IAM integrations remain provider-specific.

D:

That statement explains the distinct objective “Use image provenance and policy controls without trusting mutable tags” rather than the cause in this case. The deciding mechanism here is that containers and Kubernetes APIs reduce some environment differences, but network load balancers, storage drivers and IAM integrations remain provider-specific.

Question 968

A retailer needs a portability assessment for its customer application with attached managed database services. Which controlled observation would best validate the intended improvement?

  1. Verify a synthetic exporter is listed UP in Prometheus target status and query its request counter after generating traffic.
  2. Create a small claim in a test StorageClass, inspect its Bound status and restart the consuming Pod to check data persistence.
  3. Deploy a synthetic stateless workload to two conformant clusters and record which storage, ingress and identity settings require changes.
  4. Model a synthetic two-service checkout dependency and compare rollout independence with failure and latency overhead against a single service.

Explanation

Correct Answer

C:

The situation is that a retailer needs a portability assessment for its customer application with attached managed database services. Deploy a synthetic stateless workload to two conformant clusters and record which storage, ingress and identity settings require changes. This is the relevant test because containers and Kubernetes APIs reduce some environment differences, but network load balancers, storage drivers and IAM integrations remain provider-specific.

Incorrect Answers

A:

This check would help evaluate the distinct objective “Understand Prometheus pull-based metrics collection and exporters”, but not the required result. For this case, deploy a synthetic stateless workload to two conformant clusters and record which storage, ingress and identity settings require changes.

B:

This check would help evaluate the distinct objective “Understand PersistentVolumeClaim binding to persistent storage resources”, but not the required result. For this case, deploy a synthetic stateless workload to two conformant clusters and record which storage, ingress and identity settings require changes.

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, deploy a synthetic stateless workload to two conformant clusters and record which storage, ingress and identity settings require changes.

Question 969

A retailer needs a portability assessment for its customer application with attached managed database services. An engineer proposes: “Claim a stateful Kubernetes Deployment can move unchanged among all cloud providers without checking storage and identity assumptions.” What adverse outcome would be most direct?

  1. Sensitive workloads may remain reachable until actual identity and traffic controls are installed.
  2. A migration fails because backend volume classes and cloud authentication semantics differ.
  3. Network calls and coordination complexity grow without a business reason, creating new failure modes.
  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 retailer needs a portability assessment for its customer application with attached managed database services. A migration fails because backend volume classes and cloud authentication semantics differ. The shortcut creates this risk because containers and Kubernetes APIs reduce some environment differences, but network load balancers, storage drivers and IAM integrations remain provider-specific.

Incorrect Answers

A:

That outcome concerns the distinct objective “Use namespaces as organizational scopes without treating them as firewalls”; it is not the most direct consequence of this shortcut. The relevant consequence is that a migration fails because backend volume classes and cloud authentication semantics differ.

C:

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 a migration fails because backend volume classes and cloud authentication semantics differ.

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 a migration fails because backend volume classes and cloud authentication semantics differ.

Question 970

A retailer needs a portability assessment for its customer application with attached managed database services. What pair of supported action and practical verification should be approved?

  1. 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.
  2. Assign related namespaced resources to a project namespace and enforce authorization and network isolation with separate policies. Acceptance evidence: Create matching Service names in two namespaces and test separately configured RBAC and NetworkPolicy access boundaries.
  3. Package workloads in standard images and declarative manifests while documenting external dependencies and provider-specific integrations before claiming portability. Acceptance evidence: Deploy a synthetic stateless workload to two conformant clusters and record which storage, ingress and identity settings require changes.
  4. Use 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

C:

The situation is that a retailer needs a portability assessment for its customer application with attached managed database services. 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. This pairing is justified because containers and Kubernetes APIs reduce some environment differences, but network load balancers, storage drivers and IAM integrations remain provider-specific.

Incorrect Answers

A:

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 package workloads in standard images and declarative manifests while documenting external dependencies and provider-specific integrations before claiming portability. Its confirming test is to deploy a synthetic stateless workload to two conformant clusters and record which storage, ingress and identity settings require changes.

B:

This action and check address the distinct objective “Use namespaces as organizational scopes without treating them as firewalls” instead of the stated acceptance requirement. The matching action is to package workloads in standard images and declarative manifests while documenting external dependencies and provider-specific integrations before claiming portability. Its confirming test is to deploy a synthetic stateless workload to two conformant clusters and record which storage, ingress and identity settings require changes.

D:

The situation is that a retailer needs a portability assessment for its customer application with attached managed database services. 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 package workloads in standard images and declarative manifests while documenting external dependencies and provider-specific integrations before claiming portability. Its confirming test is to deploy a synthetic stateless workload to two conformant clusters and record which storage, ingress and identity settings require changes.

Kubernetes and Cloud Native Associate (KCNA) Practice Tests