A monitor has been defined using the HTTP monitor template. The send and receive strings were customized, but all other settings were left at their defaults. Which resources can the monitor be assigne

Restricting assignment to only specific pool members is unnecessarily narrow - an HTTP monitor can be assigned broadly to pools, which then propagate health checking to their members.

Monitors are not assigned directly to virtual servers in BIG-IP; they are assigned to pools, pool members, or nodes to track backend resource health.

While monitors can technically be assigned to nodes, an HTTP monitor sends application-layer HTTP requests and is purpose-built for pool-level assignment where backends serve HTTP traffic, not for general node-level monitoring.

HTTP monitors are designed to be assigned at the pool level, where they check the health of pool members collectively. Customizing only the send and receive strings does not restrict the monitor from being used on most pools that serve HTTP traffic. The default interval, timeout, and other settings remain valid for general HTTP pool health checking.