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 8

Question 70

A student inspects a managed Kubernetes cluster where ClusterIP traffic works but kube-proxy Pods are absent. Which combined solution and independent check are most directly justified?

  1. Identify whether the cluster uses kube-proxy or an alternative Service dataplane before diagnosing virtual Service IP forwarding behavior. Acceptance evidence: Read the cluster networking configuration, find a test Service and verify backend connectivity using the installed dataplane.
  2. Configure an HPA for an eligible scalable controller using available resource or custom metrics and sensible minimum/maximum replicas. Acceptance evidence: Generate controlled CPU load, verify HPA current/target metric reporting and observe replica changes within configured limits.
  3. Inspect Deployment, ReplicaSet and Pod owner references when verifying which controller maintains replica count. Acceptance evidence: Run kubectl get rs and kubectl describe deployment for a test rollout and verify the expected owner chain.
  4. Use the scheduler's node-binding decision to explain initial Pod placement, then inspect the chosen node's kubelet for local container lifecycle status. Acceptance evidence: Inspect a new Pod's nodeName and Events, then compare scheduling events with kubelet-reported container status.

Explanation

Correct Answer

A:

The situation is that a student inspects a managed Kubernetes cluster where ClusterIP traffic works but kube-proxy Pods are absent. Identify whether the cluster uses kube-proxy or an alternative Service dataplane before diagnosing virtual Service IP forwarding behavior. Acceptance evidence: Read the cluster networking configuration, find a test Service and verify backend connectivity using the installed dataplane. This pairing is justified because kube-proxy can maintain node networking rules for Services, but supported network implementations may replace this function.

Incorrect Answers

B:

This action and check address the distinct objective “Use HorizontalPodAutoscaler metrics rather than ad hoc instance scripts” instead of the stated acceptance requirement. The matching action is to identify whether the cluster uses kube-proxy or an alternative Service dataplane before diagnosing virtual Service IP forwarding behavior. Its confirming test is to read the cluster networking configuration, find a test Service and verify backend connectivity using the installed dataplane.

C:

This action and check address the distinct objective “Interpret ReplicaSet ownership and selectors in a Deployment” instead of the stated acceptance requirement. The matching action is to identify whether the cluster uses kube-proxy or an alternative Service dataplane before diagnosing virtual Service IP forwarding behavior. Its confirming test is to read the cluster networking configuration, find a test Service and verify backend connectivity using the installed dataplane.

D:

This action and check address the distinct objective “Separate kube-scheduler decisions from kubelet execution” instead of the stated acceptance requirement. The matching action is to identify whether the cluster uses kube-proxy or an alternative Service dataplane before diagnosing virtual Service IP forwarding behavior. Its confirming test is to read the cluster networking configuration, find a test Service and verify backend connectivity using the installed dataplane.

Question 71

A telemetry helper must read a web service's localhost diagnostic endpoint without an external Service. What technical action should the platform team take in this situation?

  1. Identify whether the cluster uses kube-proxy or an alternative Service dataplane before diagnosing virtual Service IP forwarding behavior.
  2. Use kubectl get for concise resource lists and kubectl describe for detailed status, conditions and Events when triaging a workload.
  3. Group tightly coupled containers that require the same Pod networking identity and optionally shared volumes into one Pod while keeping independently scalable services separate.
  4. Read current logs and --previous logs for the failing container and correlate timestamps with Pod restart counts before altering workloads.

Explanation

Correct Answer

C:

Group tightly coupled containers that require the same Pod networking identity and optionally shared volumes into one Pod while keeping independently scalable services separate. This resolves the issue because containers in a Pod share a network namespace and IP address and can coordinate on localhost, while the Pod is scheduled as one unit. To verify, deploy a test sidecar and main container, verify localhost communication and compare their shared Pod IP with a separate Pod.

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, containers in a Pod share a network namespace and IP address and can coordinate on localhost, while the Pod is scheduled as one unit.

B:

This option addresses the distinct objective “Use kubectl get and describe for distinct inspection needs”, not the immediate requirement. Get returns selected object information, while describe adds human-readable state and related Events helpful for initial diagnosis. For the stated case, containers in a Pod share a network namespace and IP address and can coordinate on localhost, while the Pod is scheduled as one unit.

D:

This option addresses the distinct objective “Use kubectl logs and previous container logs to isolate application crashes”, not the immediate requirement. Kubectl logs retrieves container output and --previous can expose the prior terminated instance, but application output is not a substitute for cluster Events. For the stated case, containers in a Pod share a network namespace and IP address and can coordinate on localhost, while the Pod is scheduled as one unit.

Question 72

A telemetry helper must read a web service's localhost diagnostic endpoint without an external Service. What underlying Kubernetes behavior is most relevant to this technical decision?

  1. A failed readiness probe removes a Pod from ready Service endpoints, while failed liveness checks can restart a process; their operational consequences differ.
  2. A Deployment owns ReplicaSets that manage matching Pods and supports declarative rollout history, unlike an independent Pod object.
  3. Kubernetes labels are queryable object metadata, while selectors connect controllers and Services to matching endpoints; names alone do not create these relationships.
  4. Containers in a Pod share a network namespace and IP address and can coordinate on localhost, while the Pod is scheduled as one unit.

Explanation

Correct Answer

D:

Containers in a Pod share a network namespace and IP address and can coordinate on localhost, while the Pod is scheduled as one unit. It supports this action: Group tightly coupled containers that require the same Pod networking identity and optionally shared volumes into one Pod while keeping independently scalable services separate. To confirm, deploy a test sidecar and main container, verify localhost communication and compare their shared Pod IP with a separate Pod.

Incorrect Answers

A:

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 containers in a Pod share a network namespace and IP address and can coordinate on localhost, while the Pod is scheduled as one unit.

B:

That statement explains the distinct objective “Distinguish Deployment desired state from a manually created Pod” rather than the cause in this case. The deciding mechanism here is that containers in a Pod share a network namespace and IP address and can coordinate on localhost, while the Pod is scheduled as one unit.

C:

That statement explains the distinct objective “Use labels and selectors to connect resources predictably” rather than the cause in this case. The deciding mechanism here is that containers in a Pod share a network namespace and IP address and can coordinate on localhost, while the Pod is scheduled as one unit.

Question 73

A telemetry helper must read a web service's localhost diagnostic endpoint without an external Service. What acceptance check most directly confirms this requirement is met?

  1. Deploy a test sidecar and main container, verify localhost communication and compare their shared Pod IP with a separate Pod.
  2. Create a namespaced ConfigMap with kubectl, read it back through the API, and confirm no manual edit of a worker-node process was required.
  3. Bind a synthetic ClusterRole through RoleBinding in namespace-a, then verify access fails in namespace-b.
  4. Read the cluster networking configuration, find a test Service and verify backend connectivity using the installed dataplane.

Explanation

Correct Answer

A:

Deploy a test sidecar and main container, verify localhost communication and compare their shared Pod IP with a separate Pod. This is the relevant test because containers in a Pod share a network namespace and IP address and can coordinate on localhost, while the Pod is scheduled as one unit.

Incorrect Answers

B:

This check would help evaluate the distinct objective “Trace Kubernetes API requests through the kube-apiserver entry point”, but not the required result. For this case, deploy a test sidecar and main container, verify localhost communication and compare their shared Pod IP with a separate Pod.

C:

This check would help evaluate the distinct objective “Distinguish ClusterRoles from Roles and binding scope”, but not the required result. For this case, deploy a test sidecar and main container, verify localhost communication and compare their shared Pod IP with a separate Pod.

D:

This check would help evaluate the distinct objective “Understand service proxy implementations without assuming kube-proxy is mandatory”, but not the required result. For this case, deploy a test sidecar and main container, verify localhost communication and compare their shared Pod IP with a separate Pod.

Question 74

A telemetry helper must read a web service's localhost diagnostic endpoint without an external Service. The team suggests: “Put every microservice of an enterprise into one giant Pod because all containers can technically share localhost.” Which failure should the reviewer anticipate?

  1. Independent rollout, scaling and failure isolation become difficult because the services are coupled to one scheduling unit.
  2. A working dataplane may be needlessly modified, disrupting traffic that was already being forwarded correctly.
  3. A compromised unrelated Pod may reach protected application ports across trust boundaries.
  4. Operators can see the metadata but the Service cannot select the desired Pods using that annotation.

Explanation

Correct Answer

A:

Independent rollout, scaling and failure isolation become difficult because the services are coupled to one scheduling unit. The shortcut creates this risk because containers in a Pod share a network namespace and IP address and can coordinate on localhost, while the Pod is scheduled as one unit.

