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 51

Question 500

A council sees cross-namespace packets despite a seemingly correct policy and must inspect CNI behavior. Which implementation together with matching acceptance evidence best meets this case?

  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. Select an access mode supported by the actual storage driver and workload placement requirements rather than assuming every volume supports concurrent writes from every node. Acceptance evidence: Use a synthetic two-node workload and compare expected attach behavior for an RWO volume with a documented RWX shared filesystem.
  3. Match a Service's exposed port and targetPort to the actual listening application container, checking protocol and named ports when used. Acceptance evidence: Inspect the container listener, Service port fields and a test Pod connection before changing unrelated firewall settings.
  4. Apply ingress and egress NetworkPolicy to selected Pods and verify both permitted and denied synthetic flows under a network plugin that implements policy. Acceptance evidence: Check CNI capabilities, establish a default-deny test policy and verify one allowed and one denied connection.

Explanation

Correct Answer

D:

The situation is that a council sees cross-namespace packets despite a seemingly correct policy and must inspect CNI behavior. Apply ingress and egress NetworkPolicy to selected Pods and verify both permitted and denied synthetic flows under a network plugin that implements policy. Acceptance evidence: Check CNI capabilities, establish a default-deny test policy and verify one allowed and one denied connection. This pairing is justified because networkPolicy declares traffic restrictions, but Kubernetes itself does not provide enforcement when the installed CNI lacks NetworkPolicy support.

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 apply ingress and egress NetworkPolicy to selected Pods and verify both permitted and denied synthetic flows under a network plugin that implements policy. Its confirming test is to check CNI capabilities, establish a default-deny test policy and verify one allowed and one denied connection.

B:

This action and check address the distinct objective “Choose ReadWriteOnce and ReadWriteMany access modes by backend capability” instead of the stated acceptance requirement. The matching action is to apply ingress and egress NetworkPolicy to selected Pods and verify both permitted and denied synthetic flows under a network plugin that implements policy. Its confirming test is to check CNI capabilities, establish a default-deny test policy and verify one allowed and one denied connection.

C:

This action and check address the distinct objective “Understand ports, targetPort and protocol mapping in a Service” instead of the stated acceptance requirement. The matching action is to apply ingress and egress NetworkPolicy to selected Pods and verify both permitted and denied synthetic flows under a network plugin that implements policy. Its confirming test is to check CNI capabilities, establish a default-deny test policy and verify one allowed and one denied connection.

Question 501

A public library uses a Service name for its book-search API rather than embedding a worker Pod IP. Which engineering approach is the most appropriate for this cloud-native case?

  1. Inspect the relevant object's conditions and timestamped Events to place the failure at API admission, scheduling, image pulling or runtime startup.
  2. Give clients a Service DNS name rather than hardcoding Pod IP addresses that can change when replicas are replaced.
  3. Require approved image registries, signature or digest verification and patch ownership when admitting production container images.
  4. Match a Service's exposed port and targetPort to the actual listening application container, checking protocol and named ports when used.

Explanation

Correct Answer

B:

Give clients a Service DNS name rather than hardcoding Pod IP addresses that can change when replicas are replaced. This resolves the issue because pods receive network identities that can be ephemeral, while a Service maintains a stable discovery and traffic abstraction over selected endpoints. To verify, delete and replace a Deployment Pod and verify a client continues to reach its Service DNS name despite changed backend Pod addresses.

Incorrect Answers

A:

This option addresses the distinct objective “Use describe and Events to distinguish admission, scheduling and execution errors”, not the immediate requirement. Different Kubernetes components emit distinct Events; identifying the stage prevents changing unrelated network or application settings. For the stated case, pods receive network identities that can be ephemeral, while a Service maintains a stable discovery and traffic abstraction over selected endpoints.

C:

This option addresses the distinct objective “Use image provenance and policy controls without trusting mutable tags”, not the immediate requirement. Image provenance reduces accidental or malicious image substitution; mutable tags alone cannot prove build integrity or content identity. For the stated case, pods receive network identities that can be ephemeral, while a Service maintains a stable discovery and traffic abstraction over selected endpoints.

D:

This option addresses the distinct objective “Understand ports, targetPort and protocol mapping in a Service”, not the immediate requirement. A Service exposes port to clients and forwards to targetPort on selected endpoints; a mismatched targetPort can break delivery even with valid DNS and selectors. For the stated case, pods receive network identities that can be ephemeral, while a Service maintains a stable discovery and traffic abstraction over selected endpoints.

Question 502

