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 54

Question 530

A charity wants monitoring staff to read Deployment status but not view private Secret objects. What pair of supported action and practical verification should be approved?

  1. Create a Role with only required verbs and resource types, and bind it to the intended subject within the target namespace. Acceptance evidence: Use kubectl auth can-i --as a synthetic student to verify pod get allowed and secret delete denied in the specified namespace.
  2. Give each Pod an appropriate ServiceAccount, disable automountServiceAccountToken where API access is unnecessary and test token audience and role scope. Acceptance evidence: Run a test web Pod without a token mount and verify service operation succeeds while in-cluster API calls are unavailable.
  3. 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.
  4. Recognize Kubernetes for orchestration, Prometheus for metrics, Envoy for data-plane proxying and Fluentd for log collection in the cloud-native landscape. Acceptance evidence: Build a study architecture diagram that connects each tool to its documented function and verify the expected data flow in a sample environment.

Explanation

Correct Answer

A:

The situation is that a charity wants monitoring staff to read Deployment status but not view private Secret objects. Create a Role with only required verbs and resource types, and bind it to the intended subject within the target namespace. Acceptance evidence: Use kubectl auth can-i --as a synthetic student to verify pod get allowed and secret delete denied in the specified namespace. This pairing is justified because RBAC evaluates API verbs, resources and scope; a Role is namespaced and does not grant cluster-wide access merely because the subject can authenticate.

Incorrect Answers

B:

This action and check address the distinct objective “Enforce workload service account token boundaries and avoid needless mounts” instead of the stated acceptance requirement. The matching action is to create a Role with only required verbs and resource types, and bind it to the intended subject within the target namespace. Its confirming test is to use kubectl auth can-i --as a synthetic student to verify pod get allowed and secret delete denied in the specified namespace.

C:

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 create a Role with only required verbs and resource types, and bind it to the intended subject within the target namespace. Its confirming test is to use kubectl auth can-i --as a synthetic student to verify pod get allowed and secret delete denied in the specified namespace.

D:

This action and check address the distinct objective “Identify CNCF ecosystem projects by their role rather than assuming all are Kubernetes core” instead of the stated acceptance requirement. The matching action is to create a Role with only required verbs and resource types, and bind it to the intended subject within the target namespace. Its confirming test is to use kubectl auth can-i --as a synthetic student to verify pod get allowed and secret delete denied in the specified namespace.

Question 531

A hospital compliance group needs read permissions in one application namespace only. Which engineering approach is the most appropriate for this cloud-native case?

  1. Measure request latency and error rates, inspect application logs and correlate trace spans for the affected request before guessing which Pod is slow.
  2. Give each Pod an appropriate ServiceAccount, disable automountServiceAccountToken where API access is unnecessary and test token audience and role scope.
  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.
  4. Require verified API server certificates, properly scoped identities and audit policy rather than turning off certificate checks for convenience.

Explanation

Correct Answer

C:

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. This resolves the issue because clusterRole defines permissions while ClusterRoleBinding makes them cluster-wide; RoleBinding limits effective namespaced scope even when referencing a ClusterRole. To verify, bind a synthetic ClusterRole through RoleBinding in namespace-a, then verify access fails in namespace-b.

Incorrect Answers

A:

This option addresses the distinct objective “Use metrics, logs and traces together when investigating cross-service latency”, not the immediate requirement. Metrics reveal aggregate trends, logs record events and traces connect operations across services, so each signal answers a different debugging question. For the stated case, clusterRole defines permissions while ClusterRoleBinding makes them cluster-wide; RoleBinding limits effective namespaced scope even when referencing a ClusterRole.

B:

This option addresses the distinct objective “Enforce workload service account token boundaries and avoid needless mounts”, not the immediate requirement. Mounted credentials can enable Kubernetes API calls from a compromised container; explicit token exposure and RBAC scope limit abuse. For the stated case, clusterRole defines permissions while ClusterRoleBinding makes them cluster-wide; RoleBinding limits effective namespaced scope even when referencing a ClusterRole.

