What does setting the alert threshold to 0 (zero) do when configuring replication rules?

Question

Options

• ADisables all alerts for any missed RPO cycles.
• BGenerates an alert if the data saved during the RPO cycle exceeds 20% of the storage object
• CEnables alerts if the RPO cycle was missed for three consecutive cycles.
• DGenerates an alert if the synchronization time exceeds the RPO.

• C
  5% (1)
• D
  95% (19)

Explanation

Setting the alert threshold to 0 means "no tolerance" - alert immediately if the RPO cycle is missed at all, which is exactly what option D describes: an alert fires the moment synchronization time exceeds the RPO target.

Why the distractors are wrong:

• A is the opposite - a threshold of 0 enables maximum alerting sensitivity, it doesn't disable alerts.
• B introduces a storage percentage concept (20%) that has nothing to do with alert thresholds in replication rule configuration.
• C describes a tolerance of 3 missed cycles, which would correspond to a threshold value of 3, not 0.

Memory tip: Think of the threshold as a "strikes before you're out" counter. Setting it to 0 means zero strikes allowed - you get alerted on the very first missed sync. Higher values give you more buffer before an alert fires.

No community discussion yet for this question.