A public library uses a Service name for its book-search API rather than embedding a worker Pod IP. What infrastructure principle makes the correct treatment effective?

  1. A Service exposes port to clients and forwards to targetPort on selected endpoints; a mismatched targetPort can break delivery even with valid DNS and selectors.
  2. NetworkPolicy declares traffic restrictions, but Kubernetes itself does not provide enforcement when the installed CNI lacks NetworkPolicy support.
  3. A service level objective is a target for measured user-facing behavior; error budgets quantify allowed misses and help prioritize release risk.
  4. Pods receive network identities that can be ephemeral, while a Service maintains a stable discovery and traffic abstraction over selected endpoints.

Explanation

Correct Answer

D:

Pods receive network identities that can be ephemeral, while a Service maintains a stable discovery and traffic abstraction over selected endpoints. It supports this action: Give clients a Service DNS name rather than hardcoding Pod IP addresses that can change when replicas are replaced. To confirm, delete and replace a Deployment Pod and verify a client continues to reach its Service DNS name despite changed backend Pod addresses.

Incorrect Answers

A:

That statement explains the distinct objective “Understand ports, targetPort and protocol mapping in a Service” rather than the cause in this case. The deciding mechanism here is that pods receive network identities that can be ephemeral, while a Service maintains a stable discovery and traffic abstraction over selected endpoints.

B:

That statement explains the distinct objective “Recognize NetworkPolicy isolation only when the CNI enforces it” rather than the cause in this case. The deciding mechanism here is that pods receive network identities that can be ephemeral, while a Service maintains a stable discovery and traffic abstraction over selected endpoints.

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 pods receive network identities that can be ephemeral, while a Service maintains a stable discovery and traffic abstraction over selected endpoints.

Question 503

A public library uses a Service name for its book-search API rather than embedding a worker Pod IP. What verification result would most convincingly distinguish a working solution from a claim?

  1. Deploy a test hostname route, verify a compatible controller exists and inspect the programmed listener and backend status.
  2. Delete and replace a Deployment Pod and verify a client continues to reach its Service DNS name despite changed backend Pod addresses.
  3. Run a synthetic app that exits with a nonzero code, then confirm describe, previous logs and restart data reveal the failure path.
  4. Annotate a Deployment with release notes and verify its Service still selects Pods using explicit app labels.

Explanation

Correct Answer

B:

Delete and replace a Deployment Pod and verify a client continues to reach its Service DNS name despite changed backend Pod addresses. This is the relevant test because pods receive network identities that can be ephemeral, while a Service maintains a stable discovery and traffic abstraction over selected endpoints.

Incorrect Answers

A:

This check would help evaluate the distinct objective “Choose Ingress or Gateway API with an implementing controller for HTTP exposure”, but not the required result. For this case, delete and replace a Deployment Pod and verify a client continues to reach its Service DNS name despite changed backend Pod addresses.

C:

This check would help evaluate the distinct objective “Diagnose CrashLoopBackOff from restart history and previous logs”, but not the required result. For this case, delete and replace a Deployment Pod and verify a client continues to reach its Service DNS name despite changed backend Pod addresses.

D:

This check would help evaluate the distinct objective “Use annotations for tool metadata rather than workload selection”, but not the required result. For this case, delete and replace a Deployment Pod and verify a client continues to reach its Service DNS name despite changed backend Pod addresses.

Question 504

A public library uses a Service name for its book-search API rather than embedding a worker Pod IP. The change review contains this proposal: “Configure every client with one current Pod IP and promise the address will never change during normal rollouts.” What risk matters most?

  1. Pods may start but remain unable to communicate across nodes because the CNI dataplane was never established.
  2. Volume attachment fails or concurrent access risks data integrity when the backend cannot provide shared semantics.
  3. Credential reuse could expose all namespaces and persist after the original developer loses access.
  4. Requests fail after a replica is replaced because the client bypassed the Service abstraction.

Explanation

Correct Answer

D:

Requests fail after a replica is replaced because the client bypassed the Service abstraction. The shortcut creates this risk because pods receive network identities that can be ephemeral, while a Service maintains a stable discovery and traffic abstraction over selected endpoints.

Incorrect Answers

A:

That outcome concerns the distinct objective “Distinguish the CNI Pod network from Service discovery and routing”; it is not the most direct consequence of this shortcut. The relevant consequence is that requests fail after a replica is replaced because the client bypassed the Service abstraction.

B:

That outcome concerns the distinct objective “Choose ReadWriteOnce and ReadWriteMany access modes by backend capability”; it is not the most direct consequence of this shortcut. The relevant consequence is that requests fail after a replica is replaced because the client bypassed the Service abstraction.

C:

That outcome concerns the distinct objective “Differentiate ServiceAccounts from human kubeconfig identities”; it is not the most direct consequence of this shortcut. The relevant consequence is that requests fail after a replica is replaced because the client bypassed the Service abstraction.

Question 505

A public library uses a Service name for its book-search API rather than embedding a worker Pod IP. Which implementation together with matching acceptance evidence best meets this case?

  1. Give clients a Service DNS name rather than hardcoding Pod IP addresses that can change when replicas are replaced. Acceptance evidence: Delete and replace a Deployment Pod and verify a client continues to reach its Service DNS name despite changed backend Pod addresses.
  2. Record non-identifying build or audit metadata as annotations and use labels for indexing, grouping and selector-based routing. Acceptance evidence: Annotate a Deployment with release notes and verify its Service still selects Pods using explicit app labels.
  3. Define appropriate HTTP routing through an installed Ingress controller or Gateway API controller rather than expecting the API object alone to provision a proxy. Acceptance evidence: Deploy a test hostname route, verify a compatible controller exists and inspect the programmed listener and backend status.
  4. Create a Role with only required verbs and resource types, and bind it to the intended subject within the target namespace. Acceptance evidence: Use kubectl auth can-i --as a synthetic student to verify pod get allowed and secret delete denied in the specified namespace.

Explanation

Correct Answer

A:

Give clients a Service DNS name rather than hardcoding Pod IP addresses that can change when replicas are replaced. Acceptance evidence: Delete and replace a Deployment Pod and verify a client continues to reach its Service DNS name despite changed backend Pod addresses. This pairing is justified because pods receive network identities that can be ephemeral, while a Service maintains a stable discovery and traffic abstraction over selected endpoints.

Incorrect Answers

B:

This action and check address the distinct objective “Use annotations for tool metadata rather than workload selection” instead of the stated acceptance requirement. The matching action is to give clients a Service DNS name rather than hardcoding Pod IP addresses that can change when replicas are replaced. Its confirming test is to delete and replace a Deployment Pod and verify a client continues to reach its Service DNS name despite changed backend Pod addresses.

C:

This action and check address the distinct objective “Choose Ingress or Gateway API with an implementing controller for HTTP exposure” instead of the stated acceptance requirement. The matching action is to give clients a Service DNS name rather than hardcoding Pod IP addresses that can change when replicas are replaced. Its confirming test is to delete and replace a Deployment Pod and verify a client continues to reach its Service DNS name despite changed backend Pod addresses.

D:

This action and check address the distinct objective “Implement namespaced RBAC Roles for least-privilege resource permissions” instead of the stated acceptance requirement. The matching action is to give clients a Service DNS name rather than hardcoding Pod IP addresses that can change when replicas are replaced. Its confirming test is to delete and replace a Deployment Pod and verify a client continues to reach its Service DNS name despite changed backend Pod addresses.

Question 506

A retail order processor caches a Pod IP and loses connectivity after cluster maintenance. Which engineering approach is the most appropriate for this cloud-native case?

  1. Match a Service's exposed port and targetPort to the actual listening application container, checking protocol and named ports when used.
  2. Use cluster DNS records such as service.namespace.svc.cluster.local when a Pod connects to Services in other namespaces.
  3. Give clients a Service DNS name rather than hardcoding Pod IP addresses that can change when replicas are replaced.
  4. Inspect Deployment, ReplicaSet and Pod owner references when verifying which controller maintains replica count.

Explanation

Correct Answer

C:

The situation is that a retail order processor caches a Pod IP and loses connectivity after cluster maintenance. Give clients a Service DNS name rather than hardcoding Pod IP addresses that can change when replicas are replaced. This resolves the issue because pods receive network identities that can be ephemeral, while a Service maintains a stable discovery and traffic abstraction over selected endpoints. To verify, delete and replace a Deployment Pod and verify a client continues to reach its Service DNS name despite changed backend Pod addresses.

Incorrect Answers

A:

The situation is that a retail order processor caches a Pod IP and loses connectivity after cluster maintenance. This option addresses the distinct objective “Understand ports, targetPort and protocol mapping in a Service”, not the immediate requirement. A Service exposes port to clients and forwards to targetPort on selected endpoints; a mismatched targetPort can break delivery even with valid DNS and selectors. For the stated case, pods receive network identities that can be ephemeral, while a Service maintains a stable discovery and traffic abstraction over selected endpoints.

