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 27

Question 260

A university GPU lab uses node labels to keep non-GPU tutorial Pods away from specialized compute nodes. Which implementation together with matching acceptance evidence best meets this case?

  1. Review requests, limits, QoS class and termination reasons rather than interpreting every restart as a scheduler failure. Acceptance evidence: Create a synthetic CPU-intensive workload with tight CPU limits and compare throttling metrics with an OOMKilled test Pod.
  2. 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.
  3. Label eligible nodes for a test hardware property and use nodeSelector when a Pod must run only on matching nodes. Acceptance evidence: Label one worker disk=ssd, apply a Pod requiring disk=ssd and confirm it binds only to the matching eligible worker.
  4. Verify that the installed Container Storage Interface driver supports the requested persistent storage and inspect driver controller/node components when mounting fails. Acceptance evidence: Inspect CSI driver registration, test provisioning a claim and review attachment/mount Events for a synthetic workload.

Explanation

Correct Answer

C:

The situation is that a university GPU lab uses node labels to keep non-GPU tutorial Pods away from specialized compute nodes. Label eligible nodes for a test hardware property and use nodeSelector when a Pod must run only on matching nodes. Acceptance evidence: Label one worker disk=ssd, apply a Pod requiring disk=ssd and confirm it binds only to the matching eligible worker. This pairing is justified because the scheduler enforces required node label matches in addition to resource and other constraints; labels do not create actual hardware capabilities.

Incorrect Answers

A:

This action and check address the distinct objective “Distinguish memory limits from CPU throttling for scheduling and runtime symptoms” instead of the stated acceptance requirement. The matching action is to label eligible nodes for a test hardware property and use nodeSelector when a Pod must run only on matching nodes. Its confirming test is to label one worker disk=ssd, apply a Pod requiring disk=ssd and confirm it binds only to the matching eligible worker.

B:

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 label eligible nodes for a test hardware property and use nodeSelector when a Pod must run only on matching nodes. Its confirming test is to label one worker disk=ssd, apply a Pod requiring disk=ssd and confirm it binds only to the matching eligible worker.

D:

This action and check address the distinct objective “Understand CSI drivers and volume attachment responsibilities” instead of the stated acceptance requirement. The matching action is to label eligible nodes for a test hardware property and use nodeSelector when a Pod must run only on matching nodes. Its confirming test is to label one worker disk=ssd, apply a Pod requiring disk=ssd and confirm it binds only to the matching eligible worker.

Question 261

A tourism API prefers nearby nodes but should start elsewhere if a zone is temporarily full. Which Kubernetes or cloud-native implementation decision best solves the stated problem?

  1. Give each workload an appropriate Kubernetes ServiceAccount and narrow RBAC permissions rather than embedding an administrator kubeconfig in its image.
  2. Combine a default-deny baseline with narrow app-label and namespace-label NetworkPolicy rules for approved traffic.
  3. Use requiredDuringSchedulingIgnoredDuringExecution for mandatory constraints and preferredDuringSchedulingIgnoredDuringExecution for a soft placement preference.
  4. Choose Pod affinity only when co-locating related workloads is beneficial and verify independent network policies still govern traffic.

Explanation

Correct Answer

C:

Use requiredDuringSchedulingIgnoredDuringExecution for mandatory constraints and preferredDuringSchedulingIgnoredDuringExecution for a soft placement preference. This resolves the issue because a required affinity expression blocks scheduling onto nonmatching nodes; a preferred expression influences scoring but permits fallback when necessary. To verify, test the workload with and without a preferred zone and verify it still schedules when preferred nodes are busy.

Incorrect Answers

A:

This option addresses the distinct objective “Differentiate ServiceAccounts from human kubeconfig identities”, not the immediate requirement. ServiceAccounts provide workload identities for Kubernetes API access; human authentication and authorization are separately configured and should not be shared as static image secrets. For the stated case, a required affinity expression blocks scheduling onto nonmatching nodes; a preferred expression influences scoring but permits fallback when necessary.

B:

This option addresses the distinct objective “Limit workload-to-workload access with explicit NetworkPolicy allow rules”, not the immediate requirement. NetworkPolicies select Pods and define allowed flows; when a Pod becomes isolated, traffic is allowed only as permitted by applicable rules and plugin behavior. For the stated case, a required affinity expression blocks scheduling onto nonmatching nodes; a preferred expression influences scoring but permits fallback when necessary.

D:

This option addresses the distinct objective “Use Pod affinity for co-location without assuming it creates networking permissions”, not the immediate requirement. Pod affinity affects scheduler placement relative to labeled Pods in selected topology domains, not application authentication or firewall rules. For the stated case, a required affinity expression blocks scheduling onto nonmatching nodes; a preferred expression influences scoring but permits fallback when necessary.

Question 262

A tourism API prefers nearby nodes but should start elsewhere if a zone is temporarily full. Which platform mechanism explains why the suitable approach works?

  1. Topology spread constraints compare Pod distribution in topology domains and can restrict or prefer placement depending on whenUnsatisfiable.
  2. Healthy direct IP connectivity with failed name resolution suggests a DNS path issue; failed Pod-to-Pod IP traffic suggests a lower-level network problem.
  3. Cordon marks a node unschedulable for new ordinary Pods; drain evicts managed workloads when policies and availability permit.
  4. A required affinity expression blocks scheduling onto nonmatching nodes; a preferred expression influences scoring but permits fallback when necessary.

Explanation

Correct Answer

D:

A required affinity expression blocks scheduling onto nonmatching nodes; a preferred expression influences scoring but permits fallback when necessary. It supports this action: Use requiredDuringSchedulingIgnoredDuringExecution for mandatory constraints and preferredDuringSchedulingIgnoredDuringExecution for a soft placement preference. To confirm, test the workload with and without a preferred zone and verify it still schedules when preferred nodes are busy.

Incorrect Answers

A:

That statement explains the distinct objective “Spread replicas across failure domains with topologySpreadConstraints” rather than the cause in this case. The deciding mechanism here is that a required affinity expression blocks scheduling onto nonmatching nodes; a preferred expression influences scoring but permits fallback when necessary.

B:

That statement explains the distinct objective “Diagnose cluster DNS separately from Pod network reachability” rather than the cause in this case. The deciding mechanism here is that a required affinity expression blocks scheduling onto nonmatching nodes; a preferred expression influences scoring but permits fallback when necessary.

C:

That statement explains the distinct objective “Use cordon and drain with disruption considerations for planned node maintenance” rather than the cause in this case. The deciding mechanism here is that a required affinity expression blocks scheduling onto nonmatching nodes; a preferred expression influences scoring but permits fallback when necessary.

Question 263

A tourism API prefers nearby nodes but should start elsewhere if a zone is temporarily full. Which controlled observation would best validate the intended improvement?

  1. Set an intentionally excessive memory request in a lab and inspect Pod Pending Events before adjusting it.
  2. Test the workload with and without a preferred zone and verify it still schedules when preferred nodes are busy.
  3. Run kubectl get rs and kubectl describe deployment for a test rollout and verify the expected owner chain.
  4. Create two controlled faulty workloads, one requiring an impossible node label and one referencing a missing image tag, then compare Events.

Explanation

Correct Answer

B:

Test the workload with and without a preferred zone and verify it still schedules when preferred nodes are busy. This is the relevant test because a required affinity expression blocks scheduling onto nonmatching nodes; a preferred expression influences scoring but permits fallback when necessary.

Incorrect Answers

A:

This check would help evaluate the distinct objective “Use container resource requests to help the scheduler fit Pods on nodes”, but not the required result. For this case, test the workload with and without a preferred zone and verify it still schedules when preferred nodes are busy.

C:

This check would help evaluate the distinct objective “Interpret ReplicaSet ownership and selectors in a Deployment”, but not the required result. For this case, test the workload with and without a preferred zone and verify it still schedules when preferred nodes are busy.

D:

This check would help evaluate the distinct objective “Separate Pending scheduling failures from ImagePullBackOff errors”, but not the required result. For this case, test the workload with and without a preferred zone and verify it still schedules when preferred nodes are busy.

Question 264

A tourism API prefers nearby nodes but should start elsewhere if a zone is temporarily full. An engineer proposes: “Use a preferred affinity rule as a compliance guarantee that sensitive Pods can never land outside a region.” What adverse outcome would be most direct?

  1. The scheduler may legally use a non-preferred node, violating the policy that was mistakenly assumed mandatory.
  2. The Pod might schedule on any other feasible node because tolerance is not a selection constraint.
  3. Operators can see the metadata but the Service cannot select the desired Pods using that annotation.
  4. The true database bottleneck remains and resource adjustments can increase cost without fixing service behavior.

Explanation

Correct Answer

A:

The scheduler may legally use a non-preferred node, violating the policy that was mistakenly assumed mandatory. The shortcut creates this risk because a required affinity expression blocks scheduling onto nonmatching nodes; a preferred expression influences scoring but permits fallback when necessary.

Incorrect Answers

B:

