Configurations from the deployer are merged into which location on the search head cluster member?
Configurations from the deployer are merged into which location on the search head cluster member?
Configurations from the deployer are specifically merged into the default directory of the app on the search head cluster member. This ensures that the deployed settings from the deployer do not overwrite any local or replicated runtime settings that might exist in the /local directory on the members. Therefore, the correct location is SPLUNK_HOME/etc/apps/APP_HOME/default.
My Answer is D
Yes Answer D is correct, there is no way to push an app in /etc/system/local in any push mode options from deployer.
D: https://docs.splunk.com/Documentation/Splunk/9.0.1/DistSearch/PropagateSHCconfigurationchanges#Mode:_merge_to_default
This is the way
D is correct. Deployer merges local and default from its shcluster folder and pushes it to /app/default on the SH cluster members. Captain is the one managing the /local folder.
This is the way!
The Answer is B, https://docs.splunk.com/Documentation/Splunk/8.2.3/DistSearch/PropagateSHCconfigurationchanges " For example, if the default tarball contains a /default directory for appA, that /default directory from the tarball overwrites any /appA/default directory currently on the members" For merge "Each member merges the /local settings that it receives from the captain with the app's /local settings already existing on the member."
correct answer is B - Configurations from the deployer are typically merged into the local directory within the app's configuration directory on the search head cluster member. SPLUNK_HOME/etc/apps/APP_HOME/local is the specific location where local configurations are applied, allowing for customizations at the app level.
On the members Overwrites the existing configuration in the members' /default app directories. No files are deployed to the members' /local app directories. This ensures that deployed settings never overwrite local or replicated runtime settings on the members. Otherwise, for example, app upgrades would wipe out runtime changes.
Can be A and B, but sense deployer is use to deploy apps the changes will be marge in app/local
This is not the way! D. SPLUNK_HOME/etc/apps/APP_HOME/default
The configurations from the deployer are merged into location A: SPLUNK_HOME/etc/system/local on the search head cluster member. This location is used to store local configurations that apply to the entire Splunk instance and take precedence over default settings.
Where deployed configurations live on the cluster members On cluster members, deployed apps and user configurations reside under $SPLUNK_HOME/etc/apps and $SPLUNK_HOME/etc/users, respectively.
If we're talking about push from a default perspective on the deployer it will merge to default which is D
Answer is D, pg 180 Cluster Admin pdf
The deployer only pushes the contents of subdirectories under /shcluster. It does not push any standalone files directly under /shcluster. For example, it will not push the file /shcluster/file1. To deploy standalone files, create a new apps directory under /apps and put the files in the local subdirectory. For example, put file1 under $SPLUNK_HOME/etc/shcluster/apps/newapp/local.