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 47

Question 460

A museum accidentally makes its internal cache service accessible on node ports while debugging client resolution. Which engineering change and test jointly addresses the scenario?

  1. 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.
  2. Use container runtime namespaces to isolate views of processes and networks while using cgroups to account for and constrain resources. Acceptance evidence: In a training namespace inspect PID views and a controlled memory limit, noting which mechanism changes identity or resource behavior.
  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. 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.

Explanation

Correct Answer

C:

The situation is that a museum accidentally makes its internal cache service accessible on node ports while debugging client resolution. 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. This pairing is justified because service type determines how clients can reach a stable Service: ClusterIP is internal, NodePort exposes a port on nodes, and LoadBalancer integrates external infrastructure.

Incorrect Answers

A:

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 use ClusterIP for internal backends and a properly controlled NodePort or supported LoadBalancer integration for justified external access. Its confirming test is to create a ClusterIP test Service and validate internal access, then compare the reachable endpoints under an authorized LoadBalancer configuration.

B:

This action and check address the distinct objective “Explain Linux namespaces and cgroups as distinct container isolation mechanisms” instead of the stated acceptance requirement. The matching action is to use ClusterIP for internal backends and a properly controlled NodePort or supported LoadBalancer integration for justified external access. Its confirming test is to create a ClusterIP test Service and validate internal access, then compare the reachable endpoints under an authorized LoadBalancer configuration.

D:

This action and check address the distinct objective “Distinguish Pod IPs from stable Services during rescheduling” instead of the stated acceptance requirement. The matching action is to use ClusterIP for internal backends and a properly controlled NodePort or supported LoadBalancer integration for justified external access. Its confirming test is to create a ClusterIP test Service and validate internal access, then compare the reachable endpoints under an authorized LoadBalancer configuration.

Question 461

A school enrollment Pod in admissions needs a billing Service in a different namespace. Which engineering approach is the most appropriate for this cloud-native case?

  1. Check EndpointSlices and Pod readiness when a Service exists but connections reach no application backends.
  2. Use cluster DNS records such as service.namespace.svc.cluster.local when a Pod connects to Services in other namespaces.
  3. Require verified API server certificates, properly scoped identities and audit policy rather than turning off certificate checks for convenience.
  4. Use an authorized kubectl debug ephemeral container when an application image lacks troubleshooting tools and policy permits ephemeral containers.

Explanation

Correct Answer

B:

Use cluster DNS records such as service.namespace.svc.cluster.local when a Pod connects to Services in other namespaces. This resolves the issue because coreDNS watches Service objects and serves cluster-aware names; bare names normally resolve relative to the requesting Pod's namespace and search domains. To verify, run nslookup for a Service using short and namespace-qualified names from test Pods in two different namespaces.

Incorrect Answers

A:

This option addresses the distinct objective “Use EndpointSlices to connect Service selectors with actual backend Pods”, not the immediate requirement. EndpointSlices describe endpoint addresses and readiness associated with a Service, allowing its dataplane to route toward matching healthy Pods. For the stated case, coreDNS watches Service objects and serves cluster-aware names; bare names normally resolve relative to the requesting Pod's namespace and search domains.

C:

This option addresses the distinct objective “Protect API server access using authenticated TLS clients and audited authorization”, not the immediate requirement. TLS establishes endpoint confidentiality and identity, while authentication and RBAC separately determine which API operations a caller may execute. For the stated case, coreDNS watches Service objects and serves cluster-aware names; bare names normally resolve relative to the requesting Pod's namespace and search domains.

D:

This option addresses the distinct objective “Use ephemeral debugging containers only with appropriate permission and safeguards”, not the immediate requirement. An ephemeral container can join a Pod's namespaces for observation but is not a substitute for repairing the owning Deployment's desired configuration. For the stated case, coreDNS watches Service objects and serves cluster-aware names; bare names normally resolve relative to the requesting Pod's namespace and search domains.

Question 462

A school enrollment Pod in admissions needs a billing Service in a different namespace. What infrastructure principle makes the correct treatment effective?

  1. NetworkPolicy declares traffic restrictions, but Kubernetes itself does not provide enforcement when the installed CNI lacks NetworkPolicy support.
  2. A Deployment creates or manages ReplicaSets, each ReplicaSet owns matching Pods, and selector consistency determines which Pods it counts.
  3. A failed readiness probe removes a Pod from ready Service endpoints, while failed liveness checks can restart a process; their operational consequences differ.
  4. CoreDNS watches Service objects and serves cluster-aware names; bare names normally resolve relative to the requesting Pod's namespace and search domains.

Explanation

Correct Answer

D:

CoreDNS watches Service objects and serves cluster-aware names; bare names normally resolve relative to the requesting Pod's namespace and search domains. It supports this action: Use cluster DNS records such as service.namespace.svc.cluster.local when a Pod connects to Services in other namespaces. To confirm, run nslookup for a Service using short and namespace-qualified names from test Pods in two different namespaces.

Incorrect Answers

A:

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 coreDNS watches Service objects and serves cluster-aware names; bare names normally resolve relative to the requesting Pod's namespace and search domains.

