KCSA: Kubernetes and Cloud Native Security Associate
KCSA: Kubernetes and Cloud Native Security Associate practice questions, page 3 of 5, with answer review and explanations.
Question 11
How does the kube-proxy forward traffic to a Pod based on its Service configuration?
The kube proxy configures eBPF on the node to forward traffic from the Service to the Pod
The kube proxy implements a virtual IP mechanism for Services (e.g., via iptables).
The kube proxy injects multiple A records in the CoreDNS Pod for each Service.
The kube-proxy injects reverse proxy configuration in the Ingress Controller (e.g., nginx).
Question 12
What does the 'cluster-admin' ClusterRole enable when used in a RoleBinding?
It gives full control over every resource in the cluster and in all namespaces.
It gives full control over every resource in the role binding's namespace, not including the namespace object for isolation purposes.
It gives full control over every resource in the role binding's namespace, including the namespace itself.
It allows read/write access to most resources in the role binding's namespace. This role does not allow write access to resource quota, to the namespace itself, and to EndpointSlices (or Endpoints).
Question 13
What mechanism can I use to block unsigned images from running in my cluster?
Using PodSecurityPolicy (PSP) to enforce image signing and validation
Using Pod Security Standards (PSS) to enforce validation of signatures.
Configuring Container Runtime Interface (CRI) to enforce image signing and validation.
Enabling Admission Controllers to validate image signatures.
Question 14
Which technology can be used to apply security policy for internal cluster traffic at the application layer of the network?
Network Policy
Service Mesh
Container Runtime
Ingress Controller
Question 15
How do Kubernetes namespaces impact the application of policies when using Pod Security Admission?
The default namespace enforces the strictest security policies by default.
Different policies can be applied to specific namespaces.
Each namespace can have only one active policy.
Namespaces are ignored; Pod Security Admission policies apply cluster-wide only.