Microsoft DP-700 Practice Test 7

Question 60

The release manager has just promoted approved Test changes to Production in a Fabric deployment pipeline. Which verification best demonstrates that the intended items, and no unintended ones, changed?

Verify that an unrelated Dataflow Gen2 row count is nonzero.
Compare the post-deployment stage statuses and target item definitions against the approved selection and the deployment history.
Check only that the source Git branch contains a new commit.
Change the workspace domain before inspecting differences.

Explanation

Correct Answer

Stage comparison and deployment receipts reveal which paired items were updated; checking their target definitions prevents falsely assuming unrelated items stayed untouched.

Incorrect Answers

A nonzero dataflow output cannot prove the deployed item definitions match the approved target selection.

A repository commit is not proof that the exact item selection was promoted to the correct Production workspace.

Domain membership is not a substitute for comparing deployed item definitions and history.

Question 61

A production Fabric notebook was accidentally edited. Its previously approved definition is preserved in the connected Git repository. What is a controlled method to restore the approved version?

Recreate a warehouse table with the notebook’s name.
Change Spark pool autoscale settings and expect the previous cells to return.
Restore the intended reviewed Git revision and synchronize or redeploy that notebook definition through the supported workspace workflow.
Copy the notebook’s prior output rows into a lakehouse folder.

Explanation

Correct Answer

Git provides versioned item definitions. Applying the specific approved commit or revision back to the workspace restores source code with traceable release evidence.

Incorrect Answers

A SQL table cannot restore the executable notebook definition tracked in Git.

Compute sizing does not revert code edits made to the notebook item definition.

Historical outputs are data, not the authored notebook code revision that needs restoration.

Question 62

An engineer wants to roll back a notebook change but discovers that the last approved revision was never committed and only existed as an unsynced local workspace edit. What is the core recovery limitation?

Fabric Git history automatically versions all session-local notebook outputs.
Git cannot restore an uncommitted notebook definition that was never part of its tracked revision history.
Every rollback requires changing the workspace’s capacity SKU first.
The notebook’s default lakehouse must have an Eventhouse table for rollback.

Explanation

Correct Answer

A Git rollback requires a saved commit or otherwise recoverable artifact containing the approved definition. Uncommitted changes may be lost when overwritten or the workspace is reset.

Incorrect Answers

Git tracks supported item definitions, not arbitrary notebook session state or uncommitted output data.

Capacity reassignment does not recreate source revisions missing from Git history.

Storage attachment does not supply a missing Git commit or a previously reviewed notebook definition.

Question 63

A team restores the approved Git revision of a Fabric notebook after a faulty production edit. What check proves the intended code—not just familiar output—was restored?

Compare the actual Production notebook definition with the reviewed commit and confirm the workspace reports the correct synchronized state.
Check only that yesterday’s report refresh still displays the same row count.
Verify that the Spark starter pool has more nodes than yesterday.
Confirm that the workspace remains assigned to its original domain.

Explanation

Correct Answer

Definition comparison against an identified approved commit verifies the rollback. A similar execution result alone cannot establish code identity.

Incorrect Answers

Outputs can coincide even when the notebook source differs, making row counts weak rollback evidence.

Compute provisioning is independent of the actual notebook definition restored from Git.

Domain association does not prove an item was restored to an approved source-control revision.

Question 64

Two developers modify the same Fabric notebook after the last Git sync. One adds a data-quality assertion in the workspace; the other commits an incremental watermark filter to Git. Both code changes must survive, but the workspace shows Conflict. What is the safest resolution?

Select Accept incoming changes and assume Fabric combines both developers’ code automatically.
Reconcile both edits in a merged Git revision, review and commit that combined definition, then synchronize it to the workspace.
Select Keep current content and assume the remote watermark filter is automatically merged into the workspace code.
Increase the Spark pool worker count and retry the commit without reviewing the diverged definitions.

Explanation

Correct Answer

A reviewed Git merge can contain both independent changes. Synchronizing that merged definition resolves the conflict without silently dropping either the workspace assertion or the remote watermark filter.

Incorrect Answers

