Online Access Free KCSA Practice Test

In the event that kube-proxy is in a CrashLoopBackOff state, what impact does it have on the Pods running on the same worker node?

• A.The Pod's security context restrictions cannot be enforced.
• B.The Pods cannot communicate with other Pods in the cluster.
• C.The Pod cannot mount persistent volumes through CSI drivers.
• D.The Pod's resource utilization increases significantly.

What information is stored in etcd?

• A.Sensitive user data such as usernames and passwords.
• B.Etcd manages the configuration data, state data, and metadata for Kubernetes.
• C.Pod data contained in Persistent Volume Claims (e.g. hostPath).
• D.Application logs and monitoring data for auditing and troubleshooting purposes.

Given a standard Kubernetes cluster architecture comprising a single control plane node (hosting bothetcdand the control plane as Pods) and three worker nodes, which of the following data flows crosses atrust boundary
?

• A.From kubelet to API Server
• B.From kubelet to Container Runtime
• C.From API Server to Container Runtime
• D.From kubelet to Controller Manager

A container running in a Kubernetes cluster has permission to modify host processes on the underlying node.
What combination of privileges and capabilities is most likely to have led to this privilege escalation?

• A.There is no combination of privileges and capabilities that permits this.
• B.hostPID and SYS_PTRACE
• C.hostNetwork and NET_RAW
• D.hostPath and AUDIT_WRITE

In a Kubernetes cluster, what are the security risks associated with using ConfigMaps for storing secrets?

• A.ConfigMaps store sensitive information in etcd encoded in base64 format automatically, which does not ensure confidentiality of data.
• B.Storing secrets in ConfigMaps can expose sensitive information as they are stored in plaintext and can be accessed by unauthorized users.
• C.Using ConfigMaps for storing secrets might make applications incompatible with the Kubernetes cluster.
• D.Storing secrets in ConfigMaps does not allow for fine-grained access control via RBAC.