Microsoft Implementing Analytics Solutions Using Microsoft Fabric - DP-600 FREE EXAM DUMPS QUESTIONS & ANSWERS

You have a Fabric workspace named Workspace1.
Workspace1 contains multiple semantic models, including a model named Model1. Model1 is updated by using an XMLA endpoint.
You need to increase the speed of the write operations of the XMLA endpoint.
What should you do?
Correct Answer: A Vote an answer
Explanation: Only visible for FreeCram members. You can sign-up / login (it's free).
You have a Fabric tenant that contains a semantic model. The model contains data about retail stores.
You need to write a DAX query that will be executed by using the XMLA endpoint The query must return a table of stores that have opened since December 1,2023.
How should you complete the DAX expression? To answer, drag the appropriate values to the correct targets.
Each value may be used once, more than once, or not at all. You may need to drag the split bar between panes or scroll to view content.
NOTE: Each correct selection is worth one point.
Correct Answer:

Explanation:
The correct order for the DAX expression would be:
DEFINE VAR _SalesSince = DATE ( 2023, 12, 01 )
EVALUATE
FILTER (
SUMMARIZE ( Store, Store[Name], Store[OpenDate] ),
Store[OpenDate] > = _SalesSince )
In this DAX query, you ' re defining a variable _SalesSince to hold the date from which you want to filter the stores. EVALUATE starts the definition of the query. The FILTER function is used to return a table that filters another table or expression. SUMMARIZE creates a summary table for the stores, including the Store
[Name] and Store[OpenDate] columns, and the filter expression Store[OpenDate] > = _SalesSince ensures only stores opened on or after December 1, 2023, are included in the results.
References =
DAX FILTER Function
DAX SUMMARIZE Function
You need to ensure that Contoso can use version control to meet the data analytics requirements and the general requirements. What should you do?
Correct Answer: C Vote an answer
Explanation: Only visible for FreeCram members. You can sign-up / login (it's free).
You have a Fabric warehouse that contains the following data.

The data has the following characteristics:
* Each customer is assigned a unique CustomerlD value.
* Each customer is associated to a single SalesRegion value.
* Each customer is associated to a single CustomerAddress value.
* The Customer table contains 5 million rows.
* All foreign key values are non-null.
You need to create a view to denormalize the data into a customer dimension that contains one row per distinct CustomerlD value. The solution must minimize query processing time and resources.
How should you complete the T-SQL statement? To answer, select the appropriate options in the answer area.
Correct Answer:

Explanation:

The goal is to denormalize the data into a customer dimension with one row per distinct CustomerID, minimizing query processing time and resources. Since each customer is associated with a single SalesRegion and a single CustomerAddress, and all foreign key values are non-null, a left outer join is appropriate to ensure all customers from the Customer table are included, even if there are any unexpected missing addresses (though the problem states each customer has a single address). However, given the non-null foreign key constraint, an inner join could also work, but left outer join is safer and aligns with denormalization to ensure completeness.
The join condition should link the Customer table (C) with the CustomerAddress table (CA) using CustomerID, as this ensures each customer ' s address data is included.
The join with SalesRegion (SR) on SalesRegionID is already included in the query, and since each customer has a single SalesRegion, it fits the denormalization requirement.
The where CA.AddressType = ' Main Office ' filter ensures only the main office address is included, which is a valid constraint for a customer dimension.
Thus, the completed T-SQL statement would effectively denormalize the data while minimizing resource use by leveraging the existing relationships and constraints.
You have a Fabric tenant that contains a warehouse named DW1 and a lakehouse named LH1. DW1 contains a table named Sales.Product. LH1 contains a table named Sales.Orders.
You plan to schedule an automated process that will create a new point-in-time (PIT) table named Sales.
ProductOrder in DW1. Sales.ProductOrder will be built by using the results of a query that will join Sales.
Product and Sales.Orders.
You need to ensure that the types of columns in Sales. ProductOrder match the column types in the source tables. The solution must minimize the number of operations required to create the new table.
Which operation should you use?
Correct Answer: D Vote an answer
Explanation: Only visible for FreeCram members. You can sign-up / login (it's free).
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.
Correct Answer: B,C,E Vote an answer
Explanation: Only visible for FreeCram members. You can sign-up / login (it's free).
You have two Microsoft Power Bl queries named Employee and Retired Roles.
You need to merge the Employee query with the Retired Roles query. The solution must ensure that rows in the Employee query that match the Retired Roles query are removed.
Which column and Join Kind should you use in Power Query Editor? To answer, select the appropriate options in the answer area.
NOTE: Each correct answer is worth one point
Correct Answer:

Explanation:
You have the following T-SQI statement.

Correct Answer:

Explanation:

The statement uses SUM(CASE WHEN RefundStatus = ' Refunded ' THEN SalesAmount ELSE 0 END) AS TotalRevenue, which calculates TotalRevenue by summing SalesAmount only when RefundStatus is ' Refunded ' , and 0 otherwise. This means Region values are returned regardless of RefundStatus, but the TotalRevenue reflects refunded items.
The WHERE (TransactionDate) - YEAR(GETDATE()) condition is incomplete and lacks proper comparison (e.g., no equality or range check), so it does not filter for the current year.
The TotalRevenue calculation does not aggregate all SalesAmount values with RefundStatus of ' Refunded ' ; it sums SalesAmount only for refunded items within the grouped data, with 0 for non-refunded items.
0
0
0
10