A Splunk indexer cluster has 5 peers, replication_factor=3, search_factor=2. One peer fails and is removed. During rebalancing, the master detects that one of the remaining peers has insufficient disk space to receive additional bucket copies. What is the most likely impact?

The master will delete some buckets to free up space.

The master will automatically reduce the replication factor to 2.

The rebalance will complete partially, leaving some buckets under-replicated, and the cluster will remain degraded.

The rebalance will fail entirely, and the cluster will be down.

A Splunk indexer cluster master is experiencing network latency to one peer, causing intermittent missed heartbeats. The peer is not actually down. What is the most likely consequence?

The master may falsely mark the peer as down, causing the cluster to enter a degraded state.

The master will increase the heartbeat timeout to accommodate the latency.

The cluster will continue to operate normally without any impact.

The peer will automatically restart to re-establish heartbeats.

After a peer failure, how does the cluster decide which buckets to rebalance?

It rebalances all buckets to the peer with the most free disk space.

It randomly selects buckets to copy to other peers.

It identifies buckets that are under-replicated and copies them to available peers.

It copies all buckets from the failed peer to the master for redistribution.

After a peer failure and removal, the master begins rebalancing buckets. During the rebalance, a second peer fails. What is the most likely outcome?

The rebalance continues unaffected because the master has already planned the bucket copies.

The rebalance pauses, and the cluster may become further degraded, but it will resume once the second peer is removed or returns.

The cluster automatically rolls back to the previous state and restarts the rebalance from scratch.

The master immediately removes the second peer and continues the rebalance.

SplunkCore Certified Consultant

Domain 8Objective 3

Determine Failure Modes and Recovery Processes CORE-CERTIFIED-CONSULTANT Practice Questions (Page 1)

Part of the Indexer Clustering domain, which accounts for 18% of the CORE-CERTIFIED-CONSULTANT exam. Splunk does not publish an official question count, but from its 120-minute exam (~50–80 total, ~9–14 in this domain), expect 2–3 from this objective — we provide 23 practice questions to prepare you well beyond it. (estimate)

23questions here

5free pages

7concepts

18%of the exam

Questions 1–5

1application · easy
A Splunk indexer cluster is initializing. The master is up, but the peers are still joining and downloading bucket lists. What is the cluster state during this period?
Select an answer first
2expert · hard
A Splunk indexer cluster has 5 peers, replication_factor=3, search_factor=2. One peer fails and is removed. During rebalancing, the master detects that one of the remaining peers has insufficient disk space to receive additional bucket copies. What is the most likely impact?
Select an answer first
3application · medium
A Splunk indexer cluster master is experiencing network latency to one peer, causing intermittent missed heartbeats. The peer is not actually down. What is the most likely consequence?
Select an answer first
4foundation · easy
After a peer failure, how does the cluster decide which buckets to rebalance?
Select an answer first
5application · medium
After a peer failure and removal, the master begins rebalancing buckets. During the rebalance, a second peer fails. What is the most likely outcome?
Select an answer first

Finished these 5 questions?

Review the revealed explanations, or continue through the curriculum.

Next 5 questions →Back to CORE-CERTIFIED-CONSULTANT

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. “CORE-CERTIFIED-CONSULTANT” is a trademark of its owner, used for identification only.