A county encrypts tax data with AWS KMS and must separate key administrators from key users while enabling automatic key rotation where appropriate. Which design should the architect prescribe?
Select an answer to reveal the explanation.
Short Explanation
The locksmith who cuts city keys should not be the same crew that opens every tax drawer all day. KMS key policies split admins from users, and automatic rotation refreshes eligible symmetric CMKs. Handing clerks delete/policy powers, skipping encryption, or parking a plaintext master key undoes the whole point.
Full Explanation
AWS KMS supports separation of duties by distinguishing key administrators (who manage key policies, grants, and lifecycle) from key users (who call encrypt/decrypt via IAM and key policy allow statements). Customer managed keys allow counties to enforce that split and to enable automatic rotation for eligible symmetric CMKs. Granting broad administrative KMS permissions to application clerks, disabling encryption, or storing plaintext master material outside KMS weakens control and auditability for tax data.