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 12

Question 110

An educational platform wants department-specific resource organization and mistakenly expects namespace labels alone to stop traffic. Which implementation together with matching acceptance evidence best meets this case?

  1. Assign related namespaced resources to a project namespace and enforce authorization and network isolation with separate policies. Acceptance evidence: Create matching Service names in two namespaces and test separately configured RBAC and NetworkPolicy access boundaries.
  2. 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.
  3. Observe rollout progression and use a reviewed rollback to a previous ReplicaSet revision when a new application build fails health checks. Acceptance evidence: Change a test image to a known failing build, inspect rollout status and rollback history, then verify the earlier healthy version serves requests.
  4. Prefer documented Kubernetes APIs and interoperable telemetry formats when possible while identifying any platform-specific extensions needed for the real deployment. Acceptance evidence: Test a synthetic standard API manifest and OpenTelemetry trace export across two platforms, documenting any unsupported extensions.

Explanation

Correct Answer

A:

The situation is that an educational platform wants department-specific resource organization and mistakenly expects namespace labels alone to stop traffic. Assign related namespaced resources to a project namespace and enforce authorization and network isolation with separate policies. Acceptance evidence: Create matching Service names in two namespaces and test separately configured RBAC and NetworkPolicy access boundaries. This pairing is justified because a namespace scopes many API object names and administrative boundaries, but merely creating it does not deny network communication across namespaces.

Incorrect Answers

B:

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 assign related namespaced resources to a project namespace and enforce authorization and network isolation with separate policies. Its confirming test is to create matching Service names in two namespaces and test separately configured RBAC and NetworkPolicy access boundaries.

C:

This action and check address the distinct objective “Use rollout status and undo to validate and recover a Deployment release” instead of the stated acceptance requirement. The matching action is to assign related namespaced resources to a project namespace and enforce authorization and network isolation with separate policies. Its confirming test is to create matching Service names in two namespaces and test separately configured RBAC and NetworkPolicy access boundaries.

D:

This action and check address the distinct objective “Understand open standards and vendor-neutral community collaboration” instead of the stated acceptance requirement. The matching action is to assign related namespaced resources to a project namespace and enforce authorization and network isolation with separate policies. Its confirming test is to create matching Service names in two namespaces and test separately configured RBAC and NetworkPolicy access boundaries.

Question 111

An online newsroom increases desired replica count before a major live event. Which engineering approach is the most appropriate for this cloud-native case?

  1. Change a workload's declared replicas and observe controllers update actual Pod count, understanding that status may lag behind spec during reconciliation.
  2. Apply stable application labels and ensure Services and controllers select the intended Pods by equality or set-based matching.
  3. Create a Role with only required verbs and resource types, and bind it to the intended subject within the target namespace.
  4. Observe rollout progression and use a reviewed rollback to a previous ReplicaSet revision when a new application build fails health checks.

Explanation

Correct Answer

A:

Change a workload's declared replicas and observe controllers update actual Pod count, understanding that status may lag behind spec during reconciliation. This resolves the issue because the API stores a desired spec while controllers asynchronously react to observations; status describes progress, not a guarantee of immediate convergence. To verify, set replicas from two to four, inspect generation and observed generation and watch readyReplicas converge.

Incorrect Answers

B:

This option addresses the distinct objective “Use labels and selectors to connect resources predictably”, not the immediate requirement. Kubernetes labels are queryable object metadata, while selectors connect controllers and Services to matching endpoints; names alone do not create these relationships. For the stated case, the API stores a desired spec while controllers asynchronously react to observations; status describes progress, not a guarantee of immediate convergence.

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, the API stores a desired spec while controllers asynchronously react to observations; status describes progress, not a guarantee of immediate convergence.

D:

This option addresses the distinct objective “Use rollout status and undo to validate and recover a Deployment release”, not the immediate requirement. Deployment rollout strategy gradually replaces Pods and preserves revision history, but success depends on availability and revision retention settings. For the stated case, the API stores a desired spec while controllers asynchronously react to observations; status describes progress, not a guarantee of immediate convergence.

Question 112

An online newsroom increases desired replica count before a major live event. What infrastructure principle makes the correct treatment effective?

  1. A Deployment owns ReplicaSets that manage matching Pods and supports declarative rollout history, unlike an independent Pod object.
  2. Alert rules evaluate time-series expressions while Alertmanager groups, routes and silences notifications; neither automatically fixes the underlying workload.
  3. CPU limits may throttle running processes, whereas exceeding memory constraints can cause OOM termination; Pod scheduling itself depends on requests.
  4. The API stores a desired spec while controllers asynchronously react to observations; status describes progress, not a guarantee of immediate convergence.

Explanation

