Correct Answer:

Explanation:
A replica of dbo.Sales is created in the test schema by copying the metadata only. - Yes Additional schema changes to dbo.FactSales will also apply to test.FactSales. - No Additional data changes to dbo.FactSales will also apply to test.FactSales. - No The CREATE TABLE AS CLONE statement creates a copy of an existing table, including its data and any associated data structures, like indexes. Therefore, the statement does not merely copy metadata; it also copies the data. However, subsequent schema changes to the original table do not automatically propagate to the cloned table. Any data changes in the original table after the clone operation will not be reflected in the clone unless explicitly updated.
References =
CREATE TABLE AS SELECT (CTAS) in SQL Data Warehouse

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

Correct Answer: A  🗳️

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

Correct Answer:

Explanation:

Comprehensive Detailed Explanation
We need to write a query that summarizes order quantities by year and product, and also include the yearly total for all products in each row.
Step 1: What the query needs
Extract the year from SalesOrderDetail.ModifiedDate.
Join with the Product table to get the product name.
Aggregate with SUM(OrderQty).
Return grouped data by year and product, with an additional subtotal row per year (all products combined).
Step 2: Evaluate the SELECT Clause
We must extract the year using:
YEAR(so.ModifiedDate) AS OrderDate
This converts the ModifiedDate column into a year value for grouping.
Step 3: Evaluate the GROUP BY options
CUBE(YEAR, P.Name) # Produces all combinations of year totals, product totals, and grand totals. Too many combinations, not required.
GROUPING SETS # Could achieve the result but requires explicitly listing the sets. Less direct.
ROLLUP(YEAR, P.Name) # Produces grouping by (Year, Product) and then a subtotal per Year. Exactly what is required.
YEAR only # Would group only by year, losing per-product breakdown.
Correct: ROLLUP(YEAR(so.ModifiedDate), P.Name)
Step 4: Completed Query
SELECT
YEAR(so.ModifiedDate) AS OrderDate,
p.Name,
SUM(so.OrderQty) AS OrderQty
FROM dbo.SalesOrderDetail so
INNER JOIN dbo.Product p
ON p.ProductID = so.ProductID
GROUP BY ROLLUP(YEAR(so.ModifiedDate), p.Name);
Why This Works
YEAR(so.ModifiedDate) extracts year for grouping.
ROLLUP(YEAR, P.Name) provides both product-level totals and yearly subtotals.
Ensures the requirement: "include the yearly sum of order quantities for all the products in each row." References GROUP BY ROLLUP in T-SQL Aggregate functions in Microsoft Fabric warehouses