Each dependent item must have its own unique master item when low-level discovery is used with dependent items

The same master item can be used for both data collection and low-level discovery

At least two separate master items are required, one for data collection and one for discovery

It defines the visible name for the host

It is used for action filters during the host auto-registration process

It defines the host's color in dashboard widgets

It populates the 'Type' field in the hosts inventory

Proxy group manager process on Zabbix server assigns hosts to the proxies with the smallest number of assigned hosts

Proxy group manager process on Zabbix server assigns hosts to the proxies with the smallest number of NVPS (new values per second)

Proxies in a group will vote who will take the new host. Proxy with less CPU load wins

They are assigned randomly, based on a seed generated by the Zabbix server

Hosts are assigned based on the geographical location of proxies

In alphabetical order

In the order in which they are displayed in the frontend

In a random order generated by a cryptographic hash function

Yes, but only if the Zabbix agent can connect to the Zabbix server. The Zabbix server will redirect the Zabbix agent to the assigned proxy

No, the Zabbix agent must have at least one of the proxies specified in the ServerActive configuration parameter

Yes, the Zabbix agent will send out broadcast messages to its network segment to detect proxies in the proxy group

No, exceeding the timeout in the Zabbix agent configuration file will terminate the data collection

Yes, the timeout in the Zabbix agent configuration file defines only a communication timeout

By using a regular expression in the log item key

By creating an item tag 'log : Failure' in the item configuration

By creating a value map on the host: Failure equals 1

By adding a regular expression preprocessing step in the item configuration