A site wishes to use an external monitor. Other than what is coded in the monitor script, what information must be configured on the BIG-IP for the monitor to be functional? (Choose two.)

The BIG-IP services running on the monitored system are not configured on BIG-IP itself - determining what to probe is the responsibility of the script logic, not a separate BIG-IP configuration parameter.

The IP address and port of the monitored node are automatically passed to the external script at runtime via environment variables ($NODE_IP and $NODE_PORT) and do not require explicit configuration outside the monitor assignment.

The monitor must be associated with a specific node or pool member so BIG-IP knows which object to mark up or down based on the script's exit code - without this association BIG-IP has no target to apply the health status to.

BIG-IP must be configured with the filename and path of the external monitor script so it knows which program to execute during each monitor interval, as this is a required field in the external monitor object configuration.

The function or behavior the program tests is entirely determined by the script code itself and is not a configurable parameter in the BIG-IP external monitor object.