Which of the following is a good practice for a search head cluster deployer?
Which of the following is a good practice for a search head cluster deployer?
The deployer must be used to distribute non-replicable configurations to search head cluster members. This practice ensures that configurations that are not intended to be replicated across the cluster are properly distributed, maintaining consistency and avoiding configuration conflicts.
My answer is B
Absolutely, answer A it's not a good practice its a fact.
it is not that it is a bad practice, search heads don't phone deployer...
B - https://docs.splunk.com/Documentation/Splunk/8.1.0/DistSearch/PropagateSHCconfigurationchanges
Answer is B. Explanation: Option A: No, There is no phone home concept with regards to SearchHead DEPLOYER. phone_home is with Search-Head DEPLOYMENT SERVER. Option B: Reference link - https://docs.splunk.com/Documentation/Splunk/9.0.3/DistSearch/PropagateSHCconfigurationchanges It says: "It provides the means to distribute non-replicated, non-runtime configuration updates to all search head cluster members." Option C: No, deployer must NOT be used to distribute configurations to SH cluster members. Option D: The statement is correct, but does not qualify to be a good practice.
The best practice for a search head cluster deployer is: D. The deployer only distributes configurations to search head cluster members with splunk apply shcluster-bundle. A, B, and C, do not accurately reflect best practices: A: Configurations should be pushed by the deployer actively rather than waiting for nodes to "phone home." This ensures timely and consistent distribution. B: The deployer should be used for replicable configurations. Non-replicable configurations, such as user-specific configurations, should be managed locally on each search head. C: The deployer should distribute configurations to ensure they are valid across the entire cluster. Waiting for configurations to become "valid" based on some criteria is not standard practice.
The answer is B, A does not make sense because why would the deployer wait for a phone home when it uses the push mode to push apps to members.
answer is B
B. The deployer must be used to distribute non-replicable configurations to search head cluster members.
I don't understand why the answer is A. Why "Phone Home"?
Answer: B https://docs.splunk.com/Documentation/Splunk/9.1.1/DistSearch/PropagateSHCconfigurationchanges The deployer has these main roles: It handles migration of app and user configurations into the search head cluster from non-cluster instances and search head pools. 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.