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 60

Question 590

A school district's batch worker calls only an external image service and should not receive unnecessary cluster credentials. Which combined solution and independent check are most directly justified?

  1. Read a workload's spec and status separately and inspect conditions when determining whether an API change became healthy. Acceptance evidence: Apply a test manifest with impossible node constraints, then inspect the accepted spec and Pending status/Events.
  2. 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.
  3. 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.
  4. 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.

Explanation

Correct Answer

C:

The situation is that a school district's batch worker calls only an external image service and should not receive unnecessary cluster credentials. 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. This pairing is justified because mounted credentials can enable Kubernetes API calls from a compromised container; explicit token exposure and RBAC scope limit abuse.

Incorrect Answers

A:

This action and check address the distinct objective “Interpret Kubernetes spec and status fields without confusing intent with condition” instead of the stated acceptance requirement. The matching action is to give each Pod an appropriate ServiceAccount, disable automountServiceAccountToken where API access is unnecessary and test token audience and role scope. Its confirming test is to run a test web Pod without a token mount and verify service operation succeeds while in-cluster API calls are unavailable.

B:

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 give each Pod an appropriate ServiceAccount, disable automountServiceAccountToken where API access is unnecessary and test token audience and role scope. Its confirming test is to run a test web Pod without a token mount and verify service operation succeeds while in-cluster API calls are unavailable.

D:

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 give each Pod an appropriate ServiceAccount, disable automountServiceAccountToken where API access is unnecessary and test token audience and role scope. Its confirming test is to run a test web Pod without a token mount and verify service operation succeeds while in-cluster API calls are unavailable.

Question 591

A polytechnic shares one training cluster among untrusted student cohorts. 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. Apply stable application labels and ensure Services and controllers select the intended Pods by equality or set-based matching.
  3. Combine RBAC, Pod security policies, NetworkPolicy and resource quotas for teams that share a Kubernetes control plane.
  4. Inspect Pod container last state, restart count and kubectl logs --previous when a process repeatedly exits after startup.

Explanation

Correct Answer

C:

Combine RBAC, Pod security policies, NetworkPolicy and resource quotas for teams that share a Kubernetes control plane. This resolves the issue because namespaces alone partition naming but do not provide complete security isolation, capacity governance or protection from privileged node-level workloads. To verify, test that one synthetic tenant cannot list another namespace's Secrets, send blocked traffic or exceed quota.

Incorrect Answers

A:

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, namespaces alone partition naming but do not provide complete security isolation, capacity governance or protection from privileged node-level workloads.

B:

This option addresses the distinct objective “Use labels and selectors to connect resources predictably”, not the immediate requirement. Kubernetes labels are queryable object metadata, while selectors connect controllers and Services to matching endpoints; names alone do not create these relationships. For the stated case, namespaces alone partition naming but do not provide complete security isolation, capacity governance or protection from privileged node-level workloads.

D:

This option addresses the distinct objective “Diagnose CrashLoopBackOff from restart history and previous logs”, not the immediate requirement. CrashLoopBackOff reflects kubelet restart backoff after container failures; the underlying cause may be application configuration, exit code or a failed liveness probe. For the stated case, namespaces alone partition naming but do not provide complete security isolation, capacity governance or protection from privileged node-level workloads.

Question 592

A polytechnic shares one training cluster among untrusted student cohorts. Which platform mechanism explains why the suitable approach works?

  1. CSI separates storage vendor implementation from Kubernetes core and manages provisioning, attachment and node mounting through driver-defined capabilities.
  2. NetworkPolicies select Pods and define allowed flows; when a Pod becomes isolated, traffic is allowed only as permitted by applicable rules and plugin behavior.
  3. kubectl logs retrieves container output and --previous can expose the prior terminated instance, but application output is not a substitute for cluster Events.
  4. Namespaces alone partition naming but do not provide complete security isolation, capacity governance or protection from privileged node-level workloads.

Explanation

Correct Answer

D:

Namespaces alone partition naming but do not provide complete security isolation, capacity governance or protection from privileged node-level workloads. It supports this action: Combine RBAC, Pod security policies, NetworkPolicy and resource quotas for teams that share a Kubernetes control plane. To confirm, test that one synthetic tenant cannot list another namespace's Secrets, send blocked traffic or exceed quota.

