What is the purpose of the repository path specified in the deployer's server.conf?

It specifies the location of the deployer's license and authentication files

It indicates where the deployer writes logs for all search head cluster members

It stores the deployer's local copies of search artifacts and job results

It defines the directory where the deployer stores the apps and configuration bundles that it distributes

A search head cluster has been running for months. An admin needs to add a new app to the cluster. What is the correct sequence of steps?

Install the app on each member manually, then restart each member.

Run `splunk apply shcluster-bundle` first, then place the app in the repository.

Place the app on the captain, then run `splunk apply shcluster-bundle`.

Place the app in the deployer's repository, then run `splunk apply shcluster-bundle`.

An admin is setting up a deployer for a search head cluster. They have installed Splunk on a dedicated server and want to enable the deployer. What is the correct configuration in server.conf?

In `[shclustering]`, set `deployer = true` and `repositorylocation = /path/to/repo`.

In `[general]`, set `deployer = true` and `repository = /path/to/repo`.

In `[replication]`, set `deployer = true` and `repositorylocation = /path/to/repo`.

In `[clustering]`, set `deployer = true` and `repository = /path/to/repo`.

An admin is managing a search head cluster and needs to update an app that is currently deployed. What is the recommended approach to avoid configuration conflicts?

Delete the app from all members and reinstall it manually.

Edit the app directly on one member and let the cluster replicate the change.

Use the member's UI to update the app and then run `splunk apply shcluster-bundle`.

Update the app in the deployer's repository and push it to the cluster.

What is a recommended approach to handle configuration conflicts in a search head cluster?

Disable the deployer temporarily to prevent it from overwriting member changes

Use the captain's configuration as the source of truth for all members

Resolve conflicts by editing the deployer's repository and reapplying the bundle

Allow members to keep local overrides that take precedence over the deployer's bundle

SplunkEnterprise Certified Architect

Domain 4Objective 3

Search Head Cluster Deployer SPLK-2002 Practice Questions (Page 3)

Part of the Search Head Clustering and KV Store domain, which makes up ~19% of our current practice bank. Splunk does not publish an official question count, but from its 90-minute exam (~35–60 total, ~7–11 in this domain), expect 1–2 from this objective — we provide 21 practice questions to prepare you well beyond it. (estimate)

21questions here

5free pages

4concepts

Questions 11–15

11foundation · easy
What is the purpose of the repository path specified in the deployer's server.conf?
Select an answer first
12application · medium
A search head cluster has been running for months. An admin needs to add a new app to the cluster. What is the correct sequence of steps?
Select an answer first
13application · medium
An admin is setting up a deployer for a search head cluster. They have installed Splunk on a dedicated server and want to enable the deployer. What is the correct configuration in server.conf?
Select an answer first
14application · medium
An admin is managing a search head cluster and needs to update an app that is currently deployed. What is the recommended approach to avoid configuration conflicts?
Select an answer first
15foundation · easy
What is a recommended approach to handle configuration conflicts in a search head cluster?
Select an answer first

Finished these 5 questions?

Review the revealed explanations, or continue through the curriculum.

Next 5 questions →Back to SPLK-2002

Free Basic Practice is a study aid with revealable answers — not a scored exam. Examers.io is independent and not affiliated with or endorsed by Splunk. “SPLK-2002” is a trademark of its owner, used for identification only.