Question 990
A Splunk Enterprise administrator is investigating this situation: An organization requires an index to keep 90 days of data and an engineer edits props.conf instead of index retention options. Which corrective action is the best next step?
Explanation
Correct Answer
The proposed action tackles the reported failure. Index retention and bucket lifecycle controls belong to index configuration, not general parsing properties. A successful outcome would be demonstrated by: A test index shows expected aging without unexpected early freezing due to size limits.
Incorrect Answers
This option serves the scenario “At a logistics company during a data pipeline migration, reviewers observe the following: An indexer fills its cold volume while maxTotalDataSizeMB is set higher than the available storage”. Reconcile indexes.conf capacity limits and filesystem free space before setting retention policy. The present scenario is distinguished by “Review indexes.conf retention controls including frozenTimePeriodInSecs and size limits on the relevant index”.
This addresses A team creates a new financial index without specifying a secure dedicated path or quota. rather than the stated case. The narrower corrective action is Review indexes.conf retention controls including frozenTimePeriodInSecs and size limits on the relevant index.
That action is aimed at another operational symptom: A new index is assigned a large hot path without validating the available disk and cold volume capacity. The reported issue instead depends on this requirement: Index retention and bucket lifecycle controls belong to index configuration, not general parsing properties. The expected validation is A test index shows expected aging without unexpected early freezing due to size limits.