Exam DP-203 topic 4 question 13 discussion

Should be C and D

100% CD

While B is a valid solution, it presents a serious performance issue when SQL Server has to dynamically convert DATE datatypes to INTEGER on-the-fly when joining to a date dimension that uses INTEGER for its surrogate key. Therefore, options C and D present the most efficient way of querying/filtering this fact table.

C and D but also B - should have asked for 3 steps

that makes sense , we don't use datetime if it's possible for performance

Star schema - Fact and Dim tables - they have to be connected using Date Key (int).

C&D. You can see some exapmles from modules of MS' dp-203 training.

Because of fixed date ranges used to query.

Should be A and E

A. Create a date dimension table that has a DateTime key. A date dimension table that has a DateTime key can provide fast query times when querying for arbitrary date ranges and aggregating by fiscal calendar attributes. The DateTime key allows for easy sorting and filtering of dates, and can be used to join with the fact table on the order date, order due date, and order ship date fields. B. Use built-in SQL functions to extract date attributes. Using built-in SQL functions to extract date attributes (such as year, quarter, month, week, day) from the DateTime key in the date dimension table can help with aggregating data by fiscal calendar attributes. This can improve query performance by reducing the amount of data that needs to be scanned and aggregated. Therefore, the correct actions to perform are A and B.

For sure its CD

CD with no doubt.

correct - C&D agree with StudentFromAus M

THe question has many clues, it states fiscal calendar year and then star schema which hints we need proper fact and dim tables and appropriate date keys to link these.

basic knowledge for fact and dim tables

Who gives these answers?? It's so obviously C and D. You want a Date Dim with an Integer key and the fact table also with that integer key

Should be CD!