DP-600 Maintain a Data Analytics Solution Practice Question

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

• ✗

  Assign individual user permissions to each item within the workspace for granular control.

  Why it's wrong here

  Assigning permissions at the item level to individual users is a maintenance nightmare that leads to 'permission bloat' and security gaps. It makes it extremely difficult to audit who has access to what and to revoke access when users change roles. This approach is not scalable and increases the administrative burden on the IT team.

• ✓

  Use Microsoft Entra ID (formerly Azure AD) groups for workspace role assignments.

  Why this is correct

  Using security groups allows administrators to manage access at scale. When a user's role changes, updating their group membership automatically updates their access across all relevant Fabric workspaces. This practice ensures consistency, simplifies auditing, and aligns with enterprise identity management standards, making it much easier to maintain a secure environment over time.

• ✗

  Create a separate capacity for every workspace to isolate resource consumption.

  Why it's wrong here

  Creating a separate capacity for every workspace is cost-prohibitive and inefficient. Microsoft Fabric capacities are designed to be shared across multiple workspaces, with the system managing resource allocation dynamically. A better approach is to monitor capacity usage and group related workspaces together on a capacity that matches their combined resource requirements and performance needs.

• ✗

  Disable the 'Tenant settings' for all users except for one global administrator.

  Why it's wrong here

  While tenant settings should be restricted, disabling them for all but one person creates a single point of failure and administrative bottleneck. Maintenance is better served by having a small group of trained Fabric Administrators who can manage settings. This ensures that critical updates and governance policies can be applied promptly even if one administrator is unavailable.

• ✓

  Implement a workspace naming convention that includes the department and environment.

  Why this is correct

  A standardized naming convention (e.g., 'FIN-PROD-Reporting') is a simple yet powerful maintenance tool. It allows users and administrators to quickly identify the purpose, owner, and lifecycle stage of a workspace. This clarity reduces confusion, helps in organizing the Fabric tenant, and makes it much easier to apply automated scripts for monitoring or cleanup tasks.