Question 620
A Data API builder deployment in a managed Azure container currently embeds a SQL password in its environment image. The team is considering this step: Use managed identity/approved secret injection with least-privilege SQL access. What evidence should they review before proceeding?
Explanation
Correct Answer
Review container identity, SQL Entra grants and config resolution. Secretless workload identity is preferable to hardcoded connection secrets where supported. Deployed API connects while container image contains no reusable SQL password.
Incorrect Answers
This evidence check would miss the central issue: Use managed identity or protected runtime secret injection; do not embed reusable credentials in image layers.
The proposed diagnostic comparison leaves a gap: Identity proves who connects; backend SQL object permissions remain a separate required control.
Such observations do not establish the required mechanism: Backend workload identity does not replace DAB endpoint-level client role restrictions. The candidate check cannot distinguish the required state from a superficial symptom, and so does not justify the proposed change.