What is the primary role of the Kubernetes Admission Controller in relation to the CrowdStrike Kubernetes and Container Sensor?

Question

Options

• ATo analyze and enforce policies on API requests to the Kubernetes cluster before they are
• BTo manage container image scanning and vulnerability assessments within Kubernetes clusters.
• CTo collect and report telemetry data from running Kubernetes workloads to the CrowdStrike Falcon
• DTo deploy the CrowdStrike Kubernetes and Container Sensor as a sidecar to each pod.

• A
  80% (20)
• B
  4% (1)
• C
  4% (1)
• D
  12% (3)

Explanation

Option A: The Kubernetes Admission Controller is a core Kubernetes feature that intercepts API requests to the Kubernetes cluster and applies policies before they are persisted. CrowdStrike leverages this capability to enforce security controls, such as validating configurations and applying runtime policies, before workloads are allowed to run in the cluster. This ensures that malicious or misconfigured deployments are blocked at the admission stage. Option B: While container image scanning is essential for security, this is not the function of the Admission Controller. Image scanning is typically handled by other tools or services integrated with CI/CD pipelines. Option C: This describes the function of the CrowdStrike Kubernetes and Container Sensor, not the Kubernetes Admission Controller. The Admission Controller operates at the API server level, not at the runtime monitoring level. Option D: Deployment of the sensor is handled by separate installation processes and configurations. The Admission Controller is unrelated to deploying sidecar containers.

No community discussion yet for this question.