Microsoft Implementing Analytics Solutions Using Microsoft Fabric (DP-600 Korean Version) - DP-600 Korean Exam Practice Test

Explanation:

The Spark engine will read only the ' SalesOrderNumber ' , ' OrderDate ' , ' CustomerName ' , ' UnitPrice ' columns from Sales_raw.csv. - Yes Removing the partition will reduce the execution time of the query. - No Adding inferSchema= ' true ' to the options will increase the execution time of the query. - Yes The code specifies the selection of certain columns, which means only those columns will be read into the DataFrame. Partitions in Spark are a way to optimize the execution of queries by organizing the data into parts that can be processed in parallel. Removing the partition could potentially increase the execution time because Spark would no longer be able to process the data in parallel efficiently. The inferSchema option allows Spark to automatically detect the column data types, which can increase the execution time of the initial read operation because it requires Spark to read through the data to infer the schema.

Explanation: Only visible for Fast2test members. You can sign-up / login (it's free).

Explanation:

Comprehensive Detailed Explanation
The requirement is to logically group the Research division workspaces and support filtering in the OneLake data hub .
Why Domain ?
Microsoft Fabric allows you to assign workspace domains (e.g., Finance, HR, Research).
This provides a logical grouping of workspaces within the organization.
Domains are the only supported way to enable filtering in OneLake data hub by department .
Capacity or tenant grouping would not allow filtering by department in OneLake.
Why OneLake data hub ?
The OneLake data hub is the centralized interface to browse and discover data assets across the organization.
With workspace domains configured, users can filter directly in the OneLake data hub by domain (e.g.,
"Research").
The Fabric Admin portal and Entra admin center are used for administration, not for workspace filtering in data discovery.
Correct Selection for the Hotspot
Grouping method: Domain
Tool: OneLake data hub
References
Workspace domains in Microsoft Fabric
Discover and filter data in OneLake data hub
Grouping method = Domain
Tool = OneLake data hub

Explanation:
The results will form a hierarchy of folders for each partition key. - Yes The resulting file partitions can be read in parallel across multiple nodes. - Yes The resulting file partitions will use file compression. - No Partitioning data by columns such as year, month, and day, as shown in the DataFrame write operation, organizes the output into a directory hierarchy that reflects the partitioning structure. This organization can improve the performance of read operations, as queries that filter by the partitioned columns can scan only the relevant directories. Moreover, partitioning facilitates parallelism because each partition can be processed independently across different nodes in a distributed system like Spark. However, the code snippet provided does not explicitly specify that file compression should be used, so we cannot assume that the output will be compressed without additional context.
References =
DataFrame write partitionBy
Apache Spark optimization with partitioning

Explanation:
For the HighestSellingPrice, you should use the GREATEST function to find the highest value from the given price columns. However, T-SQL does not have a GREATEST function as found in some other SQL dialects, so you would typically use a CASE statement or an IIF statement with nested MAX functions. Since neither of those are provided in the options, you should select MAX as a placeholder to indicate the function that would be used to find the highest value if combining multiple MAX functions or a similar logic was available.
For the TradePrice, you should use the COALESCE function, which returns the first non-null value in a list.
The COALESCE function is the correct choice as it will return AgentPrice if it ' s not null; if AgentPrice is null, it will check WholesalePrice , and if that is also null, it will return ListPrice .
The complete code with the correct SQL functions would look like this:
SELECT ProductID,
MAX(ListPrice, WholesalePrice, AgentPrice) AS HighestSellingPrice, -- MAX is used as a placeholder COALESCE(AgentPrice, WholesalePrice, ListPrice) AS TradePrice FROM Sales.Products Select MAX for HighestSellingPrice and COALESCE for TradePrice in the answer area.

Explanation: Only visible for Fast2test members. You can sign-up / login (it's free).

Explanation:

Step 1 - Select the required fields and count
We want to group by CustomerAltKey and count occurrences.
SELECT CustomerAltKey, COUNT ( * )
Step 2 - From the table
FROM DimCustomer
Step 3 - Grouping by email
GROUP BY CustomerAltKey
Step 4 - Filtering duplicates (only values with count > 1)
HAVING COUNT ( * ) > 1
Step 5 - Limiting the result to 1,000 rows
LIMIT 1000
(or in T-SQL, SELECT TOP(1000) ... ). Since both options are shown, we use LIMIT 1000 because Fabric Warehouse supports Synapse SQL T-SQL + ANSI SQL style.
Correct Sequence:
SELECT CustomerAltKey, COUNT(*)
FROM DimCustomer
GROUP BY CustomerAltKey
HAVING COUNT(*) > 1
LIMIT 1000

Explanation: Only visible for Fast2test members. You can sign-up / login (it's free).

Explanation:

Supports complex calculated columns (with aggregate functions, calculated tables, MDX hierarchies).
Minimizes page rendering times .
Step 1 - Choosing the Mode
Direct Lake # Best for near real-time queries, avoids duplication, but has limitations (e.g., some complex calculated columns, MDX user hierarchies are not fully supported).
DirectQuery # Sends queries to the source each time. It supports complex expressions but is slow (not optimal for minimizing page rendering times).
Import # Data is loaded into VertiPaq in-memory engine, supports full DAX capabilities, calculated tables, MDX hierarchies, and provides fastest query performance .
# Correct choice: Import .
Step 2 - Choosing Query Caching
Capacity default # Relies on the workspace/capacity setting.
Off # Disables caching, which could slow down report rendering.
On # Ensures queries are cached for faster page rendering times.
# Correct choice: On .
Mode: Import
Query Caching: On
References:
Semantic model storage modes in Fabric
Query caching in Power BI / Fabric

Explanation:

In the ROW_NUMBER() function, choose OVER (PARTITION BY CustomerID ORDER BY LastUpdated DESC) .
In the WHERE clause, choose WHERE X = 1 .
To select the most recent row for each customer ID, you use the ROW_NUMBER() window function partitioned by CustomerID and ordered by LastUpdated in descending order. This will assign a row number of 1 to the most recent update for each customer. By selecting rows where the row number ( X ) is 1, you get the latest update per customer.
References =
Use the OVER clause to aggregate data per partition
Use window functions

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.

Explanation: Only visible for Fast2test members. You can sign-up / login (it's free).