Question 660
During operational handoff for this problem: A service user has a broad static password shared by multiple applications and audit cannot identify which app queried data. Which guardrail should be included?
Explanation
Correct Answer
Inventory service-user ownership and rotate credentials with controlled revocation tests. This reduces recurrence of: Shared credentials undermine per-application attribution and least-privilege offboarding. The verification should demonstrate: Query history attributes activity to the intended service identity and a revoked app credential stops only its app.
Incorrect Answers
Audit highly privileged roles and replace convenience grants with scoped functional roles. That safeguard is aimed at ANOTHER risk: A junior analyst is made ACCOUNTADMIN solely to query a departmental reporting table. It is less targeted than the control for: Shared credentials undermine per-application attribution and least-privilege offboarding.
Test effective permissions after role hierarchy changes rather than assuming role names set power. That safeguard is aimed at ANOTHER risk: A manager grants SELECT to a child role and expects a parent role to automatically lose that permission. It is less targeted than the control for: Shared credentials undermine per-application attribution and least-privilege offboarding.
Schedule credential expiration and parallel-cutover tests for programmatic access. That safeguard is aimed at ANOTHER risk: An integration uses a long-lived shared credential and operations cannot rotate it without stopping all downstream jobs. It is less targeted than the control for: Shared credentials undermine per-application attribution and least-privilege offboarding.