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 56

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.

Question 551

A cooperative's payment processor should accept requests only from an authenticated internal gateway tier. 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. Cordon a worker to prevent new scheduling and drain safely under PodDisruptionBudgets and DaemonSet rules before maintenance.
  3. Verify that the installed Container Storage Interface driver supports the requested persistent storage and inspect driver controller/node components when mounting fails.
  4. Combine a default-deny baseline with narrow app-label and namespace-label NetworkPolicy rules for approved traffic.

Explanation

Correct Answer

D:

Combine a default-deny baseline with narrow app-label and namespace-label NetworkPolicy rules for approved traffic. This resolves the issue because networkPolicies select Pods and define allowed flows; when a Pod becomes isolated, traffic is allowed only as permitted by applicable rules and plugin behavior. To verify, test synthetic frontend-to-backend reachability and deny a third unauthorized namespace while verifying DNS access is still deliberately allowed.

Incorrect Answers

A:

This option addresses the distinct objective “Use Pod Security Standards to deny overly privileged Pod configurations”, not the immediate requirement. Pod Security Standards establish common workload hardening profiles, and admission checks can enforce restricted capabilities and privilege use at API creation. For the stated case, networkPolicies select Pods and define allowed flows; when a Pod becomes isolated, traffic is allowed only as permitted by applicable rules and plugin behavior.

B:

This option addresses the distinct objective “Use cordon and drain with disruption considerations for planned node maintenance”, not the immediate requirement. Cordon marks a node unschedulable for new ordinary Pods; drain evicts managed workloads when policies and availability permit. For the stated case, networkPolicies select Pods and define allowed flows; when a Pod becomes isolated, traffic is allowed only as permitted by applicable rules and plugin behavior.

C:

This option addresses the distinct objective “Understand CSI drivers and volume attachment responsibilities”, not the immediate requirement. CSI separates storage vendor implementation from Kubernetes core and manages provisioning, attachment and node mounting through driver-defined capabilities. For the stated case, networkPolicies select Pods and define allowed flows; when a Pod becomes isolated, traffic is allowed only as permitted by applicable rules and plugin behavior.

Question 552

A cooperative's payment processor should accept requests only from an authenticated internal gateway tier. Which platform mechanism explains why the suitable approach works?

  1. Image provenance reduces accidental or malicious image substitution; mutable tags alone cannot prove build integrity or content identity.
  2. Cordon marks a node unschedulable for new ordinary Pods; drain evicts managed workloads when policies and availability permit.
  3. NetworkPolicies select Pods and define allowed flows; when a Pod becomes isolated, traffic is allowed only as permitted by applicable rules and plugin behavior.
  4. A StorageClass defines how storage is provisioned and may use WaitForFirstConsumer to delay provisioning until scheduling requirements are known.

Explanation

Correct Answer

C:

NetworkPolicies select Pods and define allowed flows; when a Pod becomes isolated, traffic is allowed only as permitted by applicable rules and plugin behavior. It supports this action: Combine a default-deny baseline with narrow app-label and namespace-label NetworkPolicy rules for approved traffic. To confirm, test synthetic frontend-to-backend reachability and deny a third unauthorized namespace while verifying DNS access is still deliberately allowed.

Incorrect Answers

A:

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 networkPolicies select Pods and define allowed flows; when a Pod becomes isolated, traffic is allowed only as permitted by applicable rules and plugin behavior.

B:

That statement explains the distinct objective “Use cordon and drain with disruption considerations for planned node maintenance” rather than the cause in this case. The deciding mechanism here is that networkPolicies select Pods and define allowed flows; when a Pod becomes isolated, traffic is allowed only as permitted by applicable rules and plugin behavior.

D:

That statement explains the distinct objective “Use StorageClass for dynamic volume provisioning rather than handcrafting every disk” rather than the cause in this case. The deciding mechanism here is that networkPolicies select Pods and define allowed flows; when a Pod becomes isolated, traffic is allowed only as permitted by applicable rules and plugin behavior.

Question 553

A cooperative's payment processor should accept requests only from an authenticated internal gateway tier. Which controlled observation would best validate the intended improvement?

  1. Test that one synthetic tenant cannot list another namespace's Secrets, send blocked traffic or exceed quota.
  2. Reproduce a missing PVC in a test namespace and confirm the Pod Events directly indicate the unavailable claim.
  3. Create matching Service names in two namespaces and test separately configured RBAC and NetworkPolicy access boundaries.
  4. Test synthetic frontend-to-backend reachability and deny a third unauthorized namespace while verifying DNS access is still deliberately allowed.

Explanation

Correct Answer

D:

