Policy exceptions longer than 30 days must go through formal approval before remaining active. What should the compliance admin configure?
Select an answer to reveal the explanation.
Short Explanation
A 31-day exception without a boss’s nod is just hope with a calendar. Put an approval workflow on exceptions that run past 30 days. Infinite self-extend, hard auto-close with no path, or parking them in SharePoint all dodge governance.
Full Explanation
Policy exception workflows enforce review and approval when temporary deviations persist beyond defined thresholds. Configuring approval for exceptions exceeding 30 days ensures risk owners and compliance stakeholders accept prolonged non-compliance explicitly. Unbounded self-extension, automatic closure without a justified extension path, or off-platform tracking break auditability and Policy and Compliance lifecycle control.