HOTSPOT
-
You have a Fabric workspace that uses the default Spark starter pool and runtime version 1.2.
You plan to read a CSV file named Sales_raw.csv in a lakehouse, select columns, and save the data as a Delta table to the managed area of the lakehouse. Sales_raw.csv contains 12 columns.
You have the following code.
For each of the following statements, select Yes if the statement is true. Otherwise, select No.
NOTE: Each correct selection is worth one point.
Show Answer
Correct Answer: No
No
Yes
Explanation: CSV sources do not support column pruning, so all columns are read before select.
withColumn adds a new column; it does not replace OrderDate.
inferSchema requires extra passes to infer data types, increasing execution time.
Question 85
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 Fabric tenant that contains a semantic model named Model1.
You discover that the following query performs slowly against Model1.
You need to reduce the execution time of the query.
Solution: You replace line 4 by using the following code:
NOT ( CALCULATE ( COUNTROWS ( 'Order Item' ) ) < 0)
Does this meet the goal?
A. Yes
B. No
Show Answer
Correct Answer: B
Explanation: The rewritten condition is logically equivalent to the original and still requires evaluating COUNTROWS over the 'Order Item' table. It does not simplify the filter context or reduce storage engine work, so query performance will not improve.
Question 86
HOTSPOT
-
You have a Fabric tenant that contains a warehouse named WH1.
You run the following T-SQL query against WH1.
For each of the following statements, select Yes if the statement is true. Otherwise, select No.
NOTE: Each correct selection is worth one point.
Show Answer
Correct Answer: No
No
Yes
Explanation: OUTER APPLY indicates Dimension.GetDirectReports returns a table, not a scalar value. APPLY evaluates the table-valued function once per row of Dimension.Employee, not once per query. OUTER APPLY preserves all rows from Dimension.Employee, returning at least one row per employee even when the function returns no matches (with NULLs for applied columns).
Question 87
DRAG DROP
-
You have a Fabric tenant that contains a data warehouse named DW1. DW1 contains a table named DimCustomer. DimCustomer contains the fields shown in the following table.
You need to identify duplicate email addresses in DimCustomer. The solution must return a maximum of 1,000 records.
Which four T-SQL statements should you run in sequence? To answer, move the appropriate statements from the list of statements to the answer area and arrange them in the correct order.
Show Answer
Correct Answer: SELECT TOP (1000) CustomerAltKey, COUNT(*)
FROM DimCustomer
GROUP BY CustomerAltKey
HAVING COUNT(*) > 1
Explanation: Duplicates are identified by grouping on the email field (CustomerAltKey) and counting rows. HAVING COUNT(*) > 1 filters only duplicates, and TOP (1000) limits the result set to the required maximum.
Question 88
HOTSPOT
-
You have a Fabric tenant that contains a semantic model named model1. The two largest columns in model1 are shown in the following table.
You need to optimize model1. The solution must meet the following requirements:
• Reduce the model size.
• Increase refresh performance when using Import mode.
• Ensure that the datetime value for each sales transaction is available in the model.
What should you do on each column? To answer, select the appropriate options in the answer area.
NOTE: Each correct selection is worth one point.
Show Answer
Correct Answer: TransactionKey:
Remove the column.
SaleDateTime:
Split the column.
Explanation: TransactionKey is a high-cardinality surrogate key that is not required for analysis in the semantic model; removing it significantly reduces model size and improves Import refresh performance.
SaleDateTime has high cardinality at second-level precision; splitting it into separate Date and Time columns improves compression and refresh performance while preserving full datetime information.
Question 89
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 Fabric tenant that contains a new semantic model in OneLake.
You use a Fabric notebook to read the data into a Spark DataFrame.
You need to evaluate the data to calculate the min, max, mean, and standard deviation values for all the string and numeric columns.
Solution: You use the following PySpark expression:
df.describe().show()
Does this meet the goal?
A. Yes
B. No
Show Answer
Correct Answer: A
Explanation: df.describe() computes count, mean, standard deviation, minimum, and maximum for all numeric columns and also includes string columns, where applicable statistics (count, min, max) are returned. Since the goal is to evaluate min, max, mean, and standard deviation across string and numeric columns using this built-in summary, the expression satisfies the requirement in Fabric/Spark.
Question 90
Case study -
This is a case study. Case studies are not timed separately. You can use as much exam time as you would like to complete each case. However, there may be additional case studies and sections on this exam. You must manage your time to ensure that you are able to complete all questions included on this exam in the time provided.
To answer the questions included in a case study, you will need to reference information that is provided in the case study. Case studies might contain exhibits and other resources that provide more information about the scenario that is described in the case study. Each question is independent of the other questions in this case study.
At the end of this case study, a review screen will appear. This screen allows you to review your answers and to make changes before you move to the next section of the exam. After you begin a new section, you cannot return to this section.
To start the case study -
To display the first question in this case study, click the Next button. Use the buttons in the left pane to explore the content of the case study before you answer the questions. Clicking these buttons displays information such as business requirements, existing environment, and problem statements. If the case study has an All Information tab, note that the information displayed is identical to the information displayed on the subsequent tabs. When you are ready to answer a question, click the Question button to return to the question.
Overview -
Contoso, Ltd. is a US-based health supplements company. Contoso has two divisions named Sales and Research. The Sales division contains two departments named Online Sales and Retail Sales. The Research division assigns internally developed product lines to individual teams of researchers and analysts.
Existing Environment -
Identity Environment -
Contoso has a Microsoft Entra tenant named contoso.com. The tenant contains two groups named ResearchReviewersGroup1 and ResearchReviewersGroup2.
Data Environment -
Contoso has the following data environment:
• The Sales division uses a Microsoft Power BI Premium capacity.
• The semantic model of the Online Sales department includes a fact table named Orders that uses Import made. In the system of origin, the OrderID value represents the sequence in which orders are created.
• The Research department uses an on-premises, third-party data warehousing product.
• Fabric is enabled for contoso.com.
• An Azure Data Lake Storage Gen2 storage account named storage1 contains Research division data for a product line named Productline1. The data is in the delta format.
• A Data Lake Storage Gen2 storage account named storage2 contains Research division data for a product line named Productline2. The data is in the CSV format.
Requirements -
Planned Changes -
Contoso plans to make the following changes:
• Enable support for Fabric in the Power BI Premium capacity used by the Sales division.
• Make all the data for the Sales division and the Research division available in Fabric.
• For the Research division, create two Fabric workspaces named Productline1ws and Productline2ws.
• In Productline1ws, create a lakehouse named Lakehouse1.
• In Lakehouse1, create a shortcut to storage1 named ResearchProduct.
Data Analytics Requirements -
Contoso identifies the following data analytics requirements:
• All the workspaces for the Sales division and the Research division must support all Fabric experiences.
• The Research division workspaces must use a dedicated, on-demand capacity that has per-minute billing.
• The Research division workspaces must be grouped together logically to support OneLake data hub filtering based on the department name.
• For the Research division workspaces, the members of ResearchReviewersGroup1 must be able to read lakehouse and warehouse data and shortcuts by using SQL endpoints.
• For the Research division workspaces, the members of ResearchReviewersGroup2 must be able to read lakehouse data by using Lakehouse explorer.
• All the semantic models and reports for the Research division must use version control that supports branching.
Data Preparation Requirements -
Contoso identifies the following data preparation requirements:
• The Research division data for Productline1 must be retrieved from Lakehouse1 by using Fabric notebooks.
• All the Research division data in the lakehouses must be presented as managed tables in Lakehouse explorer.
Semantic Model Requirements -
Contoso identifies the following requirements for implementing and managing semantic models:
• The number of rows added to the Orders table during refreshes must be minimized.
• The semantic models in the Research division workspaces must use Direct Lake mode.
General Requirements -
Contoso identifies the following high-level requirements that must be considered for all solutions:
• Follow the principle of least privilege when applicable.
• Minimize implementation and maintenance effort when possible.
Which syntax should you use in a notebook to access the Research division data for Productline1?
A. spark.read.format(“delta”).load(“Tables/ResearchProduct”)
B. spark.read.format(“delta”).load(“Files/ResearchProduct”)
C. external_table(‘Tables/ResearchProduct)
D. external_table(ResearchProduct)
Show Answer
Correct Answer: A
Explanation: The shortcut to storage1 is created in the lakehouse Tables section as a table shortcut because the source data is Delta and must be accessible via SQL endpoints and Lakehouse explorer. In Fabric notebooks, Delta table shortcuts in the Tables area are accessed using spark.read.format("delta").load("Tables/<TableName>"). Therefore, loading from Tables/ResearchProduct is the correct syntax.
Question 91
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 Fabric tenant that contains a semantic model named Model1.
You discover that the following query performs slowly against Model1.
You need to reduce the execution time of the query.
Solution: You replace line 4 by using the following code:
ISEMPTY ( RELATEDTABLE ( 'Order Item' ) )
Does this meet the goal?
A. Yes
B. No
Show Answer
Correct Answer: B
Explanation: Replacing the original logic with ISEMPTY(RELATEDTABLE('Order Item')) reverses the filter semantics. ISEMPTY returns TRUE when there are no related rows, whereas the original pattern (typically COUNTROWS > 0) identifies rows that do have related records. While ISEMPTY can be more efficient, using it without NOT changes the result set and therefore does not meet the goal.
Question 92
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 Fabric tenant that contains a semantic model named Model1.
You discover that the following query performs slowly against Model1.
You need to reduce the execution time of the query.
Solution: You replace line 4 by using the following code:
CALCULATE ( COUNTROWS ( 'Order Item' ) ) >= 0
Does this meet the goal?
A. Yes
B. No
Show Answer
Correct Answer: B
Explanation: Replacing the condition with CALCULATE(COUNTROWS('Order Item')) >= 0 does not improve performance. The expression is always true (row count is never negative), so it does not reduce the evaluation scope or optimize the query plan; it only changes logic without reducing execution time.
Question 93
You have a Fabric tenant that contains a warehouse.
You are designing a star schema model that will contain a customer dimension. The customer dimension table will be a Type 2 slowly changing dimension (SCD).
You need to recommend which columns to add to the table. The columns must NOT already exist in the source.
Which three types of columns should you recommend? Each correct answer presents part of the solution.
NOTE: Each correct answer is worth one point.
A. a foreign key
B. a natural key
C. an effective end date and time
D. a surrogate key
E. an effective start date and time
Show Answer
Correct Answer: C, D, E
Explanation: A Type 2 slowly changing dimension requires tracking the history of changes. This is done by adding effective start and end date/time columns to define the validity period of each row, and a surrogate key to uniquely identify each version of a dimension record. Natural keys already exist in the source, and foreign keys belong in fact tables, not dimension tables.
$19
Get all 189 questions with detailed answers and explanations
Instant download HTML + PDF delivered the moment payment clears.
Secure Stripe checkout we never see or store your card details.
7-day refund if files are defective see our refund policy.