Incorrect Answers

A:

That statement explains the distinct objective “Understand CSI drivers and volume attachment responsibilities” rather than the cause in this case. The deciding mechanism here is that namespaces alone partition naming but do not provide complete security isolation, capacity governance or protection from privileged node-level workloads.

B:

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 namespaces alone partition naming but do not provide complete security isolation, capacity governance or protection from privileged node-level workloads.

C:

That statement explains the distinct objective “Use kubectl logs and previous container logs to isolate application crashes” rather than the cause in this case. The deciding mechanism here is that namespaces alone partition naming but do not provide complete security isolation, capacity governance or protection from privileged node-level workloads.

Question 593

A polytechnic shares one training cluster among untrusted student cohorts. 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. Induce a temporary readiness failure in staging and verify traffic stops without a restart; then separately test controlled liveness failure.
  3. Deploy one signed approved image and one unverified synthetic image under a test admission policy, recording expected allow and deny results.
  4. Simulate controlled resource pressure with two priorities and inspect Events for whether a high-priority test Pod can schedule.

Explanation

Correct Answer

A:

Test that one synthetic tenant cannot list another namespace's Secrets, send blocked traffic or exceed quota. This is the relevant test because namespaces alone partition naming but do not provide complete security isolation, capacity governance or protection from privileged node-level workloads.

Incorrect Answers

B:

This check would help evaluate the distinct objective “Investigate readiness failures separately from liveness-related restarts”, but not the required result. For this case, test that one synthetic tenant cannot list another namespace's Secrets, send blocked traffic or exceed quota.

C:

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 that one synthetic tenant cannot list another namespace's Secrets, send blocked traffic or exceed quota.

D:

This check would help evaluate the distinct objective “Use PriorityClasses and understand preemption without assuming they guarantee availability”, but not the required result. For this case, test that one synthetic tenant cannot list another namespace's Secrets, send blocked traffic or exceed quota.

Question 594

A polytechnic shares one training cluster among untrusted student cohorts. An engineer proposes: “Create two namespaces with names finance and students and declare them fully isolated without enforcing any additional security rules.” What adverse outcome would be most direct?

  1. Teams can share unintended network and resource access while administrators believe the naming boundary is protective.
  2. Sensitive traffic may remain allowed because the networking implementation does not enforce the declared policy.
  3. Dangerous existing configuration may persist because admission is not a universal replacement for every security control.
  4. External routing remains absent or policy is misunderstood, and internal identity controls may be incomplete.

Explanation

Correct Answer

A:

Teams can share unintended network and resource access while administrators believe the naming boundary is protective. The shortcut creates this risk because namespaces alone partition naming but do not provide complete security isolation, capacity governance or protection from privileged node-level workloads.

Incorrect Answers

B:

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 teams can share unintended network and resource access while administrators believe the naming boundary is protective.

C:

That outcome concerns the distinct objective “Use Pod Security Standards to deny overly privileged Pod configurations”; it is not the most direct consequence of this shortcut. The relevant consequence is that teams can share unintended network and resource access while administrators believe the naming boundary is protective.

D:

That outcome concerns the distinct objective “Distinguish service mesh traffic management from external ingress routing”; it is not the most direct consequence of this shortcut. The relevant consequence is that teams can share unintended network and resource access while administrators believe the naming boundary is protective.

Question 595

A polytechnic shares one training cluster among untrusted student cohorts. What pair of supported action and practical verification should be approved?

  1. 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.
  2. 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.
  3. 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.
  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

D:

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. This pairing is justified because namespaces alone partition naming but do not provide complete security isolation, capacity governance or protection from privileged node-level workloads.

Incorrect Answers

A:

This action and check address the distinct objective “Distinguish ClusterRoles from Roles and binding scope” instead of the stated acceptance requirement. The matching action is to combine RBAC, Pod security policies, NetworkPolicy and resource quotas for teams that share a Kubernetes control plane. Its confirming test is to test that one synthetic tenant cannot list another namespace's Secrets, send blocked traffic or exceed quota.

B:

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 RBAC, Pod security policies, NetworkPolicy and resource quotas for teams that share a Kubernetes control plane. Its confirming test is to test that one synthetic tenant cannot list another namespace's Secrets, send blocked traffic or exceed quota.

