Which of the following is a risk of using the Auto Deployment feature of Distributed Configuration Management to distribute indexes.conf?
Which of the following is a risk of using the Auto Deployment feature of Distributed Configuration Management to distribute indexes.conf?
One risk of using the Auto Deployment feature in Distributed Configuration Management to distribute indexes.conf is that indexers might crash. Distributing configuration files like indexes.conf can cause issues if the configuration includes errors or if the indexers are unable to handle the new settings properly. An incorrect or poorly tested configuration might lead to the indexers becoming unstable, potentially causing crashes.
I believe D is the right answer
Hi Kerb, Could you please explain briefly how D is correct NOT A. I also have doubts A is no way correct.
I think D is the right answer https://community.splunk.com/t5/Splunk-Enterprise-Security/Splunk-Enterprise-Security-requires-a-deployment-client-but/m-p/279749
D is correct
Vote for D
Friends, could you please confirm this answer?
A risk of using the Auto Deployment feature of Distributed Configuration Management to distribute indexes.conf is that indexers might not be reachable. If an indexer is not reachable during the deployment, it may not receive the updated configurations, leading to inconsistencies in the environment.