What does the deployer do in a Search Head Cluster (SHC)? (Select all that apply.)
What does the deployer do in a Search Head Cluster (SHC)? (Select all that apply.)
The deployer in a Search Head Cluster (SHC) is primarily responsible for distributing apps to SHC members and handling configuration updates that are non-search related and manual. It is used to propagate baseline app configurations and other configuration file changes across the SHC. You do not use the deployer to bootstrap a clean Splunk install for a SHC or to distribute runtime knowledge object changes made by users.
A and C
A and C
You're correct - https://docs.splunk.com/Documentation/Splunk/7.3.2/DistSearch/PropagateSHCconfigurationchanges
"You use the deployer to deploy configuration updates only. You cannot use it for initial configuration of the search head cluster or for version upgrades to the Splunk Enterprise instances that the members run on." From the same link you shared. Only A is correct
"Types of updates that the deployer handles These are the specific types of updates that require the deployer: All non-search-related updates, even those that can be configured through the CLI or Splunk Web, such as updates to indexes.conf or inputs.conf." https://docs.splunk.com/Documentation/Splunk/7.3.2/DistSearch/PropagateSHCconfigurationchanges#Types_of_updates_that_the_deployer_handles
Only A seems correct. It deploys baseline app configurations to search head cluster members. It provides the means to distribute non-replicated, non-runtime configuration updates to all search head cluster members. Does not copy any manual changes to other SHC
This is the way
A and D.
Only A is correct. B is just to confuse you by the word "bootstrap" C is incorrect, because "You do not use the deployer to distribute search-related runtime configuration changes." Ref: https://docs.splunk.com/Documentation/Splunk/latest/DistSearch/PropagateSHCconfigurationchanges#:~:text=You%20do%20not%20use%20the%20deployer%20to%20distribute%20search%2Drelated%20runtime%20configuration%20changes D is incorrect too. It distributes non-runtime configuration updates. Ref: https://docs.splunk.com/Documentation/Splunk/latest/DistSearch/PropagateSHCconfigurationchanges#Which_configurations_does_the_deployer_manage.3F:~:text=non%2Druntime%20configuration
A and C, you can make manual config changes to your Search ahead cluster, like make your web.conf file to allow https for web ui
https://docs.splunk.com/Documentation/Splunk/8.1.0/DistSearch/PropagateSHCconfigurationchanges