Load balancing on a Universal Forwarder is not scaling correctly. The forwarder's outputs. and the tcpout stanza are setup correctly. What else could be the cause of this scaling issue? (select all…

The correct answer is A. The receiving port is not properly setup to listen on the right port. C. The DNS record used is not setup with a valid list of IP addresses. The possible causes of the load balancing issue on the Universal Forwarder are A and C. The receiving port and the DNS record are both factors that affect the ability of the Universal Forwarder to distribute data across multiple receivers. If the receiving port is not properly…

Splunk Forwarding

Question

Load balancing on a Universal Forwarder is not scaling correctly. The forwarder's outputs. and the tcpout stanza are setup correctly. What else could be the cause of this scaling issue? (select all that apply)

Options

AThe receiving port is not properly setup to listen on the right port.
BThe inputs . conf'S _SYSZOG_ROVTING is not setup to use the right group names.
CThe DNS record used is not setup with a valid list of IP addresses.
DThe indexAndForward value is not set properly.

How the community answered

(46 responses)

A
78% (36)
B
15% (7)
D
7% (3)

Explanation

The possible causes of the load balancing issue on the Universal Forwarder are A and C. The receiving port and the DNS record are both factors that affect the ability of the Universal Forwarder to distribute data across multiple receivers. If the receiving port is not properly set up to listen on the right port, or if the DNS record used is not set up with a valid list of IP addresses, the Universal Forwarder might fail to connect to some or all of the receivers, resulting in poor load

Topics

#Universal Forwarder#Load Balancing#Forwarder Troubleshooting#DNS

Community Discussion

No community discussion yet for this question.

Full SPLK-1003 Practice