Question 90
A city council wants alerts when a search peer disappears. Observed: The monitoring topology is configured but health alerts were never enabled or validated. After the correction, which outcome establishes success for this case?
Explanation
Correct Answer
The specified outcome is: A controlled peer interruption creates an identifiable alert delivered to the intended responders. It provides case-specific verification that the observed behavior (The monitoring topology is configured but health alerts were never enabled or validated) has changed appropriately.
Incorrect Answers
This result checks another issue, for which the observed symptom is: A custom warning disappears after an application upgrade because its definition was edited inside vendor-managed defaults. It does not verify recovery for this situation: The monitoring topology is configured but health alerts were never enabled or validated. The relevant success check is: A controlled peer interruption creates an identifiable alert delivered to the intended responders.
The distractor measures “The topology view includes the intended remote tiers and their role-specific metrics”. This verifies a separate correction, “Complete the documented distributed monitoring setup and confirm all supported instances”, for the fault “The administrators assume standalone self-monitoring will automatically enumerate every new remote Splunk instance” and the cause “Distributed monitoring requires proper search-peer and topology configuration”. The stated fault, however, is “The monitoring topology is configured but health alerts were never enabled or validated”, which points to “Populated monitoring dashboards do not guarantee actionable notification rules”. Check “A controlled peer interruption creates an identifiable alert delivered to the intended responders” after “Configure appropriate Monitoring Console platform alerts and test their notification paths” to determine whether this incident was resolved.
The proposed signal relates to: The Monitoring Console labels all scheduled-search misses as underlying indexer outages. The evidence for this Splunk source case must instead show: A controlled peer interruption creates an identifiable alert delivered to the intended responders.