Correct Answer

D:

The API stores a desired spec while controllers asynchronously react to observations; status describes progress, not a guarantee of immediate convergence. It supports this action: Change a workload's declared replicas and observe controllers update actual Pod count, understanding that status may lag behind spec during reconciliation. To confirm, set replicas from two to four, inspect generation and observed generation and watch readyReplicas converge.

Incorrect Answers

A:

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 the API stores a desired spec while controllers asynchronously react to observations; status describes progress, not a guarantee of immediate convergence.

B:

That statement explains the distinct objective “Build meaningful alert rules and route notifications through Alertmanager” rather than the cause in this case. The deciding mechanism here is that the API stores a desired spec while controllers asynchronously react to observations; status describes progress, not a guarantee of immediate convergence.

C:

That statement explains the distinct objective “Distinguish memory limits from CPU throttling for scheduling and runtime symptoms” rather than the cause in this case. The deciding mechanism here is that the API stores a desired spec while controllers asynchronously react to observations; status describes progress, not a guarantee of immediate convergence.

Question 113

An online newsroom increases desired replica count before a major live event. What verification result would most convincingly distinguish a working solution from a claim?

  1. Inspect a new Pod's nodeName and Events, then compare scheduling events with kubelet-reported container status.
  2. Run kubectl kustomize for development and production overlays and compare the resulting YAML objects before application.
  3. Run kubectl config current-context and kubectl config view --minify, then perform a read-only lookup in the expected namespace.
  4. Set replicas from two to four, inspect generation and observed generation and watch readyReplicas converge.

Explanation

Correct Answer

D:

Set replicas from two to four, inspect generation and observed generation and watch readyReplicas converge. This is the relevant test because the API stores a desired spec while controllers asynchronously react to observations; status describes progress, not a guarantee of immediate convergence.

Incorrect Answers

A:

This check would help evaluate the distinct objective “Separate kube-scheduler decisions from kubelet execution”, but not the required result. For this case, set replicas from two to four, inspect generation and observed generation and watch readyReplicas converge.

B:

This check would help evaluate the distinct objective “Use Kustomize overlays to adapt manifests without copying whole deployments”, but not the required result. For this case, set replicas from two to four, inspect generation and observed generation and watch readyReplicas converge.

C:

This check would help evaluate the distinct objective “Manage kubectl contexts to avoid changes in the wrong cluster”, but not the required result. For this case, set replicas from two to four, inspect generation and observed generation and watch readyReplicas converge.

Question 114

An online newsroom increases desired replica count before a major live event. The change review contains this proposal: “Read an updated spec and immediately assume every requested replica is serving traffic despite pending pulls or readiness failures.” What risk matters most?

  1. A deployment is recorded as changed while the application is still below its service availability requirement.
  2. Credential reuse could expose all namespaces and persist after the original developer loses access.
  3. Monitoring dashboards show empty or stale series because the expected metrics were never exposed or scraped.
  4. The image-pull issue stays unresolved because etcd is not the node component managing container starts.

Explanation

Correct Answer

A:

A deployment is recorded as changed while the application is still below its service availability requirement. The shortcut creates this risk because the API stores a desired spec while controllers asynchronously react to observations; status describes progress, not a guarantee of immediate convergence.

Incorrect Answers

B:

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 a deployment is recorded as changed while the application is still below its service availability requirement.

C:

That outcome concerns the distinct objective “Understand Prometheus pull-based metrics collection and exporters”; it is not the most direct consequence of this shortcut. The relevant consequence is that a deployment is recorded as changed while the application is still below its service availability requirement.

D:

That outcome concerns the distinct objective “Recognize the kubelet role in local Pod lifecycle management”; it is not the most direct consequence of this shortcut. The relevant consequence is that a deployment is recorded as changed while the application is still below its service availability requirement.

Question 115

An online newsroom increases desired replica count before a major live event. Which implementation together with matching acceptance evidence best meets this case?

  1. Change a workload's declared replicas and observe controllers update actual Pod count, understanding that status may lag behind spec during reconciliation. Acceptance evidence: Set replicas from two to four, inspect generation and observed generation and watch readyReplicas converge.
  2. 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.
  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. 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.

Explanation

Correct Answer

A:

Change a workload's declared replicas and observe controllers update actual Pod count, understanding that status may lag behind spec during reconciliation. Acceptance evidence: Set replicas from two to four, inspect generation and observed generation and watch readyReplicas converge. This pairing is justified because the API stores a desired spec while controllers asynchronously react to observations; status describes progress, not a guarantee of immediate convergence.

Incorrect Answers

