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 48

Question 470

An insurance sandbox uses identical api Service names in staging and production namespaces. What pair of supported action and practical verification should be approved?

  1. Combine a default-deny baseline with narrow app-label and namespace-label NetworkPolicy rules for approved traffic. Acceptance evidence: Test synthetic frontend-to-backend reachability and deny a third unauthorized namespace while verifying DNS access is still deliberately allowed.
  2. 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.
  3. Use ClusterIP for internal backends and a properly controlled NodePort or supported LoadBalancer integration for justified external access. Acceptance evidence: Create a ClusterIP test Service and validate internal access, then compare the reachable endpoints under an authorized LoadBalancer configuration.
  4. Use cluster DNS records such as service.namespace.svc.cluster.local when a Pod connects to Services in other namespaces. Acceptance evidence: Run nslookup for a Service using short and namespace-qualified names from test Pods in two different namespaces.

Explanation

Correct Answer

D:

The situation is that an insurance sandbox uses identical api Service names in staging and production namespaces. Use cluster DNS records such as service.namespace.svc.cluster.local when a Pod connects to Services in other namespaces. Acceptance evidence: Run nslookup for a Service using short and namespace-qualified names from test Pods in two different namespaces. This pairing is justified because coreDNS watches Service objects and serves cluster-aware names; bare names normally resolve relative to the requesting Pod's namespace and search domains.

Incorrect Answers

A:

This action and check address the distinct objective “Limit workload-to-workload access with explicit NetworkPolicy allow rules” instead of the stated acceptance requirement. The matching action is to use cluster DNS records such as service.namespace.svc.cluster.local when a Pod connects to Services in other namespaces. Its confirming test is to run nslookup for a Service using short and namespace-qualified names from test Pods in two different namespaces.

B:

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 use cluster DNS records such as service.namespace.svc.cluster.local when a Pod connects to Services in other namespaces. Its confirming test is to run nslookup for a Service using short and namespace-qualified names from test Pods in two different namespaces.

C:

This action and check address the distinct objective “Choose ClusterIP, NodePort and LoadBalancer Service types for appropriate reachability” instead of the stated acceptance requirement. The matching action is to use cluster DNS records such as service.namespace.svc.cluster.local when a Pod connects to Services in other namespaces. Its confirming test is to run nslookup for a Service using short and namespace-qualified names from test Pods in two different namespaces.

Question 471

A charity's api Service resolves but curls time out after a teammate changes a Pod label. Which engineering approach is the most appropriate for this cloud-native case?

  1. Use narrowly scoped imagePullSecrets or an approved node identity to authorize the runtime to pull a private image.
  2. Inspect Pod container last state, restart count and kubectl logs --previous when a process repeatedly exits after startup.
  3. Apply ingress and egress NetworkPolicy to selected Pods and verify both permitted and denied synthetic flows under a network plugin that implements policy.
  4. Check EndpointSlices and Pod readiness when a Service exists but connections reach no application backends.

Explanation

Correct Answer

D:

Check EndpointSlices and Pod readiness when a Service exists but connections reach no application backends. This resolves the issue because endpointSlices describe endpoint addresses and readiness associated with a Service, allowing its dataplane to route toward matching healthy Pods. To verify, compare a Service's label selector, EndpointSlices and Pod readiness conditions before changing external load-balancer settings.

Incorrect Answers

A:

This option addresses the distinct objective “Handle private registry pulls with dedicated credentials instead of embedding secrets in images”, not the immediate requirement. Image-pull credentials are consumed before the application starts and should not be hardcoded into container layers or app logs. For the stated case, endpointSlices describe endpoint addresses and readiness associated with a Service, allowing its dataplane to route toward matching healthy Pods.

B:

This option addresses the distinct objective “Diagnose CrashLoopBackOff from restart history and previous logs”, not the immediate requirement. CrashLoopBackOff reflects kubelet restart backoff after container failures; the underlying cause may be application configuration, exit code or a failed liveness probe. For the stated case, endpointSlices describe endpoint addresses and readiness associated with a Service, allowing its dataplane to route toward matching healthy Pods.

C:

