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 55

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.

Question 541

A nonprofit wants to reject new privileged containers in a multi-tenant teaching cluster. What technical action should the platform team take in this situation?

  1. Review Retain versus Delete behavior for data-bearing PVs and test cleanup policy using synthetic non-sensitive data.
  2. Review requests, limits, QoS class and termination reasons rather than interpreting every restart as a scheduler failure.
  3. Create a Role with only required verbs and resource types, and bind it to the intended subject within the target namespace.
  4. Apply suitable Pod Security Admission labels such as baseline or restricted and test whether noncompliant synthetic Pod specs are rejected.

Explanation

Correct Answer

D:

Apply suitable Pod Security Admission labels such as baseline or restricted and test whether noncompliant synthetic Pod specs are rejected. This resolves the issue because pod Security Standards establish common workload hardening profiles, and admission checks can enforce restricted capabilities and privilege use at API creation. To verify, attempt to create a privileged test Pod in a restricted namespace and inspect the admission rejection message.

Incorrect Answers

A:

This option addresses the distinct objective “Compare PV reclaim policies and explain data retention on PVC deletion”, not the immediate requirement. A PV reclaim policy controls how underlying storage is treated after claim release; deleting the Pod and deleting the PVC are distinct events with different effects. For the stated case, pod Security Standards establish common workload hardening profiles, and admission checks can enforce restricted capabilities and privilege use at API creation.

B:

This option addresses the distinct objective “Distinguish memory limits from CPU throttling for scheduling and runtime symptoms”, not the immediate requirement. CPU limits may throttle running processes, whereas exceeding memory constraints can cause OOM termination; Pod scheduling itself depends on requests. For the stated case, pod Security Standards establish common workload hardening profiles, and admission checks can enforce restricted capabilities and privilege use at API creation.

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, pod Security Standards establish common workload hardening profiles, and admission checks can enforce restricted capabilities and privilege use at API creation.

Question 542

A nonprofit wants to reject new privileged containers in a multi-tenant teaching cluster. What underlying Kubernetes behavior is most relevant to this technical decision?

  1. A PVC requests storage and binds to a compatible PV; the Pod references the namespaced claim rather than assuming a fixed node directory.
  2. Different Kubernetes components emit distinct Events; identifying the stage prevents changing unrelated network or application settings.
  3. Pod Security Standards establish common workload hardening profiles, and admission checks can enforce restricted capabilities and privilege use at API creation.
  4. NetworkPolicies select Pods and define allowed flows; when a Pod becomes isolated, traffic is allowed only as permitted by applicable rules and plugin behavior.

Explanation

Correct Answer

C:

Pod Security Standards establish common workload hardening profiles, and admission checks can enforce restricted capabilities and privilege use at API creation. It supports this action: Apply suitable Pod Security Admission labels such as baseline or restricted and test whether noncompliant synthetic Pod specs are rejected. To confirm, attempt to create a privileged test Pod in a restricted namespace and inspect the admission rejection message.

Incorrect Answers

A:

That statement explains the distinct objective “Understand PersistentVolumeClaim binding to persistent storage resources” rather than the cause in this case. The deciding mechanism here is that pod Security Standards establish common workload hardening profiles, and admission checks can enforce restricted capabilities and privilege use at API creation.

B:

That statement explains the distinct objective “Use describe and Events to distinguish admission, scheduling and execution errors” rather than the cause in this case. The deciding mechanism here is that pod Security Standards establish common workload hardening profiles, and admission checks can enforce restricted capabilities and privilege use at API creation.

D:

That statement explains the distinct objective “Limit workload-to-workload access with explicit NetworkPolicy allow rules” rather than the cause in this case. The deciding mechanism here is that pod Security Standards establish common workload hardening profiles, and admission checks can enforce restricted capabilities and privilege use at API creation.

Question 543

A nonprofit wants to reject new privileged containers in a multi-tenant teaching cluster. What acceptance check most directly confirms this requirement is met?

  1. Test that one synthetic tenant cannot list another namespace's Secrets, send blocked traffic or exceed quota.
  2. Attempt to create a privileged test Pod in a restricted namespace and inspect the admission rejection message.
  3. With synthetic users verify a trusted API connection, denied privilege escalation and appropriate audit entries for failed requests.
  4. Calculate a synthetic seven-day success ratio from request metrics and compare it to the agreed target before a risky rollout.

