Q: 2
In Power BI Desktop, you are building a sales report that contains two tables. Both tables have row-
level security (RLS) configured.
You need to create a relationship between the tables. The solution must ensure that bidirectional
cross-filtering honors the RLS settings.
What should you do?
Options
Discussion
Option D is the way to go, since you need an active relationship and the "Apply security filter in both directions" box ticked for bidirectional RLS to actually work. If you only set the relationship active without that security filter setting, cross-filtering won't enforce RLS from both tables. Pretty sure about this unless Microsoft changed something recently, but correct me if I'm missing a new feature.
D imo. Only an active relationship with 'Apply security filter in both directions' will actually carry RLS across both tables for bidirectional access. The others either miss the active piece or the right filter setting. Open to corrections but pretty sure.
C is off, D is the only one that truly supports secure bidirectional filtering with active relationship.
Not C, D is correct. Only active relationships with 'Apply security filter in both directions' will enforce bidirectional RLS. The inactive trap in C trips people up. Seen similar on practice tests.
Its D. "Assume referential integrity" (trap in A/B) is not about RLS, only D ensures bi-directional security here.
I don’t think B fits here, D is the right move. The trap is confusing "Assume referential integrity" with actual RLS enforcement. Only "Apply security filter in both directions" on an active relationship will honor RLS both ways for both tables.
C vs D
I'm leaning C because you can still get RLS to work with an inactive relationship if you're using USERELATIONSHIP in your measures, right? It's not the default bidirectional, but sometimes that's enough for custom filter logic. Not totally sure though, since the question wants bidirectional all the time. Anyone else see issues with picking C?
I'm leaning C because you can still get RLS to work with an inactive relationship if you're using USERELATIONSHIP in your measures, right? It's not the default bidirectional, but sometimes that's enough for custom filter logic. Not totally sure though, since the question wants bidirectional all the time. Anyone else see issues with picking C?
D , only the active relationship with security filter in both directions handles RLS properly here.
Its D for this, but I remember seeing some confusion around C in practice dumps. Only D has both active relationship and the right security filter enabled. If you haven't already, I'd check the official docs and try out a test model in Power BI Desktop to see how RLS actually applies with those settings. Not 100% but D matches what I've seen.
C tbh, since inactive can still work if you use USERELATIONSHIP in a DAX measure.
Be respectful. No spam.