B:

This option addresses the distinct objective “Verify CoreDNS resolution and namespace-qualified Service names”, not the immediate requirement. CoreDNS watches Service objects and serves cluster-aware names; bare names normally resolve relative to the requesting Pod's namespace and search domains. For the stated case, pods receive network identities that can be ephemeral, while a Service maintains a stable discovery and traffic abstraction over selected endpoints.

D:

This option addresses the distinct objective “Interpret ReplicaSet ownership and selectors in a Deployment”, not the immediate requirement. A Deployment creates or manages ReplicaSets, each ReplicaSet owns matching Pods, and selector consistency determines which Pods it counts. For the stated case, pods receive network identities that can be ephemeral, while a Service maintains a stable discovery and traffic abstraction over selected endpoints.

Question 507

A retail order processor caches a Pod IP and loses connectivity after cluster maintenance. What infrastructure principle makes the correct treatment effective?

  1. RBAC evaluates API verbs, resources and scope; a Role is namespaced and does not grant cluster-wide access merely because the subject can authenticate.
  2. Pods receive network identities that can be ephemeral, while a Service maintains a stable discovery and traffic abstraction over selected endpoints.
  3. Open-source community processes provide transparent review and shared maintenance, but do not imply unreviewed external code should be merged into production.
  4. Service type determines how clients can reach a stable Service: ClusterIP is internal, NodePort exposes a port on nodes, and LoadBalancer integrates external infrastructure.

Explanation

Correct Answer

B:

The situation is that a retail order processor caches a Pod IP and loses connectivity after cluster maintenance. Pods receive network identities that can be ephemeral, while a Service maintains a stable discovery and traffic abstraction over selected endpoints. It supports this action: Give clients a Service DNS name rather than hardcoding Pod IP addresses that can change when replicas are replaced. To confirm, delete and replace a Deployment Pod and verify a client continues to reach its Service DNS name despite changed backend Pod addresses.

Incorrect Answers

A:

That statement explains the distinct objective “Implement namespaced RBAC Roles for least-privilege resource permissions” rather than the cause in this case. The deciding mechanism here is that pods receive network identities that can be ephemeral, while a Service maintains a stable discovery and traffic abstraction over selected endpoints.

C:

That statement explains the distinct objective “Use open community governance and contribution processes for sustainable cloud-native projects” rather than the cause in this case. The deciding mechanism here is that pods receive network identities that can be ephemeral, while a Service maintains a stable discovery and traffic abstraction over selected endpoints.

D:

That statement explains the distinct objective “Choose ClusterIP, NodePort and LoadBalancer Service types for appropriate reachability” rather than the cause in this case. The deciding mechanism here is that pods receive network identities that can be ephemeral, while a Service maintains a stable discovery and traffic abstraction over selected endpoints.

Question 508

A retail order processor caches a Pod IP and loses connectivity after cluster maintenance. What verification result would most convincingly distinguish a working solution from a claim?

  1. Delete and replace a Deployment Pod and verify a client continues to reach its Service DNS name despite changed backend Pod addresses.
  2. With synthetic users verify a trusted API connection, denied privilege escalation and appropriate audit entries for failed requests.
  3. Scale a test Deployment and inspect its ReplicaSet and owned Pods, then compare deleting a standalone Pod.
  4. Run nslookup for a Service using short and namespace-qualified names from test Pods in two different namespaces.

Explanation

Correct Answer

A:

The situation is that a retail order processor caches a Pod IP and loses connectivity after cluster maintenance. Delete and replace a Deployment Pod and verify a client continues to reach its Service DNS name despite changed backend Pod addresses. This is the relevant test because pods receive network identities that can be ephemeral, while a Service maintains a stable discovery and traffic abstraction over selected endpoints.

Incorrect Answers

B:

This check would help evaluate the distinct objective “Protect API server access using authenticated TLS clients and audited authorization”, but not the required result. For this case, delete and replace a Deployment Pod and verify a client continues to reach its Service DNS name despite changed backend Pod addresses.

C:

This check would help evaluate the distinct objective “Distinguish Deployment desired state from a manually created Pod”, but not the required result. For this case, delete and replace a Deployment Pod and verify a client continues to reach its Service DNS name despite changed backend Pod addresses.

D:

This check would help evaluate the distinct objective “Verify CoreDNS resolution and namespace-qualified Service names”, but not the required result. For this case, delete and replace a Deployment Pod and verify a client continues to reach its Service DNS name despite changed backend Pod addresses.

