A Behavior is a set of rules that determines which MID Servers launch which types of probes during a Discovery1. It can be assigned to a Discovery IP Range, which is a range of IP addresses that Discovery scans for CIs2. By using the Behavior drop-down menu on a Discovery IP Range, one can control how Discovery behaves for each IP address in that range3. The other options are not related to using a Behavior for discovery. The MID Server selection method on a Discovery Schedule is a way to specify which MID Servers are eligible to run Discovery for a given schedule4. The Behavior drop-down menu on a Discovery Status is a way to filter the Discovery Status records by the Behavior used. The Behavior checkbox on a CI is a way to indicate whether the CI was discovered using a Behavior or not.
1: Discovery behaviors 2: Discovery IP ranges 3: Assign a behavior to an IP range 4: MID Server selection method : Discovery Status : Behavior field on the cmdb_ci table Reference: https://docs.servicenow.com/bundle/paris-it-operations-management/page/product/discovery/task/ create-disco-behavior.html

The Set Parameter Value operation is used to assign a value to a variable in a Discovery pattern1. The syntax for this operation is as follows2:
Set Parameter Value: <Variable Name> = <Value>
The <Value> can be either a constant or an expression. To declare a constant, unchanging value, one must use quotes around the value. For example2:
Set Parameter Value: $name = "John"
This assigns the string "John" to the variable $name. The quotes indicate that the value is a constant and will not change. The other options, hash tag, brackets, and dollar sign, are not used to declare a constant value.
They have different meanings in the syntax of the Set Parameter Value operation. A hash tag (#) is used to indicate a comment2. Brackets ([]) are used to access an element of an array or a map2. A dollar sign

The functionality shown in the image is related to the Tracked Configuration files feature of ServiceNow Discovery. This feature allows Discovery to track changes in configuration files on Windows and Unix hosts and store them as configuration items (CIs) in the CMDB1. To modify this functionality, such as adding or removing files to track, changing the file attributes to capture, or defining the CI relationships, one needs to edit the Discovery Pattern that is associated with the Tracked Configuration files classifier2. A Discovery Patternis a series of operations that tell Discovery how to find and identify an application or a configuration file on a host3.
:
1: Tracked Configuration files - Product Documentation: San Diego - ServiceNow
2: Tracked Configuration files pattern - Product Documentation: San Diego - ServiceNow
3: Patterns and horizontal discovery - Product Documentation: Tokyo - ServiceNow

A classifier is a set of rules that identifies a device type based on the results of a probe. A classifier can have one or more related lists that define the classification criteria, the pattern probes, and the triggers probes. The pattern probes related list specifies which horizontal discovery pattern to run for the device type. The triggers probes related list specifies which probes to run after the device is classified, and before the horizontal discovery pattern is executed. The triggers probes can be used to gather additional information or credentials that are needed for the horizontal discovery pattern12.
:
1: ServiceNow Discovery Overview, page 9
2: ServiceNow Discovery Documentation, Classifiers section

The recommended method for excluding specific software from discovery on Windows and Unix Servers in ServiceNow Discovery is by modifying the probes. Probes are the components in ServiceNow that collect data from devices. By modifying the probes, specific software can be excluded from the discovery process.
Options A, C, and D are less direct methods for achieving this specific requirement.References= ServiceNow Discovery documentation, particularly in the sections related to probe configuration and modification.