Q: 7
You have a Fabric tenant that contains two workspaces named Woritspace1 and Workspace2. Workspace1 contains a lakehouse named Lakehouse1. Workspace2 contains a lakehouse named Lakehouse2. Lakehouse! contains a table named dbo.Sales. Lakehouse2 contains a table named dbo.Customers. You need to ensure that you can write queries that reference both dbo.Sales and dbo.Customers in the same SQL query without making additional copies of the tables. What should you use?
Options
Discussion
ResearchReviewersGroup1: Viewer
ResearchReviewersGroup2: Contributor
This matches least privilege. Group1 just needs to see reports, so Viewer is enough. Group2 edits, so Contributor fits. Pretty sure this is what MS expects here, but open if anyone sees a catch.
Saw this in some practice sets-Group1 gets Viewer, Group2 gets Contributor. That lines up with least privilege since only the second group should modify anything. Pretty sure that's right but let me know if anyone read the requirements differently.
Nah, I don’t think Contributor fits for ResearchReviewersGroup1 here, despite what some mocks show. Viewer is right for them since they just need to read and RLS should stay enforced. ResearchReviewersGroup2 gets Contributor so they can make changes. Sometimes people mix them up but least privilege is the key.
D . Shortcut is made for referencing tables across lakehouses without copying data. Easy trap is B, but dataflow would transform, not just link. Pretty confident unless Fabric changed something recently.
Makes sense to split it this way: Group1 as Viewer, Group2 as Contributor. That matches least privilege since Group1 just needs read access and RLS would apply, while Group2 can edit if necessary. Not totally sure unless the requirements say otherwise.
If RLS is a factor, then Group1 must stay Viewer so those filters apply. Group2: Contributor.
ResearchReviewersGroup1: Viewer, ResearchReviewersGroup2: Contributor
If Group1 was supposed to edit anything, they'd need Contributor. Otherwise, strict least privilege applies and Viewer is safest. Seen a similar question where RLS mattered for Group1 access level. Disagree?
ResearchReviewersGroup1: Viewer, ResearchReviewersGroup2: Contributor
Makes sense to flip them, but I put ResearchReviewersGroup1: Contributor, ResearchReviewersGroup2: Viewer. Thought Group1 would need more access since sometimes 'reviewers' means they edit. Could be overthinking-what do you guys think?
Hmm, if Group1 sometimes needs to refresh datasets, wouldn't Contributor fit? ResearchReviewersGroup1: Contributor, ResearchReviewersGroup2: Viewer
Be respectful. No spam.