Free Microsoft Data Engineering DP-700 Actual Exam Questions - Question 6 Discussion
Workspace2.
The company decides to implement a domain strategy to organize the workspaces.
You need to ensure that a user can perform the following tasks:
Create a new domain for the sales department.
Create two subdomains: one for the east region and one for the west region.
Assign Workspace1 to the east region subdomain.
Assign Workspace2 to the west region subdomain.
The solution must follow the principle of least privilege.
Which role should you assign to the user?
C, since domain contributor covers creation without full admin rights, fitting least privilege.
Assigning workspaces to subdomains seems like a step beyond just creating them, so domain contributor might not cover it fully. Domain admin probably fits better for managing both creation and assignments while still scoped to domains.
It’s C because domain contributor lets you create domains and subdomains without full admin rights, which is more aligned with least privilege than domain admin or Fabric admin roles.
C/D? Domain contributor might let you create domains and subdomains without full admin rights, which fits least privilege better than domain admin. But assigning workspaces could need elevated permissions, maybe Fabric admin? Workspace admin seems too narrow since it’s only about managing workspaces, not domains. So, if the key is least privilege and they must assign workspaces within domains, Fabric admin could cover both creation and assignment without full domain control. Still unsure if contributor alone can handle workspace assignment though.
B imo, since creating domains and subdomains plus assigning workspaces sounds like full control over the domain setup, which fits domain admin. Contributor seems too limited for all these tasks.
Option B looks right since you need to create domains and assign workspaces, which usually requires domain admin rights. Contributor might not cover the workspace assignments.
B makes sense since assigning workspaces usually needs domain admin rights, not just contributor.
Maybe B fits best since domain admin likely covers creation and assignment fully.
B imo. The question requires both creating domains/subdomains and assigning workspaces to them. From what I understand, the domain contributor role likely only lets you create or edit domains but not assign workspaces. Workspace admin is too limited since it focuses on workspace-level permissions, and Fabric admin is too broad. Domain admin covers all needed permissions without going full admin on everything else, so it fits the least privilege principle better than D.
B/C? Domain admin feels like it covers both creation and assignment fully, which is needed here. Domain contributor might be too limited if it can't assign workspaces, so B seems safer for least privilege with all tasks.
Maybe B makes sense since creating domains and assigning workspaces seems like more than just contributing; it probably needs higher privileges than option C.
C imo makes the most sense here since you want the user to create domains and subdomains but not have full admin control. Domain contributor should let them manage domains with enough permissions to assign workspaces without giving excessive rights. Workspace Admin feels too limited, and Fabric Admin is overkill. Domain Admin might be close, but it usually grants broader permissions than needed for least privilege.