CrowdStrike Falcon Certification Program Changed CCFA-200b Questions

The No Action option is assigned when an administrator wants to save the IOC for future use but does not want Falcon to take an enforcement or detection action at that time. In IOC Management, hash indicators can be assigned actions such as Block, Detect Only, Allow, or None/No Action. Block prevents the hash and can show it as a detection when the required prevention policy setting is enabled. Detect Only generates a detection but takes no prevention action. Allow adds the hash to the allowlist and suppresses detection for that indicator. No Action is different from all three: it retains the indicator in IOC Management without blocking it, allowing it, or generating a detection. This is useful when an indicator is being staged, tracked, reviewed, or retained for future activation after validation. It is not an allowlist or blocklist action. Reference topics: Rule Configuration, Custom IOCs, IOC Management Actions, Hash Indicator Handling.

The default role that allows viewing all analyst session details is Falcon Administrator . RTR-specific roles allow users to perform or view their own RTR activities according to their level, but the Falcon Administrator has broader administrative visibility across the CID, including all RTR session details. The RTR Administrator role has elevated RTR execution and script/file capabilities, but the course guide distinguishes complete administrative session visibility from RTR execution authority. Falcon Security Lead and RTR Read-Only Analyst do not provide all analyst session detail visibility. This separation is important because Falcon uses roles to distinguish operational response permissions from audit and administrative oversight. The correct default role for all-session visibility is Falcon Administrator.

IP addresses are added to a containment policy to allow contained hosts to communicate with specific trusted resources during network containment. Network containment isolates the host to reduce attacker movement while maintaining required Falcon cloud communication. Organizations may need contained hosts to access patch servers, update sources, remediation infrastructure, domain services, or other tightly controlled internal systems. The purpose is not to automate containment based on IP address; automation is handled through workflows. Analyst permissions are controlled by user roles, not containment policy IP entries. Falcon console access is unrelated because containment policy applies to endpoint network communication, not administrative access to the web console. The course guide explicitly connects containment-policy IP allowances with patching and controlled access during containment.

Falcon user accounts must be created using an email address from the approved domains configured for the CID. This ensures that account creation is limited to authorized organizational identity domains and reduces the risk of adding unauthorized external users. New users are not automatically assigned the Falcon Analyst role by default; roles must be assigned according to operational need. Employee identification numbers and domain-number prefixes are not Falcon account requirements. The CCFA user management topic emphasizes identity governance, approved domains, role assignment, and least privilege. Falcon Administrators create users, assign appropriate roles, and ensure that access aligns with approved organizational identity controls. Therefore, the approved-domain email requirement is the correct statement.