Option A: This is the correct answer because pre-configured compliance report templates are designed to align with industry standards and include relevant data, such as security events, configurations, and compliance status. They save time and ensure completeness.
Option B: Endpoint protection is important but insufficient for a cloud-focused compliance report.
Cloud workload security metrics and compliance details are also essential.
Option C: While feasible, this method is time-consuming, prone to errors, and inefficient compared to leveraging the built-in reporting capabilities of CrowdStrike Falcon.
Option D: Focusing solely on failed login attempts overlooks other critical aspects, such as detections, vulnerabilities, and workload protection, which are essential for comprehensive compliance reporting.

Option A: While "read-only" permissions reduce risk, this blanket approach might hinder required operations if the account needs more specific access. Permissions should match the actual usage needs.
Option B: Using shared accounts violates best practices for identity and access management (IAM). Shared accounts obscure accountability and increase the risk of privilege misuse.
Option C: Deleting permissions without assessing operational needs can disrupt workflows and lead to unintended downtime. A more measured approach is required.
Option D: The best approach to mitigate risks is to reduce the account's permissions to only what is necessary for its current activities. This minimizes the potential for misuse or exploitation while maintaining operational functionality.

Option A: RBAC is a critical requirement for deploying the Kubernetes protection agent. It ensures that the agent has the necessary permissions to monitor and protect the cluster effectively. Without proper RBAC configuration, the agent cannot access required resources or enforce security policies.
Option B: While enabling Kubernetes audit logs is a good practice for security monitoring, it is not a substitute for configuring the Kubernetes protection agent. The agent requires additional setup to monitor and protect workloads effectively.
Option C: Granting full administrative privileges to all service accounts violates the principle of least privilege and increases the attack surface. The agent requires specific permissions, which can be granted using RBAC without over-provisioning access.
Option D: Installing the agent directly on individual containers is not how the Kubernetes protection agent operates. The agent is deployed at the node level or via DaemonSet to monitor containerized workloads across the cluster.

Option A: The primary function of the Falcon Container Sensor is to monitor container runtime activity, identify anomalies, and detect potential threats or malicious behavior.
Option B: The Falcon Container Sensor does not control pod scaling. Kubernetes itself handles scaling based on resource usage, not security threats.
Option C: The sensor does not encrypt data in Persistent Volumes. Data encryption is managed by the storage provider or Kubernetes itself, not by the Falcon Container Sensor.
Option D: The Falcon Container Sensor is not responsible for deploying application code. It focuses on securing containerized workloads rather than application delivery.