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 59

Question 580

A research laboratory has a copied kubeconfig that disables TLS verification because of an outdated CA bundle. 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. Verify that the installed Container Storage Interface driver supports the requested persistent storage and inspect driver controller/node components when mounting fails. Acceptance evidence: Inspect CSI driver registration, test provisioning a claim and review attachment/mount Events for a synthetic workload.
  3. 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.
  4. Define post-release checks for readiness, error rate and latency, and revert an unhealthy revision using an approved rollout mechanism. Acceptance evidence: Deploy a synthetic faulty image, monitor request errors and confirm the release controller or operator restores the last known healthy revision.

Explanation

Correct Answer

C:

The situation is that a research laboratory has a copied kubeconfig that disables TLS verification because of an outdated CA bundle. 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. This pairing is justified because TLS establishes endpoint confidentiality and identity, while authentication and RBAC separately determine which API operations a caller may execute.

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 require verified API server certificates, properly scoped identities and audit policy rather than turning off certificate checks for convenience. Its confirming test is to with synthetic users verify a trusted API connection, denied privilege escalation and appropriate audit entries for failed requests.

B:

The situation is that a research laboratory has a copied kubeconfig that disables TLS verification because of an outdated CA bundle. This action and check address the distinct objective “Understand CSI drivers and volume attachment responsibilities” instead of the stated acceptance requirement. The matching action is to require verified API server certificates, properly scoped identities and audit policy rather than turning off certificate checks for convenience. Its confirming test is to with synthetic users verify a trusted API connection, denied privilege escalation and appropriate audit entries for failed requests.

D:

This action and check address the distinct objective “Design a release rollback trigger from measurable service signals” instead of the stated acceptance requirement. The matching action is to require verified API server certificates, properly scoped identities and audit policy rather than turning off certificate checks for convenience. Its confirming test is to with synthetic users verify a trusted API connection, denied privilege escalation and appropriate audit entries for failed requests.

Question 581

A financial services public web front end never needs the Kubernetes API after startup. Which engineering approach is the most appropriate for this cloud-native case?

  1. Read Pod Events and node assignment to distinguish a Pod that cannot be scheduled from a scheduled Pod whose image cannot be pulled.
  2. Give each Pod an appropriate ServiceAccount, disable automountServiceAccountToken where API access is unnecessary and test token audience and role scope.
  3. Use a Deployment for a replicated stateless application requiring rolling updates and replacement of failed Pods.
  4. Require approved image registries, signature or digest verification and patch ownership when admitting production container images.

Explanation

Correct Answer

B:

Give each Pod an appropriate ServiceAccount, disable automountServiceAccountToken where API access is unnecessary and test token audience and role scope. This resolves the issue because mounted credentials can enable Kubernetes API calls from a compromised container; explicit token exposure and RBAC scope limit abuse. To verify, run a test web Pod without a token mount and verify service operation succeeds while in-cluster API calls are unavailable.

Incorrect Answers

A:

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, mounted credentials can enable Kubernetes API calls from a compromised container; explicit token exposure and RBAC scope limit abuse.

C:

This option addresses the distinct objective “Distinguish Deployment desired state from a manually created Pod”, not the immediate requirement. A Deployment owns ReplicaSets that manage matching Pods and supports declarative rollout history, unlike an independent Pod object. For the stated case, mounted credentials can enable Kubernetes API calls from a compromised container; explicit token exposure and RBAC scope limit abuse.

D:

This option addresses the distinct objective “Use image provenance and policy controls without trusting mutable tags”, not the immediate requirement. Image provenance reduces accidental or malicious image substitution; mutable tags alone cannot prove build integrity or content identity. For the stated case, mounted credentials can enable Kubernetes API calls from a compromised container; explicit token exposure and RBAC scope limit abuse.

Question 582

A financial services public web front end never needs the Kubernetes API after startup. What infrastructure principle makes the correct treatment effective?

  1. Canary release needs traffic steering and metrics for a subset; blue-green shifts a complete traffic target after validation, and neither is automatically provided by a plain Deployment update.
  2. 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.
  3. RBAC evaluates API verbs, resources and scope; a Role is namespaced and does not grant cluster-wide access merely because the subject can authenticate.
  4. Mounted credentials can enable Kubernetes API calls from a compromised container; explicit token exposure and RBAC scope limit abuse.

