Question 860
A financial services firm rotates deployment server hosts. Observed: Client bootstrap config still points to an obsolete server and no updates arrive. Which ongoing verification would best guard against the same failure?
Explanation
Correct Answer
This check ties the expected state (Agents successfully phone home to the new server after old host withdrawal) to the original warning (Client bootstrap config still points to an obsolete server and no updates arrive). It is a source-case regression control, not an independently Splunk-certified testing procedure.
Incorrect Answers
The proposed check applies to: Broad server-class targeting creates unnecessary deployment blast radius. The current failure was: Client bootstrap config still points to an obsolete server and no updates arrive. Its validation must test: Agents successfully phone home to the new server after old host withdrawal.
That gate watches a different case: App changes are approved in tickets but cannot be tied to the exact deployed revision. It does not detect the current warning: Client bootstrap config still points to an obsolete server and no updates arrive. The necessary confirmation is: Agents successfully phone home to the new server after old host withdrawal.
This is an unrelated recovery test. It is connected to: The proposed app rollout tries to manage clustered indexer peer configurations with an inappropriate deployment mechanism. The present source situation requires: Agents successfully phone home to the new server after old host withdrawal.