Incorrect Answers

B:

That outcome concerns the distinct objective “Understand service proxy implementations without assuming kube-proxy is mandatory”; it is not the most direct consequence of this shortcut. The relevant consequence is that independent rollout, scaling and failure isolation become difficult because the services are coupled to one scheduling unit.

C:

That outcome concerns the distinct objective “Limit workload-to-workload access with explicit NetworkPolicy allow rules”; it is not the most direct consequence of this shortcut. The relevant consequence is that independent rollout, scaling and failure isolation become difficult because the services are coupled to one scheduling unit.

D:

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 independent rollout, scaling and failure isolation become difficult because the services are coupled to one scheduling unit.

Question 75

A telemetry helper must read a web service's localhost diagnostic endpoint without an external Service. Which engineering change and test jointly addresses the scenario?

  1. Apply appropriate ResourceQuota and LimitRange policy to bound namespace consumption and guide default container resource requests or limits. Acceptance evidence: Create a controlled test namespace with a tiny quota and verify a request exceeding aggregate limits is rejected.
  2. Group tightly coupled containers that require the same Pod networking identity and optionally shared volumes into one Pod while keeping independently scalable services separate. Acceptance evidence: Deploy a test sidecar and main container, verify localhost communication and compare their shared Pod IP with a separate Pod.
  3. Run controlled DNS queries and IP connectivity tests before changing service discovery, CNI routes or application endpoints. Acceptance evidence: Test the same Service from a diagnostic Pod by fully qualified DNS name and known ClusterIP, then inspect CoreDNS logs if only resolution fails.
  4. Use a Deployment for a replicated stateless application requiring rolling updates and replacement of failed Pods. Acceptance evidence: Scale a test Deployment and inspect its ReplicaSet and owned Pods, then compare deleting a standalone Pod.

Explanation

Correct Answer

B:

Group tightly coupled containers that require the same Pod networking identity and optionally shared volumes into one Pod while keeping independently scalable services separate. Acceptance evidence: Deploy a test sidecar and main container, verify localhost communication and compare their shared Pod IP with a separate Pod. This pairing is justified because containers in a Pod share a network namespace and IP address and can coordinate on localhost, while the Pod is scheduled as one unit.

Incorrect Answers

A:

This action and check address the distinct objective “Understand resource quotas and LimitRanges for namespace capacity governance” instead of the stated acceptance requirement. The matching action is to group tightly coupled containers that require the same Pod networking identity and optionally shared volumes into one Pod while keeping independently scalable services separate. Its confirming test is to deploy a test sidecar and main container, verify localhost communication and compare their shared Pod IP with a separate Pod.

C:

This action and check address the distinct objective “Diagnose cluster DNS separately from Pod network reachability” instead of the stated acceptance requirement. The matching action is to group tightly coupled containers that require the same Pod networking identity and optionally shared volumes into one Pod while keeping independently scalable services separate. Its confirming test is to deploy a test sidecar and main container, verify localhost communication and compare their shared Pod IP with a separate Pod.

D:

This action and check address the distinct objective “Distinguish Deployment desired state from a manually created Pod” instead of the stated acceptance requirement. The matching action is to group tightly coupled containers that require the same Pod networking identity and optionally shared volumes into one Pod while keeping independently scalable services separate. Its confirming test is to deploy a test sidecar and main container, verify localhost communication and compare their shared Pod IP with a separate Pod.

Question 76

A financial cooperative asks whether a billing API and a separately scalable reporting job should share one Pod. Which engineering approach is the most appropriate for this cloud-native case?

  1. Use the scheduler's node-binding decision to explain initial Pod placement, then inspect the chosen node's kubelet for local container lifecycle status.
  2. Compare Deployment rollout history, changed image digests, readiness events and application error times to identify an introduced regression.
  3. Group tightly coupled containers that require the same Pod networking identity and optionally shared volumes into one Pod while keeping independently scalable services separate.
  4. Change a workload's declared replicas and observe controllers update actual Pod count, understanding that status may lag behind spec during reconciliation.

Explanation

Correct Answer

C:

The situation is that a financial cooperative asks whether a billing API and a separately scalable reporting job should share one Pod. Group tightly coupled containers that require the same Pod networking identity and optionally shared volumes into one Pod while keeping independently scalable services separate. This resolves the issue because containers in a Pod share a network namespace and IP address and can coordinate on localhost, while the Pod is scheduled as one unit. To verify, deploy a test sidecar and main container, verify localhost communication and compare their shared Pod IP with a separate Pod.

Incorrect Answers

A:

This option addresses the distinct objective “Separate kube-scheduler decisions from kubelet execution”, not the immediate requirement. The scheduler selects a suitable node for an unscheduled Pod; kubelet on that node uses the runtime to start and monitor containers. For the stated case, containers in a Pod share a network namespace and IP address and can coordinate on localhost, while the Pod is scheduled as one unit.

B:

This option addresses the distinct objective “Correlate application rollout revisions with error spikes”, not the immediate requirement. Kubernetes object transitions and application telemetry must be correlated; a healthy rollout condition alone does not prove user-level functionality. For the stated case, containers in a Pod share a network namespace and IP address and can coordinate on localhost, while the Pod is scheduled as one unit.

D:

This option addresses the distinct objective “Explain desired state versus observed status in Kubernetes objects”, not the immediate requirement. The API stores a desired spec while controllers asynchronously react to observations; status describes progress, not a guarantee of immediate convergence. For the stated case, containers in a Pod share a network namespace and IP address and can coordinate on localhost, while the Pod is scheduled as one unit.

Question 77

A financial cooperative asks whether a billing API and a separately scalable reporting job should share one Pod. What infrastructure principle makes the correct treatment effective?

  1. The API stores a desired spec while controllers asynchronously react to observations; status describes progress, not a guarantee of immediate convergence.
  2. A Service name may resolve successfully while its selector yields no ready endpoints, and both differ from a backend listening on the wrong port.
  3. Each kubelet watches assigned Pod specifications and coordinates the container runtime, volumes and health information on its node.
  4. Containers in a Pod share a network namespace and IP address and can coordinate on localhost, while the Pod is scheduled as one unit.

Explanation

Correct Answer

D:

The situation is that a financial cooperative asks whether a billing API and a separately scalable reporting job should share one Pod. Containers in a Pod share a network namespace and IP address and can coordinate on localhost, while the Pod is scheduled as one unit. It supports this action: Group tightly coupled containers that require the same Pod networking identity and optionally shared volumes into one Pod while keeping independently scalable services separate. To confirm, deploy a test sidecar and main container, verify localhost communication and compare their shared Pod IP with a separate Pod.

Incorrect Answers

A:

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 containers in a Pod share a network namespace and IP address and can coordinate on localhost, while the Pod is scheduled as one unit.

B:

That statement explains the distinct objective “Distinguish a failed Service selector from broken DNS or a failing backend” rather than the cause in this case. The deciding mechanism here is that containers in a Pod share a network namespace and IP address and can coordinate on localhost, while the Pod is scheduled as one unit.

C:

That statement explains the distinct objective “Recognize the kubelet role in local Pod lifecycle management” rather than the cause in this case. The deciding mechanism here is that containers in a Pod share a network namespace and IP address and can coordinate on localhost, while the Pod is scheduled as one unit.

Question 78

A financial cooperative asks whether a billing API and a separately scalable reporting job should share one Pod. What verification result would most convincingly distinguish a working solution from a claim?

  1. Resolve an approved image digest, deploy that reference in staging and verify the same digest exists in the production Pod spec.
  2. Deploy a test sidecar and main container, verify localhost communication and compare their shared Pod IP with a separate Pod.
  3. In a staging gateway route 5 percent to a canary, inspect version-specific success rates and verify a rollback rule.
  4. Inspect the cluster backup policy for etcd snapshots and separately restore synthetic application data from its own backup.

Explanation

Correct Answer

B:

The situation is that a financial cooperative asks whether a billing API and a separately scalable reporting job should share one Pod. Deploy a test sidecar and main container, verify localhost communication and compare their shared Pod IP with a separate Pod. This is the relevant test because containers in a Pod share a network namespace and IP address and can coordinate on localhost, while the Pod is scheduled as one unit.

Incorrect Answers

A:

This check would help evaluate the distinct objective “Use an immutable image digest for exact deployment provenance”, but not the required result. For this case, deploy a test sidecar and main container, verify localhost communication and compare their shared Pod IP with a separate Pod.

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, deploy a test sidecar and main container, verify localhost communication and compare their shared Pod IP with a separate Pod.