B:

That statement explains the distinct objective “Interpret ReplicaSet ownership and selectors in a Deployment” rather than the cause in this case. The deciding mechanism here is that coreDNS watches Service objects and serves cluster-aware names; bare names normally resolve relative to the requesting Pod's namespace and search domains.

C:

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 coreDNS watches Service objects and serves cluster-aware names; bare names normally resolve relative to the requesting Pod's namespace and search domains.

Question 463

A school enrollment Pod in admissions needs a billing Service in a different namespace. What verification result would most convincingly distinguish a working solution from a claim?

  1. Run nslookup for a Service using short and namespace-qualified names from test Pods in two different namespaces.
  2. Compare kubectl get pods -l app=inventory with Service selectors and EndpointSlices for a test workload.
  3. Create a ClusterIP test Service and validate internal access, then compare the reachable endpoints under an authorized LoadBalancer configuration.
  4. 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:

Run nslookup for a Service using short and namespace-qualified names from test Pods in two different namespaces. This is the relevant test 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

B:

This check would help evaluate the distinct objective “Use labels and selectors to connect resources predictably”, but not the required result. For this case, run nslookup for a Service using short and namespace-qualified names from test Pods in two different namespaces.

C:

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, run nslookup for a Service using short and namespace-qualified names from test Pods in two different namespaces.

D:

This check would help evaluate the distinct objective “Implement namespaced RBAC Roles for least-privilege resource permissions”, but not the required result. For this case, run nslookup for a Service using short and namespace-qualified names from test Pods in two different namespaces.

Question 464

A school enrollment Pod in admissions needs a billing Service in a different namespace. The change review contains this proposal: “Assume a short Service name always resolves to another namespace's workload regardless of the client's search path.” What risk matters most?

  1. Cross-namespace calls can fail or resolve a same-named but unrelated local Service.
  2. Availability and rollout behavior diverge because no workload controller owns the independent Pods.
  3. Dangerous existing configuration may persist because admission is not a universal replacement for every security control.
  4. Requests fail after a replica is replaced because the client bypassed the Service abstraction.

Explanation

Correct Answer

A:

Cross-namespace calls can fail or resolve a same-named but unrelated local Service. The shortcut creates this risk 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

B:

That outcome concerns the distinct objective “Distinguish Deployment desired state from a manually created Pod”; it is not the most direct consequence of this shortcut. The relevant consequence is that cross-namespace calls can fail or resolve a same-named but unrelated local Service.

C:

That outcome concerns the distinct objective “Use Pod Security Standards to deny overly privileged Pod configurations”; it is not the most direct consequence of this shortcut. The relevant consequence is that cross-namespace calls can fail or resolve a same-named but unrelated local Service.

D:

That outcome concerns the distinct objective “Distinguish Pod IPs from stable Services during rescheduling”; it is not the most direct consequence of this shortcut. The relevant consequence is that cross-namespace calls can fail or resolve a same-named but unrelated local Service.

Question 465

A school enrollment Pod in admissions needs a billing Service in a different namespace. Which implementation together with matching acceptance evidence best meets this case?

  1. 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.
  2. 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.
  3. 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.
  4. Inspect the relevant object's conditions and timestamped Events to place the failure at API admission, scheduling, image pulling or runtime startup. Acceptance evidence: Create synthetic invalid quota, unschedulable node and missing-image cases and compare their event reasons and assigned node status.

Explanation

Correct Answer

A:

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

B:

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 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 “Understand PersistentVolumeClaim binding to persistent storage resources” 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.

D:

This action and check address the distinct objective “Use describe and Events to distinguish admission, scheduling and execution errors” 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 466

An insurance sandbox uses identical api Service names in staging and production namespaces. Which Kubernetes or cloud-native implementation decision best solves the stated problem?

  1. Check EndpointSlices and Pod readiness when a Service exists but connections reach no application backends.
  2. Define appropriate HTTP routing through an installed Ingress controller or Gateway API controller rather than expecting the API object alone to provision a proxy.
  3. Use cluster DNS records such as service.namespace.svc.cluster.local when a Pod connects to Services in other namespaces.
  4. Expose appropriately labeled /metrics endpoints or exporters and configure Prometheus scrape targets to collect time-series measurements.

Explanation

Correct Answer

C:

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. This resolves the issue because coreDNS watches Service objects and serves cluster-aware names; bare names normally resolve relative to the requesting Pod's namespace and search domains. To verify, run nslookup for a Service using short and namespace-qualified names from test Pods in two different namespaces.

Incorrect Answers

A:

The situation is that an insurance sandbox uses identical api Service names in staging and production namespaces. This option addresses the distinct objective “Use EndpointSlices to connect Service selectors with actual backend Pods”, not the immediate requirement. EndpointSlices describe endpoint addresses and readiness associated with a Service, allowing its dataplane to route toward matching healthy Pods. For the stated case, coreDNS watches Service objects and serves cluster-aware names; bare names normally resolve relative to the requesting Pod's namespace and search domains.

B:

This option addresses the distinct objective “Choose Ingress or Gateway API with an implementing controller for HTTP exposure”, not the immediate requirement. Ingress and Gateway API express routing intent, while an actual controller/dataplane implements TLS termination, listeners and backend forwarding. For the stated case, coreDNS watches Service objects and serves cluster-aware names; bare names normally resolve relative to the requesting Pod's namespace and search domains.

D:

This option addresses the distinct objective “Understand Prometheus pull-based metrics collection and exporters”, not the immediate requirement. Prometheus commonly pulls numeric samples from configured targets, stores them as labeled time series and supports PromQL queries over those samples. For the stated case, coreDNS watches Service objects and serves cluster-aware names; bare names normally resolve relative to the requesting Pod's namespace and search domains.

Question 467

An insurance sandbox uses identical api Service names in staging and production namespaces. Which platform mechanism explains why the suitable approach works?

  1. CoreDNS watches Service objects and serves cluster-aware names; bare names normally resolve relative to the requesting Pod's namespace and search domains.
  2. kubectl logs retrieves container output and --previous can expose the prior terminated instance, but application output is not a substitute for cluster Events.
  3. StatefulSet manages stable ordinal identities and preserves PVC-associated storage per replica across routine Pod replacement, subject to retention policy.
  4. Ingress and Gateway API express routing intent, while an actual controller/dataplane implements TLS termination, listeners and backend forwarding.

Explanation

Correct Answer

A:

The situation is that an insurance sandbox uses identical api Service names in staging and production namespaces. CoreDNS watches Service objects and serves cluster-aware names; bare names normally resolve relative to the requesting Pod's namespace and search domains. It supports this action: Use cluster DNS records such as service.namespace.svc.cluster.local when a Pod connects to Services in other namespaces. To confirm, run nslookup for a Service using short and namespace-qualified names from test Pods in two different namespaces.

Incorrect Answers

B:

That statement explains the distinct objective “Use kubectl logs and previous container logs to isolate application crashes” rather than the cause in this case. The deciding mechanism here is that coreDNS watches Service objects and serves cluster-aware names; bare names normally resolve relative to the requesting Pod's namespace and search domains.

C:

That statement explains the distinct objective “Use StatefulSet for stable ordinal identity and persistent per-replica claims” rather than the cause in this case. The deciding mechanism here is that coreDNS watches Service objects and serves cluster-aware names; bare names normally resolve relative to the requesting Pod's namespace and search domains.

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 coreDNS watches Service objects and serves cluster-aware names; bare names normally resolve relative to the requesting Pod's namespace and search domains.

Question 468

An insurance sandbox uses identical api Service names in staging and production namespaces. Which controlled observation would best validate the intended improvement?

  1. Create a ClusterIP test Service and validate internal access, then compare the reachable endpoints under an authorized LoadBalancer configuration.
  2. Run a test web Pod without a token mount and verify service operation succeeds while in-cluster API calls are unavailable.
  3. In a staging gateway route 5 percent to a canary, inspect version-specific success rates and verify a rollback rule.
  4. 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. Run nslookup for a Service using short and namespace-qualified names from test Pods in two different namespaces. This is the relevant test 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:

The situation is that an insurance sandbox uses identical api Service names in staging and production namespaces. 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, run nslookup for a Service using short and namespace-qualified names from test Pods in two different namespaces.

B:

This check would help evaluate the distinct objective “Enforce workload service account token boundaries and avoid needless mounts”, but not the required result. For this case, run nslookup for a Service using short and namespace-qualified names from test Pods in two different namespaces.

C:

This check would help evaluate the distinct objective “Distinguish canary and blue-green delivery strategies from Kubernetes Deployment defaults”, but not the required result. For this case, run nslookup for a Service using short and namespace-qualified names from test Pods in two different namespaces.

Question 469

An insurance sandbox uses identical api Service names in staging and production namespaces. An engineer proposes: “Assume a short Service name always resolves to another namespace's workload regardless of the client's search path.” What adverse outcome would be most direct?

  1. The claim remains Pending and dependent Pods cannot mount the missing volume.
  2. Cross-namespace calls can fail or resolve a same-named but unrelated local Service.
  3. Sensitive traffic may remain allowed because the networking implementation does not enforce the declared policy.
  4. The production binary can differ from the validated image even though the release version label matches.

Explanation

Correct Answer

B:

The situation is that an insurance sandbox uses identical api Service names in staging and production namespaces. Cross-namespace calls can fail or resolve a same-named but unrelated local Service. The shortcut creates this risk 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:

That outcome concerns the distinct objective “Use StorageClass for dynamic volume provisioning rather than handcrafting every disk”; it is not the most direct consequence of this shortcut. The relevant consequence is that cross-namespace calls can fail or resolve a same-named but unrelated local Service.

C:

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 cross-namespace calls can fail or resolve a same-named but unrelated local Service.

D:

That outcome concerns the distinct objective “Separate CI build verification from CD environment promotion”; it is not the most direct consequence of this shortcut. The relevant consequence is that cross-namespace calls can fail or resolve a same-named but unrelated local Service.

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.

Kubernetes and Cloud Native Associate (KCNA) Practice Tests