To group workspaces for certain company divisions that should support OneLake data hub filtering, which pairing of grouping method and tool is correct?

To group workspaces for certain company divisions that should support OneLake data hub filtering, which pairing of grouping method and tool is correct?

• A. Capacity / The Fabric Admin portal
• B. Domain / The Fabric Admin portal
• C. Tenant / OneLake data hub
• D. Domain / The Microsoft Entra admin center

Answer: (B)

Grouping by domain matches how the company is structured, which lets OneLake data hub filtering apply per division. The Fabric Admin portal is the right place to configure this—it's where you manage workspaces, assign them to domains, and enforce domain-based filtering for OneLake. Capacity and tenant are resource or broader- scope boundaries that don’t align with division-level filtering, and the Microsoft Entra admin center handles identities rather than organizing workspaces for OneLake filtering. So the domain-based grouping implemented through the Fabric Admin portal is the correct pairing.

Grouping by domain matches how the company is structured, which lets OneLake data hub filtering apply per division. The Fabric Admin portal is the right place to configure this—it's where you manage workspaces, assign them to domains, and enforce domain-based filtering for OneLake. Capacity and tenant are resource or broader- scope boundaries that don’t align with division-level filtering, and the Microsoft Entra admin center handles identities rather than organizing workspaces for OneLake filtering. So the domain-based grouping implemented through the Fabric Admin portal is the correct pairing.