A new forwarder has been installed with a manually created deploymentclient.conf. What is the next step to enable the communication between the forwarder and the deployment server?

Question

Options

• ARestart Splunk on the deployment server.
• BEnable the deployment client in Splunk Web under Forwarder Management.
• CRestart Splunk on the deployment client.
• DWait for up to the time set in the phoneHomeIntervalInSecs setting.

• A
  7% (4)
• B
  2% (1)
• C
  87% (48)
• D
  4% (2)

Explanation

When deploymentclient.conf is manually created or edited on a forwarder, Splunk must be restarted on that deployment client for the configuration to be read and applied. The forwarder only loads configuration files at startup, so it cannot pick up the new deploymentclient.conf settings (including the deployment server address and phoneHomeIntervalInSecs) until a restart occurs. Restarting the deployment server (A) is unnecessary since the server did not change. Option B is incorrect because deployment client settings are configured via conf files, not Splunk Web's Forwarder Management page. Option D is incorrect because the client cannot phone home to a server it has not yet been configured to contact-the configuration is not active until after a restart.

No community discussion yet for this question.