Question 1170
A travel group plans capacity for 300 concurrent analysts. Observed: The design increases the number of SHC members without assessing per-member concurrent-search limits and scheduler load. After the correction, which outcome establishes success for this case?
Explanation
Correct Answer
The specified outcome is: A representative load test meets response and scheduled-search service levels. It provides case-specific verification that the observed behavior (The design increases the number of SHC members without assessing per-member concurrent-search limits and scheduler load) has changed appropriately.
Incorrect Answers
The proposed verification result is “Equivalent searches extract the field on every healthy member”. That tests the different scenario “A new search-time field extraction appears on one SHC member only because it is stored as an unsupported local configuration file”, whose underlying issue is “Knowledge object replication and deployer-managed app configuration follow different propagation rules” and whose remedy is “Place the extraction in the supported shared object or managed app location”. This question instead reports “The design increases the number of SHC members without assessing per-member concurrent-search limits and scheduler load”, indicating “Horizontal search head scaling still requires workload-based sizing and role limits”. The appropriate response is “Capacity-plan search concurrency, memory and scheduler demand per member and overall”, confirmed by the case-specific result “A representative load test meets response and scheduled-search service levels”.
The proposed signal relates to: The architecture requires a large search head cluster despite no concurrency, outage or shared knowledge-object need. The evidence for this Splunk source case must instead show: A representative load test meets response and scheduled-search service levels.
This result checks another issue, for which the observed symptom is: Repeated election attempts occur because several members cannot communicate over the cluster management network. It does not verify recovery for this situation: The design increases the number of SHC members without assessing per-member concurrent-search limits and scheduler load. The relevant success check is: A representative load test meets response and scheduled-search service levels.