Free DP-700 sample questions

Correct answer: It physically sorts the underlying Parquet files based on the `OrderDateKey` column, enabling better file pruning.

V-Order is a write-time optimization for Delta Lake tables (which power the Fabric Warehouse) that physically sorts the data within the Parquet files. By ordering the data by a frequently filtered column like `OrderDateKey`, the query engine can perform file pruning (also known as data skipping) much more effectively, reading only the files that contain the relevant date ranges and significantly speeding up queries.

Correct answer: The commit is in Git, but to deploy it, the `Sales_Prod` workspace must be updated from the connected Git branch before the changes appear in that workspace.

Committing a change from a workspace pushes it to the connected Git branch. However, deployment pipelines promote items *between workspaces*. The `Sales_Prod` workspace is unaware of the Git commit. To get the new notebook version into production, the team must first go to the `Sales_Prod` workspace and perform an 'Update' action from source control to pull the changes from the `main` branch. A deployment pipeline alone does not sync changes from Git.

Correct answer: The Eventstream's built-in event processor.

The Eventstream's event processor provides a no-code/low-code graphical interface to design data transformations on the fly. It includes operations like 'Manage fields', 'Filter', and crucially, 'Expand', which can be used to join the streaming data with reference data from a Lakehouse table. This is the most direct and integrated way to perform such enrichment within the Eventstream itself.

Correct answers: Assign the data engineers to the Admin role and the business analysts to the Viewer role at the workspace level.; Implement row-level security (RLS) on the `Sales` table to filter data based on the user's role.

Workspace roles provide the broad level of access control. 'Admin' gives data engineers full control. 'Viewer' allows business analysts to read content, including querying the SQL endpoint, but prevents them from modifying items or accessing files directly, fulfilling the second requirement.

Row-level security (RLS) is the correct mechanism for filtering rows based on user identity or role. You would create a security predicate (e.g., `[Region] = 'North America'`) and apply it to a role that the junior analysts belong to, fulfilling the third requirement.

Correct answer: Use the `broadcast` hint to force a broadcast hash join.

The scenario describes a classic large-table-to-small-table join, which is a perfect candidate for a broadcast hash join. By default, Spark might choose a shuffle-based join, causing massive data movement. Using `from pyspark.sql.functions import broadcast` and rewriting the join as `large_df.join(broadcast(small_df), 'user_id', 'inner')` instructs Spark to send the small DataFrame to every executor, avoiding the costly shuffle of the large DataFrame and dramatically improving performance.

Correct answer: SensorData | where sensorId == 'SN01-T5' | summarize avg(temperature) by bin(timestamp, 5m) | where avg_temperature > 150

This query correctly implements the logic. It first filters for the specific sensor. Then, `summarize avg(temperature) by bin(timestamp, 5m)` calculates the average temperature over 5-minute tumbling windows. Finally, `where avg_temperature > 150` filters these aggregated results to find the windows where the anomaly condition is met.

Correct answer: True

This statement is true. The Fabric Mirroring feature is designed for seamless, low-latency replication. It automatically handles the initial snapshot of the source database tables and then uses the source's change data capture (CDC) mechanism to replicate ongoing inserts, updates, and deletes to OneLake in Delta format. This provides a continuously updated, queryable copy without the need to build and manage a manual ETL pipeline.

Correct answer: In the 'Corporate' workspace, create a master pipeline with three parallel activities, each running a notebook to filter and write data to the respective regional Gold Lakehouse.

This centralized approach aligns with the company's goal of maintaining central data engineering standards. A master pipeline in the 'Corporate' workspace can orchestrate the entire Silver-to-Gold process. Using notebooks for the transformation allows for the simple filtering and aggregation logic required. This design provides a single point of management and monitoring for the population of all Gold layers, ensuring consistency and leveraging the central team's expertise. It also avoids granting cross-workspace permissions to regional resources.

Correct answer: Deployment rules

Deployment rules are a feature of Fabric deployment pipelines specifically designed to handle differences in configuration between stages. You can create a rule for the Lakehouse shortcut that specifies the new connection details (e.g., the Production storage account URL) to be applied when deploying to the Production stage. This allows the same Fabric item to be used across stages while pointing to the correct environment-specific resources.

Correct answer: A OneLake shortcut pointing to the S3 bucket.

OneLake shortcuts are the ideal solution for this scenario. A shortcut acts as a symbolic link to the data in the S3 bucket without copying it. This allows data engineers to query and explore the data in place using Spark or SQL, avoiding data duplication and egress costs for initial analysis. Later, a pipeline or notebook can read from the shortcut to transform and load the necessary data into managed Delta tables within the Lakehouse.