Test synthetic frontend-to-backend reachability and deny a third unauthorized namespace while verifying DNS access is still deliberately allowed. This is the relevant test because networkPolicies select Pods and define allowed flows; when a Pod becomes isolated, traffic is allowed only as permitted by applicable rules and plugin behavior.

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, test synthetic frontend-to-backend reachability and deny a third unauthorized namespace while verifying DNS access is still deliberately allowed.

B:

This check would help evaluate the distinct objective “Use Events and pod describe for failed volume mounting”, but not the required result. For this case, test synthetic frontend-to-backend reachability and deny a third unauthorized namespace while verifying DNS access is still deliberately allowed.

C:

This check would help evaluate the distinct objective “Use namespaces as organizational scopes without treating them as firewalls”, but not the required result. For this case, test synthetic frontend-to-backend reachability and deny a third unauthorized namespace while verifying DNS access is still deliberately allowed.

Question 554

A cooperative's payment processor should accept requests only from an authenticated internal gateway tier. An engineer proposes: “Allow all ingress traffic to make one API work, discarding the existing namespace segmentation policy.” What adverse outcome would be most direct?

  1. One application vulnerability can expose a credential allowing changes unrelated to its actual business function.
  2. A compromised unrelated Pod may reach protected application ports across trust boundaries.
  3. A working dataplane may be needlessly modified, disrupting traffic that was already being forwarded correctly.
  4. The team may gain Pod access across all namespaces, expanding exposure beyond its job.

Explanation

Correct Answer

B:

A compromised unrelated Pod may reach protected application ports across trust boundaries. The shortcut creates this risk because networkPolicies select Pods and define allowed flows; when a Pod becomes isolated, traffic is allowed only as permitted by applicable rules and plugin behavior.

Incorrect Answers

A:

That outcome concerns the distinct objective “Enforce workload service account token boundaries and avoid needless mounts”; it is not the most direct consequence of this shortcut. The relevant consequence is that a compromised unrelated Pod may reach protected application ports across trust boundaries.

C:

That outcome concerns the distinct objective “Understand service proxy implementations without assuming kube-proxy is mandatory”; it is not the most direct consequence of this shortcut. The relevant consequence is that a compromised unrelated Pod may reach protected application ports across trust boundaries.

D:

That outcome concerns the distinct objective “Distinguish ClusterRoles from Roles and binding scope”; it is not the most direct consequence of this shortcut. The relevant consequence is that a compromised unrelated Pod may reach protected application ports across trust boundaries.

Question 555

A cooperative's payment processor should accept requests only from an authenticated internal gateway tier. What pair of supported action and practical verification should be approved?

  1. Apply ingress and egress NetworkPolicy to selected Pods and verify both permitted and denied synthetic flows under a network plugin that implements policy. Acceptance evidence: Check CNI capabilities, establish a default-deny test policy and verify one allowed and one denied connection.
  2. 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.
  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. 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.

Explanation

Correct Answer

C:

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. This pairing is justified because networkPolicies select Pods and define allowed flows; when a Pod becomes isolated, traffic is allowed only as permitted by applicable rules and plugin behavior.

Incorrect Answers

A:

This action and check address the distinct objective “Recognize NetworkPolicy isolation only when the CNI enforces it” instead of the stated acceptance requirement. The matching action is to combine a default-deny baseline with narrow app-label and namespace-label NetworkPolicy rules for approved traffic. Its confirming test is to test synthetic frontend-to-backend reachability and deny a third unauthorized namespace while verifying DNS access is still deliberately allowed.

B:

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 combine a default-deny baseline with narrow app-label and namespace-label NetworkPolicy rules for approved traffic. Its confirming test is to test synthetic frontend-to-backend reachability and deny a third unauthorized namespace while verifying DNS access is still deliberately allowed.

D:

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 combine a default-deny baseline with narrow app-label and namespace-label NetworkPolicy rules for approved traffic. Its confirming test is to test synthetic frontend-to-backend reachability and deny a third unauthorized namespace while verifying DNS access is still deliberately allowed.

Question 556

A university catalog service needs DNS and a single database endpoint but should deny unrelated lab Pods. Which Kubernetes or cloud-native implementation decision best solves the stated problem?

  1. Combine a default-deny baseline with narrow app-label and namespace-label NetworkPolicy rules for approved traffic.
  2. 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.
  3. Read Pod Events and node assignment to distinguish a Pod that cannot be scheduled from a scheduled Pod whose image cannot be pulled.
  4. Use narrowly scoped imagePullSecrets or an approved node identity to authorize the runtime to pull a private image.

Explanation

Correct Answer

A:

