How can a Malware profile be configured to prevent a specific executable from being uploaded to the cloud?

Question

Options

• ADisable on-demand file examination for the executable
• BSet PE and DLL examination for the executable to report action mode
• CAdd the executable to the allow list for executions
• DCreate an exclusion rule for the executable

• A
  7% (2)
• B
  3% (1)
• C
  3% (1)
• D
  87% (26)

Explanation

D is correct because an exclusion rule in a Malware profile is the dedicated mechanism for scoping which files are subject to specific security actions - including cloud submission for analysis. By creating an exclusion rule targeting the executable, you explicitly remove it from the cloud upload workflow while leaving other profile settings intact.

Why the distractors are wrong:

• A - Disabling on-demand file examination affects when scanning occurs, not whether the file gets uploaded to the cloud. The two functions are independent.
• B - Setting PE/DLL examination to "report" mode means findings are logged but actions are not blocked; the file can still be submitted to the cloud.
• C - Allow-listing an executable controls whether it is permitted to run, not whether it gets uploaded. Execution permission and cloud upload are separate pipeline stages.

Memory tip: Match the verb to the goal. You want to exclude the file from a process → use an exclusion rule. Allow lists govern execution, report mode governs alerting, and on-demand settings govern scan triggers - none of those touch the upload path directly.

No community discussion yet for this question.