Option A: When creating an image assessment policy, defining the severity levels to flag ensures that only vulnerabilities meeting the specified thresholds are flagged. This configuration allows the policy to effectively prioritize risks and generate actionable insights.
Option B: Audit Mode is for runtime enforcement policies. Image assessment occurs during the CI/CD pipeline or image pull operations and is unrelated to runtime configurations.
Option C: Real-time scanning is unrelated to image assessment policies, as it pertains to runtime protection. Image assessment focuses on pre-deployment scanning, not real-time monitoring.
Option D: Image assessment policies apply to container images and are not limited to namespaces. Namespace-specific configurations are part of runtime or admission policies, not image assessment.

Option A: The primary purpose of scheduled reports is to provide automated security insights, compliance overviews, and periodic monitoring of cloud environments, helping teams proactively manage risks.
Option B: Scheduled reports complement real-time monitoring but do not replace tools like SIEMs, which aggregate and analyze security data continuously.
Option C: Scheduled reports are designed for periodic insights, not for real-time alerting. Real- time alerts are handled by Falcon's detection and response mechanisms, not scheduled reports.
Option D: While security reports provide valuable insights, they do not execute remediation actions directly. Remediation is handled by security teams based on insights from reports.

Option A: Default Falcon registry settings may not cover all organizational needs. Custom configurations should be made to ensure alignment with security policies.
Option B: Allowing all registries without authentication increases security risks, as unauthorized or malicious images can be pulled and deployed.
Option C: To ensure pre-runtime protection, administrators should define registry connection details, specify the registry URL, enable authentication (if needed), and set image scanning policies for security compliance.
Option D: Private repositories are not automatically secure. Vulnerabilities can still exist in private images, making it critical to enable scanning even for internal sources.

Option A: The Falcon Cloud Security Console provides tools to edit existing policies, ensuring that changes are implemented efficiently without creating redundant configurations or policies.
Option B: Falcon Cloud Security does not require exporting and re-importing YAML files for policy updates. Changes are made directly in the console.
Option C: Falcon Cloud Security Admission Controller policies are managed in the Falcon Console, not through Kubernetes ConfigMaps. Disabling and replacing the policy is not the correct approach.
Option D: Deleting and recreating the policy is unnecessary and could introduce downtime or configuration gaps. Editing the policy is more efficient and preserves continuity.

Option A: Kernel-level protections are managed by the CrowdStrike Falcon Container Sensor, not the Admission Controller. The Admission Controller focuses on admission-time security policies rather than runtime protections.
Option B: The Kubernetes Admission Controller intercepts pod creation requests submitted to the Kubernetes API server. It verifies these requests against security policies configured by the CrowdStrike platform, such as ensuring containers include the CrowdStrike Falcon sensor or restricting the use of insecure configurations (e.g., running containers as root). This functionality enforces security at the earliest stage of workload deployment.
Option C: Vulnerability scanning is typically performed by image scanning tools or registry integrations. The Admission Controller does not scan images but ensures security compliance during pod admission.
Option D: Network monitoring and blocking are functions of network security solutions, not the Kubernetes Admission Controller. The Admission Controller focuses solely on admission control.