nerdexam
Microsoft

DP-700 · Question #30

You have a Fabric workspace that contains an eventhouse and a KQL database named Database1. Database1 has the following: - A table named Table1 - A table named Table2 - An update policy named…

The correct answer is A. Table with Timestamp (datetime: 2024-05-18 12:45:17.16524), DeviceId (guid: 81416f30-60a2-4e75-9b19-2a84ea059735), StreamData ({ "index": 0, "eventid": "719afca0-be30-4559-bb5e-59feade642f6", "temperature": 32}) D. Table with Timestamp (datetime: 2024-05-24 12:45:17.16524), DeviceId (guid: 81416f30-60a2-4e75-9b19-2a84ea059735), StreamData ({ "index": 0, "eventid": "719afca0-be30-4559-bb5e-59feade642f6", "temperature": null}). Records will load from Table1 to Table2 if their Timestamp and DeviceId data types are compatible with Table2's schema (datetime and guid, respectively) and the StreamData (dynamic) column structure allows for added or null fields.

Design and implement data ingestion and transformation

Question

You have a Fabric workspace that contains an eventhouse and a KQL database named Database1. Database1 has the following: - A table named Table1 - A table named Table2 - An update policy named Policy1 - Policy1 sends data from Table1 to Table2. The following is a sample of the data in Table2. [Table showing Timestamp, DeviceId, StreamData] Recently, the following actions were performed on Table1: - An additional element named temperature was added to the StreamData column. - The data type of the Timestamp column was changed to date. - The data type of the DeviceId column was changed to string. You plan to load additional records to Table2. Which two records will load from Table1 to Table2? Each correct answer presents a complete solution. Note: Each correct selection is worth one point.

Options

  • ATable with Timestamp (datetime: 2024-05-18 12:45:17.16524), DeviceId (guid: 81416f30-60a2-4e75-9b19-2a84ea059735), StreamData ({ "index": 0, "eventid": "719afca0-be30-4559-bb5e-59feade642f6", "temperature": 32})
  • BTable with Timestamp (datetime: 2024-05-21 12:45:17.16524), DeviceId (guid: 81416f30), StreamData ({ "index": 0, "eventid": "719afca0-be30-4559-bb5e-5werade642f6", "temperature": 27})
  • CTable with Timestamp (datetime: 2024-05-23 12:45:17.16524), DeviceId (guid: 81416f3002a4e759b192a84ea0597352d3dyle3), StreamData ({ "index": 0, "eventid": "719afca0-be30-4559-bb5e-59feade642f6"}) (Note: Missing 'temperature' field)
  • DTable with Timestamp (datetime: 2024-05-24 12:45:17.16524), DeviceId (guid: 81416f30-60a2-4e75-9b19-2a84ea059735), StreamData ({ "index": 0, "eventid": "719afca0-be30-4559-bb5e-59feade642f6", "temperature": null})

How the community answered

(34 responses)
  • A
    76% (26)
  • B
    9% (3)
  • C
    15% (5)

Why each option

Records will load from Table1 to Table2 if their Timestamp and DeviceId data types are compatible with Table2's schema (datetime and guid, respectively) and the StreamData (dynamic) column structure allows for added or null fields.

ATable with Timestamp (datetime: 2024-05-18 12:45:17.16524), DeviceId (guid: 81416f30-60a2-4e75-9b19-2a84ea059735), StreamData ({ "index": 0, "eventid": "719afca0-be30-4559-bb5e-59feade642f6", "temperature": 32})Correct

The Timestamp is in a valid datetime format and DeviceId is a valid guid string, which both match or are implicitly convertible to Table2's schema. The StreamData column is dynamic and can accommodate new elements like 'temperature'.

BTable with Timestamp (datetime: 2024-05-21 12:45:17.16524), DeviceId (guid: 81416f30), StreamData ({ "index": 0, "eventid": "719afca0-be30-4559-bb5e-5werade642f6", "temperature": 27})

The DeviceId value 81416f30 is not a valid GUID format and will cause a type conversion error during ingestion into Table2's guid column.

CTable with Timestamp (datetime: 2024-05-23 12:45:17.16524), DeviceId (guid: 81416f3002a4e759b192a84ea0597352d3dyle3), StreamData ({ "index": 0, "eventid": "719afca0-be30-4559-bb5e-59feade642f6"}) (Note: Missing 'temperature' field)

The DeviceId value 81416f3002a4e759b192a84ea0597352d3dyle3 is not a valid GUID format and will prevent the record from loading into Table2's guid column.

DTable with Timestamp (datetime: 2024-05-24 12:45:17.16524), DeviceId (guid: 81416f30-60a2-4e75-9b19-2a84ea059735), StreamData ({ "index": 0, "eventid": "719afca0-be30-4559-bb5e-59feade642f6", "temperature": null})Correct

Similar to A, the Timestamp is a valid datetime and DeviceId is a valid guid string, ensuring successful type conversion or matching for Table2's schema. The dynamic StreamData column also correctly handles the null value for 'temperature'.

Concept tested: KQL update policies, data type compatibility, and schema evolution for dynamic types

Source: https://learn.microsoft.com/en-us/azure/data-explorer/kusto/management/updatepolicy

Topics

#Kusto Update Policies#Data Type Conversion#Fabric Real-Time Analytics#Data Ingestion

Community Discussion

No community discussion yet for this question.

Sign up to join the discussion
Full DP-700 Practice