An administrator is decommissioning a peer and wants to ensure that the process is graceful and does not cause data loss. What is the most important step to verify before initiating the decommission?

Ensure the search_factor is set to 1 to prevent search impact.

Ensure the peer is online and healthy.

Ensure the replication_factor is set to 1 to simplify the migration.

Ensure the master is online and healthy.

What happens to bucket replication when a peer goes offline?

The replication factor is automatically reduced to account for the missing peer.

The master initiates replication of the offline peer's buckets to other peers to restore the replication factor.

Replication stops entirely until the peer returns.

The master rebalances all buckets immediately to maintain the replication factor.

A peer indexer in a cluster has been offline for 15 minutes. The master has not yet marked it as down. What is the master's role during this grace period?

The master is immediately rebalancing the peer's buckets to other peers to maintain replication.

The master is waiting for the peer to initiate a rejoin request before it can be marked down.

The master has paused all indexing and replication until the peer returns.

The master is actively monitoring the peer's heartbeat and will mark it down if it does not resume within the configured timeout.

A peer indexer has been marked down by the master. The administrator plans to bring it back online after a hardware fix. What is the expected behavior of the cluster when the peer rejoins?

The peer will be treated as a new peer and must be added to the cluster again.

The peer will only serve search requests but will not participate in replication.

The peer will be automatically decommissioned to prevent future issues.

The peer will resume its role and the cluster will rebalance buckets to restore the replication factor.

What is the first step in gracefully decommissioning a peer from an indexer cluster?

Run the `splunk offline` command on the peer.

Stop the Splunk service on the peer.

Use the master to mark the peer as decommissioned.

Delete the peer's configuration from the cluster.

SplunkEnterprise Certified Architect

Domain 3Objective 6

Peer Offline and Decommission SPLK-2002 Practice Questions (Page 1)

Part of the Indexer Clustering domain, which makes up ~25% of our current practice bank. Splunk does not publish an official question count, but from its 90-minute exam (~35–60 total, ~9–15 in this domain), expect 1–2 from this objective — we provide 22 practice questions to prepare you well beyond it. (estimate)

22questions here

5free pages

6concepts

Questions 1–5

1application · medium
An administrator is decommissioning a peer and wants to ensure that the process is graceful and does not cause data loss. What is the most important step to verify before initiating the decommission?
Select an answer first
2foundation · easy
What happens to bucket replication when a peer goes offline?
Select an answer first
3application · medium
A peer indexer in a cluster has been offline for 15 minutes. The master has not yet marked it as down. What is the master's role during this grace period?
Select an answer first
4application · medium
A peer indexer has been marked down by the master. The administrator plans to bring it back online after a hardware fix. What is the expected behavior of the cluster when the peer rejoins?
Select an answer first
5foundation · easy
What is the first step in gracefully decommissioning a peer from an indexer 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.