Explanation

Correct Answer

D:

Mounted credentials can enable Kubernetes API calls from a compromised container; explicit token exposure and RBAC scope limit abuse. It supports this action: Give each Pod an appropriate ServiceAccount, disable automountServiceAccountToken where API access is unnecessary and test token audience and role scope. To confirm, run a test web Pod without a token mount and verify service operation succeeds while in-cluster API calls are unavailable.

Incorrect Answers

A:

That statement explains the distinct objective “Distinguish canary and blue-green delivery strategies from Kubernetes Deployment defaults” rather than the cause in this case. The deciding mechanism here is that mounted credentials can enable Kubernetes API calls from a compromised container; explicit token exposure and RBAC scope limit abuse.

B:

That statement explains the distinct objective “Compare PV reclaim policies and explain data retention on PVC deletion” rather than the cause in this case. The deciding mechanism here is that mounted credentials can enable Kubernetes API calls from a compromised container; explicit token exposure and RBAC scope limit abuse.

C:

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 mounted credentials can enable Kubernetes API calls from a compromised container; explicit token exposure and RBAC scope limit abuse.

Question 583

A financial services public web front end never needs the Kubernetes API after startup. What verification result would most convincingly distinguish a working solution from a claim?

  1. Send a synthetic request with a correlation ID and confirm it appears in the trace and relevant logs while latency metrics change.
  2. Create two controlled faulty workloads, one requiring an impossible node label and one referencing a missing image tag, then compare Events.
  3. Run a test web Pod without a token mount and verify service operation succeeds while in-cluster API calls are unavailable.
  4. 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:

Run a test web Pod without a token mount and verify service operation succeeds while in-cluster API calls are unavailable. This is the relevant test because mounted credentials can enable Kubernetes API calls from a compromised container; explicit token exposure and RBAC scope limit abuse.

Incorrect Answers

A:

This check would help evaluate the distinct objective “Explain metrics, logs and traces as complementary observability signals”, but not the required result. For this case, run a test web Pod without a token mount and verify service operation succeeds while in-cluster API calls are unavailable.

B:

This check would help evaluate the distinct objective “Separate Pending scheduling failures from ImagePullBackOff errors”, but not the required result. For this case, run a test web Pod without a token mount and verify service operation succeeds while in-cluster API calls are unavailable.

D:

This check would help evaluate the distinct objective “Implement namespaced RBAC Roles for least-privilege resource permissions”, but not the required result. For this case, run a test web Pod without a token mount and verify service operation succeeds while in-cluster API calls are unavailable.

Question 584

A financial services public web front end never needs the Kubernetes API after startup. The change review contains this proposal: “Mount a broad administration token into every nginx container solely because it is the cluster default.” What risk matters most?

  1. Teams can share unintended network and resource access while administrators believe the naming boundary is protective.
  2. One application vulnerability can expose a credential allowing changes unrelated to its actual business function.
  3. Sensitive workloads may remain reachable until actual identity and traffic controls are installed.
  4. The subject receives unnecessary authority to alter privileged resources or unrelated namespaces.

Explanation

Correct Answer

B:

One application vulnerability can expose a credential allowing changes unrelated to its actual business function. The shortcut creates this risk because mounted credentials can enable Kubernetes API calls from a compromised container; explicit token exposure and RBAC scope limit abuse.

Incorrect Answers

A:

That outcome concerns the distinct objective “Separate multi-tenant namespace governance from actual isolation guarantees”; it is not the most direct consequence of this shortcut. The relevant consequence is that one application vulnerability can expose a credential allowing changes unrelated to its actual business function.

C:

That outcome concerns the distinct objective “Use namespaces as organizational scopes without treating them as firewalls”; it is not the most direct consequence of this shortcut. The relevant consequence is that one application vulnerability can expose a credential allowing changes unrelated to its actual business function.

D:

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 one application vulnerability can expose a credential allowing changes unrelated to its actual business function.

