Question 800
A media company removes an obsolete file monitor. Observed: Deleting the app on the deployment server leaves its previous configuration effective on some clients. Which ongoing verification would best guard against the same failure?
Explanation
Correct Answer
This check ties the expected state (Removed inputs no longer appear in the effective client configuration) to the original warning (Deleting the app on the deployment server leaves its previous configuration effective on some clients). 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: App changes are approved in tickets but cannot be tied to the exact deployed revision. The present source situation requires: Removed inputs no longer appear in the effective client configuration.
That gate watches a different case: Forwarders appear under the wrong business unit because the serverclass.conf whitelist regex is too permissive. It does not detect the current warning: Deleting the app on the deployment server leaves its previous configuration effective on some clients. The necessary confirmation is: Removed inputs no longer appear in the effective client configuration.
The proposed check applies to: Large fleets may require controlled polling and deployment-server capacity planning. The current failure was: Deleting the app on the deployment server leaves its previous configuration effective on some clients. Its validation must test: Removed inputs no longer appear in the effective client configuration.