That outcome concerns the distinct objective “Understand taints and tolerations as repulsion controls”; it is not the most direct consequence of this shortcut. The relevant consequence is that the scheduler may legally use a non-preferred node, violating the policy that was mistakenly assumed mandatory.

C:

That outcome concerns the distinct objective “Use annotations for tool metadata rather than workload selection”; it is not the most direct consequence of this shortcut. The relevant consequence is that the scheduler may legally use a non-preferred node, violating the policy that was mistakenly assumed mandatory.

D:

That outcome concerns the distinct objective “Use metrics, logs and traces together when investigating cross-service latency”; it is not the most direct consequence of this shortcut. The relevant consequence is that the scheduler may legally use a non-preferred node, violating the policy that was mistakenly assumed mandatory.

Question 265

A tourism API prefers nearby nodes but should start elsewhere if a zone is temporarily full. What pair of supported action and practical verification should be approved?

  1. Define meaningful topology keys, matching label selectors and skew limits when balancing eligible replicas across nodes or zones. Acceptance evidence: Deploy a matching replica set across two labeled zones and inspect skew after adding a new Pod.
  2. Label eligible nodes for a test hardware property and use nodeSelector when a Pod must run only on matching nodes. Acceptance evidence: Label one worker disk=ssd, apply a Pod requiring disk=ssd and confirm it binds only to the matching eligible worker.
  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 requiredDuringSchedulingIgnoredDuringExecution for mandatory constraints and preferredDuringSchedulingIgnoredDuringExecution for a soft placement preference. Acceptance evidence: Test the workload with and without a preferred zone and verify it still schedules when preferred nodes are busy.

Explanation

Correct Answer

D:

Use requiredDuringSchedulingIgnoredDuringExecution for mandatory constraints and preferredDuringSchedulingIgnoredDuringExecution for a soft placement preference. Acceptance evidence: Test the workload with and without a preferred zone and verify it still schedules when preferred nodes are busy. This pairing is justified because a required affinity expression blocks scheduling onto nonmatching nodes; a preferred expression influences scoring but permits fallback when necessary.

Incorrect Answers

A:

This action and check address the distinct objective “Spread replicas across failure domains with topologySpreadConstraints” instead of the stated acceptance requirement. The matching action is to use requiredDuringSchedulingIgnoredDuringExecution for mandatory constraints and preferredDuringSchedulingIgnoredDuringExecution for a soft placement preference. Its confirming test is to test the workload with and without a preferred zone and verify it still schedules when preferred nodes are busy.

B:

This action and check address the distinct objective “Use nodeSelector to place a workload on nodes with required labels” instead of the stated acceptance requirement. The matching action is to use requiredDuringSchedulingIgnoredDuringExecution for mandatory constraints and preferredDuringSchedulingIgnoredDuringExecution for a soft placement preference. Its confirming test is to test the workload with and without a preferred zone and verify it still schedules when preferred nodes are busy.

C:

This action and check address the distinct objective “Apply cloud-native portability and immutable infrastructure principles pragmatically” instead of the stated acceptance requirement. The matching action is to use requiredDuringSchedulingIgnoredDuringExecution for mandatory constraints and preferredDuringSchedulingIgnoredDuringExecution for a soft placement preference. Its confirming test is to test the workload with and without a preferred zone and verify it still schedules when preferred nodes are busy.

Question 266

An insurer must enforce a regulated node pool while an optional app merely prefers cheaper workers. Which Kubernetes or cloud-native implementation decision best solves the stated problem?

  1. Identify whether the cluster uses kube-proxy or an alternative Service dataplane before diagnosing virtual Service IP forwarding behavior.
  2. Define symptom-based Prometheus alerting rules with sensible durations and route alerts through Alertmanager to the responsible service team.
  3. Use requiredDuringSchedulingIgnoredDuringExecution for mandatory constraints and preferredDuringSchedulingIgnoredDuringExecution for a soft placement preference.
  4. Review requests, limits, QoS class and termination reasons rather than interpreting every restart as a scheduler failure.

Explanation

Correct Answer

C:

The situation is that an insurer must enforce a regulated node pool while an optional app merely prefers cheaper workers. Use requiredDuringSchedulingIgnoredDuringExecution for mandatory constraints and preferredDuringSchedulingIgnoredDuringExecution for a soft placement preference. This resolves the issue because a required affinity expression blocks scheduling onto nonmatching nodes; a preferred expression influences scoring but permits fallback when necessary. To verify, test the workload with and without a preferred zone and verify it still schedules when preferred nodes are busy.

Incorrect Answers

A:

This option addresses the distinct objective “Understand service proxy implementations without assuming kube-proxy is mandatory”, not the immediate requirement. Kube-proxy can maintain node networking rules for Services, but supported network implementations may replace this function. For the stated case, a required affinity expression blocks scheduling onto nonmatching nodes; a preferred expression influences scoring but permits fallback when necessary.

B:

This option addresses the distinct objective “Build meaningful alert rules and route notifications through Alertmanager”, not the immediate requirement. Alert rules evaluate time-series expressions while Alertmanager groups, routes and silences notifications; neither automatically fixes the underlying workload. For the stated case, a required affinity expression blocks scheduling onto nonmatching nodes; a preferred expression influences scoring but permits fallback when necessary.

D:

This option addresses the distinct objective “Distinguish memory limits from CPU throttling for scheduling and runtime symptoms”, not the immediate requirement. CPU limits may throttle running processes, whereas exceeding memory constraints can cause OOM termination; Pod scheduling itself depends on requests. For the stated case, a required affinity expression blocks scheduling onto nonmatching nodes; a preferred expression influences scoring but permits fallback when necessary.

Question 267

An insurer must enforce a regulated node pool while an optional app merely prefers cheaper workers. Which platform mechanism explains why the suitable approach works?

  1. A required affinity expression blocks scheduling onto nonmatching nodes; a preferred expression influences scoring but permits fallback when necessary.
  2. CPU limits may throttle running processes, whereas exceeding memory constraints can cause OOM termination; Pod scheduling itself depends on requests.
  3. etcd persists Kubernetes API objects and cluster configuration, while application records ordinarily live in workload-specific storage outside etcd.
  4. Canary release needs traffic steering and metrics for a subset; blue-green shifts a complete traffic target after validation, and neither is automatically provided by a plain Deployment update.

Explanation

Correct Answer

A:

The situation is that an insurer must enforce a regulated node pool while an optional app merely prefers cheaper workers. A required affinity expression blocks scheduling onto nonmatching nodes; a preferred expression influences scoring but permits fallback when necessary. It supports this action: Use requiredDuringSchedulingIgnoredDuringExecution for mandatory constraints and preferredDuringSchedulingIgnoredDuringExecution for a soft placement preference. To confirm, test the workload with and without a preferred zone and verify it still schedules when preferred nodes are busy.

Incorrect Answers

B:

That statement explains the distinct objective “Distinguish memory limits from CPU throttling for scheduling and runtime symptoms” rather than the cause in this case. The deciding mechanism here is that a required affinity expression blocks scheduling onto nonmatching nodes; a preferred expression influences scoring but permits fallback when necessary.

C:

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 a required affinity expression blocks scheduling onto nonmatching nodes; a preferred expression influences scoring but permits fallback when necessary.

D:

That statement explains the distinct objective “Distinguish canary and blue-green delivery strategies from Kubernetes Deployment defaults” rather than the cause in this case. The deciding mechanism here is that a required affinity expression blocks scheduling onto nonmatching nodes; a preferred expression influences scoring but permits fallback when necessary.

Question 268

An insurer must enforce a regulated node pool while an optional app merely prefers cheaper workers. Which controlled observation would best validate the intended improvement?

  1. Send a synthetic request with a correlation ID and confirm it appears in the trace and relevant logs while latency metrics change.
  2. Create a synthetic CPU-intensive workload with tight CPU limits and compare throttling metrics with an OOMKilled test Pod.
  3. Test the workload with and without a preferred zone and verify it still schedules when preferred nodes are busy.
  4. Deploy a matching replica set across two labeled zones and inspect skew after adding a new Pod.

Explanation

Correct Answer

C:

The situation is that an insurer must enforce a regulated node pool while an optional app merely prefers cheaper workers. Test the workload with and without a preferred zone and verify it still schedules when preferred nodes are busy. This is the relevant test because a required affinity expression blocks scheduling onto nonmatching nodes; a preferred expression influences scoring but permits fallback when necessary.

Incorrect Answers

A:

This check would help evaluate the distinct objective “Explain metrics, logs and traces as complementary observability signals”, but not the required result. For this case, test the workload with and without a preferred zone and verify it still schedules when preferred nodes are busy.

B:

This check would help evaluate the distinct objective “Distinguish memory limits from CPU throttling for scheduling and runtime symptoms”, but not the required result. For this case, test the workload with and without a preferred zone and verify it still schedules when preferred nodes are busy.

D:

This check would help evaluate the distinct objective “Spread replicas across failure domains with topologySpreadConstraints”, but not the required result. For this case, test the workload with and without a preferred zone and verify it still schedules when preferred nodes are busy.

Question 269