D:

This check would help evaluate the distinct objective “Distinguish etcd persistence from running workload data”, but not the required result. For this case, deploy a test sidecar and main container, verify localhost communication and compare their shared Pod IP with a separate Pod.

Question 79

A financial cooperative asks whether a billing API and a separately scalable reporting job should share one Pod. The change review contains this proposal: “Put every microservice of an enterprise into one giant Pod because all containers can technically share localhost.” What risk matters most?

  1. The scheduler may legally use a non-preferred node, violating the policy that was mistakenly assumed mandatory.
  2. Pods may start but remain unable to communicate across nodes because the CNI dataplane was never established.
  3. Independent rollout, scaling and failure isolation become difficult because the services are coupled to one scheduling unit.
  4. Sensitive workloads may remain reachable until actual identity and traffic controls are installed.

Explanation

Correct Answer

C:

The situation is that a financial cooperative asks whether a billing API and a separately scalable reporting job should share one Pod. Independent rollout, scaling and failure isolation become difficult because the services are coupled to one scheduling unit. The shortcut creates this risk because containers in a Pod share a network namespace and IP address and can coordinate on localhost, while the Pod is scheduled as one unit.

Incorrect Answers

A:

That outcome concerns the distinct objective “Distinguish preferred node affinity from required scheduling rules”; it is not the most direct consequence of this shortcut. The relevant consequence is that independent rollout, scaling and failure isolation become difficult because the services are coupled to one scheduling unit.

B:

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 independent rollout, scaling and failure isolation become difficult because the services are coupled to one scheduling unit.

D:

That outcome concerns the distinct objective “Use namespaces as organizational scopes without treating them as firewalls”; it is not the most direct consequence of this shortcut. The relevant consequence is that independent rollout, scaling and failure isolation become difficult because the services are coupled to one scheduling unit.

Question 80

A financial cooperative asks whether a billing API and a separately scalable reporting job should share one Pod. Which implementation together with matching acceptance evidence best meets this case?

  1. 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.
  2. Require approved image registries, signature or digest verification and patch ownership when admitting production container images. Acceptance evidence: Deploy one signed approved image and one unverified synthetic image under a test admission policy, recording expected allow and deny results.
  3. Treat etcd as Kubernetes control-plane state storage and protect its snapshots, keys, and access separately from an application's database or PVC. Acceptance evidence: Inspect the cluster backup policy for etcd snapshots and separately restore synthetic application data from its own backup.
  4. Group tightly coupled containers that require the same Pod networking identity and optionally shared volumes into one Pod while keeping independently scalable services separate. Acceptance evidence: Deploy a test sidecar and main container, verify localhost communication and compare their shared Pod IP with a separate Pod.

Explanation

Correct Answer

D:

The situation is that a financial cooperative asks whether a billing API and a separately scalable reporting job should share one Pod. Group tightly coupled containers that require the same Pod networking identity and optionally shared volumes into one Pod while keeping independently scalable services separate. Acceptance evidence: Deploy a test sidecar and main container, verify localhost communication and compare their shared Pod IP with a separate Pod. This pairing is justified because containers in a Pod share a network namespace and IP address and can coordinate on localhost, while the Pod is scheduled as one unit.

Incorrect Answers

A:

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 group tightly coupled containers that require the same Pod networking identity and optionally shared volumes into one Pod while keeping independently scalable services separate. Its confirming test is to deploy a test sidecar and main container, verify localhost communication and compare their shared Pod IP with a separate Pod.

B:

This action and check address the distinct objective “Use image provenance and policy controls without trusting mutable tags” instead of the stated acceptance requirement. The matching action is to group tightly coupled containers that require the same Pod networking identity and optionally shared volumes into one Pod while keeping independently scalable services separate. Its confirming test is to deploy a test sidecar and main container, verify localhost communication and compare their shared Pod IP with a separate Pod.

C:

This action and check address the distinct objective “Distinguish etcd persistence from running workload data” instead of the stated acceptance requirement. The matching action is to group tightly coupled containers that require the same Pod networking identity and optionally shared volumes into one Pod while keeping independently scalable services separate. Its confirming test is to deploy a test sidecar and main container, verify localhost communication and compare their shared Pod IP with a separate Pod.

Kubernetes and Cloud Native Associate (KCNA) Practice Tests