Question 730
What should be observed after successful remediation of this condition? A workload uses one long-running scheduled search that saturates indexer resources while search-head CPU remains low.
Explanation
Correct Answer
Profiling proves the targeted bottleneck improves under an appropriate search or indexing change. This outcome directly confirms the control associated with search-head clustering addresses head-tier resilience and concurrency, not automatic correction of inefficient SPL or undersized indexers. The original concern was: A workload uses one long-running scheduled search that saturates indexer resources while search-head CPU remains low. The required implementation is: Fix the actual indexing or search workload bottleneck before adding search-head-cluster capacity.
Incorrect Answers
This proof would apply to a different incident: A consultant confuses deployer-managed baseline app objects with user-created replicated knowledge. Its result would be: A test push preserves authorized user-created content while updating only intended managed app settings. The current acceptance criterion instead follows from search-head clustering addresses head-tier resilience and concurrency, not automatic correction of inefficient SPL or undersized indexers.
The alternative observation measures a separate technical dependency: A three-member search head cluster loses its network majority and cannot elect a stable captain. The current incident requires evidence tied to search-head clustering addresses head-tier resilience and concurrency, not automatic correction of inefficient SPL or undersized indexers.
A maintenance test retains required searches, dashboards, and report schedules through one member outage. would confirm remediation of a customer runs a critical app on one search UI host and requires maintenance without complete loss of service. It does not establish that the target situation has been resolved, where search-head clustering addresses head-tier resilience and concurrency, not automatic correction of inefficient SPL or undersized indexers.