Which of the following clarification steps should be taken if apps are not appearing on a deployment client? (Select all that apply.)

Question

Options

• ACheck serverclass.conf of the deployment server.
• BCheck deploymentclient.conf of the deployment client.
• CCheck the content of SPLUNK_HOME/etc/apps of the deployment server.
• DSearch for relevant events in splunkd.log of the deployment server.

Explanation

All four options appear plausible at first glance, but the correct answers are A, B, and D.

Why A is correct: serverclass.conf on the deployment server defines which apps are assigned to which deployment clients via server classes. If an app isn't mapped to the correct server class (or the client isn't in the right class), it will never be pushed - this is the most common root cause.

Why B is correct: deploymentclient.conf on the client specifies which deployment server to connect to and the polling interval. A misconfigured target URI or disabled client will prevent apps from ever being received.

Why D is correct: splunkd.log on the deployment server records all deployment activity, including handshake errors, phone-home events, and push failures - essential for diagnosing why delivery is failing.

Why C is wrong (the distractor): Apps intended for deployment clients must reside in $SPLUNK_HOME/etc/deployment-apps/, not $SPLUNK_HOME/etc/apps/. The apps/ directory holds apps running on the deployment server itself. Checking that directory won't help diagnose client delivery issues.

Memory tip: Think "Server config → Client config → Logs" (A → B → D). The trick is remembering that Splunk uses a separate deployment-apps/ folder - if an option points you to plain apps/ on the deployment server, it's a red herring.

No community discussion yet for this question.