| Exam Name: | Implementing Data Engineering Solutions Using Microsoft Fabric | ||
| Exam Code: | DP-700 Dumps | ||
| Vendor: | Microsoft | Certification: | Microsoft Certified: Fabric Data Engineer Associate |
| Questions: | 142 Q&A's | Shared By: | yusra |
You have an Azure Data Lake Storage Gen2 account named storage1 and an Amazon S3 bucket named storage2.
You have the Delta Parquet files shown in the following table.

You have a Fabric workspace named Workspace1 that has the cache for shortcuts enabled. Workspace1 contains a lakehouse named Lakehouse1. Lakehouse1 has the following shortcuts:
A shortcut to ProductFile aliased as Products
A shortcut to StoreFile aliased as Stores
A shortcut to TripsFile aliased as Trips
The data from which shortcuts will be retrieved from the cache?
You have a Fabric warehouse named DW1 that contains a Type 2 slowly changing dimension (SCD) dimension table named DimCustomer. DimCustomer contains 100 columns and 20 million rows. The columns are of various data types, including int, varchar, date, and varbinary.
You need to identify incoming changes to the table and update the records when there is a change. The solution must minimize resource consumption.
What should you use to identify changes to attributes?
HOTSPOT
You have a Fabric workspace.
You are debugging a statement and discover the following issues:
Sometimes, the statement fails to return all the expected rows.
The PurchaseDate output column is NOT in the expected format of mmm dd, yy.
You need to resolve the issues. The solution must ensure that the data types of the results are retained. The results can contain blank cells.
How should you complete the statement? To answer, select the appropriate options in the answer area.
NOTE: Each correct selection is worth one point.

You have a Fabric workspace named Workspace1 that uses Git integration and is connected to the main branch of an Azure Repos Git repository named Repo1.
Multiple developers sync from Workspace1.
A hotfix was introduced two commits ago in main. The most recent commit in main contains unrelated changes that are NOT approved for release.
You need to deploy only the hotfix, while keeping the main branch history intact. The solution must minimize disruptions for other developers working in main.
What should you do?