How Do Fabric Default Domains Affect Workspace3 Access?
HOTSPOT
You have three users named User1, User2, and User3.
You have the Fabric workspaces shown in the following table.
You have a security group named Group1 that contains User1 and User3.
The Fabric admin creates the domains shown in the following table.
User1 creates a new workspace named Workspace3.
You add Group1 to the default domain of Domain1.
For each of the following statements, select Yes if the statement is true. Otherwise, select No.
NOTE: Each correct selection is worth one point.

Community Insight
The tested point is separating domain roles from workspace roles; the trap is assuming Domain1 default-domain membership gives Group1 members Viewer or Contributor access to Workspace3.
Microsoft Fabric default-domain membership can assign a new workspace to a domain and make group members domain contributors, but it does not grant workspace item access. This page establishes the hotspot verdict as No for workspace access, Yes for User3's domain contributor status, and No for workspace-level permissions.
The common wrong approach is treating domain contributor status as equivalent to a workspace role, so learners incorrectly grant User3 item-level access to Workspace3 even though workspace permissions must be assigned separately.
Community Discussion (23 comments)
Comments & Corrections
No comments yet — spotted an error or have a note? Share it below.
Expert Analysis
Why the Answer Is Correct
User1 creates Workspace3, and Group1, which contains User1 and User3, is in the default domain of Domain1. That default-domain setup means new workspaces created by specified users are associated with the domain, and Group1 members generally become domain contributors; however, domain contributor is a domain role, not a Workspace3 workspace role. Therefore the correct selections are No for User2/workspace access, Yes for User3 becoming a domain contributor, and No for User3 having workspace-level permissions through that domain role.Why Other Candidate Answers Are Wrong
Answering Yes where the question asks about workspace access confuses Fabric domains with workspace roles. User2 is not in Group1 and was not added to Workspace3, so User2 does not gain access through Domain1. The all-No response is also wrong because it ignores the automatic domain contributor behavior triggered when Group1 is added to the default domain.Community Comment Notes
As giraf noted, "Being a domain contributor doesn't give you any permissions on the workspace itself"—domain governance and workspace item permissions are separate. Rozamunde and Waloo2_11 correctly focus on the default-domain rule that new workspaces created by specified users are assigned to the domain and that specified group members generally become domain contributors. vish9's all-No answer illustrates the common error of dismissing the default-domain contributor effect entirely.Official Reference
Exam Strategy
Evaluate domain assignment and domain role first, then evaluate workspace access only from the workspace role table or explicit workspace permissions. Never let a Yes for domain contributor become a Yes for Viewer, Contributor, or Admin in Workspace3.
Frequently Asked Questions
Does adding Group1 to Domain1's default domain give User3 Viewer access to Workspace3?
No. Domain contributor status is separate from workspace roles; User3 needs an explicit Workspace3 role for item-level access.
Is Workspace3 automatically assigned to Domain1 when User1 creates it?
Yes. New workspaces created by users in a default domain are automatically assigned to that domain, and Group1 members generally become domain contributors.