The situation is that a university catalog service needs DNS and a single database endpoint but should deny unrelated lab Pods. Combine a default-deny baseline with narrow app-label and namespace-label NetworkPolicy rules for approved traffic. This resolves the issue because networkPolicies select Pods and define allowed flows; when a Pod becomes isolated, traffic is allowed only as permitted by applicable rules and plugin behavior. To verify, test synthetic frontend-to-backend reachability and deny a third unauthorized namespace while verifying DNS access is still deliberately allowed.

Incorrect Answers

B:

This option addresses the distinct objective “Distinguish ClusterRoles from Roles and binding scope”, not the immediate requirement. ClusterRole defines permissions while ClusterRoleBinding makes them cluster-wide; RoleBinding limits effective namespaced scope even when referencing a ClusterRole. For the stated case, networkPolicies select Pods and define allowed flows; when a Pod becomes isolated, traffic is allowed only as permitted by applicable rules and plugin behavior.

C:

This option addresses the distinct objective “Separate Pending scheduling failures from ImagePullBackOff errors”, not the immediate requirement. FailedScheduling occurs before node binding; ImagePullBackOff occurs when a node's kubelet cannot obtain the container image. For the stated case, networkPolicies select Pods and define allowed flows; when a Pod becomes isolated, traffic is allowed only as permitted by applicable rules and plugin behavior.

D:

This option addresses the distinct objective “Handle private registry pulls with dedicated credentials instead of embedding secrets in images”, not the immediate requirement. Image-pull credentials are consumed before the application starts and should not be hardcoded into container layers or app logs. For the stated case, networkPolicies select Pods and define allowed flows; when a Pod becomes isolated, traffic is allowed only as permitted by applicable rules and plugin behavior.

Question 557

A university catalog service needs DNS and a single database endpoint but should deny unrelated lab Pods. Which platform mechanism explains why the suitable approach works?

  1. NetworkPolicies select Pods and define allowed flows; when a Pod becomes isolated, traffic is allowed only as permitted by applicable rules and plugin behavior.
  2. A quota constrains aggregate namespace resource usage, while a LimitRange validates or defaults eligible individual resource settings.
  3. Mounted credentials can enable Kubernetes API calls from a compromised container; explicit token exposure and RBAC scope limit abuse.
  4. RBAC evaluates API verbs, resources and scope; a Role is namespaced and does not grant cluster-wide access merely because the subject can authenticate.

Explanation

Correct Answer

A:

The situation is that a university catalog service needs DNS and a single database endpoint but should deny unrelated lab Pods. NetworkPolicies select Pods and define allowed flows; when a Pod becomes isolated, traffic is allowed only as permitted by applicable rules and plugin behavior. It supports this action: Combine a default-deny baseline with narrow app-label and namespace-label NetworkPolicy rules for approved traffic. To confirm, test synthetic frontend-to-backend reachability and deny a third unauthorized namespace while verifying DNS access is still deliberately allowed.

Incorrect Answers

B:

That statement explains the distinct objective “Understand resource quotas and LimitRanges for namespace capacity governance” rather than the cause in this case. The deciding mechanism here is that networkPolicies select Pods and define allowed flows; when a Pod becomes isolated, traffic is allowed only as permitted by applicable rules and plugin behavior.

C:

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 networkPolicies select Pods and define allowed flows; when a Pod becomes isolated, traffic is allowed only as permitted by applicable rules and plugin behavior.

D:

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 networkPolicies select Pods and define allowed flows; when a Pod becomes isolated, traffic is allowed only as permitted by applicable rules and plugin behavior.

Question 558

A university catalog service needs DNS and a single database endpoint but should deny unrelated lab Pods. Which controlled observation would best validate the intended improvement?

  1. In a staging gateway route 5 percent to a canary, inspect version-specific success rates and verify a rollback rule.
  2. Create a small claim in a test StorageClass, inspect its Bound status and restart the consuming Pod to check data persistence.
  3. Test synthetic frontend-to-backend reachability and deny a third unauthorized namespace while verifying DNS access is still deliberately allowed.
  4. Deploy one signed approved image and one unverified synthetic image under a test admission policy, recording expected allow and deny results.

Explanation

Correct Answer

C:

The situation is that a university catalog service needs DNS and a single database endpoint but should deny unrelated lab Pods. Test synthetic frontend-to-backend reachability and deny a third unauthorized namespace while verifying DNS access is still deliberately allowed. This is the relevant test because networkPolicies select Pods and define allowed flows; when a Pod becomes isolated, traffic is allowed only as permitted by applicable rules and plugin behavior.

Incorrect Answers

A:

This check would help evaluate the distinct objective “Distinguish canary and blue-green delivery strategies from Kubernetes Deployment defaults”, but not the required result. For this case, test synthetic frontend-to-backend reachability and deny a third unauthorized namespace while verifying DNS access is still deliberately allowed.

