Question 770
A regional telecom operator manages universal forwarder apps centrally. Observed: A configuration edit on the deployment server does not reach forwarders because they were never assigned to a server class. After the correction, which outcome establishes success for this case?
Explanation
Correct Answer
The specified outcome is: Target forwarders report receiving the intended app with the current version. It provides case-specific verification that the observed behavior (A configuration edit on the deployment server does not reach forwarders because they were never assigned to a server class) has changed appropriately.
Incorrect Answers
This result checks another issue, for which the observed symptom is: Operators have no archived copy of the prior app revision after publishing a broken input setting. It does not verify recovery for this situation: A configuration edit on the deployment server does not reach forwarders because they were never assigned to a server class. The relevant success check is: Target forwarders report receiving the intended app with the current version.
The proposed signal relates to: Forwarders appear under the wrong business unit because the serverclass.conf whitelist regex is too permissive. The evidence for this Splunk source case must instead show: Target forwarders report receiving the intended app with the current version.
In the alternative case “One agent receives overlapping server classes that deliver contradictory input definitions”, the outcome “The effective client configuration contains one approved input definition” is a useful test of “Resolve class membership and app precedence deliberately”, because that case involves “Overlapping server-class assignments can create conflicting configurations on a deployment client”. The present case instead has the warning “A configuration edit on the deployment server does not reach forwarders because they were never assigned to a server class” and the failure mechanism “Deployment server pushes apps only to clients selected by appropriate server classes”. Its remediation is “Assign approved clients to the correct server class and reload the deployment configuration”; the matching acceptance observation is “Target forwarders report receiving the intended app with the current version”.