You have an Amazon Web Services (AWS) subscription that contains an Amazon Simple Storage Service (Amazon S3) bucket named bucket1.
You have a Fabric tenant that contains a lakehouse named LH1.
In LH1, you plan to create a OneLake shortcut to bucket1.
You need to configure authentication for the connection.
Which two values should you provide? Each correct answer presents part of the solution.
NOTE: Each correct selection is worth one point.
A. the shared access signature (SAS) token
B. the secret access key
C. the access ID
D. the access key ID
E. the certificate thumbprint
Show Answer
Correct Answer: B, D
Explanation: To authenticate a OneLake shortcut to an Amazon S3 bucket, you provide AWS IAM credentials: the Access Key ID and the Secret Access Key. A SAS token is used for Azure Storage, not Amazon S3. 'Access ID' is not the AWS credential name, and a certificate thumbprint is not used for S3 shortcut authentication.
Question 93
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(“Files/ResearchProduct”)
B. spark.sql(“SELECT * FROM Lakehouse1.ResearchProduct ”)
C. spark.sql(“SELECT * FROM Lakehouse1.Tables.ResearchProduct ”)
D. external_table(ResearchProduct)
Show Answer
Correct Answer: B
Explanation: In Microsoft Fabric, a shortcut to Delta data can be created in the Lakehouse Tables area, making it queryable from notebooks with Spark SQL using the lakehouse namespace. The case also requires shortcuts to be readable through SQL endpoints, which aligns with exposing the shortcut as a table. Option A reads Delta files directly from the Files area, but the scenario's requirements favor table-based access. Option C uses an incorrect object path, and D is not valid syntax.
Question 94
HOTSPOT
-
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.
You need to migrate the Research division data for Productline2. The solution must meet the data preparation requirements.
How should you complete the code? To answer, select the appropriate options in the answer area.
NOTE: Each correct selection is worth one point.
Show Answer
Correct Answer: delta
Tables/productline2
Explanation: To present the imported CSV data as managed tables in Lakehouse Explorer, write it in Delta format to the managed Tables path. Writing to Tables/productline2 creates a managed table location.
Question 95
You have a Fabric tenant.
You are creating a Fabric Data Factory pipeline.
You have a stored procedure that returns the number of active customers and their average sales for the current month.
You need to add an activity that will execute the stored procedure in a warehouse. The returned values must be available to the downstream activities of the pipeline.
Which type of activity should you add?
A. Switch
B. KQL
C. Append variable
D. Lookup
Show Answer
Correct Answer: D
Explanation: A Lookup activity can execute a query or stored procedure against a supported source such as a Fabric warehouse and returns the result set as activity output, making the values available to downstream pipeline activities. Switch controls flow, KQL is for Kusto queries, and Append variable only appends values to an existing array variable rather than executing stored procedures.
Question 96
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 is not a columnar format, so Spark must read full rows before projecting selected columns. withColumn("Year", ...) adds a new column rather than replacing OrderDate. inferSchema=true requires schema inference, adding extra work and typically increasing execution time.
Question 97
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: No. Replacing the condition with NOT ( CALCULATE ( COUNTROWS('Order Item') ) < 0 ) is logically equivalent to checking that a row count is nonnegative, which is always true because COUNTROWS cannot return a negative value. This does not reduce the computational work or improve query execution time, so it does not meet the performance goal.
Question 98
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 is used with a table-valued function, not a scalar function. The table-valued function is evaluated for each row from Dimension.Employee. OUTER APPLY preserves all rows from the left table, returning NULLs for function columns when no matching rows are produced, so at least one output row exists for each employee.
Question 99
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: Use TOP(1000) to limit results in T-SQL, aggregate by the email field (CustomerAltKey), and filter duplicate groups with HAVING COUNT(*) > 1.
Question 100
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: Removing the high-cardinality surrogate key reduces model size and improves Import refresh when it is not needed for reporting. Splitting the datetime into separate date and time columns lowers cardinality and improves compression while preserving the full datetime information by combining the two values when needed.
Question 101
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 summary statistics for all numeric and string columns. The output includes count, mean, stddev, min, and max. For string columns, mean and stddev are present but have null values because those statistics are not applicable; the method still evaluates all numeric and string columns and returns the requested summary statistics.
$19
Get all 204 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.