You are designing a data warehouse with two fact tables. The first table contains sales per month and the
second table contains orders per day. Referential integrity must be enforced declaratively. You need to design a
solution that can join a single time dimension to both fact tables. What should you do?
A.
Create a time mapping table.
B.
Change the level of granularity in both fact tables to be the same.
C.
Merge the fact tables.
D.
Create a view on the sales table.
Explanation:
Not Sure
A.
Create a time mapping table.
0
0
B.
Change the level of granularity in both fact tables to be the same.
0
0
Same question as Q41. Answer in both is to create time dimension table
Q41 C
Q72 A
0
0
A, because in test w cannot assume that we have sales fact table on a day granularity level (B or C).
0
0
The time mapping table is Change Data Capture-related. It lists a transaction ID as well as the time of the insert/update/delete. So isn’t the best answer B (there is no option for ‘Create a Time Dimension table’…)?
0
0
B
0
0
b IS THE MOST LOGICAL CHOICE
0
0
This is utter nonsense. I’ve read this question in 4 other areas and the answer has always been time mapping. Only now do I see PB’s thing. If you google, you will only find this:
https://msdn.microsoft.com/en-us/library/bb510494.aspx
Yes, time mapping, which isn’t even an actual microsoft term, is a cdc concept and is otherwise undefined everywhere in the world. It can be an answer to nothing as it isn’t a commonly accepted definition. So the answer must be B
0
0
Bellow link explains how (a) can achieve this https://www.oraylis.de/blog/different-granularity-in-a-single-dimension
0
0