Explanation:

Comprehensive Detailed Explanation
We have a KQL table (TaxiData) with columns:
VendorID
tpep_pickup_datetime (timestamp)
payment_type
total_amount
The requirement:
Create a new column FirstPickupDateTime
It should contain the first pickup timestamp per hour
Partitioning should be done by payment_type
Step 1: Which windowing function?
row_cumsum # running cumulative sum (not needed here).
row_rank_dense # assigns ranks without gaps, but does not guarantee minimum value only.
row_rank_min # gives the first/minimum value in each window partition. # Correct.
row_window_session # sessionization of events, not required.
So, the correct function is row_rank_min.
Step 2: Which comparison operator?
We need to select the row where the rank = 1 (the first per partition).
So the correct operator is == (equals).
Step 3: Partitioning
The KQL query should partition by:
bin(tpep_pickup_datetime, 1h) # buckets data into 1-hour windows
payment_type # partitions further by payment type
Completed KQL Query
TaxiData
| sort by tpep_pickup_datetime asc, payment_type asc
| extend FirstPickupDateTime = row_rank_min(tpep_pickup_datetime, 1h, 0m, payment_type)
| where FirstPickupDateTime == 1
This assigns a rank within each 1-hour, per-payment-type window, then keeps the first pickup timestamp.
Why This Works
row_rank_min # ensures we capture the first occurrence in each hour.
== # filters only the first row per partition.
bin(..., 1h) ensures grouping is by hour.
References
Kusto row_rank_min() function
KQL window functions

Explanation:

o add new data to the Delta table while meeting the specified requirements:
You should use the append mode to ensure that all new data is added to the table without affecting the existing rows.
You should set the mergeSchema option to true to allow the schema of the Delta table to be updated with the new columns found in the DataFrame.
The completed code would look like this:
df.write.format("delta").mode("append")
option("mergeSchema", "true")
saveAsTable("Lakehouse1.TableName")

Explanation:

The relationship between OrderItem and Product must be based on: Both the CompanyID and the ProductID columns The Company entity must be: Denormalized into the Customer and Product entities In a dimensional model, the relationships are typically based on foreign key constraints between the fact table (OrderItem) and dimension tables (Product, Customer, Date). Since CompanyID is present in both the OrderItem and Product tables, it acts as a foreign key in the relationship. Similarly, ProductID is a foreign key that relates these two tables. To enable analysis by date, product, and customer, the Company entity would need to be denormalized into the Customer and Product entities to ensure that the relevant company information is available within those dimensions for querying and reporting purposes.
References =
Dimensional modeling
Star schema design

Step 1: Understand the scenario
Workspace1 contains a semantic model and two Power BI reports.
A Microsoft 365 Data Loss Prevention (DLP) policy (DLP1) already exists.
Requirement: Apply DLP1 to the workspace items.
In Microsoft Fabric and Power BI, DLP policies are enforced through Microsoft Purview Information Protection (MIP) sensitivity labels.
Step 2: Evaluate each option
A). Apply a master data endorsement to the semantic model.
Endorsements (promoted, certified) help users find and trust datasets but do not enforce DLP policies.
Not correct.
B). Apply a certified endorsement to the semantic model.
Certification improves discoverability and trust, but again, it does not trigger DLP policy enforcement.
Not correct.
C). Create a workspace identity.
Workspace identity (service principal) is used for connecting to external resources with managed identity.
It does not relate to DLP policy application.
Not correct.
D). Apply sensitivity labels to the semantic model and reports.
Sensitivity labels (from Microsoft Purview) integrate with Microsoft 365 DLP policies.
When sensitivity labels are applied to Power BI datasets, reports, dashboards, and workspaces, DLP1 can enforce protections such as preventing sharing or exporting sensitive data.
This is the correct answer.
Step 3: Correct Action
To apply DLP1 to Workspace1 items, you must:
Configure sensitivity labels in Microsoft Purview.
Apply those sensitivity labels to the semantic model and reports inside Workspace1.
The existing DLP1 policy will then govern data handling for those items.
References
Sensitivity labels in Power BI
Apply sensitivity labels to Power BI items
DLP policies in Microsoft Purview

A lakehouse (A) is the type of data store you should use. It supports dataflows to load and append data and ensures that Delta tables are Z-Order optimized and compacted automatically. References = The capabilities of a lakehouse and its support for Delta tables are described in the lakehouse and Delta table documentation.