Question 970
A team stores model API keys directly in a version-controlled SQL Database Project. Which technical reason BEST explains the proposed correction?
Explanation
Correct Answer
Repository history retains secrets even after a visible commit is removed. This explains why the corrective action is to remove keys and use deployment-time secret references or supported managed identity. Confirm the diagnosis when secret scans pass and deployments resolve approved credentials securely.
Incorrect Answers
Identity permission at one Azure service does not imply access to adjacent resources. The actual technical constraint is that repository history retains secrets even after a visible commit is removed.
Database roles and schema grants can bound an automation's change surface. The actual technical constraint is that repository history retains secrets even after a visible commit is removed.
Exposing a constrained view can limit data surface without broad base-table rights. The actual technical constraint is that repository history retains secrets even after a visible commit is removed.