This option addresses the distinct objective “Recognize NetworkPolicy isolation only when the CNI enforces it”, not the immediate requirement. NetworkPolicy declares traffic restrictions, but Kubernetes itself does not provide enforcement when the installed CNI lacks NetworkPolicy support. For the stated case, endpointSlices describe endpoint addresses and readiness associated with a Service, allowing its dataplane to route toward matching healthy Pods.

Question 472

A charity's api Service resolves but curls time out after a teammate changes a Pod label. What infrastructure principle makes the correct treatment effective?

  1. EndpointSlices describe endpoint addresses and readiness associated with a Service, allowing its dataplane to route toward matching healthy Pods.
  2. Pods receive network identities that can be ephemeral, while a Service maintains a stable discovery and traffic abstraction over selected endpoints.
  3. The API stores a desired spec while controllers asynchronously react to observations; status describes progress, not a guarantee of immediate convergence.
  4. Ingress and Gateway API express routing intent, while an actual controller/dataplane implements TLS termination, listeners and backend forwarding.

Explanation

Correct Answer

A:

EndpointSlices describe endpoint addresses and readiness associated with a Service, allowing its dataplane to route toward matching healthy Pods. It supports this action: Check EndpointSlices and Pod readiness when a Service exists but connections reach no application backends. To confirm, compare a Service's label selector, EndpointSlices and Pod readiness conditions before changing external load-balancer settings.

Incorrect Answers

B:

That statement explains the distinct objective “Distinguish Pod IPs from stable Services during rescheduling” rather than the cause in this case. The deciding mechanism here is that endpointSlices describe endpoint addresses and readiness associated with a Service, allowing its dataplane to route toward matching healthy Pods.

C:

That statement explains the distinct objective “Explain desired state versus observed status in Kubernetes objects” rather than the cause in this case. The deciding mechanism here is that endpointSlices describe endpoint addresses and readiness associated with a Service, allowing its dataplane to route toward matching healthy Pods.

D:

That statement explains the distinct objective “Choose Ingress or Gateway API with an implementing controller for HTTP exposure” rather than the cause in this case. The deciding mechanism here is that endpointSlices describe endpoint addresses and readiness associated with a Service, allowing its dataplane to route toward matching healthy Pods.

Question 473

A charity's api Service resolves but curls time out after a teammate changes a Pod label. What verification result would most convincingly distinguish a working solution from a claim?

  1. Compare a Service's label selector, EndpointSlices and Pod readiness conditions before changing external load-balancer settings.
  2. Trigger a controlled error-rate alert, verify its pending/firing transition and confirm the correct team receives a grouped notification.
  3. Deploy two synthetic Pods on different nodes and test direct Pod IP connectivity before testing the Service virtual IP.
  4. Create a ClusterIP test Service and validate internal access, then compare the reachable endpoints under an authorized LoadBalancer configuration.

Explanation

Correct Answer

A:

Compare a Service's label selector, EndpointSlices and Pod readiness conditions before changing external load-balancer settings. This is the relevant test because endpointSlices describe endpoint addresses and readiness associated with a Service, allowing its dataplane to route toward matching healthy Pods.

Incorrect Answers

B:

This check would help evaluate the distinct objective “Build meaningful alert rules and route notifications through Alertmanager”, but not the required result. For this case, compare a Service's label selector, EndpointSlices and Pod readiness conditions before changing external load-balancer settings.

C:

This check would help evaluate the distinct objective “Distinguish the CNI Pod network from Service discovery and routing”, but not the required result. For this case, compare a Service's label selector, EndpointSlices and Pod readiness conditions before changing external load-balancer settings.

D:

This check would help evaluate the distinct objective “Choose ClusterIP, NodePort and LoadBalancer Service types for appropriate reachability”, but not the required result. For this case, compare a Service's label selector, EndpointSlices and Pod readiness conditions before changing external load-balancer settings.

Question 474

A charity's api Service resolves but curls time out after a teammate changes a Pod label. The change review contains this proposal: “Change the client's DNS resolver while a Service selector matches no Pods and its EndpointSlices are empty.” What risk matters most?

  1. The operator may deploy unsupported changes without release provenance or a responsible maintenance path.
  2. Packets reach the wrong destination socket and the Service appears unavailable despite healthy Pod processes.
  3. One application vulnerability can expose a credential allowing changes unrelated to its actual business function.
  4. Name lookup may succeed but no usable endpoint exists to receive traffic.