B:

This check would help evaluate the distinct objective “Understand PersistentVolumeClaim binding to persistent storage resources”, but not the required result. For this case, test synthetic frontend-to-backend reachability and deny a third unauthorized namespace while verifying DNS access is still deliberately allowed.

D:

This check would help evaluate the distinct objective “Use image provenance and policy controls without trusting mutable tags”, but not the required result. For this case, test synthetic frontend-to-backend reachability and deny a third unauthorized namespace while verifying DNS access is still deliberately allowed.

Question 559

A university catalog service needs DNS and a single database endpoint but should deny unrelated lab Pods. An engineer proposes: “Allow all ingress traffic to make one API work, discarding the existing namespace segmentation policy.” What adverse outcome would be most direct?

  1. The subject receives unnecessary authority to alter privileged resources or unrelated namespaces.
  2. An unrelated object may be targeted or the intended workload may remain untouched and unavailable.
  3. A compromised unrelated Pod may reach protected application ports across trust boundaries.
  4. Name lookup may succeed but no usable endpoint exists to receive traffic.

Explanation

Correct Answer

C:

The situation is that a university catalog service needs DNS and a single database endpoint but should deny unrelated lab Pods. A compromised unrelated Pod may reach protected application ports across trust boundaries. The shortcut creates this risk because networkPolicies select Pods and define allowed flows; when a Pod becomes isolated, traffic is allowed only as permitted by applicable rules and plugin behavior.

Incorrect Answers

A:

That outcome concerns the distinct objective “Implement namespaced RBAC Roles for least-privilege resource permissions”; it is not the most direct consequence of this shortcut. The relevant consequence is that a compromised unrelated Pod may reach protected application ports across trust boundaries.

B:

That outcome concerns the distinct objective “Read the API resource model using namespaces and names rather than guessing ownership”; it is not the most direct consequence of this shortcut. The relevant consequence is that a compromised unrelated Pod may reach protected application ports across trust boundaries.

D:

That outcome concerns the distinct objective “Use EndpointSlices to connect Service selectors with actual backend Pods”; it is not the most direct consequence of this shortcut. The relevant consequence is that a compromised unrelated Pod may reach protected application ports across trust boundaries.

Question 560

A university catalog service needs DNS and a single database endpoint but should deny unrelated lab Pods. What pair of supported action and practical verification should be approved?

  1. Configure an HPA for an eligible scalable controller using available resource or custom metrics and sensible minimum/maximum replicas. Acceptance evidence: Generate controlled CPU load, verify HPA current/target metric reporting and observe replica changes within configured limits.
  2. 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.
  3. Review Retain versus Delete behavior for data-bearing PVs and test cleanup policy using synthetic non-sensitive data. Acceptance evidence: Create a disposable PVC with test content, delete its consuming Pod and then the claim, observing actual PV and backing volume behavior.
  4. Require verified API server certificates, properly scoped identities and audit policy rather than turning off certificate checks for convenience. Acceptance evidence: With synthetic users verify a trusted API connection, denied privilege escalation and appropriate audit entries for failed requests.

Explanation

Correct Answer

B:

The situation is that a university catalog service needs DNS and a single database endpoint but should deny unrelated lab Pods. 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. This pairing is justified because networkPolicies select Pods and define allowed flows; when a Pod becomes isolated, traffic is allowed only as permitted by applicable rules and plugin behavior.

Incorrect Answers

A:

This action and check address the distinct objective “Use HorizontalPodAutoscaler metrics rather than ad hoc instance scripts” instead of the stated acceptance requirement. The matching action is to combine a default-deny baseline with narrow app-label and namespace-label NetworkPolicy rules for approved traffic. Its confirming test is to test synthetic frontend-to-backend reachability and deny a third unauthorized namespace while verifying DNS access is still deliberately allowed.

C:

This action and check address the distinct objective “Compare PV reclaim policies and explain data retention on PVC deletion” instead of the stated acceptance requirement. The matching action is to combine a default-deny baseline with narrow app-label and namespace-label NetworkPolicy rules for approved traffic. Its confirming test is to test synthetic frontend-to-backend reachability and deny a third unauthorized namespace while verifying DNS access is still deliberately allowed.

D:

This action and check address the distinct objective “Protect API server access using authenticated TLS clients and audited authorization” instead of the stated acceptance requirement. The matching action is to combine a default-deny baseline with narrow app-label and namespace-label NetworkPolicy rules for approved traffic. Its confirming test is to test synthetic frontend-to-backend reachability and deny a third unauthorized namespace while verifying DNS access is still deliberately allowed.

Kubernetes and Cloud Native Associate (KCNA) Practice Tests