Microsoft DP-700 Practice Test 31

Question 300

A Structured Streaming job has been configured for restart safety. What acceptance test is meaningful?

Stop and restart after a controlled batch using the same checkpoint, then reconcile new and previously committed output keys without unintended duplicates.
Delete the checkpoint and rerun from the beginning, then accept duplicated sink records.
Check the notebook executes without exceptions, but do not reconcile output event IDs.
Run two separate queries with different checkpoint paths and compare only their input counts.

Explanation

Correct Answer

A two-session test demonstrates checkpoint recovery and sink consistency rather than just initial streaming success.

Incorrect Answers

Removing checkpoint state invites reprocessing instead of verifying stable recovery and idempotent output.

A successful execution can duplicate previously committed records after restart.

Different paths mean different query state; similar counts don't establish exactly-once business results.

Question 301

An operations team has recent alarm events in an Eventhouse native table and must summarize them by device. Which query surface should be used?

Copy Eventhouse native alarm rows into a new SQL Warehouse before each KQL summary.
Query the existing KQL table with KQL summarize/filter expressions on the appropriate event fields.
Use a notebook environment to execute KQL `summarize` as if it were Spark SQL.
Query a lakehouse Files path that has no connection to the Eventhouse alarm table.

Explanation

Correct Answer

Eventhouse native tables are directly queryable with KQL and need no additional warehouse copy for straightforward real-time analytics.

Incorrect Answers

The existing KQL database already provides native query and summarize operations without extra copies.

KQL queries run in Eventhouse/Kusto, not natively in an unrelated Spark execution environment.

A storage path to unrelated data cannot summarize the ingested native KQL alarm events.

Question 302

An engineer cannot find events in a newly created SQL warehouse, although they are visible in an existing Eventhouse table. What explains the difference?

The SQL warehouse automatically inherits every KQL table upon Eventhouse creation.
The analyst did not configure a Power BI refresh on the Eventhouse table.
The events were ingested into the KQL database, not automatically replicated into an unrelated SQL warehouse.
The KQL table needs to be stored under the SQL warehouse's Files directory.

Explanation

Correct Answer

Fabric separates physical data stores and query engines; an Eventhouse table does not become a warehouse table just because both are in one workspace.

Incorrect Answers

An Eventhouse is a separate KQL database; unrelated warehouse tables are not automatically populated.

Report refresh does not copy an Eventhouse native table into a new SQL warehouse.

The KQL native table uses Eventhouse storage/query semantics, not an unlinked warehouse Files folder.

Question 303

A KQL aggregation on an Eventhouse native table is deployed. What validates it?

Confirm the SQL warehouse has a table named AlarmEvents but do not query the Eventhouse table.
Check that the KQL query executes but ignore the device grouping and filtered time range.
Validate only a screenshot of a recent dashboard, with no underlying KQL row reconciliation.
Run a bounded query on known device events and compare grouped counts and timestamps to those ingested into the native KQL table.

Explanation

Correct Answer

The direct query and per-device reconciliation validate the intended source and KQL aggregation.

Incorrect Answers

A similarly named unrelated warehouse table does not verify the KQL source data or aggregation.

Execution alone cannot establish correct per-device summary values.

A dashboard could show cached or differently filtered results and does not prove the KQL aggregate.

Question 304

An Eventhouse KQL database must read a maintained Delta table in a different Fabric lakehouse without importing its historical contents. What should it configure?

Create a supported OneLake shortcut in the KQL database and reference it through `external_table()` with effective source permissions.
Refer to the OneLake shortcut name directly as a native KQL table identifier.
Perform a full one-time KQL ingestion of all historical Delta data despite the no-import requirement.
Use a lakehouse SQL endpoint view as a substitute for a KQL external table reference.

Explanation

Correct Answer

KQL database shortcuts present compatible source Delta data as external tables for in-place queries rather than always requiring native ingest.

Incorrect Answers

The shortcut is exposed as an external KQL table and must be accessed through the supported `external_table()` surface.

Physical duplication contradicts the requirement to retain the maintained lakehouse as the data source.

A SQL view is a different query surface and cannot by itself expose the Delta table to Eventhouse KQL.

Question 305

A KQL query fails when it uses a shortcut name as though it were a native KQL table. What is the query-surface distinction?

The KQL shortcut query is missing a SQL `SELECT TOP` clause before the shortcut name.
A OneLake shortcut in a KQL database is an external table accessed using `external_table()` rather than a native table identifier.
The source lakehouse table must be physically replicated into Eventhouse for `external_table` to work.
The shortcut was given a Fabric domain name that conflicts with a native table.

Explanation

Correct Answer

Eventhouse treats shortcut-backed Delta data through its external-table interface and has separate access and performance characteristics.

Incorrect Answers

OneLake shortcuts in KQL databases are external tables addressed with `external_table()`, not SQL syntax.

KQL external-table references can query external Delta data directly when properly configured and authorized.

Domain labels do not turn an external shortcut reference into a native KQL table name.

Question 306

A KQL database shortcut to a lakehouse table is created. What verifies its effective use?

Execute a query using the shortcut name as an unqualified native table identifier.
Confirm the shortcut exists but avoid querying any of the known source rows.
Run `external_table()` against the shortcut as an authorized user and compare known rows with the source Delta table and current shortcut schema.
Test the table only via a lakehouse SQL endpoint and assume KQL uses identical query syntax.