Accept incoming changes replaces the workspace item with the Git version and can discard its uncommitted assertion; Fabric does not automatically combine the two code edits.

Keep current content retains the workspace copy and makes it an uncommitted change; it does not automatically incorporate code that exists only in the remote Git revision.

Spark compute capacity does not merge two notebook definitions or repair Git conflict state. Reconciliation of the source code is required.

Question 65

A Fabric notebook shows Git status Conflict after two independent edits. The release manager chooses Accept incoming changes and the prior workspace-only modifications disappear. Why did that happen?

Changing an item’s Git branch automatically deletes all OneLake data.
Accept incoming changes replaces the conflicted workspace item with the incoming repository version.
Domain contributors cannot own notebooks, so the system removed their code.
The notebook’s Spark memory profile changed its stored source cells.

Explanation

Correct Answer

Fabric documents that accepting incoming changes can override workspace modifications. An unsaved workspace-only version can be lost unless reviewed and preserved first.

Incorrect Answers

Git conflict resolution concerns item definitions; wholesale OneLake data deletion is not the documented outcome of accepting an incoming notebook change.

Workspace-domain contributor status is unrelated to the conflict-resolution overwrite semantics.

Spark execution profiles do not decide which of two conflicting source definitions replaces the other.

Question 66

The Fabric notebook conflict has been resolved by a reviewed merge that should preserve both a data-quality assertion and an incremental watermark filter. The workspace Git status now says Synced. Which verification best proves neither developer’s change was lost?

Trust the Synced label without examining the merged notebook source.
Confirm the notebook runs with the same Spark pool as before the conflict.
Compare the destination notebook definition with the approved merged Git revision and inspect the assertion and watermark filter in both.
Check that the Fabric domain remains unchanged after the merge.

Explanation

Correct Answer

The content comparison ties the deployed notebook to the specifically reviewed merged revision and explicitly proves both distinct edits survived, beyond a generic conflict-free Git status.

Incorrect Answers

Synced status establishes agreement with a particular Git revision but does not prove the intended merge contains both developers’ changes; the wrong winning version can also be synchronized.

A Spark pool can remain unchanged when the notebook source loses either code change, so runtime allocation cannot validate the merged definition.

Domain affiliation is a governance setting unrelated to the two code changes or their source-control preservation.

Question 67

A finance analyst should discover one Fabric lakehouse and read a curated Delta table without changing any table data or workspace objects. Which access arrangement best fits?

Grant the analyst ReadAll through the default role for every lakehouse folder and table.
Grant only Build permission on an associated semantic model.
Give the analyst SQL endpoint SELECT while leaving OneLake data roles unconfigured.
Grant the analyst item-level Read and appropriate scoped OneLake Read data access, while avoiding Contributor or other write-granting workspace roles.

Explanation

Correct Answer

Item Read permits discovery while a suitably scoped OneLake role permits data reads; Contributor carries workspace-wide write authority and violates the stated restriction.

Incorrect Answers

DefaultReader backed by ReadAll can open substantially more than the single curated table. The requirement combines discovery with narrowly scoped table reads, so an all-data grant is too broad even without workspace editing rights.

Semantic-model Build enables supported model usage but does not itself authorize direct reads of the specified lakehouse Delta table through OneLake.

A SQL-granular grant applies on the supported SQL endpoint. The requested arrangement must also authorize the analyst’s direct OneLake access to the curated table without granting unrelated data.

Question 68

An analyst can see a lakehouse in the Fabric catalog but cannot read its Files directory in a compatible OneLake client. The user has only item Read. Which missing boundary explains the denial?

The SQL analytics endpoint needs a SELECT grant before OneLake can list the Files folder.
Item Read alone does not grant data access; a matching OneLake data role or ReadAll-backed DefaultReader grant is still required.
The analyst must publish the lakehouse before OneLake data can be read.
The lakehouse has no default attached notebook, so external OneLake reads are denied.

Explanation

Correct Answer

Fabric distinguishes item visibility from OneLake table/folder permissions. A user can discover an item without having effective Read access to its contents.

Incorrect Answers

