When an identity-based detection is determined to be afalse positive, Falcon Identity Protection allows administrators to take corrective action usingexceptions. According to the CCIS curriculum, exceptions are the mechanism by which detections can be suppressed for specific entities or conditions without disabling the detection entirely.
Exceptions are configured from theDetection detailsview and are intended to handle known, acceptable behavior that would otherwise continue to trigger detections. This allows security teams to reduce noise while maintaining visibility into true threats. Exceptions are especially valuable in environments with complex authentication patterns or legacy configurations.
The other options are incorrect:
* Exitsare not a detection control mechanism.
* Remediationsrefer to corrective actions, not suppression logic.
* Recommendationsprovide guidance but do not change detection behavior.
By usingexceptions, Falcon ensures that false positives are handled in a controlled and auditable way, aligning with best practices outlined in the CCIS material. Therefore,Option Cis the correct answer.

To retrieve identity-based detections and incident-related data using the CrowdStrike APIs, the API key must include the correctpermission scope. According to the CCIS curriculum, theIdentity Protection Detections scope is required to access identity-based detection and incident information through GraphQL.
This scope allows API queries to retrieve:
* Identity-based detections
* Associated incident metadata
* Detection attributes such as severity, status, and related entities
Incident data in Falcon Identity Protection isderived from detections, making the Detections scope the authoritative permission set for this information. Without this scope, GraphQL queries related to identity detections and incidents will fail authorization.
The other scopes are either too narrow or unrelated to detection retrieval. Therefore,Option Ais the correct and verified answer.

Falcon Identity Protection is architected as alog-free identity security platform, a core tenet emphasized throughout the CCIS curriculum. Unlike traditional SIEM- or log-based solutions, Falcon Identity Protection doesnot require string-based queriesto continuously assess identity events or associate them with threats.
Instead, the platform relies onmachine-learning-powered detection rules,real-time authentication traffic inspection, andAPI-based connectorsto collect and analyze identity telemetry directly from domain controllers and identity providers. This approach eliminates the operational complexity of building, tuning, and maintaining query logic.
String-based queries are commonly associated with legacy log aggregation tools and SIEM platforms, where analysts must manually search logs to identify suspicious behavior. Falcon Identity Protection replaces this model withbehavioral baselining and automated correlation, enabling continuous identity risk assessment without human-driven query execution.
Because Falcon does not require string-based queries to operate,Option Dis the correct and verified answer.

Falcon Identity Protection establishes auser baselineby observing authentication behavior over time, including login frequency, endpoints used, access patterns, and protocol usage. According to the CCIS curriculum, Falcon typically requiresapproximately one weekof consistent activity to develop an initial, reliable baseline for a user.
This baseline allows Falcon to distinguish normal behavior from anomalies and to calculate accurate risk scores. While the baseline continues to mature over time and becomes more precise with additional data, the first usable behavioral model is generally formed within a week.
Longer timeframes such as one or three months are not required to begin detecting abnormal behavior.
Conversely, periods shorter than a week may not provide sufficient behavioral data to accurately model normal usage patterns.
Because Falcon can rapidly establish a functional baseline while continuously refining it,Option C (One week)is the correct and verified answer.

Within Falcon Identity Protection,Predefined Reportsallow administrators to generate standardized reports based on specific data subjects. TheSubject dropdowndetermines the type of data the report will be built from, such as identity risks, authentication activity, or endpoint-related telemetry.
The category associated withendpointsin the Subject dropdown isEvents. Endpoint-related data-such as authentication attempts, logons, protocol usage, and domain controller-observed activity-is captured and represented aseventswithin Falcon. These events form the foundational telemetry used for identity detections, investigations, and reporting.
By contrast:
* Insightsrepresent aggregated analytical findings derived from events.
* Incidentsgroup multiple detections into a single investigative narrative.
* Accountsfocus on identity entities such as users and service accounts.
Endpoint visibility in reporting is therefore tied directly toEvents, as events reflect the raw and enriched activity observed on endpoints and domain controllers. This structure aligns with Falcon's identity-first security model, where endpoint-observed authentication behavior feeds identity risk scoring and Zero Trust decisions.
The CCIS curriculum explicitly associatesendpoint-related reportingwith theEventssubject, makingOption Bthe correct and verified answer.