Microsoft DP-700 Practice Test 42

Question 410

Source authentication has been repaired for Eventstream. What test verifies recovery?

Verify that the Eventhouse sink can accept an unrelated manual event.
Check only that Eventstream's connection form saved the new key, not that it receives events.
Generate a known upstream event and confirm its source arrival and matching downstream destination record under the repaired source identity.
Run a source event through a different connector identity than the production service.

Explanation

Correct Answer

End-to-end event tracing demonstrates that both authorization and routing are operational.

Incorrect Answers

Sink health alone cannot prove that the upstream connector authenticates and receives live source records.

Configuration persistence isn't proof of successful source authentication or resumed delivery.

An alternate principal can hide the actual rotated-secret failure; test the configured route.

Question 411

An Eventstream is receiving JSON events but fails when sending to Eventhouse because a timestamp field maps to an incompatible destination type. What should be fixed?

Increase the number of Eventhouse query dashboards without editing the mapping.
Change the Eventstream name to the expected destination column.
Disable source processing while claiming the destination is fixed.
Inspect the Eventhouse destination schema and Eventstream field mapping, then apply a supported timestamp conversion or compatible ingestion mapping.

Explanation

Correct Answer

Destination ingestion validates data types; source arrival alone cannot guarantee the record can be inserted into a typed KQL table.

Incorrect Answers

Dashboard creation does not fix type incompatibility on the ingestion path. It does not implement the corrective control requested in this incident.

Renaming an item cannot cast a source timestamp into the target type. It does not implement the corrective control requested in this incident.

Stopping input prevents any meaningful validation of the repaired mapping. It does not implement the corrective control requested in this incident.

Question 412

An Eventstream source counter increases but Eventhouse ingestion failures rise after a new payload version. Why?

The destination field mapping or type conversion does not match the revised event payload, so accepted source messages are rejected downstream.
The increased source count proves the destination KQL ingestion mapping is also successful.
The destination table requires a larger retention period before accepting timestamps.
A source payload-version change automatically updates all Eventhouse mapping definitions.

Explanation

Correct Answer

Input success and sink ingestion success are separate stages and can diverge after schema evolution.

Incorrect Answers

Source ingestion and destination type conversion are separate; an incompatible timestamp field can fail at the sink.

Retention controls how long accepted events remain, not whether an invalid type mapping parses them.

Mappings need compatible field names/types; a changed payload can invalidate previously valid settings.

Question 413

A destination mapping is repaired for Eventstream. What validation should be performed?

Inspect only Eventstream Live view without querying or examining Eventhouse ingestion failures.
Send controlled old and new payloads, then query Eventhouse for correctly typed fields and compare input, rejected and written event counts.
Verify one pre-upgrade JSON payload and declare the new schema supported.
Count delivered records but ignore the parsed timestamp values and rejected-event diagnostics.

Explanation

Correct Answer

A mixed-version fixture verifies compatibility and catches silent null conversion or dropped records.

Incorrect Answers

Source events can appear before the destination rejects them for field conversion errors.

Old payloads can still work while the updated timestamp type fails ingestion.

Destination totals alone do not establish a correct event-time mapping or absence of silent rejects.

Question 414

An Eventhouse ingest mapping expects `reading` as an integer, but devices now send it as a JSON string. What should ingestion engineers do?

Rename the Eventhouse item without editing JSON field mapping.
Use a warehouse SQL view as the primary Eventhouse ingest mapping.
Compare sample source payloads with the KQL ingestion mapping and define a supported type conversion or revise the mapping/schema deliberately.
Increase cache retention to make invalid fields parse correctly.

Explanation

Correct Answer

An ingestion mapping must produce destination types compatible with its table schema; mismatched JSON types can reject otherwise well-formed messages.

Incorrect Answers

Database or table display names cannot repair a mismatched extraction path or target type. It does not implement the corrective control requested in this incident.

A separate SQL view does not define the KQL database ingestion-time JSON mapping. It does not implement the corrective control requested in this incident.

Query cache settings are independent of ingestion schema compatibility. It does not implement the corrective control requested in this incident.

Question 415

An Eventhouse table receives ingestion mapping errors after an event producer changes field types. Select TWO likely root causes.

The mapping still projects a source JSON field using its old type or incorrect path.
Every JSON string can be stored into an integer KQL column without a conversion rule.
The ingestion error is caused by a missing Power BI semantic model for the KQL table.
The destination KQL table schema and mapped column type are incompatible with the new producer values.
A new Eventhouse capacity name will coerce string numbers automatically.

Explanation

Correct Answers

A renamed or retyped field no longer satisfies the originally configured JSON extraction path and conversion.

The ingest engine enforces target type constraints independently of whether the JSON is syntactically valid.

Incorrect Answers

Changing the sender from numeric to quoted values can break typed mappings or introduce invalid tokens.

Semantic models are not prerequisites for Eventhouse's ingestion mapping type validation.

Item naming has no effect on whether the mapping safely parses or rejects changed value types.

Question 416

A KQL ingestion mapping is updated for a new payload. What fixture verifies the change?

