Exam SPLK-1005 topic 1 question 15 discussion

D. ./splunk show config inputs is the right answer When running ths on the Command Line Interface, if you add the ".conf" extension file, it will show that the file doesn't exist. This occurs because most splunk commands (such as splunk btool) do not include the .conf file extension name when executing them. Based on loopfastener response, it is confirmed on the outputs that this is true. Besides, when running a commmand such as ./splunk _internal in bin, it will definitely show an error because as far as I recall, no splunk command includes "_word" with the underscore sign.

D is the correct answer. I entered D in the cli: [root@splunk-69bd4f78f7-qkv6s splunk]# ./bin/splunk show config inputs [batch://$SPLUNK_HOME/var/run/splunk/search_telemetry/*search_telemetry.json] _rcvbuf=1572864 crcSalt=<SOURCE> host=$decideOnStartup index=_introspection log_on_completion=0 move_policy=sinkhole sourcetype=search_telemetry [...] --- The output for the commands from A, B or C to the cli fail [root@splunk-69bd4f78f7-qkv6s splunk]# ./bin/splunk _internal call /services/data/inputs/filemonitor FAILED: 'HTTP/1.1 404 Not Found' --- [root@splunk-69bd4f78f7-qkv6s splunk]# ./bin/splunk _internal rest /services/data/inputs/monitor The subcommand rest is not valid for command '_internal'. --- [root@splunk-69bd4f78f7-qkv6s splunk]# ./bin/splunk show config inputs.conf WARNING: Server Certificate Hostname Validation is disabled. Please see server.conf/[sslConfig]/cliVerifyServerName for details. inputs.conf does not exist