You have the data model shown in the exhibit. (Click the Exhibit tab.) You need to create a hierarchy from DimproductSubcategory[ProductSubcategoryName] and DimProduct[ProductName]. What should you do before you create the hierarchy?
A.
Create a relationship between the tables. To DimProductSubcategory, add a calculated column named ProductName that uses the LOOKUPVALUE (DimProduct[ProductName],DimProduct[ProductKey],[ProductKey]) DAX formula.
B.
To DimProduct, add a calculated column named ProductSubcategoryName that uses the LOOKUPVALUE(DimProductSubcategory [ProductSubcategoryName],DimProductSubcategory[ProductCategoryKey],[ProductSubcategoryKey]) DAX formula.
C.
Create a relationship between the tables. To DimProduct, add a calculated column named ProductSubcategoryName that uses the RELATEDTABLE (DimProductSubcategory[ProductSubcategoryName]) DAX formula.
D.
To DimProduct, add a calculated column named ProductSubcategoryName that uses the VALUES(DimProductSubcategory[ProductSubcategoryName]) DAX formula.
Correct Answer is B
A is adding a column to DimproductSubcategory table which lacks the product detail. By no way this can be correct
C would have been correct if instead of RELATEDTABLE function, RELATED had been used.
D is incorrect. VALUES will return a TABLE where a single value (the subcategory for each product) is expected. It will produce an #ERROR
B is correct. VALUELOOKUP is used correctly and it does not need a relationship to exist between the tables
1, if relationship exists, (option C: not correct)
To DimProduct, add a calculated column named ProductSubcategoryName that uses the : RELATED(DimProductSubcategory[ProductSubcategoryName]).
2, if no relationship, (option B: not correct neither, the 2nd argument, A also wrong becoz the second argument.)
To DimProduct, add a calculated column named ProductSubcategoryName that uses the LOOKUPVALUE(DimProductSubcategory [ProductSubcategoryName],DimProductSubcategory[ProductSubcategoryKey],[ProductSubcategoryKey]).
Reference Link: https://docs.microsoft.com/en-us/dax/lookupvalue-function-dax
How can B be correct? - LOOKUPVALUE expects a scalar value as the third argument. Here, the coloumn [ProductSubcategoryKey] is the third argument. If I try this formula, it gives me exactly this error.
C is not correct. RELATEDTABLE can return a calculated column, however it takes a table name as the parameter, in this case, if RELATEDTABLE('DimProductSubcategory') then correct.
B is correct, but it has a typo.
Should be...
LOOKUPVALUE(DimProductSubcategory [ProductSubcategoryName],DimProductSubcategory[ProductSubcategoryKey],[ProductSubcategoryKey])
True, but B is incorrect for sure => please look carefully at the formula => The formule in B mistakenly connects [ProductCategoryKey] to [ProductSubcategoryKey] => this should have matching [ProductSubcategoryKey] with [ProductSubcategoryKey].
C is also incorrect => it creates a table because it uses RELATEDTABLE instead of RELATED.
Therefore the answer is A
I think A is correct. B Dax Formula is incorrect. The correct is
LOOKUPVALUE(DimProductSubcategory [ProductSubcategoryName],DimProductSubcategory[ProductSubcategoryKey],[ProductSubcategoryKey])
This section is not available anymore. Please use the main Exam Page.70-779 Exam Questions
Log in to ExamTopics
Sign in:
Community vote distribution
A (35%)
C (25%)
B (20%)
Other
Most Voted
A voting comment increases the vote count for the chosen answer by one.
Upvoting a comment with a selected answer will also increase the vote count towards that answer by one.
So if you see a comment that you already agree with, you can upvote it instead of posting a new comment.
tho
Highly Voted 5 years, 7 months agoRutRut
5 years, 4 months agoArklur
5 years, 3 months agothecov
Highly Voted 5 years, 8 months agoFrdFrd
Most Recent 4 years, 5 months agoCDL
4 years, 8 months agomssql
4 years, 8 months agoSymone
4 years, 9 months agoclaudia_learner
5 years, 1 month agoamar111
5 years, 2 months agotdu7
5 years, 3 months agomcsetc
5 years, 4 months agoSN22
5 years, 4 months agocs3122
5 years, 5 months agomohroshdy
5 years, 6 months agoPowerBIconsultant12
4 years, 8 months agowanjinyou
4 years, 8 months agotrantrongw
5 years, 7 months agoOye
5 years, 7 months agoPowerBIconsultant12
4 years, 8 months agoThe_Marv
5 years, 7 months ago