An insurer must enforce a regulated node pool while an optional app merely prefers cheaper workers. An engineer proposes: “Use a preferred affinity rule as a compliance guarantee that sensitive Pods can never land outside a region.” What adverse outcome would be most direct?

  1. Applications fail on migration when plugin behavior or provider-specific components were never evaluated.
  2. The scheduler may legally use a non-preferred node, violating the policy that was mistakenly assumed mandatory.
  3. An unrelated object may be targeted or the intended workload may remain untouched and unavailable.
  4. The planned maintenance causes avoidable downtime because no safe application replica remains available.

Explanation

Correct Answer

B:

The situation is that an insurer must enforce a regulated node pool while an optional app merely prefers cheaper workers. The scheduler may legally use a non-preferred node, violating the policy that was mistakenly assumed mandatory. The shortcut creates this risk because a required affinity expression blocks scheduling onto nonmatching nodes; a preferred expression influences scoring but permits fallback when necessary.

Incorrect Answers

A:

That outcome concerns the distinct objective “Understand open standards and vendor-neutral community collaboration”; it is not the most direct consequence of this shortcut. The relevant consequence is that the scheduler may legally use a non-preferred node, violating the policy that was mistakenly assumed mandatory.

C:

That outcome concerns the distinct objective “Read the API resource model using namespaces and names rather than guessing ownership”; it is not the most direct consequence of this shortcut. The relevant consequence is that the scheduler may legally use a non-preferred node, violating the policy that was mistakenly assumed mandatory.

D:

That outcome concerns the distinct objective “Use cordon and drain with disruption considerations for planned node maintenance”; it is not the most direct consequence of this shortcut. The relevant consequence is that the scheduler may legally use a non-preferred node, violating the policy that was mistakenly assumed mandatory.

Question 270

An insurer must enforce a regulated node pool while an optional app merely prefers cheaper workers. What pair of supported action and practical verification should be approved?

  1. Use requiredDuringSchedulingIgnoredDuringExecution for mandatory constraints and preferredDuringSchedulingIgnoredDuringExecution for a soft placement preference. Acceptance evidence: Test the workload with and without a preferred zone and verify it still schedules when preferred nodes are busy.
  2. Configure anti-affinity against other Pods with a specific label so replicas prefer or require separate failure domains as appropriate. Acceptance evidence: Deploy replicas with hostname anti-affinity and inspect their node placements in a cluster with enough eligible workers.
  3. Keep desired workload YAML in version control and use kubectl apply to reconcile supported object fields through the API. Acceptance evidence: Edit the test Deployment manifest image tag, apply it, and confirm the API spec and rollout reflect the reviewed change.
  4. Choose service boundaries around business capabilities and operational needs, documenting communication cost, ownership and fault tolerance. Acceptance evidence: Model a synthetic two-service checkout dependency and compare rollout independence with failure and latency overhead against a single service.

Explanation

Correct Answer

A:

The situation is that an insurer must enforce a regulated node pool while an optional app merely prefers cheaper workers. Use requiredDuringSchedulingIgnoredDuringExecution for mandatory constraints and preferredDuringSchedulingIgnoredDuringExecution for a soft placement preference. Acceptance evidence: Test the workload with and without a preferred zone and verify it still schedules when preferred nodes are busy. This pairing is justified because a required affinity expression blocks scheduling onto nonmatching nodes; a preferred expression influences scoring but permits fallback when necessary.

Incorrect Answers

B:

This action and check address the distinct objective “Use Pod anti-affinity to reduce correlated replica failure” instead of the stated acceptance requirement. The matching action is to use requiredDuringSchedulingIgnoredDuringExecution for mandatory constraints and preferredDuringSchedulingIgnoredDuringExecution for a soft placement preference. Its confirming test is to test the workload with and without a preferred zone and verify it still schedules when preferred nodes are busy.

C:

This action and check address the distinct objective “Apply resource manifests declaratively instead of depending on imperative drift” instead of the stated acceptance requirement. The matching action is to use requiredDuringSchedulingIgnoredDuringExecution for mandatory constraints and preferredDuringSchedulingIgnoredDuringExecution for a soft placement preference. Its confirming test is to test the workload with and without a preferred zone and verify it still schedules when preferred nodes are busy.

D:

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 requiredDuringSchedulingIgnoredDuringExecution for mandatory constraints and preferredDuringSchedulingIgnoredDuringExecution for a soft placement preference. Its confirming test is to test the workload with and without a preferred zone and verify it still schedules when preferred nodes are busy.

Kubernetes and Cloud Native Associate (KCNA) Practice Tests