Explanation

Correct Answer

D:

Name lookup may succeed but no usable endpoint exists to receive traffic. The shortcut creates this risk because endpointSlices describe endpoint addresses and readiness associated with a Service, allowing its dataplane to route toward matching healthy Pods.

Incorrect Answers

A:

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 name lookup may succeed but no usable endpoint exists to receive traffic.

B:

That outcome concerns the distinct objective “Understand ports, targetPort and protocol mapping in a Service”; it is not the most direct consequence of this shortcut. The relevant consequence is that name lookup may succeed but no usable endpoint exists to receive traffic.

C:

That outcome concerns the distinct objective “Enforce workload service account token boundaries and avoid needless mounts”; it is not the most direct consequence of this shortcut. The relevant consequence is that name lookup may succeed but no usable endpoint exists to receive traffic.

Question 475

A charity's api Service resolves but curls time out after a teammate changes a Pod label. Which implementation together with matching acceptance evidence best meets this case?

  1. Request persistent storage with a PVC and examine the bound PersistentVolume capacity, class and access mode before deploying a data-bearing Pod. Acceptance evidence: Create a small claim in a test StorageClass, inspect its Bound status and restart the consuming Pod to check data persistence.
  2. Check EndpointSlices and Pod readiness when a Service exists but connections reach no application backends. Acceptance evidence: Compare a Service's label selector, EndpointSlices and Pod readiness conditions before changing external load-balancer settings.
  3. 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.
  4. Configure readiness to stop sending Service traffic to an unready Pod, liveness to restart an unhealthy container and startup to allow slow initialization. Acceptance evidence: Delay a synthetic app response and compare EndpointSlice readiness with restart counts under controlled probe settings.

Explanation

Correct Answer

B:

Check EndpointSlices and Pod readiness when a Service exists but connections reach no application backends. Acceptance evidence: Compare a Service's label selector, EndpointSlices and Pod readiness conditions before changing external load-balancer settings. This pairing is justified because endpointSlices describe endpoint addresses and readiness associated with a Service, allowing its dataplane to route toward matching healthy Pods.

Incorrect Answers

A:

This action and check address the distinct objective “Understand PersistentVolumeClaim binding to persistent storage resources” instead of the stated acceptance requirement. The matching action is to check EndpointSlices and Pod readiness when a Service exists but connections reach no application backends. Its confirming test is to compare a Service's label selector, EndpointSlices and Pod readiness conditions before changing external load-balancer settings.

C:

This action and check address the distinct objective “Recognize NetworkPolicy isolation only when the CNI enforces it” instead of the stated acceptance requirement. The matching action is to check EndpointSlices and Pod readiness when a Service exists but connections reach no application backends. Its confirming test is to compare a Service's label selector, EndpointSlices and Pod readiness conditions before changing external load-balancer settings.

D:

This action and check address the distinct objective “Understand readiness, liveness and startup probes as different signals” instead of the stated acceptance requirement. The matching action is to check EndpointSlices and Pod readiness when a Service exists but connections reach no application backends. Its confirming test is to compare a Service's label selector, EndpointSlices and Pod readiness conditions before changing external load-balancer settings.

Question 476

A bank's backend Pods run but fail readiness, leaving the Service without ready targets. Which engineering approach is the most appropriate for this cloud-native case?

  1. Inspect image default command and Pod command or args settings to determine what executable starts in the container.
  2. Use cluster DNS records such as service.namespace.svc.cluster.local when a Pod connects to Services in other namespaces.
  3. Create a Role with only required verbs and resource types, and bind it to the intended subject within the target namespace.
  4. Check EndpointSlices and Pod readiness when a Service exists but connections reach no application backends.

Explanation

Correct Answer

D:

The situation is that a bank's backend Pods run but fail readiness, leaving the Service without ready targets. Check EndpointSlices and Pod readiness when a Service exists but connections reach no application backends. This resolves the issue because endpointSlices describe endpoint addresses and readiness associated with a Service, allowing its dataplane to route toward matching healthy Pods. To verify, compare a Service's label selector, EndpointSlices and Pod readiness conditions before changing external load-balancer settings.

Incorrect Answers

A:

This option addresses the distinct objective “Understand ENTRYPOINT and command overrides when a container exits immediately”, not the immediate requirement. The container runtime starts the configured process, and a crash or early exit can terminate the container regardless of Kubernetes placement. For the stated case, endpointSlices describe endpoint addresses and readiness associated with a Service, allowing its dataplane to route toward matching healthy Pods.

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, endpointSlices describe endpoint addresses and readiness associated with a Service, allowing its dataplane to route toward matching healthy Pods.

C:

This option addresses the distinct objective “Implement namespaced RBAC Roles for least-privilege resource permissions”, not the immediate requirement. RBAC evaluates API verbs, resources and scope; a Role is namespaced and does not grant cluster-wide access merely because the subject can authenticate. For the stated case, endpointSlices describe endpoint addresses and readiness associated with a Service, allowing its dataplane to route toward matching healthy Pods.

Question 477

A bank's backend Pods run but fail readiness, leaving the Service without ready targets. What infrastructure principle makes the correct treatment effective?

  1. Topology spread constraints compare Pod distribution in topology domains and can restrict or prefer placement depending on whenUnsatisfiable.
  2. A failed readiness probe removes a Pod from ready Service endpoints, while failed liveness checks can restart a process; their operational consequences differ.
  3. CoreDNS watches Service objects and serves cluster-aware names; bare names normally resolve relative to the requesting Pod's namespace and search domains.
  4. EndpointSlices describe endpoint addresses and readiness associated with a Service, allowing its dataplane to route toward matching healthy Pods.

Explanation

Correct Answer

D:

The situation is that a bank's backend Pods run but fail readiness, leaving the Service without ready targets. EndpointSlices describe endpoint addresses and readiness associated with a Service, allowing its dataplane to route toward matching healthy Pods. It supports this action: Check EndpointSlices and Pod readiness when a Service exists but connections reach no application backends. To confirm, compare a Service's label selector, EndpointSlices and Pod readiness conditions before changing external load-balancer settings.

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 endpointSlices describe endpoint addresses and readiness associated with a Service, allowing its dataplane to route toward matching healthy Pods.

B:

That statement explains the distinct objective “Investigate readiness failures separately from liveness-related restarts” rather than the cause in this case. The deciding mechanism here is that endpointSlices describe endpoint addresses and readiness associated with a Service, allowing its dataplane to route toward matching healthy Pods.

C:

That statement explains the distinct objective “Verify CoreDNS resolution and namespace-qualified Service names” rather than the cause in this case. The deciding mechanism here is that endpointSlices describe endpoint addresses and readiness associated with a Service, allowing its dataplane to route toward matching healthy Pods.

Question 478

A bank's backend Pods run but fail readiness, leaving the Service without ready targets. What verification result would most convincingly distinguish a working solution from a claim?

  1. Compare a Service's label selector, EndpointSlices and Pod readiness conditions before changing external load-balancer settings.
  2. Create a synthetic CPU-intensive workload with tight CPU limits and compare throttling metrics with an OOMKilled test Pod.
  3. Inspect the container listener, Service port fields and a test Pod connection before changing unrelated firewall settings.
  4. Bind a synthetic ClusterRole through RoleBinding in namespace-a, then verify access fails in namespace-b.

Explanation

Correct Answer

A:

The situation is that a bank's backend Pods run but fail readiness, leaving the Service without ready targets. Compare a Service's label selector, EndpointSlices and Pod readiness conditions before changing external load-balancer settings. This is the relevant test because endpointSlices describe endpoint addresses and readiness associated with a Service, allowing its dataplane to route toward matching healthy Pods.

Incorrect Answers

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, compare a Service's label selector, EndpointSlices and Pod readiness conditions before changing external load-balancer settings.

C:

This check would help evaluate the distinct objective “Understand ports, targetPort and protocol mapping in a Service”, but not the required result. For this case, compare a Service's label selector, EndpointSlices and Pod readiness conditions before changing external load-balancer settings.

D:

This check would help evaluate the distinct objective “Distinguish ClusterRoles from Roles and binding scope”, but not the required result. For this case, compare a Service's label selector, EndpointSlices and Pod readiness conditions before changing external load-balancer settings.

Question 479