A warehouse or SQL-endpoint SELECT privilege is scoped to its SQL execution surface. The failed request is a direct OneLake Files read, which depends on the caller’s effective OneLake data permission rather than a SQL object grant.

Lakehouse content is stored independently of publishing a Spark environment or notebook. The catalog item is visible already; the failure is the absence of data-level authorization.

A compatible external OneLake client addresses a workspace and item directly. Notebook attachment is not a prerequisite; item Read alone still needs a OneLake data grant to open Files.

Question 69

An analyst receives new read-only lakehouse permissions. What test demonstrates the intended least-privilege result?

Review only the lakehouse item-sharing list, without trying any table operation.
Run the test as a Finance workspace Admin and record the returned row count.
Sign in as that analyst, read the specifically granted table, attempt an unauthorized table write and verify denial, and verify no unrelated item access.
Show that the analyst can open the lakehouse overview page, then assume data and write tests passed.

Explanation

Correct Answer

Testing the actual principal, permitted table and denied modification checks effective authorization beyond the permission dialog and guards against broad workspace grants.

Incorrect Answers

The sharing list can show item Read while not proving the data role authorizes the curated Delta table or that writes and unrelated items are denied.

Workspace administrators receive elevated data access. Success under that identity does not establish that the intended read-only analyst can read the table without write privileges.

Opening the item establishes discovery, not a successful data-plane read or a blocked modification. Least privilege needs positive and negative tests with the actual analyst identity.

Question 70

A contractor may read `Files/exports/public` in a lakehouse, but not `Files/exports/payroll`. Which TWO controls help enforce this boundary?

Keep lakehouse-wide ReadAll while adding a separate narrow public-folder security role.
Assign lakehouse item Read plus a OneLake security role granting Read on the intended public folder only.
Move payroll underneath a directory labeled Confidential but grant the parent exports folder.
Remove any broad DefaultReader or ReadAll path that would also grant payroll, and test the role with the contractor identity.
Define a SQL-endpoint DENY on payroll and assume all OneLake Files API reads are denied.

Explanation

Correct Answers

Both item-level discovery and folder-scoped data authorization are necessary for read-only external personnel.

OneLake grants are additive; an existing role with broader scope defeats the intended narrow folder permission.

Incorrect Answers

A custom public Read grant cannot subtract the existing broader DefaultReader grant. The contractor would retain payroll access despite the apparently restrictive role.

Folder names and sensitivity descriptions do not block inherited OneLake Read. Granting the exports parent includes both public and payroll descendants.

SQL data-plane permissions do not create a filesystem permission boundary on Files/exports/payroll. A separate OneLake security role must govern the direct file path.

Implementing Data Engineering Solutions Using Microsoft Fabric (DP-700) Practice Tests

Microsoft DP-700 Practice Test 5 - 10 Questions (Last Reviewed 30-Oct-2026)
Microsoft DP-700 Practice Test 6 - 10 Questions (Last Reviewed 29-Oct-2026)
Microsoft DP-700 Practice Test 7 - 10 Questions (Last Reviewed 28-Oct-2026)
Microsoft DP-700 Practice Test 8 - 10 Questions (Last Reviewed 27-Oct-2026)
Microsoft DP-700 Practice Test 9 - 10 Questions (Last Reviewed 26-Oct-2026)

Pass Your Microsoft DP-700 Exam Easy!

Question 60

Explanation

Correct Answer

Incorrect Answers

Question 61

Explanation

Correct Answer

Incorrect Answers

Question 62

Explanation

Correct Answer

Incorrect Answers

Question 63

Explanation

Correct Answer

Incorrect Answers

Question 64

Explanation

Correct Answer

Incorrect Answers

Question 65

Explanation

Correct Answer

Incorrect Answers

Question 66

Explanation

Correct Answer

Incorrect Answers

Question 67

Explanation

Correct Answer

Incorrect Answers

Question 68

Explanation

Correct Answer

Incorrect Answers

Question 69

Explanation

Correct Answer

Incorrect Answers

Question 70

Explanation

Correct Answers

Incorrect Answers

Implementing Data Engineering Solutions Using Microsoft Fabric (DP-700) Practice Tests