SPLK-1003 practice question 18 of 25

A Splunk administrator has been tasked with developing a retention strategy to have frequently accessed data sets on SSD storage and to have older, less frequently accessed data on slower NAS storage. They have set a mount point for the NAS. Which parameter do they need to modify to set the path for the older, less frequently accessed data in indexes.conf?

Full set: 188 questions
Answer options
A: homepath
B: thawedPath
C: summaryHomePath
D: colddeath
Correct Answer:
N
Explanation

To store older, less frequently accessed data on a separate, slower storage tier like NAS, the coldPath parameter in indexes.conf must be configured. This parameter defines the file system path for cold buckets, which are buckets rolled over from the warm tier. The question is flawed as it does not list the correct parameter. The option colddeath is not a valid or recognized parameter within Splunk's configuration files for this purpose. The other options define paths for different data states or types.

Why Incorrect

A. homepath: This parameter specifies the location for hot and warm buckets, which contain the newest and most frequently accessed data, not the older data intended for NAS.
B. thawedPath: This parameter defines the directory where data restored from a frozen state (archived) is placed. It is not the primary path for cold data.
C. summaryHomePath: This parameter is specifically for defining the storage path for summary indexes, not for the main event data buckets being discussed.
D. colddeath: This is not a valid parameter in the indexes.conf file or any standard Splunk configuration. It is likely a typo for the correct parameter, coldPath.

References

- Splunk Enterprise Documentation, indexes.conf specification. See the descriptions for homePath, coldPath, and thawedPath under the "[]" stanza details. (Splunk Docs: Admin Manual -> indexes.conf)

Scroll to Top