Splunk Cloud Certified Admin Questions and Answers
Question 17
What two files are used in the data transformation process?
Options:
A.
parsing.conf and transforms.conf
B.
props.conf and transforms.conf
C.
transforms.conf and fields.conf
D.
transforms.conf and sourcetypes.conf
Answer:
B
Explanation:
Explanation: props.conf and transforms.conf define data parsing, transformations, and routing rules, making them essential for data transformations. [Reference: Splunk Docs on props.conf and transforms.conf]
Question 18
What can be used in a Splunk Cloud environment to create new sourcetypes?
Options:
A.
Data Preview
B.
props. conf can be edited directly from the GUI
C.
Splunk's CLI
D.
Deployment Server
Answer:
A
Explanation:
In a Splunk Cloud environment, the Data Preview feature is used to create and test new sourcetypes. This feature allows you to upload sample data, configure parsing settings, and define sourcetypes interactively without directly editing configuration files like props.conf or using the CLI.
Splunk Documentation Reference: Data Preview
Question 19
Which of the following is a valid stanza in props. conf?
Options:
A.
[sourcetype::linux_secure]
B.
[host=nyc25]
C.
[host::nyc*]
D.
[host:nyc*]
Answer:
A
Explanation:
In props.conf, valid stanzas can include source types, hosts, and source specifications. The correct syntax uses colons for specific types, such as source types and hosts, but follows a particular format:
A. [sourcetype::linux_secure] is the correct answer. This is a valid stanza format for a source type in props.conf. It indicates that the following configurations apply specifically to the linux_secure source type.
B. [host=nyc25]: Incorrect, the correct format for a host-based stanza uses double colons, not an equal sign.
C. [host::nyc]:* Incorrect, wildcards are not used in this manner within props.conf.
D. [host
]:* Incorrect, the correct format requires double colons for host stanzas.
Splunk Documentation References:
props.conf Specification
Question 20
What does the followTail attribute do in inputs.conf?
Options:
A.
Pauses a file monitor if the queue is full.
B.
Only creates a tail checkpoint of the monitored file.
C.
Ingests a file starting with new content and then reading older events.
D.
Prevents pre-existing content in a file from being ingested.
Answer:
D
Explanation:
The followTail attribute in inputs.conf controls how Splunk processes existing content in a monitored file.
D. Prevents pre-existing content in a file from being ingested: This is the correct answer. When followTail = true is set, Splunk will ignore any pre-existing content in a file and only start monitoring from the end of the file, capturing new data as it is added. This is useful when you want to start monitoring a log file but do not want to index the historical data that might be present in the file.
A. Pauses a file monitor if the queue is full: Incorrect, this is not related to the followTail attribute.
B. Only creates a tail checkpoint of the monitored file: Incorrect, while a tailing checkpoint is created for state tracking, followTail specifically refers to skipping the existing content.
C. Ingests a file starting with new content and then reading older events: Incorrect, followTail does not read older events; it skips them.
Splunk Documentation References:
followTail Attribute Documentation
Monitoring Files
These answers align with Splunk's best practices and available documentation on managing and configuring Splunk environments.