Microsoft Fabric Analytics Engineer Associate (DP-600) practice questions

An analytics engineer joins a "Microsoft Fabric" workspace and must be able to create and edit reports, semantic models, and a "Lakehouse", and to publish content into the workspace. The team lead wants this person to have the lowest workspace role that still allows authoring all those items, without the ability to add or remove other users or change workspace settings. Which workspace role should be assigned?

• AAssign the Contributor role, which lets the engineer create, edit, and publish workspace items while withholding the ability to manage workspace access and settings.check_circle Correct
• BAssign the Viewer role, which lets the engineer open and consume the workspace items and refresh any semantic models that back the published reports.
• CAssign the Member role, which lets the engineer author all items and additionally share the workspace and add other users with lower roles.
• DAssign the Admin role, which grants full authoring plus control over workspace settings, user roles, and deletion of the entire workspace.

Why A is correct: Contributor is the lowest role that grants full authoring of items yet excludes adding users and changing settings, matching the least-privilege authoring requirement exactly.

Why B is wrong: Viewer is read-only and cannot create or edit items, so it cannot satisfy a requirement to author reports, semantic models, and a Lakehouse.

Why C is wrong: Member does grant authoring, but it also lets the user add others and reshare, exceeding the stated limit of no access management, so it is not the lowest sufficient role.

Why D is wrong: Admin gives the broadest control including settings and user management, far more than authoring needs, so it breaks the least-privilege constraint the lead set.

An enterprise "semantic model" must report over billions of Delta rows held in a "Lakehouse" in "OneLake". The team needs near real-time freshness without scheduled refreshes, in-memory query speed for reports, and no duplication of the data into the model. Which storage mode should they choose for these tables?

• AImport mode, because it loads the Delta tables into the model for fast in-memory queries and refreshes them on a schedule so reports stay close to the source data.
• BDirectQuery mode, because it queries the Delta tables in place for near real-time freshness and answers report queries from memory without copying any data into the model.
• CDual storage mode, because it both imports the Delta tables for in-memory speed and queries them live for freshness while avoiding any copy of the data into the model.
• D"Direct Lake" mode, because it reads the Delta tables directly from "OneLake" with in-memory speed and reflects source changes without copying data or running scheduled refreshes.check_circle Correct

Why A is wrong: Import mode copies the Delta tables into the model and depends on scheduled refresh, which both duplicates the data and breaks the near real-time requirement, so it does not fit.

Why B is wrong: DirectQuery avoids duplication and stays fresh, but it sends each query to the source rather than serving results from memory, so it cannot deliver the in-memory query speed required.

Why C is wrong: Dual mode lets a table behave as import or DirectQuery per query, but its import side still caches a copy of the data, so it does not avoid duplication the way the requirement demands.

Why D is correct: "Direct Lake" loads Delta data from OneLake into memory on demand and tracks source changes, delivering import-like speed with near real-time freshness and no data duplication, which meets every stated need.

A single Power BI report in a "Microsoft Fabric" workspace must be made available to one external auditor who needs to view only that report and nothing else in the workspace. The auditor should not appear in the workspace role list and should not gain access to other reports, the "Lakehouse", or the semantic models stored alongside it. What is the most appropriate way to grant this access?

• AAdd the auditor to the workspace with the Viewer role so the read scope is limited to viewing rather than editing any of the contained items.
• BShare the individual report with the auditor using item-level sharing, granting read access to just that report without adding the auditor to any workspace role.check_circle Correct
• CCreate a OneLake data access role on the underlying "Lakehouse" and map the auditor to it so the report data is reachable through that role.
• DPublish the workspace as an app and add the auditor to the app audience so the single report is delivered through the packaged app instead.

Why A is wrong: Viewer is scoped to the whole workspace, so the auditor would see every report and item there, breaking the requirement to expose only one report.

Why B is correct: Item-level sharing grants access to a single item without workspace membership, so the auditor sees only that report and never appears in the workspace role list.

Why C is wrong: OneLake data access roles govern table and folder access in a Lakehouse, not visibility of a Power BI report, so they cannot scope report viewing.

Why D is wrong: An app can scope content, but building and maintaining an app for one external viewer is heavier than directly sharing the one report the requirement names.