What is a key requirement for deploying the CrowdStrike Kubernetes Admission Controller to monitor and secure Kubernetes workloads?

Option A: The CrowdStrike Kubernetes Admission Controller uses the MutatingAdmissionWebhook to

intercept and modify requests to the Kubernetes API server. This webhook allows the controller to

enforce security policies and inject the required sensor configurations into pods at creation time. Ensuring

the MutatingAdmissionWebhook configuration is enabled is a critical setup step for proper functionality.

Option B: The Admission Controller does not require root-level or privileged permissions. It relies on

webhook functionality to perform its operations and does not interact directly with host-level resources.

20/192

Option C: While namespaces are often used for logical organization, the Admission Controller does not

necessarily require a dedicated namespace. It can be deployed in any namespace, depending on the user’s

configuration p

.

Option D: The Admission Controller is not deployed as a DaemonSet; instead, it operates as a webhook

server integrated with the Kubernetes API server. DaemonSets are typically used for agents that need to

run on every node, such as logging or monitoring tools.