DP-600 Practice Test

Sample DP-600 Practice Questions

10 real questions from the free DP-600bank. Pick an answer in your head, then open “Show answer” for the explanation.

1. 1. An analyst opens impact analysis on a data source item to see what downstream items depend on it. What is the analyst able to see for this data source, compared to a Fabric item like a lakehouse?

   • A. The same view as a Fabric item - downstream items regardless of how many hops away, plus the connection string
   • B. Nothing, since data sources do not support impact analysis
   • C. Only the direct child items of the data source, along with the connection string used to connect to it
   • D. Affected workspaces alone, with no item-level detail
   Show answer

   Correct answer: C

   For data sources specifically, impact analysis shows only direct children, not further downstream items, plus the connection string used to connect - to see further downstream effects, you must then run impact analysis on those direct children. Option A overstates what is shown for a data source. Option B is false, since data sources are supported. Option D understates what is shown, since item-level direct children are visible.

2. 2. A shared enterprise semantic model must hide the Salary column from most report viewers to satisfy a payroll-data compliance requirement, but the Finance leadership sub-team still needs full access to that column through the same shared model - the team cannot maintain a second duplicate model just for this one column. Which security capability, configured with different roles for the two viewer groups, satisfies both the compliance requirement and the single-shared-model constraint?

   • A. Row-level security (RLS), since a single set of DAX roles can filter out the Salary column for most viewers while allowing Finance leadership through
   • B. A sensitivity label protection policy applied to the whole semantic model, restricting the entire model to Finance leadership alone
   • C. A second, duplicate semantic model containing non-sensitive columns, published for the general viewer audience
   • D. Object-level security (OLS), configured with one role that excludes the Salary column for most viewers and a separate role that includes it for Finance leadership
   Show answer

   Correct answer: D

   OLS lets model authors define multiple roles with different table and column permissions and assign different viewer groups to each, so one role hides the Salary column for general viewers while a separate role grants Finance leadership full access, all within the one shared model. Option A is wrong on the technical merits, since RLS filters rows, not columns, and cannot hide a specific column. Option B satisfies the compliance requirement but violates the shared-model constraint's other half, since it would also block the general viewer audience the model still needs to serve. Option C avoids duplicating the Salary column but violates the single-shared-model constraint by requiring a second model to be maintained just for the general audience.

3. 3. When Power BI Desktop saves work as a Power BI Project (.pbip), what does the project folder contain for the report and semantic model, as opposed to a single binary file?

   • A. Separate folders, such as *.Report and *.SemanticModel, with individual metadata text files defining the report and model
   • B. A single compressed binary file identical in structure to a .pbix, just renamed with a .pbip extension
   • C. A .pbip pointer file, with report and model content stored in Fabric's cloud service rather than locally
   • D. A single large JSON file containing the entire report and model definition, similar to a legacy Model.bim file
   Show answer

   Correct answer: A

   Saving as a project splits the content into a folder structure with separate *.Report and *.SemanticModel folders, each containing individual, human-readable text files defining the item. Option B mischaracterizes .pbip as just a renamed binary. Option C is wrong, since the local project folder itself holds the definitions, independent of cloud storage. Option D describes the older Model.bim single-file approach, not the PBIP folder structure.

4. 4. A Fabric admin wants workspace admins to be able to override sensitivity labels that were applied automatically through label inheritance from data sources, without following the normal label change enforcement rules. Which tenant setting should the admin enable?

   • A. Restrict content with protected labels from being shared via link with everyone in your organization
   • B. Domain admins can set default sensitivity labels for their domains
   • C. Allow workspace admins to override automatically applied sensitivity labels
   • D. Allow users to apply sensitivity labels for Power BI content
   Show answer

   Correct answer: C

   The tenant setting "Allow workspace admins to override automatically applied sensitivity labels" specifically lets workspace admins override auto-applied labels regardless of the normal enforcement rules. Option A restricts sharing links, not label overrides. Option B sets domain-level default labels for new items, not overrides on existing auto-applied ones. Option D is the base toggle that enables sensitivity labels generally, not the override capability.

5. 5. A workspace-level setting called "Allow users with at least Contributor role to change Git branch" is enabled. A Contributor on the workspace has write access to all items in it. What Git action can this Contributor now perform that a Contributor could not do with the setting disabled?

   • A. Connect or disconnect the workspace from its Git repository
   • B. Grant other users Contributor or Member roles on the workspace
   • C. Certify items in the workspace as meeting organizational quality standards
   • D. Switch the connected branch and check out new branches
   Show answer

   Correct answer: D

   With that setting enabled, Contributors who have write access to all items gain the ability to switch branches and check out new branches - actions otherwise reserved for higher-privileged Git roles. Option A, connecting or disconnecting, remains an Admin-level action tied to the workspace-to-repo connection itself. Option B is a workspace role-management action unrelated to this Git setting. Option C is an endorsement action, unrelated to Git branch permissions.