What capability does the Kubernetes Admission Controller provide within CrowdStrike Falcon Cloud Security?

Question

Options

• ASchedules container scans
• BBlocks or allows container deployments based on policy
• CEncrypts data in motion
• DMonitors IAM user behavior

• A
  6% (2)
• B
  91% (29)
• C
  3% (1)

Explanation

Kubernetes Admission Controllers act as gatekeepers that intercept API requests to the Kubernetes cluster before objects are persisted, making them the ideal enforcement point for security policies - CrowdStrike Falcon leverages this to block or allow container deployments based on image assessment results (e.g., whether an image has critical vulnerabilities or passes registry trust checks).

Why the distractors are wrong:

• A (Schedules container scans): Scanning is handled by the image assessment pipeline, not the Admission Controller - the Controller acts on scan results, it doesn't trigger them.
• C (Encrypts data in motion): Encryption is a network/TLS concern entirely outside the Admission Controller's scope.
• D (Monitors IAM user behavior): IAM monitoring is a CSPM/CIEM function, not a Kubernetes Admission Controller function.

Memory tip: Think of the Admission Controller as a bouncer at a club door - it checks credentials (policy) and decides who gets in (deploy) or gets turned away (block) before they enter, not after.

No community discussion yet for this question.