D:

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, clusterRole defines permissions while ClusterRoleBinding makes them cluster-wide; RoleBinding limits effective namespaced scope even when referencing a ClusterRole.

Question 532

A hospital compliance group needs read permissions in one application namespace only. What infrastructure principle makes the correct treatment effective?

  1. Kubelet cannot launch containers requiring unresolved or unmountable volumes, and Events often identify a storage provisioning or attachment failure.
  2. ClusterRole defines permissions while ClusterRoleBinding makes them cluster-wide; RoleBinding limits effective namespaced scope even when referencing a ClusterRole.
  3. Image provenance reduces accidental or malicious image substitution; mutable tags alone cannot prove build integrity or content identity.
  4. CNCF projects address different layers of a cloud-native platform and interoperability does not turn them into interchangeable cluster control-plane components.

Explanation

Correct Answer

B:

ClusterRole defines permissions while ClusterRoleBinding makes them cluster-wide; RoleBinding limits effective namespaced scope even when referencing a ClusterRole. It supports this action: 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. To confirm, bind a synthetic ClusterRole through RoleBinding in namespace-a, then verify access fails in namespace-b.

Incorrect Answers

A:

That statement explains the distinct objective “Use Events and pod describe for failed volume mounting” rather than the cause in this case. The deciding mechanism here is that clusterRole defines permissions while ClusterRoleBinding makes them cluster-wide; RoleBinding limits effective namespaced scope even when referencing a ClusterRole.

C:

That statement explains the distinct objective “Use image provenance and policy controls without trusting mutable tags” rather than the cause in this case. The deciding mechanism here is that clusterRole defines permissions while ClusterRoleBinding makes them cluster-wide; RoleBinding limits effective namespaced scope even when referencing a ClusterRole.

D:

That statement explains the distinct objective “Identify CNCF ecosystem projects by their role rather than assuming all are Kubernetes core” rather than the cause in this case. The deciding mechanism here is that clusterRole defines permissions while ClusterRoleBinding makes them cluster-wide; RoleBinding limits effective namespaced scope even when referencing a ClusterRole.

Question 533

A hospital compliance group needs read permissions in one application namespace only. What verification result would most convincingly distinguish a working solution from a claim?

  1. Attempt to create a privileged test Pod in a restricted namespace and inspect the admission rejection message.
  2. Test that one synthetic tenant cannot list another namespace's Secrets, send blocked traffic or exceed quota.
  3. Bind a synthetic ClusterRole through RoleBinding in namespace-a, then verify access fails in namespace-b.
  4. Build a test image, run a Pod and recreate it, verifying packaged files remain while an unmounted temporary file disappears.

Explanation

Correct Answer

C:

Bind a synthetic ClusterRole through RoleBinding in namespace-a, then verify access fails in namespace-b. This is the relevant test because clusterRole defines permissions while ClusterRoleBinding makes them cluster-wide; RoleBinding limits effective namespaced scope even when referencing a ClusterRole.

Incorrect Answers

A:

This check would help evaluate the distinct objective “Use Pod Security Standards to deny overly privileged Pod configurations”, but not the required result. For this case, bind a synthetic ClusterRole through RoleBinding in namespace-a, then verify access fails in namespace-b.

B:

This check would help evaluate the distinct objective “Separate multi-tenant namespace governance from actual isolation guarantees”, but not the required result. For this case, bind a synthetic ClusterRole through RoleBinding in namespace-a, then verify access fails in namespace-b.

D:

This check would help evaluate the distinct objective “Distinguish a container image from a running container and its writable layer”, but not the required result. For this case, bind a synthetic ClusterRole through RoleBinding in namespace-a, then verify access fails in namespace-b.

Question 534