Question 509

A retail order processor caches a Pod IP and loses connectivity after cluster maintenance. The change review contains this proposal: “Configure every client with one current Pod IP and promise the address will never change during normal rollouts.” What risk matters most?

  1. A workload continues crashing because the root cause is memory exhaustion, not name resolution.
  2. Requests fail after a replica is replaced because the client bypassed the Service abstraction.
  3. Cross-namespace calls can fail or resolve a same-named but unrelated local Service.
  4. Sensitive traffic may remain allowed because the networking implementation does not enforce the declared policy.

Explanation

Correct Answer

B:

The situation is that a retail order processor caches a Pod IP and loses connectivity after cluster maintenance. Requests fail after a replica is replaced because the client bypassed the Service abstraction. The shortcut creates this risk because pods receive network identities that can be ephemeral, while a Service maintains a stable discovery and traffic abstraction over selected endpoints.

Incorrect Answers

A:

That outcome concerns the distinct objective “Distinguish memory limits from CPU throttling for scheduling and runtime symptoms”; it is not the most direct consequence of this shortcut. The relevant consequence is that requests fail after a replica is replaced because the client bypassed the Service abstraction.

C:

That outcome concerns the distinct objective “Verify CoreDNS resolution and namespace-qualified Service names”; it is not the most direct consequence of this shortcut. The relevant consequence is that requests fail after a replica is replaced because the client bypassed the Service abstraction.

D:

That outcome concerns the distinct objective “Recognize NetworkPolicy isolation only when the CNI enforces it”; it is not the most direct consequence of this shortcut. The relevant consequence is that requests fail after a replica is replaced because the client bypassed the Service abstraction.

Question 510

A retail order processor caches a Pod IP and loses connectivity after cluster maintenance. Which implementation together with matching acceptance evidence best meets this case?

  1. Choose an available StorageClass with a compatible CSI provisioner and appropriate binding behavior when creating a PVC. Acceptance evidence: Create a claim using a named test StorageClass and compare provisioner events and binding timing with a non-existent class.
  2. Give clients a Service DNS name rather than hardcoding Pod IP addresses that can change when replicas are replaced. Acceptance evidence: Delete and replace a Deployment Pod and verify a client continues to reach its Service DNS name despite changed backend Pod addresses.
  3. Follow a project's published governance, issue templates, contributor guides and code of conduct when reporting bugs or proposing changes. Acceptance evidence: Submit a reproducible synthetic issue and examine how maintainers triage, review and test a proposed patch before release.
  4. Match a Service's exposed port and targetPort to the actual listening application container, checking protocol and named ports when used. Acceptance evidence: Inspect the container listener, Service port fields and a test Pod connection before changing unrelated firewall settings.

Explanation

Correct Answer

B:

The situation is that a retail order processor caches a Pod IP and loses connectivity after cluster maintenance. Give clients a Service DNS name rather than hardcoding Pod IP addresses that can change when replicas are replaced. Acceptance evidence: Delete and replace a Deployment Pod and verify a client continues to reach its Service DNS name despite changed backend Pod addresses. This pairing is justified because pods receive network identities that can be ephemeral, while a Service maintains a stable discovery and traffic abstraction over selected endpoints.

Incorrect Answers

A:

This action and check address the distinct objective “Use StorageClass for dynamic volume provisioning rather than handcrafting every disk” instead of the stated acceptance requirement. The matching action is to give clients a Service DNS name rather than hardcoding Pod IP addresses that can change when replicas are replaced. Its confirming test is to delete and replace a Deployment Pod and verify a client continues to reach its Service DNS name despite changed backend Pod addresses.

C:

This action and check address the distinct objective “Use open community governance and contribution processes for sustainable cloud-native projects” instead of the stated acceptance requirement. The matching action is to give clients a Service DNS name rather than hardcoding Pod IP addresses that can change when replicas are replaced. Its confirming test is to delete and replace a Deployment Pod and verify a client continues to reach its Service DNS name despite changed backend Pod addresses.

D:

This action and check address the distinct objective “Understand ports, targetPort and protocol mapping in a Service” instead of the stated acceptance requirement. The matching action is to give clients a Service DNS name rather than hardcoding Pod IP addresses that can change when replicas are replaced. Its confirming test is to delete and replace a Deployment Pod and verify a client continues to reach its Service DNS name despite changed backend Pod addresses.

Kubernetes and Cloud Native Associate (KCNA) Practice Tests