Question 510
A reporting app has duplicated SQL projections and developers want one reusable logical SELECT surface. The team implemented this change: Create a reviewed view over required columns and apply separate tenant-appropriate security. Which result would best confirm the change worked?
Explanation
Correct Answer
Authorized queries return the same approved projection without exposing excluded fields. A view encapsulates a query projection but does not automatically enforce complete tenant security. A view alone is not sufficient substitute for row-level security.
Incorrect Answers
That observation could pass while the problem persists: Projection and row authorization are separate; validate effective predicates and role grants.
This acceptance test measures the wrong outcome: A shared view must explicitly project approved columns and be governed by backend grants.
The suggested success signal is inadequate because SCHEMABINDING is a separate feature; ordinary view reuse does not guarantee schema stability. The suggested measurement would appear successful even in a reproducible case where the original failure remains.