Explanation

Correct Answer

B:

Attempt to create a privileged test Pod in a restricted namespace and inspect the admission rejection message. This is the relevant test because pod Security Standards establish common workload hardening profiles, and admission checks can enforce restricted capabilities and privilege use at API creation.

Incorrect Answers

A:

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, attempt to create a privileged test Pod in a restricted namespace and inspect the admission rejection message.

C:

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, attempt to create a privileged test Pod in a restricted namespace and inspect the admission rejection message.

D:

This check would help evaluate the distinct objective “Use SLI and SLO measures to focus reliability objectives”, but not the required result. For this case, attempt to create a privileged test Pod in a restricted namespace and inspect the admission rejection message.

Question 544

A nonprofit wants to reject new privileged containers in a multi-tenant teaching cluster. The team suggests: “Assume setting a restricted namespace label automatically rotates all existing workload credentials and network rules.” Which failure should the reviewer anticipate?

  1. A compromised unrelated Pod may reach protected application ports across trust boundaries.
  2. Dangerous existing configuration may persist because admission is not a universal replacement for every security control.
  3. The Service still has no ready endpoints and clients continue to encounter unavailable responses.
  4. Operators can see the metadata but the Service cannot select the desired Pods using that annotation.

Explanation

Correct Answer

B:

Dangerous existing configuration may persist because admission is not a universal replacement for every security control. The shortcut creates this risk because pod Security Standards establish common workload hardening profiles, and admission checks can enforce restricted capabilities and privilege use at API creation.

Incorrect Answers

A:

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 dangerous existing configuration may persist because admission is not a universal replacement for every security control.

C:

That outcome concerns the distinct objective “Investigate readiness failures separately from liveness-related restarts”; it is not the most direct consequence of this shortcut. The relevant consequence is that dangerous existing configuration may persist because admission is not a universal replacement for every security control.

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 dangerous existing configuration may persist because admission is not a universal replacement for every security control.

Question 545

A nonprofit wants to reject new privileged containers in a multi-tenant teaching cluster. Which engineering change and test jointly addresses the scenario?

  1. Give clients a Service DNS name rather than hardcoding Pod IP addresses that can change when replicas are replaced. Acceptance evidence: Delete and replace a Deployment Pod and verify a client continues to reach its Service DNS name despite changed backend Pod addresses.
  2. Set realistic CPU and memory requests for Pods and investigate FailedScheduling when no node has sufficient allocatable resources. Acceptance evidence: Set an intentionally excessive memory request in a lab and inspect Pod Pending Events before adjusting it.
  3. 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.
  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:

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. This pairing is justified because pod Security Standards establish common workload hardening profiles, and admission checks can enforce restricted capabilities and privilege use at API creation.

Incorrect Answers

A:

This action and check address the distinct objective “Distinguish Pod IPs from stable Services during rescheduling” instead of the stated acceptance requirement. The matching action is to apply suitable Pod Security Admission labels such as baseline or restricted and test whether noncompliant synthetic Pod specs are rejected. Its confirming test is to attempt to create a privileged test Pod in a restricted namespace and inspect the admission rejection message.

B:

This action and check address the distinct objective “Use container resource requests to help the scheduler fit Pods on nodes” instead of the stated acceptance requirement. The matching action is to apply suitable Pod Security Admission labels such as baseline or restricted and test whether noncompliant synthetic Pod specs are rejected. Its confirming test is to attempt to create a privileged test Pod in a restricted namespace and inspect the admission rejection message.

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 apply suitable Pod Security Admission labels such as baseline or restricted and test whether noncompliant synthetic Pod specs are rejected. Its confirming test is to attempt to create a privileged test Pod in a restricted namespace and inspect the admission rejection message.

Question 546

A medical organization adopts the restricted Pod Security Standard before onboarding third-party workloads. Which Kubernetes or cloud-native implementation decision best solves the stated problem?

  1. Apply suitable Pod Security Admission labels such as baseline or restricted and test whether noncompliant synthetic Pod specs are rejected.
  2. Combine a default-deny baseline with narrow app-label and namespace-label NetworkPolicy rules for approved traffic.
  3. Observe rollout progression and use a reviewed rollback to a previous ReplicaSet revision when a new application build fails health checks.
  4. Choose an available StorageClass with a compatible CSI provisioner and appropriate binding behavior when creating a PVC.