B:

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 change a workload's declared replicas and observe controllers update actual Pod count, understanding that status may lag behind spec during reconciliation. Its confirming test is to set replicas from two to four, inspect generation and observed generation and watch readyReplicas converge.

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 change a workload's declared replicas and observe controllers update actual Pod count, understanding that status may lag behind spec during reconciliation. Its confirming test is to set replicas from two to four, inspect generation and observed generation and watch readyReplicas converge.

D:

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 change a workload's declared replicas and observe controllers update actual Pod count, understanding that status may lag behind spec during reconciliation. Its confirming test is to set replicas from two to four, inspect generation and observed generation and watch readyReplicas converge.

Question 116

A small retailer scales its Deployment but reports success from spec alone while new Pods are still Pending. Which engineering approach is the most appropriate for this cloud-native case?

  1. Inspect kubelet-reported Pod and container conditions when a scheduled workload fails to start, while keeping cluster resources managed through the API.
  2. Match a Service's exposed port and targetPort to the actual listening application container, checking protocol and named ports when used.
  3. Use kubectl get for concise resource lists and kubectl describe for detailed status, conditions and Events when triaging a workload.
  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

D:

The situation is that a small retailer scales its Deployment but reports success from spec alone while new Pods are still Pending. Change a workload's declared replicas and observe controllers update actual Pod count, understanding that status may lag behind spec during reconciliation. This resolves the issue because the API stores a desired spec while controllers asynchronously react to observations; status describes progress, not a guarantee of immediate convergence. To verify, set replicas from two to four, inspect generation and observed generation and watch readyReplicas converge.

Incorrect Answers

A:

This option addresses the distinct objective “Recognize the kubelet role in local Pod lifecycle management”, not the immediate requirement. Each kubelet watches assigned Pod specifications and coordinates the container runtime, volumes and health information on its node. For the stated case, the API stores a desired spec while controllers asynchronously react to observations; status describes progress, not a guarantee of immediate convergence.

B:

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, the API stores a desired spec while controllers asynchronously react to observations; status describes progress, not a guarantee of immediate convergence.

C:

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, the API stores a desired spec while controllers asynchronously react to observations; status describes progress, not a guarantee of immediate convergence.

Question 117

A small retailer scales its Deployment but reports success from spec alone while new Pods are still Pending. What infrastructure principle makes the correct treatment effective?

  1. Multistage builds reduce image contents and potential attack surface by keeping build toolchains and source artifacts out of the final runtime layer.
  2. Each kubelet watches assigned Pod specifications and coordinates the container runtime, volumes and health information on its node.
  3. RBAC evaluates API verbs, resources and scope; a Role is namespaced and does not grant cluster-wide access merely because the subject can authenticate.
  4. The API stores a desired spec while controllers asynchronously react to observations; status describes progress, not a guarantee of immediate convergence.

Explanation

Correct Answer

D:

The situation is that a small retailer scales its Deployment but reports success from spec alone while new Pods are still Pending. The API stores a desired spec while controllers asynchronously react to observations; status describes progress, not a guarantee of immediate convergence. It supports this action: Change a workload's declared replicas and observe controllers update actual Pod count, understanding that status may lag behind spec during reconciliation. To confirm, set replicas from two to four, inspect generation and observed generation and watch readyReplicas converge.

Incorrect Answers

A:

That statement explains the distinct objective “Build smaller images with multistage builds and remove unnecessary tooling” rather than the cause in this case. The deciding mechanism here is that the API stores a desired spec while controllers asynchronously react to observations; status describes progress, not a guarantee of immediate convergence.

B:

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 the API stores a desired spec while controllers asynchronously react to observations; status describes progress, not a guarantee of immediate convergence.

C:

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 the API stores a desired spec while controllers asynchronously react to observations; status describes progress, not a guarantee of immediate convergence.

Question 118

A small retailer scales its Deployment but reports success from spec alone while new Pods are still Pending. What verification result would most convincingly distinguish a working solution from a claim?

  1. With synthetic users verify a trusted API connection, denied privilege escalation and appropriate audit entries for failed requests.
  2. Delete one test Deployment-owned Pod and observe a replacement appear without a new Deployment definition.
  3. Set replicas from two to four, inspect generation and observed generation and watch readyReplicas converge.
  4. Inspect a new Pod's nodeName and Events, then compare scheduling events with kubelet-reported container status.

Explanation

Correct Answer

C:

The situation is that a small retailer scales its Deployment but reports success from spec alone while new Pods are still Pending. Set replicas from two to four, inspect generation and observed generation and watch readyReplicas converge. This is the relevant test because the API stores a desired spec while controllers asynchronously react to observations; status describes progress, not a guarantee of immediate convergence.

Incorrect Answers

A:

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, set replicas from two to four, inspect generation and observed generation and watch readyReplicas converge.

