Question 830
A mobile games publisher reviews forwarder rollout speed. Observed: Deployment clients all phone home simultaneously, producing a traffic spike on the management instance. After the correction, which outcome establishes success for this case?
Explanation
Correct Answer
The specified outcome is: A fleet rollout completes without management server saturation. It provides case-specific verification that the observed behavior (Deployment clients all phone home simultaneously, producing a traffic spike on the management instance) has changed appropriately.
Incorrect Answers
Option B would be useful evidence if the observed failure were “Operators have no archived copy of the prior app revision after publishing a broken input setting”: it checks “The pilot returns to the last known working input definition” after the action “Store approved deployment app versions and test rollback on a pilot client” addresses “Deployment rollback depends on retained versioned configuration artifacts”. But the current failure is “Deployment clients all phone home simultaneously, producing a traffic spike on the management instance”, linked to “Large fleets may require controlled polling and deployment-server capacity planning”. Here the targeted action is “Stagger deployment check-ins or size the management service according to supported guidance”, and the required proof is “A fleet rollout completes without management server saturation”.
This result checks another issue, for which the observed symptom is: Deleting the app on the deployment server leaves its previous configuration effective on some clients. It does not verify recovery for this situation: Deployment clients all phone home simultaneously, producing a traffic spike on the management instance. The relevant success check is: A fleet rollout completes without management server saturation.
The proposed signal relates to: App changes are approved in tickets but cannot be tied to the exact deployed revision. The evidence for this Splunk source case must instead show: A fleet rollout completes without management server saturation.