Linux Foundation KCNA Dumps
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?
Explanation
Correct Answer
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
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.
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.
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?
Explanation
Correct Answer
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
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.
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.
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?
Explanation
Correct Answer
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
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.
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.
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?
Explanation
Correct Answer
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
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.
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.
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?
Explanation
Correct Answer
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
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.
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.
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?
Explanation
Correct Answer
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
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.
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.
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?
Explanation
Correct Answer
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
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.
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.
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?
Explanation
Correct Answer
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
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.
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.
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?
Explanation
Correct Answer
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
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.
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.
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?
Explanation
Correct Answer
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
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.
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.
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?
Explanation
Correct Answer
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
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.
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.
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
- Linux Foundation KCNA Practice Test 52 - 10 Questions (Last Reviewed 30-Sep-2026)
- Linux Foundation KCNA Practice Test 53 - 10 Questions (Last Reviewed 29-Sep-2026)
- Linux Foundation KCNA Practice Test 54 - 10 Questions (Last Reviewed 28-Sep-2026)
- Linux Foundation KCNA Practice Test 55 - 10 Questions (Last Reviewed 27-Sep-2026)
- Linux Foundation KCNA Practice Test 56 - 10 Questions (Last Reviewed 26-Sep-2026)