A governance administrator account has full rights across every project. What control best reduces the risk this account represents?
Select an answer to reveal the explanation.
Short Explanation
Use a powerful admin account only for the tasks that truly need that power. Give people project-level roles for day-to-day work, and don't make the admin account a general-purpose login.
Full Explanation
The correct control is the one that restricts the governance administrator account to genuinely administrative tasks, assigns project-level roles for day-to-day work, and avoids using the admin account as a general-purpose login. This limits the exposure created by a single high-privilege credential by reducing how often it is used and by keeping routine access scoped to the least privilege needed.
The approach of sharing the admin account's credentials with all senior staff is wrong because it multiplies the number of people who could misuse or leak the credential and removes individual attribution. The approach of removing logging on the admin account is wrong because it removes the audit trail that is most needed for the most powerful account. The approach of granting the admin account additional permissions so it can also perform routine daily work is wrong because expanding the account's routine use increases, rather than reduces, its risk.
For the exam, treat high-privilege accounts as something to minimize the use of, not to expand or share.