ITSI Saved Search Scheduling is configured to use realtime_schedule = 0. Which statement is accurate about this configuration?

ITSI Saved Search Scheduling is a feature that allows you to schedule searches that run periodically to

populate the data for your KPIs. You can configure various settings for your scheduled searches, such

as the search frequency, the time range, the cron expression, and so on. One of the settings is

realtime_schedule, which controls the way the scheduler computes the next execution time of a

scheduled search. The statement that is accurate about this configuration is:

B) If this value is set to 0, the scheduler bases its determination of the next scheduled search on the

last search execution time. This is called continuous scheduling. If set to 0, the scheduler never skips

scheduled execution periods. However, the execution of the saved search might fall behind

depending on the scheduler’s load. Use continuous scheduling whenever you enable the summary

index option.

The other statements are not accurate because:

A) If this value is set to 0, the scheduler bases its determination of the next scheduled search

execution time on the current time. This is not true because this is what happens when the value is

set to 1, not 0.

C) If this value is set to 0, the scheduler may skip scheduled execution periods. This is not true

because this is what happens when the value is set to 1, not 0.

D) If this value is set to 0, the scheduler might skip some execution periods to make sure that the

scheduler is executing the searches running over the most recent time range. This is not true because

this is what happens when the value is set to 1, not 0.

Reference: Create KPI base searches in ITSI, Rrealtime_schedule in SavedSearches.conf