If row-level security must filter data based on the viewer's identity using dynamic rules, what should you implement?

If row-level security must filter data based on the viewer's identity using dynamic rules, what should you implement?

• A. RLS with dynamic rule
• B. OLS with static rule
• C. RLS with static rule
• D. OLS with dynamic rule

Answer: (A)

Row-level security with a dynamic rule. You need per-row filtering that adapts to who is querying, so the policy must evaluate the viewer’s identity at query time and filter each row accordingly. Static rules wouldn’t change based on who runs the query, and object-level security blocks access to entire objects rather than individual rows, which doesn’t achieve per-row filtering. A dynamic policy tied to the current user ensures only the appropriate rows are visible to each viewer.

Row-level security with a dynamic rule. You need per-row filtering that adapts to who is querying, so the policy must evaluate the viewer’s identity at query time and filter each row accordingly. Static rules wouldn’t change based on who runs the query, and object-level security blocks access to entire objects rather than individual rows, which doesn’t achieve per-row filtering. A dynamic policy tied to the current user ensures only the appropriate rows are visible to each viewer.