C:

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 combine RBAC, Pod security policies, NetworkPolicy and resource quotas for teams that share a Kubernetes control plane. Its confirming test is to test that one synthetic tenant cannot list another namespace's Secrets, send blocked traffic or exceed quota.

Question 596

A small SaaS platform runs customers' development environments in separate namespaces with resource and access limits. What technical action should the platform team take in this situation?

  1. Combine a default-deny baseline with narrow app-label and namespace-label NetworkPolicy rules for approved traffic.
  2. Check that a supported CNI plugin assigns reachable Pod addresses across worker nodes before troubleshooting Service routing or DNS names.
  3. Combine RBAC, Pod security policies, NetworkPolicy and resource quotas for teams that share a Kubernetes control plane.
  4. Inspect the active kubeconfig context and namespace before applying manifests to staging or production.

Explanation

Correct Answer

C:

The situation is that a small SaaS platform runs customers' development environments in separate namespaces with resource and access limits. Combine RBAC, Pod security policies, NetworkPolicy and resource quotas for teams that share a Kubernetes control plane. This resolves the issue because namespaces alone partition naming but do not provide complete security isolation, capacity governance or protection from privileged node-level workloads. To verify, test that one synthetic tenant cannot list another namespace's Secrets, send blocked traffic or exceed quota.

Incorrect Answers

A:

The situation is that a small SaaS platform runs customers' development environments in separate namespaces with resource and access limits. 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, namespaces alone partition naming but do not provide complete security isolation, capacity governance or protection from privileged node-level workloads.

B:

This option addresses the distinct objective “Distinguish the CNI Pod network from Service discovery and routing”, not the immediate requirement. Kubernetes expects a Pod network providing Pod-to-Pod connectivity; the CNI implementation configures networking while Services provide stable virtual access to changing endpoints. For the stated case, namespaces alone partition naming but do not provide complete security isolation, capacity governance or protection from privileged node-level workloads.

D:

This option addresses the distinct objective “Manage kubectl contexts to avoid changes in the wrong cluster”, not the immediate requirement. A kubeconfig context binds cluster, identity and default namespace, so command syntax can be valid yet target the wrong environment. For the stated case, namespaces alone partition naming but do not provide complete security isolation, capacity governance or protection from privileged node-level workloads.

Question 597

A small SaaS platform runs customers' development environments in separate namespaces with resource and access limits. 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. TLS establishes endpoint confidentiality and identity, while authentication and RBAC separately determine which API operations a caller may execute.
  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. Topology spread constraints compare Pod distribution in topology domains and can restrict or prefer placement depending on whenUnsatisfiable.

Explanation

Correct Answer

A:

The situation is that a small SaaS platform runs customers' development environments in separate namespaces with resource and access limits. Namespaces alone partition naming but do not provide complete security isolation, capacity governance or protection from privileged node-level workloads. It supports this action: Combine RBAC, Pod security policies, NetworkPolicy and resource quotas for teams that share a Kubernetes control plane. To confirm, test that one synthetic tenant cannot list another namespace's Secrets, send blocked traffic or exceed quota.

Incorrect Answers

B:

That statement explains the distinct objective “Protect API server access using authenticated TLS clients and audited authorization” rather than the cause in this case. The deciding mechanism here is that namespaces alone partition naming but do not provide complete security isolation, capacity governance or protection from privileged node-level workloads.

C:

The situation is that a small SaaS platform runs customers' development environments in separate namespaces with resource and access limits. 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 namespaces alone partition naming but do not provide complete security isolation, capacity governance or protection from privileged node-level workloads.

D:

That statement explains the distinct objective “Spread replicas across failure domains with topologySpreadConstraints” rather than the cause in this case. The deciding mechanism here is that namespaces alone partition naming but do not provide complete security isolation, capacity governance or protection from privileged node-level workloads.

Question 598

A small SaaS platform runs customers' development environments in separate namespaces with resource and access limits. 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. Bind a synthetic ClusterRole through RoleBinding in namespace-a, then verify access fails in namespace-b.
  3. Compare the governance and release activity of two projects and document which operational support and security tests are still required.
  4. Deploy a test hostname route, verify a compatible controller exists and inspect the programmed listener and backend status.

Explanation

Correct Answer

A:

The situation is that a small SaaS platform runs customers' development environments in separate namespaces with resource and access limits. Test that one synthetic tenant cannot list another namespace's Secrets, send blocked traffic or exceed quota. This is the relevant test because namespaces alone partition naming but do not provide complete security isolation, capacity governance or protection from privileged node-level workloads.

Incorrect Answers

B:

This check would help evaluate the distinct objective “Distinguish ClusterRoles from Roles and binding scope”, but not the required result. For this case, test that one synthetic tenant cannot list another namespace's Secrets, send blocked traffic or exceed quota.

C:

This check would help evaluate the distinct objective “Understand CNCF project maturity stages without equating them to security approval”, but not the required result. For this case, test that one synthetic tenant cannot list another namespace's Secrets, send blocked traffic or exceed quota.

D:

This check would help evaluate the distinct objective “Choose Ingress or Gateway API with an implementing controller for HTTP exposure”, but not the required result. For this case, test that one synthetic tenant cannot list another namespace's Secrets, send blocked traffic or exceed quota.

Question 599

A small SaaS platform runs customers' development environments in separate namespaces with resource and access limits. The team suggests: “Create two namespaces with names finance and students and declare them fully isolated without enforcing any additional security rules.” Which failure should the reviewer anticipate?

  1. An unrelated object may be targeted or the intended workload may remain untouched and unavailable.
  2. Replicas can collide on storage ownership and application state ordering assumptions fail.
  3. One application vulnerability can expose a credential allowing changes unrelated to its actual business function.
  4. Teams can share unintended network and resource access while administrators believe the naming boundary is protective.

Explanation

Correct Answer

D:

The situation is that a small SaaS platform runs customers' development environments in separate namespaces with resource and access limits. Teams can share unintended network and resource access while administrators believe the naming boundary is protective. The shortcut creates this risk because namespaces alone partition naming but do not provide complete security isolation, capacity governance or protection from privileged node-level workloads.

Incorrect Answers

A:

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 teams can share unintended network and resource access while administrators believe the naming boundary is protective.

B:

That outcome concerns the distinct objective “Use StatefulSet for stable ordinal identity and persistent per-replica claims”; it is not the most direct consequence of this shortcut. The relevant consequence is that teams can share unintended network and resource access while administrators believe the naming boundary is protective.

C:

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 teams can share unintended network and resource access while administrators believe the naming boundary is protective.

Question 600

A small SaaS platform runs customers' development environments in separate namespaces with resource and access limits. Which engineering change and test jointly addresses the scenario?

  1. 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.
  2. 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.
  3. Package reusable Kubernetes resource templates in a Helm chart and review rendered manifests and values before installation or upgrade. Acceptance evidence: Run helm template with staging values, inspect the generated Deployment and Service, and compare a revision's upgrade history.
  4. Use cluster DNS records such as service.namespace.svc.cluster.local when a Pod connects to Services in other namespaces. Acceptance evidence: Run nslookup for a Service using short and namespace-qualified names from test Pods in two different namespaces.

Explanation

Correct Answer

A:

The situation is that a small SaaS platform runs customers' development environments in separate namespaces with resource and access limits. 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. This pairing is justified because namespaces alone partition naming but do not provide complete security isolation, capacity governance or protection from privileged node-level workloads.

Incorrect Answers

B:

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 combine RBAC, Pod security policies, NetworkPolicy and resource quotas for teams that share a Kubernetes control plane. Its confirming test is to test that one synthetic tenant cannot list another namespace's Secrets, send blocked traffic or exceed quota.

C:

This action and check address the distinct objective “Use Helm charts for parameterized application packages without equating them to cluster controllers” instead of the stated acceptance requirement. The matching action is to combine RBAC, Pod security policies, NetworkPolicy and resource quotas for teams that share a Kubernetes control plane. Its confirming test is to test that one synthetic tenant cannot list another namespace's Secrets, send blocked traffic or exceed quota.

D:

This action and check address the distinct objective “Verify CoreDNS resolution and namespace-qualified Service names” instead of the stated acceptance requirement. The matching action is to combine RBAC, Pod security policies, NetworkPolicy and resource quotas for teams that share a Kubernetes control plane. Its confirming test is to test that one synthetic tenant cannot list another namespace's Secrets, send blocked traffic or exceed quota.

Kubernetes and Cloud Native Associate (KCNA) Practice Tests