A bank's backend Pods run but fail readiness, leaving the Service without ready targets. The change review contains this proposal: “Change the client's DNS resolver while a Service selector matches no Pods and its EndpointSlices are empty.” What risk matters most?

  1. The actual capacity or node selection problem remains because no node was assigned.
  2. The deployed artifact grows, may leak build credentials and exposes unnecessary packages.
  3. The change unnecessarily exposes a data service externally while the original DNS problem remains unresolved.
  4. Name lookup may succeed but no usable endpoint exists to receive traffic.

Explanation

Correct Answer

D:

The situation is that a bank's backend Pods run but fail readiness, leaving the Service without ready targets. Name lookup may succeed but no usable endpoint exists to receive traffic. The shortcut creates this risk because endpointSlices describe endpoint addresses and readiness associated with a Service, allowing its dataplane to route toward matching healthy Pods.

Incorrect Answers

A:

That outcome concerns the distinct objective “Separate Pending scheduling failures from ImagePullBackOff errors”; it is not the most direct consequence of this shortcut. The relevant consequence is that name lookup may succeed but no usable endpoint exists to receive traffic.

B:

That outcome concerns the distinct objective “Build smaller images with multistage builds and remove unnecessary tooling”; it is not the most direct consequence of this shortcut. The relevant consequence is that name lookup may succeed but no usable endpoint exists to receive traffic.

C:

That outcome concerns the distinct objective “Choose ClusterIP, NodePort and LoadBalancer Service types for appropriate reachability”; it is not the most direct consequence of this shortcut. The relevant consequence is that name lookup may succeed but no usable endpoint exists to receive traffic.

Question 480

A bank's backend Pods run but fail readiness, leaving the Service without ready targets. Which implementation together with matching acceptance evidence best meets this case?

  1. Grant operators only required API verbs and resources using RBAC, then test with kubectl auth can-i and separate synthetic identities. Acceptance evidence: With restricted identities, check get pods succeeds while delete secrets and create clusterroles are denied.
  2. Check EndpointSlices and Pod readiness when a Service exists but connections reach no application backends. Acceptance evidence: Compare a Service's label selector, EndpointSlices and Pod readiness conditions before changing external load-balancer settings.
  3. Use a ClusterRole for cluster-scoped resources or reusable rule definitions, recognizing that a RoleBinding to a ClusterRole grants those rules only in one namespace for namespaced resources. Acceptance evidence: Bind a synthetic ClusterRole through RoleBinding in namespace-a, then verify access fails in namespace-b.
  4. Check that a supported CNI plugin assigns reachable Pod addresses across worker nodes before troubleshooting Service routing or DNS names. Acceptance evidence: Deploy two synthetic Pods on different nodes and test direct Pod IP connectivity before testing the Service virtual IP.

Explanation

Correct Answer

B:

The situation is that a bank's backend Pods run but fail readiness, leaving the Service without ready targets. Check EndpointSlices and Pod readiness when a Service exists but connections reach no application backends. Acceptance evidence: Compare a Service's label selector, EndpointSlices and Pod readiness conditions before changing external load-balancer settings. This pairing is justified because endpointSlices describe endpoint addresses and readiness associated with a Service, allowing its dataplane to route toward matching healthy Pods.

Incorrect Answers

A:

This action and check address the distinct objective “Use least-privilege kubectl authentication and authorization during routine administration” instead of the stated acceptance requirement. The matching action is to check EndpointSlices and Pod readiness when a Service exists but connections reach no application backends. Its confirming test is to compare a Service's label selector, EndpointSlices and Pod readiness conditions before changing external load-balancer settings.

C:

This action and check address the distinct objective “Distinguish ClusterRoles from Roles and binding scope” instead of the stated acceptance requirement. The matching action is to check EndpointSlices and Pod readiness when a Service exists but connections reach no application backends. Its confirming test is to compare a Service's label selector, EndpointSlices and Pod readiness conditions before changing external load-balancer settings.

D:

This action and check address the distinct objective “Distinguish the CNI Pod network from Service discovery and routing” instead of the stated acceptance requirement. The matching action is to check EndpointSlices and Pod readiness when a Service exists but connections reach no application backends. Its confirming test is to compare a Service's label selector, EndpointSlices and Pod readiness conditions before changing external load-balancer settings.

Kubernetes and Cloud Native Associate (KCNA) Practice Tests