Explanation

Correct Answer

A:

The situation is that a medical organization adopts the restricted Pod Security Standard before onboarding third-party workloads. Apply suitable Pod Security Admission labels such as baseline or restricted and test whether noncompliant synthetic Pod specs are rejected. This resolves the issue because pod Security Standards establish common workload hardening profiles, and admission checks can enforce restricted capabilities and privilege use at API creation. To verify, attempt to create a privileged test Pod in a restricted namespace and inspect the admission rejection message.

Incorrect Answers

B:

This option addresses the distinct objective “Limit workload-to-workload access with explicit NetworkPolicy allow rules”, not the immediate requirement. NetworkPolicies select Pods and define allowed flows; when a Pod becomes isolated, traffic is allowed only as permitted by applicable rules and plugin behavior. For the stated case, pod Security Standards establish common workload hardening profiles, and admission checks can enforce restricted capabilities and privilege use at API creation.

C:

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, pod Security Standards establish common workload hardening profiles, and admission checks can enforce restricted capabilities and privilege use at API creation.

D:

This option addresses the distinct objective “Use StorageClass for dynamic volume provisioning rather than handcrafting every disk”, not the immediate requirement. A StorageClass defines how storage is provisioned and may use WaitForFirstConsumer to delay provisioning until scheduling requirements are known. For the stated case, pod Security Standards establish common workload hardening profiles, and admission checks can enforce restricted capabilities and privilege use at API creation.

Question 547

A medical organization adopts the restricted Pod Security Standard before onboarding third-party workloads. Which platform mechanism explains why the suitable approach works?

  1. A rolling Deployment temporarily creates and removes Pods within its surge and unavailable budgets, but readiness is required for new replicas to count as available.
  2. Mounted credentials can enable Kubernetes API calls from a compromised container; explicit token exposure and RBAC scope limit abuse.
  3. 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.
  4. Pod Security Standards establish common workload hardening profiles, and admission checks can enforce restricted capabilities and privilege use at API creation.

Explanation

Correct Answer

D:

The situation is that a medical organization adopts the restricted Pod Security Standard before onboarding third-party workloads. Pod Security Standards establish common workload hardening profiles, and admission checks can enforce restricted capabilities and privilege use at API creation. It supports this action: Apply suitable Pod Security Admission labels such as baseline or restricted and test whether noncompliant synthetic Pod specs are rejected. To confirm, attempt to create a privileged test Pod in a restricted namespace and inspect the admission rejection message.

Incorrect Answers

A:

That statement explains the distinct objective “Configure Deployment rolling updates with availability safeguards” rather than the cause in this case. The deciding mechanism here is that pod Security Standards establish common workload hardening profiles, and admission checks can enforce restricted capabilities and privilege use at API creation.

B:

That statement explains the distinct objective “Enforce workload service account token boundaries and avoid needless mounts” rather than the cause in this case. The deciding mechanism here is that pod Security Standards establish common workload hardening profiles, and admission checks can enforce restricted capabilities and privilege use at API creation.

C:

That statement explains the distinct objective “Understand ports, targetPort and protocol mapping in a Service” rather than the cause in this case. The deciding mechanism here is that pod Security Standards establish common workload hardening profiles, and admission checks can enforce restricted capabilities and privilege use at API creation.

Question 548

A medical organization adopts the restricted Pod Security Standard before onboarding third-party workloads. Which controlled observation would best validate the intended improvement?

  1. Use a synthetic two-node workload and compare expected attach behavior for an RWO volume with a documented RWX shared filesystem.
  2. Run kubectl kustomize for development and production overlays and compare the resulting YAML objects before application.
  3. Attempt to create a privileged test Pod in a restricted namespace and inspect the admission rejection message.
  4. With synthetic users verify a trusted API connection, denied privilege escalation and appropriate audit entries for failed requests.

Explanation

Correct Answer

C:

The situation is that a medical organization adopts the restricted Pod Security Standard before onboarding third-party workloads. Attempt to create a privileged test Pod in a restricted namespace and inspect the admission rejection message. This is the relevant test because pod Security Standards establish common workload hardening profiles, and admission checks can enforce restricted capabilities and privilege use at API creation.

Incorrect Answers

A:

