Endpoint Discover scanning stops when the DLP agent cannot send a status report within what period?

Endpoint Discover scanning stops when the DLP agent cannot send a status report within what period?

• A. When the device loses network connectivity
• B. When the agent is unable to send a status report within the Scan Idle Timeout period
• C. When the policy is changed
• D. When the disk space is low

Answer: (B)

Endpoint Discover relies on the agent regularly reporting its status to the DLP server as it scans. If the agent cannot deliver a status report within the configured Scan Idle Timeout period, the scanning process stops. This timeout keeps resources from being wasted on a scan that isn’t being monitored or communicating properly, and it flags a potential connectivity or server issue for investigation. Losing network connectivity would ultimately prevent status reports, but the stopping rule is specifically tied to exceeding the Scan Idle Timeout. Changes to the policy or low disk space can affect operation in other ways, but they are not the defined trigger for stopping the scan.

Endpoint Discover relies on the agent regularly reporting its status to the DLP server as it scans. If the agent cannot deliver a status report within the configured Scan Idle Timeout period, the scanning process stops. This timeout keeps resources from being wasted on a scan that isn’t being monitored or communicating properly, and it flags a potential connectivity or server issue for investigation.

Losing network connectivity would ultimately prevent status reports, but the stopping rule is specifically tied to exceeding the Scan Idle Timeout. Changes to the policy or low disk space can affect operation in other ways, but they are not the defined trigger for stopping the scan.