Microsoft DP-700 Practice Test 29

Question 280

A daily sales metric calculated in KQL disagrees with the same metric in SQL. Which normalization approach should the team use?

Define a common business date, grouping keys, null policy, filters and rounding semantics, then implement equivalent aggregates in both engines.
Make both KQL and SQL queries display the same metric name and assume sums are equal.
Force both engines to round each input record independently before aggregation without business approval.
Compare only overall daily totals and omit region/product grouping keys.

Explanation

Correct Answer

KQL and SQL can differ in null handling and expression typing; a shared aggregation contract is necessary for comparable results.

Incorrect Answers

Display labels do not align source data, date boundaries, numeric types or filter logic.

Premature rounding can change sums; reconcile numeric precision and rounding at the defined aggregation stage.

Totals can match across engines while their group-level allocations remain inconsistent.

Question 281

A KQL `sum()` daily total differs from the SQL result despite reading similar data. Select TWO likely root causes to investigate.

The SQL aggregate must match KQL automatically because both use a function named SUM.
The discrepancy proves KQL always uses a different numeric type than SQL.
The engines use different event-time filters, time-zone conversions or binning boundaries.
Null or invalid numeric values are handled differently in the casts and aggregate expressions.
The displayed metric labels are different, which changes numeric aggregation in KQL.

Explanation

Correct Answers

If one engine groups by UTC day and the other by local day, near-midnight rows land in different buckets.

Differences in accepted rows and null conversion can produce different sums even over similar source files.

Incorrect Answers

Equivalent function names don't force identical input filters, numeric casts or time boundaries.

Each query's explicit casts and null policy must be examined; the engine name alone doesn't establish a specific discrepancy.

Presentation labels don't determine which source rows or values enter SUM.

Question 282

A KQL and a SQL daily metric are revised to a shared business definition. What is a robust equivalence test?

Compare only one daily total without including nulls or midnight-boundary events.
Ensure both queries have similar names and matching visualization colors.
Use an identical fixed dataset with nulls and boundary timestamps, compare group keys and sums, and investigate any remaining per-record differences.
Inspect only whether both engines execute the query without errors.

Explanation

Correct Answer

A deterministic fixture catches diverging row selection and arithmetic rather than relying on total-only comparison across unrelated datasets.

Incorrect Answers

A happy-path total can match while timezone, binning or cast differences remain.

Names and colors do not test source-row identity or grouping semantics.

Successful execution doesn't establish identical filters, grouping or numeric treatment.

Question 283

A mobile app generates live JSON telemetry and an operations team needs to query it through KQL with low latency. What Fabric ingestion architecture fits?

Configure an Eventstream source but omit the Eventhouse destination until the dashboard is built.
Point a nightly SQL Warehouse Copy activity at the live source and query the last completed batch.
Create an Eventhouse destination without validating timestamp field types or publishing the stream.
Create a supported Eventstream source and configure an Eventhouse/KQL database destination with appropriate mapping and publication.

Explanation

Correct Answer

Eventstream can ingest and route application events to an Eventhouse native store for low-latency KQL queries.

Incorrect Answers

Source ingestion alone doesn't place JSON telemetry into the KQL table needed for low-latency querying.

Nightly import fails the live event-to-query freshness requirement even with a KQL report layered on top.

An uncommitted or invalid destination mapping can reject records although the source receives messages.

Question 284

A live telemetry Eventstream receives events but the Eventhouse table remains empty. Select TWO likely configuration failures to investigate.

The Eventhouse destination was never attached or its changes were not published.
The Eventstream has not been renamed to match the Eventhouse target database.
The destination ingestion configuration or schema mapping rejects the incoming event payload.
A warehouse scheduled import has not been created to deliver daily JSON files.
The sensor lakehouse data has not been optimized by a nightly V-Order job.

Explanation

Correct Answers

A source-only stream does not automatically push records into a separate Eventhouse database.

Even with source traffic and a destination configured, invalid mapping can prevent accepted records from landing in the KQL table.

Incorrect Answers

Display names do not create or publish an Eventhouse destination, nor do they map incoming JSON fields.

The source events already reach Eventstream; the missing path is its published continuous Eventhouse destination.

Delta optimization does not activate an Eventstream sink or repair a rejected KQL ingestion mapping.

Question 285

An application Eventstream now routes to Eventhouse. What test proves the end-to-end path?

Verify that the Eventstream preview receives some events, but never query the target KQL table.
Publish the stream, emit a uniquely identified test event and query the expected KQL table for its parsed fields and arrival time.
Check the names of Eventstream and the KQL database instead of the destination connection.
Count the number of optimized Parquet files in an unrelated lakehouse.

Explanation

Correct Answer

A source-to-query correlation validates actual routing, ingestion mapping and observable freshness beyond a successful source connection.

Incorrect Answers

Source preview proves arrival at the source node, not successful routing and mapping to Eventhouse.

Name equality cannot prove the sink is connected, published or accepting actual event payloads.

