Linux Foundation KCNA Dumps
Linux Foundation KCNA Practice Test 58
Question 570
A hospital discovers that a third-party image tag was changed after its release approval. Which combined solution and independent check are most directly justified?
Explanation
Correct Answer
The situation is that a hospital discovers that a third-party image tag was changed after its release approval. 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. This pairing is justified because image provenance reduces accidental or malicious image substitution; mutable tags alone cannot prove build integrity or content identity.
Incorrect Answers
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 require approved image registries, signature or digest verification and patch ownership when admitting production container images. Its confirming test is to deploy one signed approved image and one unverified synthetic image under a test admission policy, recording expected allow and deny results.
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 require approved image registries, signature or digest verification and patch ownership when admitting production container images. Its confirming test is to deploy one signed approved image and one unverified synthetic image under a test admission policy, recording expected allow and deny results.
This action and check address the distinct objective “Use annotations for tool metadata rather than workload selection” instead of the stated acceptance requirement. The matching action is to require approved image registries, signature or digest verification and patch ownership when admitting production container images. Its confirming test is to deploy one signed approved image and one unverified synthetic image under a test admission policy, recording expected allow and deny results.
Question 571
A regional retailer connects CI jobs to Kubernetes over an untrusted corporate network. What technical action should the platform team take in this situation?
Explanation
Correct Answer
Require verified API server certificates, properly scoped identities and audit policy rather than turning off certificate checks for convenience. This resolves the issue because TLS establishes endpoint confidentiality and identity, while authentication and RBAC separately determine which API operations a caller may execute. To verify, with synthetic users verify a trusted API connection, denied privilege escalation and appropriate audit entries for failed requests.
Incorrect Answers
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, TLS establishes endpoint confidentiality and identity, while authentication and RBAC separately determine which API operations a caller may execute.
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, TLS establishes endpoint confidentiality and identity, while authentication and RBAC separately determine which API operations a caller may execute.
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, TLS establishes endpoint confidentiality and identity, while authentication and RBAC separately determine which API operations a caller may execute.
Question 572
A regional retailer connects CI jobs to Kubernetes over an untrusted corporate network. What underlying Kubernetes behavior is most relevant to this technical decision?
Explanation
Correct Answer
TLS establishes endpoint confidentiality and identity, while authentication and RBAC separately determine which API operations a caller may execute. It supports this action: Require verified API server certificates, properly scoped identities and audit policy rather than turning off certificate checks for convenience. To confirm, with synthetic users verify a trusted API connection, denied privilege escalation and appropriate audit entries for failed requests.
Incorrect Answers
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 TLS establishes endpoint confidentiality and identity, while authentication and RBAC separately determine which API operations a caller may execute.
That statement explains the distinct objective “Distinguish memory limits from CPU throttling for scheduling and runtime symptoms” rather than the cause in this case. The deciding mechanism here is that TLS establishes endpoint confidentiality and identity, while authentication and RBAC separately determine which API operations a caller may execute.
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 TLS establishes endpoint confidentiality and identity, while authentication and RBAC separately determine which API operations a caller may execute.
Question 573
A regional retailer connects CI jobs to Kubernetes over an untrusted corporate network. What acceptance check most directly confirms this requirement is met?
Explanation
Correct Answer
With synthetic users verify a trusted API connection, denied privilege escalation and appropriate audit entries for failed requests. This is the relevant test because TLS establishes endpoint confidentiality and identity, while authentication and RBAC separately determine which API operations a caller may execute.
Incorrect Answers
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, with synthetic users verify a trusted API connection, denied privilege escalation and appropriate audit entries for failed requests.
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, with synthetic users verify a trusted API connection, denied privilege escalation and appropriate audit entries for failed requests.
This check would help evaluate the distinct objective “Spread replicas across failure domains with topologySpreadConstraints”, but not the required result. For this case, with synthetic users verify a trusted API connection, denied privilege escalation and appropriate audit entries for failed requests.
Question 574
A regional retailer connects CI jobs to Kubernetes over an untrusted corporate network. The team suggests: “Set insecure-skip-tls-verify for every cluster client and reuse one administrator token across automated jobs.” Which failure should the reviewer anticipate?
Explanation
Correct Answer
Clients may connect to an impersonated API endpoint and the token could grant excessive permissions. The shortcut creates this risk because TLS establishes endpoint confidentiality and identity, while authentication and RBAC separately determine which API operations a caller may execute.
Incorrect Answers
That outcome concerns the distinct objective “Choose Ingress or Gateway API with an implementing controller for HTTP exposure”; it is not the most direct consequence of this shortcut. The relevant consequence is that clients may connect to an impersonated API endpoint and the token could grant excessive permissions.
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 clients may connect to an impersonated API endpoint and the token could grant excessive permissions.
That outcome concerns the distinct objective “Run images with least-privilege runtime security contexts”; it is not the most direct consequence of this shortcut. The relevant consequence is that clients may connect to an impersonated API endpoint and the token could grant excessive permissions.
Question 575
A regional retailer connects CI jobs to Kubernetes over an untrusted corporate network. Which engineering change and test jointly addresses the scenario?
Explanation
Correct Answer
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
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.
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 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.
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 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 576
A research laboratory has a copied kubeconfig that disables TLS verification because of an outdated CA bundle. What technical action should the platform team take in this situation?
Explanation
Correct Answer
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. This resolves the issue because TLS establishes endpoint confidentiality and identity, while authentication and RBAC separately determine which API operations a caller may execute. To verify, with synthetic users verify a trusted API connection, denied privilege escalation and appropriate audit entries for failed requests.
Incorrect Answers
This option addresses the distinct objective “Use EndpointSlices to connect Service selectors with actual backend Pods”, not the immediate requirement. EndpointSlices describe endpoint addresses and readiness associated with a Service, allowing its dataplane to route toward matching healthy Pods. For the stated case, TLS establishes endpoint confidentiality and identity, while authentication and RBAC separately determine which API operations a caller may execute.
This option addresses the distinct objective “Correlate application rollout revisions with error spikes”, not the immediate requirement. Kubernetes object transitions and application telemetry must be correlated; a healthy rollout condition alone does not prove user-level functionality. For the stated case, TLS establishes endpoint confidentiality and identity, while authentication and RBAC separately determine which API operations a caller may execute.
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, TLS establishes endpoint confidentiality and identity, while authentication and RBAC separately determine which API operations a caller may execute.
Question 577
A research laboratory has a copied kubeconfig that disables TLS verification because of an outdated CA bundle. What underlying Kubernetes behavior is most relevant to this technical decision?
Explanation
Correct Answer
The situation is that a research laboratory has a copied kubeconfig that disables TLS verification because of an outdated CA bundle. TLS establishes endpoint confidentiality and identity, while authentication and RBAC separately determine which API operations a caller may execute. It supports this action: Require verified API server certificates, properly scoped identities and audit policy rather than turning off certificate checks for convenience. To confirm, with synthetic users verify a trusted API connection, denied privilege escalation and appropriate audit entries for failed requests.
Incorrect Answers
That statement explains the distinct objective “Verify CoreDNS resolution and namespace-qualified Service names” rather than the cause in this case. The deciding mechanism here is that TLS establishes endpoint confidentiality and identity, while authentication and RBAC separately determine which API operations a caller may execute.
That statement explains the distinct objective “Separate multi-tenant namespace governance from actual isolation guarantees” rather than the cause in this case. The deciding mechanism here is that TLS establishes endpoint confidentiality and identity, while authentication and RBAC separately determine which API operations a caller may execute.
That statement explains the distinct objective “Distinguish Deployment desired state from a manually created Pod” rather than the cause in this case. The deciding mechanism here is that TLS establishes endpoint confidentiality and identity, while authentication and RBAC separately determine which API operations a caller may execute.
Question 578
A research laboratory has a copied kubeconfig that disables TLS verification because of an outdated CA bundle. What acceptance check most directly confirms this requirement is met?
Explanation
Correct Answer
The situation is that a research laboratory has a copied kubeconfig that disables TLS verification because of an outdated CA bundle. With synthetic users verify a trusted API connection, denied privilege escalation and appropriate audit entries for failed requests. This is the relevant test because TLS establishes endpoint confidentiality and identity, while authentication and RBAC separately determine which API operations a caller may execute.
Incorrect Answers
The situation is that a research laboratory has a copied kubeconfig that disables TLS verification because of an outdated CA bundle. 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, with synthetic users verify a trusted API connection, denied privilege escalation and appropriate audit entries for failed requests.
This check would help evaluate the distinct objective “Understand PersistentVolumeClaim binding to persistent storage resources”, but not the required result. For this case, with synthetic users verify a trusted API connection, denied privilege escalation and appropriate audit entries for failed requests.
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, with synthetic users verify a trusted API connection, denied privilege escalation and appropriate audit entries for failed requests.
Question 579
A research laboratory has a copied kubeconfig that disables TLS verification because of an outdated CA bundle. The team suggests: “Set insecure-skip-tls-verify for every cluster client and reuse one administrator token across automated jobs.” Which failure should the reviewer anticipate?
Explanation
Correct Answer
The situation is that a research laboratory has a copied kubeconfig that disables TLS verification because of an outdated CA bundle. Clients may connect to an impersonated API endpoint and the token could grant excessive permissions. The shortcut creates this risk because TLS establishes endpoint confidentiality and identity, while authentication and RBAC separately determine which API operations a caller may execute.
Incorrect Answers
That outcome concerns the distinct objective “Use nodeSelector to place a workload on nodes with required labels”; it is not the most direct consequence of this shortcut. The relevant consequence is that clients may connect to an impersonated API endpoint and the token could grant excessive permissions.
That outcome concerns the distinct objective “Use Events and pod describe for failed volume mounting”; it is not the most direct consequence of this shortcut. The relevant consequence is that clients may connect to an impersonated API endpoint and the token could grant excessive permissions.
The situation is that a research laboratory has a copied kubeconfig that disables TLS verification because of an outdated CA bundle. 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 clients may connect to an impersonated API endpoint and the token could grant excessive permissions.
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?
Explanation
Correct Answer
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
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.
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.
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.
Kubernetes and Cloud Native Associate (KCNA) Practice Tests
- Linux Foundation KCNA Practice Test 56 - 10 Questions (Last Reviewed 26-Sep-2026)
- Linux Foundation KCNA Practice Test 57 - 10 Questions (Last Reviewed 21-Nov-2026)
- Linux Foundation KCNA Practice Test 58 - 10 Questions (Last Reviewed 20-Nov-2026)
- Linux Foundation KCNA Practice Test 59 - 10 Questions (Last Reviewed 19-Nov-2026)
- Linux Foundation KCNA Practice Test 60 - 10 Questions (Last Reviewed 18-Nov-2026)