Note: This question is part of a series of questions that present the same scenario. Each question in the series contains a unique solution that might meet the stated goals. Some question sets might have more than one correct solution, while others might not have a correct solution. After you answer a question in this section, you will NOT be able to return to it. As a result, these questions will not appear in the review screen. You have a KQL database that contains two tables named Stream and Reference. Stream contains streaming data in the following format. [Table showing Column name: Timestamp, Geolocation, Temperature, DeviceId and Data type: Datetime, Dynamic, Decimal, Int] Reference contains reference data in the following format. [Table showing Column name: DeviceId, DeviceName and Data type: Int, String] Both tables contain millions of rows. You have the following KQL queryset. [KQL query shown: `01 Stream
02 | extend lat = todecimal(Geolocation.Latitude), long = todecimal(Geolocation.Longitude)
03 | join kind=inner Reference on DeviceId
04 | project Timestamp, lat, long, Temperature, DeviceName
05 | filter Temperature 10
06 | render scatterchart with (kind = map)`] You need to reduce how long it takes to run the KQL queryset. Solution: You change the join type to kind=outer. Does this meet the goal?

Question

Note: This question is part of a series of questions that present the same scenario. Each question in the series contains a unique solution that might meet the stated goals. Some question sets might have more than one correct solution, while others might not have a correct solution. After you answer a question in this section, you will NOT be able to return to it. As a result, these questions will not appear in the review screen. You have a KQL database that contains two tables named Stream and Reference. Stream contains streaming data in the following format. [Table showing Column name: Timestamp, Geolocation, Temperature, DeviceId and Data type: Datetime, Dynamic, Decimal, Int] Reference contains reference data in the following format. [Table showing Column name: DeviceId, DeviceName and Data type: Int, String] Both tables contain millions of rows. You have the following KQL queryset. [KQL query shown: `01 Stream
02 | extend lat = todecimal(Geolocation.Latitude), long = todecimal(Geolocation.Longitude)
03 | join kind=inner Reference on DeviceId
04 | project Timestamp, lat, long, Temperature, DeviceName
05 | filter Temperature > 10
06 | render scatterchart with (kind = map)`] You need to reduce how long it takes to run the KQL queryset. Solution: You change the join type to kind=outer. Does this meet the goal?

Accepted Answer

B. No The provided question abruptly cuts off, omitting the specific solution proposed to reduce the KQL queryset's runtime. Without this crucial information, it is impossible to evaluate whether the suggested modification would actually improve query performance.

Answer

A. Yes Assuming "Yes" would imply that the truncated, unknown solution is effective, which cannot be determined given the incomplete problem statement.

Note: This question is part of a series of questions that present the same scenario. Each question in the series contains a unique solution that might meet the stated goals. Some question sets might…

Question

Options

How the community answered

Why each option

Topics

Community Discussion