Question 585

A financial services public web front end never needs the Kubernetes API after startup. Which implementation together with matching acceptance evidence best meets this case?

  1. Define appropriate HTTP routing through an installed Ingress controller or Gateway API controller rather than expecting the API object alone to provision a proxy. Acceptance evidence: Deploy a test hostname route, verify a compatible controller exists and inspect the programmed listener and backend status.
  2. Use requiredDuringSchedulingIgnoredDuringExecution for mandatory constraints and preferredDuringSchedulingIgnoredDuringExecution for a soft placement preference. Acceptance evidence: Test the workload with and without a preferred zone and verify it still schedules when preferred nodes are busy.
  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. 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:

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 “Choose Ingress or Gateway API with an implementing controller for HTTP exposure” 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 “Distinguish preferred node affinity from required scheduling rules” 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 “Implement namespaced RBAC Roles for least-privilege resource permissions” 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 586

A school district's batch worker calls only an external image service and should not receive unnecessary cluster credentials. Which supported Kubernetes practice directly addresses the stated requirement?

  1. Inspect kubectl describe node and reported conditions, taints, disk pressure and kubelet health before moving workloads.
  2. Use Kubernetes controllers to keep replicas and other managed resources aligned with their declared specifications rather than manually re-creating each missing pod.
  3. Combine RBAC, Pod security policies, NetworkPolicy and resource quotas for teams that share a Kubernetes control plane.
  4. Give each Pod an appropriate ServiceAccount, disable automountServiceAccountToken where API access is unnecessary and test token audience and role scope.

Explanation

Correct Answer

D:

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. This resolves the issue because mounted credentials can enable Kubernetes API calls from a compromised container; explicit token exposure and RBAC scope limit abuse. To verify, run a test web Pod without a token mount and verify service operation succeeds while in-cluster API calls are unavailable.

Incorrect Answers

A:

This option addresses the distinct objective “Use node conditions and allocatable capacity to diagnose NotReady workloads”, not the immediate requirement. A NotReady or pressure-affected node can stop hosting healthy Pods even when their Deployment and Service definitions remain valid. For the stated case, mounted credentials can enable Kubernetes API calls from a compromised container; explicit token exposure and RBAC scope limit abuse.

B:

This option addresses the distinct objective “Identify reconciliation work performed by kube-controller-manager”, not the immediate requirement. The controller manager runs controllers that observe API resources and make changes so current state moves toward desired state. For the stated case, mounted credentials can enable Kubernetes API calls from a compromised container; explicit token exposure and RBAC scope limit abuse.

C:

This option addresses the distinct objective “Separate multi-tenant namespace governance from actual isolation guarantees”, not the immediate requirement. Namespaces alone partition naming but do not provide complete security isolation, capacity governance or protection from privileged node-level workloads. For the stated case, mounted credentials can enable Kubernetes API calls from a compromised container; explicit token exposure and RBAC scope limit abuse.

Question 587

A school district's batch worker calls only an external image service and should not receive unnecessary cluster credentials. Which causal explanation supports the intended design choice?

  1. ClusterRole defines permissions while ClusterRoleBinding makes them cluster-wide; RoleBinding limits effective namespaced scope even when referencing a ClusterRole.
  2. Image immutability separates software from environment configuration; mounted or environment-provided configuration can be updated by approved mechanisms, sometimes requiring rollout.
  3. Pod Security Standards establish common workload hardening profiles, and admission checks can enforce restricted capabilities and privilege use at API creation.
  4. Mounted credentials can enable Kubernetes API calls from a compromised container; explicit token exposure and RBAC scope limit abuse.

Explanation

Correct Answer

D:

The situation is that a school district's batch worker calls only an external image service and should not receive unnecessary cluster credentials. Mounted credentials can enable Kubernetes API calls from a compromised container; explicit token exposure and RBAC scope limit abuse. It supports this action: Give each Pod an appropriate ServiceAccount, disable automountServiceAccountToken where API access is unnecessary and test token audience and role scope. To confirm, run a test web Pod without a token mount and verify service operation succeeds while in-cluster API calls are unavailable.

