A government agency's IT governance committee is finalizing its governance framework. A dispute arises over who should approve exceptions to the enterprise architecture standards when a business unit needs a rapid technology deployment. Which principle should guide the committee's decision on where to place exception approval authority?
Placing exception authority with a designated architecture authority, governed by explicit criteria and expiration dates, balances agility with control. It ensures decisions are made by a body with the expertise and objectivity to assess architectural and risk impacts, while time limits prevent exceptions from becoming permanent de facto standards. This aligns with ISACA CGEIT governance design principles.
Why this answer
Exception authority should sit with a designated architecture authority operating under explicit criteria, documented rationale, and time limits, which preserves both agility and control. Self-approval by requesters, case-by-case governance committee review, and external auditor approval all misplace authority, creating conflicts, bottlenecks, or independence breaches. ISACA CGEIT guidance supports delegated decision rights bounded by criteria and escalation for material impacts.
Exam trap
The trap here is assuming that faster deployment requires approval by the requesting party, when speed can be preserved through a delegated authority with clear criteria and time limits.