A hospital compliance group needs read permissions in one application namespace only. The change review contains this proposal: “Use ClusterRoleBinding for a team that should inspect Pods in one namespace and assume the binding does not broaden access.” What risk matters most?

  1. The actual capacity or node selection problem remains because no node was assigned.
  2. An untrusted dependency or replaced tag can run within otherwise well-configured Pods.
  3. The team may gain Pod access across all namespaces, expanding exposure beyond its job.
  4. The production binary can differ from the validated image even though the release version label matches.

Explanation

Correct Answer

C:

The team may gain Pod access across all namespaces, expanding exposure beyond its job. The shortcut creates this risk because clusterRole defines permissions while ClusterRoleBinding makes them cluster-wide; RoleBinding limits effective namespaced scope even when referencing a ClusterRole.

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 the team may gain Pod access across all namespaces, expanding exposure beyond its job.

B:

That outcome concerns the distinct objective “Use image provenance and policy controls without trusting mutable tags”; it is not the most direct consequence of this shortcut. The relevant consequence is that the team may gain Pod access across all namespaces, expanding exposure beyond its job.

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 the team may gain Pod access across all namespaces, expanding exposure beyond its job.

Question 535

A hospital compliance group needs read permissions in one application namespace only. Which implementation together with matching acceptance evidence best meets this case?

  1. Label eligible nodes for a test hardware property and use nodeSelector when a Pod must run only on matching nodes. Acceptance evidence: Label one worker disk=ssd, apply a Pod requiring disk=ssd and confirm it binds only to the matching eligible worker.
  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. 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 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.

Explanation

Correct Answer

D:

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. This pairing is justified because clusterRole defines permissions while ClusterRoleBinding makes them cluster-wide; RoleBinding limits effective namespaced scope even when referencing a ClusterRole.

Incorrect Answers

A:

This action and check address the distinct objective “Use nodeSelector to place a workload on nodes with required labels” instead of the stated acceptance requirement. The matching action is to 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. Its confirming test is to bind a synthetic ClusterRole through RoleBinding in namespace-a, then verify access fails in namespace-b.

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 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. Its confirming test is to bind a synthetic ClusterRole through RoleBinding in namespace-a, then verify access fails in namespace-b.

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 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. Its confirming test is to bind a synthetic ClusterRole through RoleBinding in namespace-a, then verify access fails in namespace-b.

Question 536

A training administrator wants to reuse a ClusterRole rule set without granting it across the cluster. What technical action should the platform team take in this situation?

  1. Select an access mode supported by the actual storage driver and workload placement requirements rather than assuming every volume supports concurrent writes from every node.
  2. Apply PriorityClasses sparingly for essential workloads and plan capacity so preemption does not unnecessarily evict useful lower-priority Pods.
  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.
  4. Require verified API server certificates, properly scoped identities and audit policy rather than turning off certificate checks for convenience.

Explanation

Correct Answer

C:

The situation is that a training administrator wants to reuse a ClusterRole rule set without granting it across the cluster. 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. This resolves the issue because clusterRole defines permissions while ClusterRoleBinding makes them cluster-wide; RoleBinding limits effective namespaced scope even when referencing a ClusterRole. To verify, bind a synthetic ClusterRole through RoleBinding in namespace-a, then verify access fails in namespace-b.

Incorrect Answers

A:

This option addresses the distinct objective “Choose ReadWriteOnce and ReadWriteMany access modes by backend capability”, not the immediate requirement. PV access modes express volume mount constraints and driver support; ReadWriteOnce normally restricts writable use to one node, while ReadWriteMany requires a capable backend. For the stated case, clusterRole defines permissions while ClusterRoleBinding makes them cluster-wide; RoleBinding limits effective namespaced scope even when referencing a ClusterRole.

B:

This option addresses the distinct objective “Use PriorityClasses and understand preemption without assuming they guarantee availability”, not the immediate requirement. Under pressure, a higher-priority pending Pod may preempt eligible lower-priority Pods, but constraints and eviction rules still apply. For the stated case, clusterRole defines permissions while ClusterRoleBinding makes them cluster-wide; RoleBinding limits effective namespaced scope even when referencing a ClusterRole.

D:

The situation is that a training administrator wants to reuse a ClusterRole rule set without granting it across the cluster. 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, clusterRole defines permissions while ClusterRoleBinding makes them cluster-wide; RoleBinding limits effective namespaced scope even when referencing a ClusterRole.

Question 537

A training administrator wants to reuse a ClusterRole rule set without granting it across the cluster. What underlying Kubernetes behavior is most relevant to this technical decision?

  1. Namespaces alone partition naming but do not provide complete security isolation, capacity governance or protection from privileged node-level workloads.
  2. CrashLoopBackOff reflects kubelet restart backoff after container failures; the underlying cause may be application configuration, exit code or a failed liveness probe.
  3. ClusterRole defines permissions while ClusterRoleBinding makes them cluster-wide; RoleBinding limits effective namespaced scope even when referencing a ClusterRole.
  4. SecurityContext configures process identity and privilege boundaries, and unnecessary root privileges increase impact if an application is compromised.

Explanation

Correct Answer

C:

The situation is that a training administrator wants to reuse a ClusterRole rule set without granting it across the cluster. ClusterRole defines permissions while ClusterRoleBinding makes them cluster-wide; RoleBinding limits effective namespaced scope even when referencing a ClusterRole. It supports this action: 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. To confirm, bind a synthetic ClusterRole through RoleBinding in namespace-a, then verify access fails in namespace-b.

Incorrect Answers

A:

That statement explains the distinct objective “Separate multi-tenant namespace governance from actual isolation guarantees” rather than the cause in this case. The deciding mechanism here is that clusterRole defines permissions while ClusterRoleBinding makes them cluster-wide; RoleBinding limits effective namespaced scope even when referencing a ClusterRole.

B:

That statement explains the distinct objective “Diagnose CrashLoopBackOff from restart history and previous logs” rather than the cause in this case. The deciding mechanism here is that clusterRole defines permissions while ClusterRoleBinding makes them cluster-wide; RoleBinding limits effective namespaced scope even when referencing a ClusterRole.

D:

That statement explains the distinct objective “Run images with least-privilege runtime security contexts” rather than the cause in this case. The deciding mechanism here is that clusterRole defines permissions while ClusterRoleBinding makes them cluster-wide; RoleBinding limits effective namespaced scope even when referencing a ClusterRole.

Question 538

A training administrator wants to reuse a ClusterRole rule set without granting it across the cluster. What acceptance check most directly confirms this requirement is met?

  1. Bind a synthetic ClusterRole through RoleBinding in namespace-a, then verify access fails in namespace-b.
  2. Test synthetic frontend-to-backend reachability and deny a third unauthorized namespace while verifying DNS access is still deliberately allowed.
  3. Run a test web Pod without a token mount and verify service operation succeeds while in-cluster API calls are unavailable.
  4. Inspect the cluster backup policy for etcd snapshots and separately restore synthetic application data from its own backup.

Explanation

Correct Answer

A:

The situation is that a training administrator wants to reuse a ClusterRole rule set without granting it across the cluster. Bind a synthetic ClusterRole through RoleBinding in namespace-a, then verify access fails in namespace-b. This is the relevant test because clusterRole defines permissions while ClusterRoleBinding makes them cluster-wide; RoleBinding limits effective namespaced scope even when referencing a ClusterRole.

Incorrect Answers

B:

This check would help evaluate the distinct objective “Limit workload-to-workload access with explicit NetworkPolicy allow rules”, but not the required result. For this case, bind a synthetic ClusterRole through RoleBinding in namespace-a, then verify access fails in namespace-b.

C:

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, bind a synthetic ClusterRole through RoleBinding in namespace-a, then verify access fails in namespace-b.