B:

This check would help evaluate the distinct objective “Identify reconciliation work performed by kube-controller-manager”, but not the required result. For this case, set replicas from two to four, inspect generation and observed generation and watch readyReplicas converge.

D:

The situation is that a small retailer scales its Deployment but reports success from spec alone while new Pods are still Pending. This check would help evaluate the distinct objective “Separate kube-scheduler decisions from kubelet execution”, but not the required result. For this case, set replicas from two to four, inspect generation and observed generation and watch readyReplicas converge.

Question 119

A small retailer scales its Deployment but reports success from spec alone while new Pods are still Pending. The change review contains this proposal: “Read an updated spec and immediately assume every requested replica is serving traffic despite pending pulls or readiness failures.” What risk matters most?

  1. A deployment is recorded as changed while the application is still below its service availability requirement.
  2. Credentials can leak through registries and the binaries cannot be compared as the same tested artifact.
  3. Compromised credentials can perform widespread cluster changes without attribution or least privilege.
  4. The image-pull issue stays unresolved because etcd is not the node component managing container starts.

Explanation

Correct Answer

A:

The situation is that a small retailer scales its Deployment but reports success from spec alone while new Pods are still Pending. A deployment is recorded as changed while the application is still below its service availability requirement. The shortcut creates this risk because the API stores a desired spec while controllers asynchronously react to observations; status describes progress, not a guarantee of immediate convergence.

Incorrect Answers

B:

That outcome concerns the distinct objective “Externalize application configuration from an image while protecting secrets”; it is not the most direct consequence of this shortcut. The relevant consequence is that a deployment is recorded as changed while the application is still below its service availability requirement.

C:

That outcome concerns the distinct objective “Use least-privilege kubectl authentication and authorization during routine administration”; it is not the most direct consequence of this shortcut. The relevant consequence is that a deployment is recorded as changed while the application is still below its service availability requirement.

D:

The situation is that a small retailer scales its Deployment but reports success from spec alone while new Pods are still Pending. That outcome concerns the distinct objective “Recognize the kubelet role in local Pod lifecycle management”; it is not the most direct consequence of this shortcut. The relevant consequence is that a deployment is recorded as changed while the application is still below its service availability requirement.

Question 120

A small retailer scales its Deployment but reports success from spec alone while new Pods are still Pending. Which implementation together with matching acceptance evidence best meets this case?

  1. Give each workload an appropriate Kubernetes ServiceAccount and narrow RBAC permissions rather than embedding an administrator kubeconfig in its image. Acceptance evidence: Run a synthetic read-only Pod with a restricted ServiceAccount and verify one permitted API read and one forbidden Secret list.
  2. Cordon a worker to prevent new scheduling and drain safely under PodDisruptionBudgets and DaemonSet rules before maintenance. Acceptance evidence: Observe a controlled drain with replica owners and a PDB, then verify workloads move and uncordon restores eligibility.
  3. 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.
  4. Change a workload's declared replicas and observe controllers update actual Pod count, understanding that status may lag behind spec during reconciliation. Acceptance evidence: Set replicas from two to four, inspect generation and observed generation and watch readyReplicas converge.

Explanation

Correct Answer

D:

The situation is that a small retailer scales its Deployment but reports success from spec alone while new Pods are still Pending. Change a workload's declared replicas and observe controllers update actual Pod count, understanding that status may lag behind spec during reconciliation. Acceptance evidence: Set replicas from two to four, inspect generation and observed generation and watch readyReplicas converge. This pairing is justified because the API stores a desired spec while controllers asynchronously react to observations; status describes progress, not a guarantee of immediate convergence.

Incorrect Answers

A:

This action and check address the distinct objective “Differentiate ServiceAccounts from human kubeconfig identities” instead of the stated acceptance requirement. The matching action is to change a workload's declared replicas and observe controllers update actual Pod count, understanding that status may lag behind spec during reconciliation. Its confirming test is to set replicas from two to four, inspect generation and observed generation and watch readyReplicas converge.

B:

This action and check address the distinct objective “Use cordon and drain with disruption considerations for planned node maintenance” instead of the stated acceptance requirement. The matching action is to change a workload's declared replicas and observe controllers update actual Pod count, understanding that status may lag behind spec during reconciliation. Its confirming test is to set replicas from two to four, inspect generation and observed generation and watch readyReplicas converge.

C:

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 change a workload's declared replicas and observe controllers update actual Pod count, understanding that status may lag behind spec during reconciliation. Its confirming test is to set replicas from two to four, inspect generation and observed generation and watch readyReplicas converge.

Kubernetes and Cloud Native Associate (KCNA) Practice Tests