An index receives approximately 50GB of data per day per indexer at an even and consistent rate. The customer would like to keep this data searchable for a minimum of 30 days. In addition, they have…

Question

Options

• AfrozenTimePeriodInSecs, maxDataSize, maxVolumeDataSizeMB, maxHotBuckets
• BmaxDataSize, maxTotalDataSizeMB, maxHotBuckets, maxGlobalDataSizeMB
• CmaxDataSize, frozenTimePeriodInSecs, maxVolumeDataSizeMB
• DfrozenTimePeriodInSecs, maxWarmDBCount, homePath.maxDataSizeMB, maxHotSpanSecs

• A
  62% (38)
• B
  21% (13)
• C
  5% (3)
• D
  11% (7)

Explanation

Option A is correct because it covers all four dimensions the scenario demands: frozenTimePeriodInSecs enforces the 30-day time-based retention requirement; maxDataSize controls hot bucket sizing for a consistent 50 GB/day ingest rate; maxVolumeDataSizeMB caps total disk consumption at the volume level (PS best practice over per-index size limits); and maxHotBuckets tunes parallelism to protect the search performance of those weekly, hourly scheduled jobs.

B is wrong because maxTotalDataSizeMB is size-based, not time-based - without frozenTimePeriodInSecs, data can be frozen before 30 days are reached if the size cap is hit, and maxGlobalDataSizeMB is a redundant volume setting that duplicates maxVolumeDataSizeMB rather than replacing it. C is wrong because it omits maxHotBuckets, which is the primary lever for improving search concurrency and performance against the week's worth of data those scheduled searches touch. D is wrong because maxWarmDBCount and homePath.maxDataSizeMB are legacy or path-specific settings that PS best practices discourage in favour of volume-level controls, and maxHotSpanSecs controls bucket time span rather than data retention duration - it does not substitute for frozenTimePeriodInSecs.

Memory tip: Think of the acronym F-M-M-H - Frozen time (retention), Max data size (bucket size), Max volume (disk cap), Hot buckets (search performance) - these four settings form the complete toolkit for a well-balanced, PS-compliant index configuration.

No community discussion yet for this question.