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.

Option A: Running assessments only after significant changes leaves security gaps during periods of no updates. Regular, automated assessments are necessary for comprehensive security monitoring.
Option B: Weekly assessments may suffice for static or less critical environments, but they are inadequate for dynamic production environments where daily updates are crucial for maintaining security posture.
Option C: Running assessments every 30 minutes is overly frequent for most use cases and can increase operational costs without providing significant added value. This frequency may be justified only in environments with extremely high change rates.
Option D: Daily assessments strike a balance between timely security posture updates and cost efficiency, especially in dynamic production environments where changes occur regularly but not continuously.

Option A: Unauthorized API calls are typically detected and alerted by audit logging or monitoring solutions, not Admission Controller policies.
Option B: While Falcon Cloud Security does monitor network traffic, this is not related to Kubernetes Admission Controllers. Network monitoring is handled by different components or tools such as service mesh or network policies.
Option C: Scanning container images for vulnerabilities is a separate functionality provided by container security tools but not directly related to Admission Controller policies.
Option D: Kubernetes Admission Controllers intercept and validate API requests before they are persisted to the etcd store, allowing policies to enforce security and configuration requirements during resource creation or updates. This is exactly the purpose of creating such policies in Falcon Cloud Security.

Option A: This is incorrect because CrowdStrike's IP addresses for image assessment are distinct from general regional data center IPs. Using only regional data center IPs will not enable the image assessment functionality.
Option B: This is incorrect because CrowdStrike services require external IP addresses for communication. Internal IP addresses are irrelevant to enabling CrowdStrike's image assessment functionality.
Option C: This is incorrect because adding CrowdStrike IP addresses to the denylist would block their access, making image assessments impossible. Allowlisting is the correct approach.
Option D: This is correct because CrowdStrike publishes specific IP addresses that its services use to communicate with container registries for image assessments. These IP addresses must be added to the allowlist of the container registry to permit scanning activities without interruption.

Option A: This is incorrect because detecting malware and ransomware is the primary role of Falcon Endpoint Protection, not Falcon Horizon. Endpoint detection and response (EDR) features are distinct from the cloud-native security provided by Horizon.
Option B: This answer is correct because the Falcon Horizon module is specifically designed for cloud-native environments. It provides visibility into cloud configurations, detects misconfigurations, and ensures compliance with cloud security standards. It is focused on protecting modern cloud workloads, including containers and serverless architectures.
Option C: This is incorrect because Falcon Horizon does not operate at the email gateway level.
Blocking phishing attempts is typically a function of email security solutions, not cloud-native security tools.
Option D: This is incorrect because data encryption for transit is typically handled by network security protocols like TLS, and it is not a primary feature of the Falcon Horizon module.