Question 830
A shared application database password is emailed to dozens of developers and nobody can identify which user made a change. What is the most defensible technical decision?
Explanation
Correct Answer
Individual accountability and secret hygiene are lost when many actors use the same static login.
Incorrect Answers
Validate the client key store, key metadata and coordinated rotation path before enabling the new key for production traffic: validate the client key store, key metadata and coordinated rotation path before enabling the new key for production traffic: client-side encryption depends on matching key access and metadata, not just a successful SQL connection; Replace the shared login with identifiable least-privileged principals and rotate the exposed credential.
Inspect the user's effective token and all group and database role grants before confirming revocation: inspect the user's effective token and all group and database role grants before confirming revocation: effective rights combine multiple principals, so removing one grant may leave another access path; Replace the shared login with identifiable least-privileged principals and rotate the exposed credential.
Fix the trusted certificate name or connection target and keep verified encrypted transport enabled: fix the trusted certificate name or connection target and keep verified encrypted transport enabled: skipping certificate validation can turn a configuration mismatch into an interception opportunity; Replace the shared login with identifiable least-privileged principals and rotate the exposed credential.



Developing AI-Enabled Database Solutions (DP-800) Practice Tests