A configuration file in a deployed app needs to be directly edited. Which steps would ensure a successful deployment to clients?

Question

Options

• AMake the change in $SPLUNK HOME/etc/dep10yment apps/$appName/10ca1/ on the
• BMake the change in $SPLUNK HOME /etc/apps/$appname/local/ on any of the deployment
• CMake the change in $SPLUNK HOME/etc/dep10yment apps/$appName/10ca1/ on the
• DMake the change in $SPLUNK HOME/etc/apps/$appName/defau1t on the deployment server,

• A
  12% (6)
• B
  4% (2)
• C
  78% (40)
• D
  6% (3)

Explanation

To customize a configuration file, you need to create a new file with the same name in a local or app directory. Then, add the specific settings that you want to customize to the local configuration file. Never change or copy the configuration files in the default directory. The files in the default directory must remain intact and in their original location. The Splunk Enterprise upgrade process overwrites the default directory. To deploy configuration files to deployment clients, you need to use the deployment server. The deployment server is a Splunk Enterprise instance that distributes content and updates to deployment clients. The deployment server uses a directory called $SPLUNK_HOME/etc/deployment-apps to store the apps and configuration files that it deploys to clients. To update the configuration files in this directory, you need to edit them manually and then run the command $SPLUNK_HOME/bin/sp1unk reload deploy--server to make the changes take effect.

No community discussion yet for this question.