This check would help evaluate the distinct objective “Choose ReadWriteOnce and ReadWriteMany access modes by backend capability”, but not the required result. For this case, attempt to create a privileged test Pod in a restricted namespace and inspect the admission rejection message.

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, attempt to create a privileged test Pod in a restricted namespace and inspect the admission rejection message.

D:

The situation is that a medical organization adopts the restricted Pod Security Standard before onboarding third-party workloads. 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, attempt to create a privileged test Pod in a restricted namespace and inspect the admission rejection message.

Question 549

A medical organization adopts the restricted Pod Security Standard before onboarding third-party workloads. An engineer proposes: “Assume setting a restricted namespace label automatically rotates all existing workload credentials and network rules.” What adverse outcome would be most direct?

  1. Dangerous existing configuration may persist because admission is not a universal replacement for every security control.
  2. An untrusted dependency or replaced tag can run within otherwise well-configured Pods.
  3. Sensitive traffic may remain allowed because the networking implementation does not enforce the declared policy.
  4. Network calls and coordination complexity grow without a business reason, creating new failure modes.

Explanation

Correct Answer

A:

The situation is that a medical organization adopts the restricted Pod Security Standard before onboarding third-party workloads. Dangerous existing configuration may persist because admission is not a universal replacement for every security control. The shortcut creates this risk because pod Security Standards establish common workload hardening profiles, and admission checks can enforce restricted capabilities and privilege use at API creation.

Incorrect Answers

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 dangerous existing configuration may persist because admission is not a universal replacement for every security control.

C:

That outcome concerns the distinct objective “Recognize NetworkPolicy isolation only when the CNI enforces it”; it is not the most direct consequence of this shortcut. The relevant consequence is that dangerous existing configuration may persist because admission is not a universal replacement for every security control.

D:

That outcome concerns the distinct objective “Contrast cloud-native microservices with a monolith without treating either as inherently superior”; it is not the most direct consequence of this shortcut. The relevant consequence is that dangerous existing configuration may persist because admission is not a universal replacement for every security control.

Question 550

A medical organization adopts the restricted Pod Security Standard before onboarding third-party workloads. What pair of supported action and practical verification should be approved?

  1. Pin validated production images by registry digest and promote the same signed artifact across environments. Acceptance evidence: Resolve an approved image digest, deploy that reference in staging and verify the same digest exists in the production Pod spec.
  2. Combine RBAC, Pod security policies, NetworkPolicy and resource quotas for teams that share a Kubernetes control plane. Acceptance evidence: Test that one synthetic tenant cannot list another namespace's Secrets, send blocked traffic or exceed quota.
  3. Match a Service's exposed port and targetPort to the actual listening application container, checking protocol and named ports when used. Acceptance evidence: Inspect the container listener, Service port fields and a test Pod connection before changing unrelated firewall settings.
  4. 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.

Explanation

Correct Answer

D:

The situation is that a medical organization adopts the restricted Pod Security Standard before onboarding third-party workloads. 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. This pairing is justified because pod Security Standards establish common workload hardening profiles, and admission checks can enforce restricted capabilities and privilege use at API creation.

Incorrect Answers

A:

This action and check address the distinct objective “Use an immutable image digest for exact deployment provenance” instead of the stated acceptance requirement. The matching action is to apply suitable Pod Security Admission labels such as baseline or restricted and test whether noncompliant synthetic Pod specs are rejected. Its confirming test is to attempt to create a privileged test Pod in a restricted namespace and inspect the admission rejection message.

B:

This action and check address the distinct objective “Separate multi-tenant namespace governance from actual isolation guarantees” instead of the stated acceptance requirement. The matching action is to apply suitable Pod Security Admission labels such as baseline or restricted and test whether noncompliant synthetic Pod specs are rejected. Its confirming test is to attempt to create a privileged test Pod in a restricted namespace and inspect the admission rejection message.

C:

This action and check address the distinct objective “Understand ports, targetPort and protocol mapping in a Service” instead of the stated acceptance requirement. The matching action is to apply suitable Pod Security Admission labels such as baseline or restricted and test whether noncompliant synthetic Pod specs are rejected. Its confirming test is to attempt to create a privileged test Pod in a restricted namespace and inspect the admission rejection message.

Kubernetes and Cloud Native Associate (KCNA) Practice Tests