Question 1100
A legal-services platform modifies a dashboard directly on one SHC member. Observed: The change appears temporarily but later disappears because it conflicts with deployed app configuration. Which ongoing verification would best guard against the same failure?
Explanation
Correct Answer
This check ties the expected state (The dashboard remains consistent across members after a controlled deployer push) to the original warning (The change appears temporarily but later disappears because it conflicts with deployed app configuration). It is a source-case regression control, not an independently Splunk-certified testing procedure.
Incorrect Answers
This is an unrelated recovery test. It is connected to: The member is removed from the load balancer but remains in the SHC membership inventory. The present source situation requires: The dashboard remains consistent across members after a controlled deployer push.
That gate watches a different case: The team believes the load balancer always chooses which Splunk member becomes captain. It does not detect the current warning: The change appears temporarily but later disappears because it conflicts with deployed app configuration. The necessary confirmation is: The dashboard remains consistent across members after a controlled deployer push.
The proposed check applies to: SHC recovery depends on preserving both cluster state and separately managed deployment artifacts. The current failure was: The change appears temporarily but later disappears because it conflicts with deployed app configuration. Its validation must test: The dashboard remains consistent across members after a controlled deployer push.