Unrelated file layout cannot establish that the uniquely identified test event reached the expected KQL table.

Question 286

A security Eventstream receives severity values `debug`, `info` and `critical`, but only critical events should reach a sensitive alert destination. Which transformation should be applied?

Add a supported Eventstream Filter operation for critical severity before the alert destination and publish the topology.
Hide noncritical messages only in the Eventhouse dashboard visual.
Create the severity Filter branch but leave the protected destination connected to the unfiltered default output.
Use KQL dynamic data masking instead of an Eventstream severity Filter.

Explanation

Correct Answer

A pre-destination stream filter excludes unwanted event categories while preserving approved events for routing.

Incorrect Answers

Visualization filtering doesn't keep debug/info payloads from reaching the sensitive destination storage.

The destination will still ingest all severities unless routing is attached to the filtered branch.

Masking changes visibility of selected values, not the event-category routing before ingestion.

Question 287

An Eventhouse destination receives debug records even though a Filter was added to a separate derived branch. Why?

The derived filter is inactive because the Eventhouse capacity is too small to store debug messages.
The Eventstream severity column was renamed in the workspace's Fabric domain settings.
The dashboard has not excluded debug messages from visual display.
The Eventhouse destination remains connected to the unfiltered default stream instead of the filtered derived output.

Explanation

Correct Answer

Filtering one branch does not automatically affect destinations attached to another stream path.

Incorrect Answers

Capacity pressure might cause throttling, not deterministic bypass of a Filter attached to a different branch.

Domain labels do not determine which published stream branch feeds the Eventhouse destination.

Visual filtering only hides presentation; the physical Eventhouse destination still receives its unfiltered route.

Question 288

A severity Filter is deployed. What validation demonstrates that the routed stream includes only intended categories?

Send one known event of each severity, inspect the filter’s test result and destination records, and verify only critical events arrive at the protected target.
Check the destination only for critical messages while ignoring whether debug also arrives.
Compare the source Eventstream name to the destination's display name.
Inspect the Eventhouse compute-size setting after sending no test messages.

Explanation

Correct Answer

A multi-category fixture proves the actual stream branch and predicate are active rather than merely configured in the editor.

Incorrect Answers

Presence of critical records alone cannot prove noncritical events are excluded from the protected sink.

Connection labels do not show whether the sink uses filtered derived output rather than unfiltered default.

Compute configuration says nothing about per-severity routing and rejection behavior.

Question 289

A telemetry stream contains device IDs but analysts need the registered device type beside each event. What transformation approach is appropriate?

Sort incoming events by device ID and assume identical types are automatically attached.
Use a supported event enrichment/join operation with a maintained device reference dataset or perform the lookup in the chosen streaming/KQL engine.
Cross join the entire device reference with every telemetry event and filter later by event time.
Create separate Eventhouse tables for every device type instead of maintaining one keyed reference.

Explanation

Correct Answer

A key-based reference lookup can append contextual device attributes while avoiding hard-coded device metadata in every producer message.

Incorrect Answers

Sorting doesn't join live device IDs against their maintained reference attributes.

A cross join multiplies rows and won't enforce device-ID matching without an appropriate join predicate.

Per-type tables add routing complexity without providing authoritative type enrichment for incoming device IDs.

Question 290

After introducing an enrichment join, events from devices absent in the lookup table have missing type values. What explains the gap?

Every unregistered device must automatically be assigned the alphabetically first registered type.
The streaming engine lacks enough nodes to normalize the device ID column.
The join reference does not have a matching device key or the join policy excludes unmatched events.
Sorting incoming events by timestamp should produce their static device type.

Explanation

Correct Answer

A lookup can attach values only for matching source identifiers; the team must define handling for unknown devices and reference refresh timing.

Incorrect Answers

A reference-key miss should follow an explicit unmatched-event policy, not an arbitrary default attribute.

Insufficient compute would affect throughput; no matching lookup row explains missing enrichment for specific IDs.

Temporal ordering doesn't retrieve device attributes without a matching reference record.

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

Microsoft DP-700 Practice Test 27 - 10 Questions (Last Reviewed 08-Oct-2026)
Microsoft DP-700 Practice Test 28 - 10 Questions (Last Reviewed 07-Oct-2026)
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)

Pass Your Microsoft DP-700 Exam Easy!

Question 280

Explanation

Correct Answer

Incorrect Answers

Question 281

Explanation

Correct Answers

Incorrect Answers

Question 282

Explanation

Correct Answer

Incorrect Answers

Question 283

Explanation

Correct Answer

Incorrect Answers

Question 284

Explanation

Correct Answers

Incorrect Answers

Question 285

Explanation

Correct Answer

Incorrect Answers

Question 286

Explanation

Correct Answer

Incorrect Answers

Question 287

Explanation

Correct Answer

Incorrect Answers

Question 288

Explanation

Correct Answer

Incorrect Answers

Question 289

Explanation

Correct Answer

Incorrect Answers

Question 290

Explanation

Correct Answer

Incorrect Answers

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