Incorrect Answers

A:

That statement explains the distinct objective “Distinguish ClusterRoles from Roles and binding scope” rather than the cause in this case. The deciding mechanism here is that mounted credentials can enable Kubernetes API calls from a compromised container; explicit token exposure and RBAC scope limit abuse.

B:

That statement explains the distinct objective “Externalize application configuration from an image while protecting secrets” rather than the cause in this case. The deciding mechanism here is that mounted credentials can enable Kubernetes API calls from a compromised container; explicit token exposure and RBAC scope limit abuse.

C:

That statement explains the distinct objective “Use Pod Security Standards to deny overly privileged Pod configurations” rather than the cause in this case. The deciding mechanism here is that mounted credentials can enable Kubernetes API calls from a compromised container; explicit token exposure and RBAC scope limit abuse.

Question 588

A school district's batch worker calls only an external image service and should not receive unnecessary cluster credentials. Which test provides the strongest evidence of a correct implementation?

  1. Inspect CSI driver registration, test provisioning a claim and review attachment/mount Events for a synthetic workload.
  2. Run a test web Pod without a token mount and verify service operation succeeds while in-cluster API calls are unavailable.
  3. Use kubectl auth can-i --as a synthetic student to verify pod get allowed and secret delete denied in the specified namespace.
  4. Insert a deliberately unsigned test image into staging and confirm the release gate blocks production promotion while logging a reason.

Explanation

Correct Answer

B:

The situation is that a school district's batch worker calls only an external image service and should not receive unnecessary cluster credentials. Run a test web Pod without a token mount and verify service operation succeeds while in-cluster API calls are unavailable. This is the relevant test because mounted credentials can enable Kubernetes API calls from a compromised container; explicit token exposure and RBAC scope limit abuse.

Incorrect Answers

A:

This check would help evaluate the distinct objective “Understand CSI drivers and volume attachment responsibilities”, but not the required result. For this case, run a test web Pod without a token mount and verify service operation succeeds while in-cluster API calls are unavailable.

C:

The situation is that a school district's batch worker calls only an external image service and should not receive unnecessary cluster credentials. This check would help evaluate the distinct objective “Implement namespaced RBAC Roles for least-privilege resource permissions”, but not the required result. For this case, run a test web Pod without a token mount and verify service operation succeeds while in-cluster API calls are unavailable.

D:

This check would help evaluate the distinct objective “Define secure release governance with staged approvals and policy verification”, but not the required result. For this case, run a test web Pod without a token mount and verify service operation succeeds while in-cluster API calls are unavailable.

Question 589

A school district's batch worker calls only an external image service and should not receive unnecessary cluster credentials. A shortcut is proposed: “Mount a broad administration token into every nginx container solely because it is the cluster default.” Which technical consequence follows most closely?

  1. One application vulnerability can expose a credential allowing changes unrelated to its actual business function.
  2. Applications fail on migration when plugin behavior or provider-specific components were never evaluated.
  3. Pods may start but remain unable to communicate across nodes because the CNI dataplane was never established.
  4. An untrusted dependency or replaced tag can run within otherwise well-configured Pods.

Explanation

Correct Answer

A:

The situation is that a school district's batch worker calls only an external image service and should not receive unnecessary cluster credentials. One application vulnerability can expose a credential allowing changes unrelated to its actual business function. The shortcut creates this risk because mounted credentials can enable Kubernetes API calls from a compromised container; explicit token exposure and RBAC scope limit abuse.

Incorrect Answers

B:

That outcome concerns the distinct objective “Understand open standards and vendor-neutral community collaboration”; it is not the most direct consequence of this shortcut. The relevant consequence is that one application vulnerability can expose a credential allowing changes unrelated to its actual business function.

C:

That outcome concerns the distinct objective “Distinguish the CNI Pod network from Service discovery and routing”; it is not the most direct consequence of this shortcut. The relevant consequence is that one application vulnerability can expose a credential allowing changes unrelated to its actual business function.

D:

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 one application vulnerability can expose a credential allowing changes unrelated to its actual business function.

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.

Kubernetes and Cloud Native Associate (KCNA) Practice Tests