Question 930
A Splunk platform team observes this behavior: A security retention rule asks for two years but a small maxTotalDataSizeMB freezes the oldest buckets within weeks. Which technical principle best explains the issue?
Explanation
Correct Answer
The controlling mechanism is that an index can freeze data when the size limit is hit before the desired time limit. Resolve the problem by model both time-based and size-based retirement thresholds and provision storage accordingly. Then validate with: A capacity estimate and retention test show neither threshold forces premature removal.
Incorrect Answers
This option serves the scenario “An archive policy assumes frozen data is kept automatically even though no coldToFrozen configuration exists”. Without explicit archival, frozen bucket aging commonly results in deletion from the active index. The present scenario is distinguished by “An index can freeze data when the size limit is hit before the desired time limit”.
The option would apply to “A compliance analyst needs to search expired records immediately but they were already rolled to frozen storage”. Archived data and active indexed data have different availability and recovery requirements. This question instead requires “An index can freeze data when the size limit is hit before the desired time limit”.
This principle explains a different operational condition: An organization requires an index to keep 90 days of data and an engineer edits props.conf instead of index retention options. For the current issue, an index can freeze data when the size limit is hit before the desired time limit. The corresponding action is Model both time-based and size-based retirement thresholds and provision storage accordingly.