Explanation

Correct Answer

A real external-table query establishes correct reference, identity access and data type mapping.

Incorrect Answers

That reproduces the original surface confusion; a valid external-table query is needed.

An icon alone cannot validate KQL external-table syntax or effective source permissions.

SQL and KQL query surfaces differ; SQL success cannot validate `external_table()` in Eventhouse.

Question 307

A KQL query over an external Delta shortcut is much slower than a native Eventhouse table, but the source must remain in OneLake. Which supported acceleration can help?

Copy source Delta files into every query node and disable caching.
Turn on lakehouse V-Order and assume every KQL external query is served from a native Eventhouse index.
Replace `external_table()` with a native table name without ingesting a native KQL table.
Evaluate query acceleration for the shortcut’s external Delta table, including cache horizon, data format and regional/cost requirements.

Explanation

Correct Answer

Query acceleration caches/indexes eligible external Delta data for faster KQL reads without converting it to a fully managed native table.

Incorrect Answers

Manual duplication adds maintenance burden and doesn't use supported Eventhouse external-table acceleration.

Delta file layout can help scans but doesn't automatically activate KQL query acceleration/caching.

Renaming the expression doesn't convert a OneLake shortcut into a native, indexed Eventhouse table.

Question 308

An Eventhouse shortcut is slow despite frequent queries; no acceleration policy is active. Why might its performance differ from a native KQL table?

Queries may repeatedly fetch external Delta files without native Eventhouse indexing or shortcut cache acceleration.
The cache policy is ineffective because the external Delta source does not have a KQL native ingestion mapping.
The shortcut's OneLake path must be renamed after every KQL query to keep it fresh.
Changing the KQL shortcut query to a native table identifier will enable native indexes even though no native table has been ingested.

Explanation

Correct Answer

The external-table query path can incur remote object retrieval and pruning overhead not present for native ingested KQL data.

Incorrect Answers

Query acceleration can cache supported external Delta references without converting them to native ingestion.

Renaming paths breaks references and cannot establish cache acceleration for repeated scans.

The shortcut is still an external table and requires `external_table()`; changing only the query identifier cannot create a native KQL table or its indexes.

Question 309

A query acceleration policy is enabled for a KQL shortcut. What should be measured to validate its effect?

Compare only the first cold query after enabling acceleration and stop measuring.
Compare identical bounded KQL queries before and after cache warm-up, reviewing latency, accelerated data statistics and storage cost.
Report cache policy status without confirming that the query reads correct source data.
Benchmark an unrelated native Eventhouse table instead of the target shortcut.

Explanation

Correct Answer

Accelerated cache behavior must be observed under equivalent workloads rather than inferred from toggling a policy.

Incorrect Answers

Acceleration may require warmup; single cold timings cannot establish steady-state gains.

A configured cache can be stale, ineligible or not beneficial; correctness and observed query metrics matter.

Native table latency does not measure the benefit for the accelerated external Delta path.

Question 310

An Eventhouse is expected to serve very frequent low-latency telemetry searches with native indexing and retention. Which storage architecture fits?

Use an external OneLake shortcut for all hot telemetry reads without assessing latency or acceleration.
Reimport every event into a SQL Warehouse at a nightly cadence.
Ingest the event feed into a native Eventhouse KQL table using a supported connector and appropriate retention/ingestion mapping.
Set Eventhouse retention to zero while attempting to preserve a history of alarm records.

Explanation

Correct Answer

Native KQL tables provide Eventhouse indexing and query behavior designed for high-QPS event workloads.

Incorrect Answers

External shortcut scans may be slower than native KQL ingestion/indexing under frequent search workloads.

A scheduled warehouse import cannot serve the required frequent low-latency native KQL search pattern.

Aggressive removal conflicts with the stated retention and recent-search use case.

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

Microsoft DP-700 Practice Test 29 - 10 Questions (Last Reviewed 06-Oct-2026)
Microsoft DP-700 Practice Test 30 - 10 Questions (Last Reviewed 05-Oct-2026)
Microsoft DP-700 Practice Test 31 - 10 Questions (Last Reviewed 04-Oct-2026)
Microsoft DP-700 Practice Test 32 - 10 Questions (Last Reviewed 03-Oct-2026)
Microsoft DP-700 Practice Test 33 - 10 Questions (Last Reviewed 02-Oct-2026)

Pass Your Microsoft DP-700 Exam Easy!

Question 300

Explanation

Correct Answer

Incorrect Answers

Question 301

Explanation

Correct Answer

Incorrect Answers

Question 302

Explanation

Correct Answer

Incorrect Answers

Question 303

Explanation

Correct Answer

Incorrect Answers

Question 304

Explanation

Correct Answer

Incorrect Answers

Question 305

Explanation

Correct Answer

Incorrect Answers

Question 306

Explanation

Correct Answer

Incorrect Answers

Question 307

Explanation

Correct Answer

Incorrect Answers

Question 308

Explanation

Correct Answer

Incorrect Answers

Question 309

Explanation

Correct Answer

Incorrect Answers

Question 310

Explanation

Correct Answer

Incorrect Answers

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