D:

This check would help evaluate the distinct objective “Distinguish etcd persistence from running workload data”, but not the required result. For this case, bind a synthetic ClusterRole through RoleBinding in namespace-a, then verify access fails in namespace-b.

Question 539

A training administrator wants to reuse a ClusterRole rule set without granting it across the cluster. The team suggests: “Use ClusterRoleBinding for a team that should inspect Pods in one namespace and assume the binding does not broaden access.” Which failure should the reviewer anticipate?

  1. The team may gain Pod access across all namespaces, expanding exposure beyond its job.
  2. The route remains nonfunctional because nothing reconciles it into an application traffic proxy.
  3. A compromised unrelated Pod may reach protected application ports across trust boundaries.
  4. Independent rollout, scaling and failure isolation become difficult because the services are coupled to one scheduling unit.

Explanation

Correct Answer

A:

The situation is that a training administrator wants to reuse a ClusterRole rule set without granting it across the cluster. The team may gain Pod access across all namespaces, expanding exposure beyond its job. The shortcut creates this risk because clusterRole defines permissions while ClusterRoleBinding makes them cluster-wide; RoleBinding limits effective namespaced scope even when referencing a ClusterRole.

Incorrect Answers

B:

That outcome concerns the distinct objective “Choose Ingress or Gateway API with an implementing controller for HTTP exposure”; it is not the most direct consequence of this shortcut. The relevant consequence is that the team may gain Pod access across all namespaces, expanding exposure beyond its job.

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 the team may gain Pod access across all namespaces, expanding exposure beyond its job.

D:

That outcome concerns the distinct objective “Use Pods as the shared network and storage execution unit”; it is not the most direct consequence of this shortcut. The relevant consequence is that the team may gain Pod access across all namespaces, expanding exposure beyond its job.

Question 540

A training administrator wants to reuse a ClusterRole rule set without granting it across the cluster. Which engineering change and test jointly addresses the scenario?

  1. Apply suitable Pod Security Admission labels such as baseline or restricted and test whether noncompliant synthetic Pod specs are rejected. Acceptance evidence: Attempt to create a privileged test Pod in a restricted namespace and inspect the admission rejection message.
  2. Define meaningful topology keys, matching label selectors and skew limits when balancing eligible replicas across nodes or zones. Acceptance evidence: Deploy a matching replica set across two labeled zones and inspect skew after adding a new Pod.
  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. Create a Role with only required verbs and resource types, and bind it to the intended subject within the target namespace. Acceptance evidence: Use kubectl auth can-i --as a synthetic student to verify pod get allowed and secret delete denied in the specified namespace.

Explanation

Correct Answer

C:

The situation is that a training administrator wants to reuse a ClusterRole rule set without granting it across the cluster. 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. This pairing is justified because clusterRole defines permissions while ClusterRoleBinding makes them cluster-wide; RoleBinding limits effective namespaced scope even when referencing a ClusterRole.

Incorrect Answers

A:

This action and check address the distinct objective “Use Pod Security Standards to deny overly privileged Pod configurations” instead of the stated acceptance requirement. The matching action is to 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. Its confirming test is to bind a synthetic ClusterRole through RoleBinding in namespace-a, then verify access fails in namespace-b.

B:

This action and check address the distinct objective “Spread replicas across failure domains with topologySpreadConstraints” instead of the stated acceptance requirement. The matching action is to 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. Its confirming test is to bind a synthetic ClusterRole through RoleBinding in namespace-a, then verify access fails in namespace-b.

D:

This action and check address the distinct objective “Implement namespaced RBAC Roles for least-privilege resource permissions” instead of the stated acceptance requirement. The matching action is to 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. Its confirming test is to bind a synthetic ClusterRole through RoleBinding in namespace-a, then verify access fails in namespace-b.

Kubernetes and Cloud Native Associate (KCNA) Practice Tests