Which baseline criterion triggers notifications for audit tasks when they expire?

• A. Expiration
• B. At 50% completion
• C. Reassignment
• D. Due date change

Answer: (A)

In IRM, notifications for audit tasks are driven by specific events, and a time-based event is expiration. When an audit task reaches its expiration, that event matches the expiration baseline criterion and triggers the configured notification to the task owner and stakeholders. This ensures timely awareness and follow-up when the task can no longer be completed within its original timeframe. Other scenarios don’t align with expiry: triggering at 50% completion is about progress, not overdue status; reassignment concerns ownership changes; a change to the due date only fires if the due date itself is altered, not when the task becomes overdue. So, expiring is the trigger that best matches the requirement.