Test only old messages where `reading` is already numeric.
Accept every string, including nonnumeric `bad`, and assert ingestion is reliable.
Check that the mapping definition is saved without querying newly ingested values.
Ingest a known JSON message with the revised field representation and query the typed columns, reconciling error counters and values.

Explanation

Correct Answer

A controlled event proves both source-path extraction and target type conversion work after the mapping change.

Incorrect Answers

Old-format tests don't exercise the new string-to-integer conversion and validation path.

Successful typed ingestion must handle invalid strings according to the approved reject/diagnostic policy.

A persisted mapping can still fail at runtime or produce null/incorrect numeric readings.

Question 417

A KQL query calls `external_table()` on a OneLake shortcut but gets a source access error. What should the engineer verify?

Increase Eventhouse retention days without reviewing target access.
Check shortcut target path, supported external-table connection and effective producer-side OneLake permissions for the executing identity.
Rename the shortcut without testing the underlying location.
Set a notebook default lakehouse and assume it controls KQL external-table access.

Explanation

Correct Answer

The external query resolves a referenced data location and authorization; a KQL database role alone may not authorize the source.

Incorrect Answers

Retention does not grant a reader permission to a referenced OneLake producer table. It does not implement the corrective control requested in this incident.

A new label cannot repair a wrong or unauthorized source target. It does not implement the corrective control requested in this incident.

A notebook storage attachment is not the Eventhouse external query identity or connection grant. It does not implement the corrective control requested in this incident.

Question 418

A KQL shortcut works for a database Admin but not a limited analyst. Both can see the shortcut name. What explains the difference?

The missing source access is caused by using `external_table()` instead of an ordinary native table name.
The limited analyst should be promoted to KQL database Admin for any shortcut read.
The analyst lacks an effective source data grant or compatible query access despite being able to discover the KQL shortcut.
OneLake shortcut object visibility guarantees the analyst can read its underlying Delta bytes.

Explanation

Correct Answer

Catalog visibility and external table data-plane permissions remain distinct authorization boundaries.

Incorrect Answers

`external_table()` is the correct query surface for shortcuts; data-source grants may still differ.

Broad administrator rights are excessive and can hide the missing permitted external source access.

Metadata visibility does not imply effective permission for external storage or the source connection.

Question 419

KQL shortcut access is repaired. What verification is most direct?

Run the repaired query as the KQL database Admin only.
Check that the shortcut name resolves in autocomplete but skip the actual `external_table()` read.
Verify the target lakehouse is accessible via an unrelated workspace owner account.
Run `external_table()` as the intended analyst against known source rows and confirm rejected access to unrelated source paths.

Explanation

Correct Answer

A permitted and denied external read demonstrates correct path resolution and least-privilege source permissions.

Incorrect Answers

Administrator success doesn't prove the intended limited analyst has authorized access to source data.

Discovery/metadata may succeed when data-plane authorization still denies the query.

An owner's source access doesn't establish the effective limited analyst's KQL shortcut identity.

Question 420

A KQL query compares `TimeGenerated` to a datetime literal, but source messages contain invalid local-time strings. What should its author correct?

Parse the source field with a supported KQL datetime conversion, normalize time-zone semantics and handle conversion failures explicitly.
Use a string comparison to sort all local timestamps with different offsets.
Change KQL query font size to display more digits.
Remove the query’s time filter and claim temporal accuracy.

Explanation

Correct Answer

Invalid strings and missing offsets can break date filters or silently discard rows; typed datetime values are required for reliable temporal comparisons.

Incorrect Answers

Lexical order is not reliable chronological order across offset-bearing representations. It does not implement the corrective control requested in this incident.

Presentation settings cannot correct datetime parsing or calendar-day assignment. It does not implement the corrective control requested in this incident.

Dropping the condition avoids the error but no longer selects the specified incident window. It does not implement the corrective control requested in this incident.

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

Microsoft DP-700 Practice Test 40 - 10 Questions (Last Reviewed 25-Sep-2026)
Microsoft DP-700 Practice Test 41 - 10 Questions (Last Reviewed 24-Sep-2026)
Microsoft DP-700 Practice Test 42 - 10 Questions (Last Reviewed 23-Sep-2026)
Microsoft DP-700 Practice Test 43 - 10 Questions (Last Reviewed 22-Sep-2026)
Microsoft DP-700 Practice Test 44 - 10 Questions (Last Reviewed 21-Sep-2026)

Pass Your Microsoft DP-700 Exam Easy!

Question 410

Explanation

Correct Answer

Incorrect Answers

Question 411

Explanation

Correct Answer

Incorrect Answers

Question 412

Explanation

Correct Answer

Incorrect Answers

Question 413

Explanation

Correct Answer

Incorrect Answers

Question 414

Explanation

Correct Answer

Incorrect Answers

Question 415

Explanation

Correct Answers

Incorrect Answers

Question 416

Explanation

Correct Answer

Incorrect Answers

Question 417

Explanation

Correct Answer

Incorrect Answers

Question 418

Explanation

Correct Answer

Incorrect Answers

Question 419

Explanation

Correct Answer

Incorrect Answers

Question 420

Explanation

Correct Answer

Incorrect Answers

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