Free CrowdStrike CCFR-201b Practice Exam with Questions & Answers | Set: 3

The correct navigation path is Actions > Connect to host. In Falcon, responders commonly initiate live response actions directly from the detection or host context using the Actions menu. This allows an authorized responder to start a Real Time Response session for hands-on investigation, artifact collection, command execution, and remediation. “Investigate > Connect to host” is not the direct path shown for this detection-driven workflow. “View Incident > Connect to host” is also incorrect because the task is to remotely connect to the affected host from the detection context, not simply open the incident view. The key requirement is permission-based RTR access; without the correct role and response policy permissions, the connection option may not be available.

The correct fix is to set the -timeout argument to a longer period. Custom remediation scripts can take longer than expected, especially when they enumerate files, remove persistence entries, clean adware components, or wait for operating-system operations to complete. If the script is valid but exceeds the default execution window, extending the timeout gives RTR enough time to complete the task. Setting timeout to “off” is not the correct approach because response commands should still have controlled execution limits. Simply rerunning the script may reproduce the same timeout failure. Changing a console-wide timeout policy is unnecessary when the command-level timeout argument can solve the issue directly. In RTR remediation, tuning execution parameters is often required for longer-running scripts.