nerdexam
Microsoft

70-466 · Question #131

You need to configure a hierarchy for DimProduct that meets the technical requirements. What should you do?

The correct answer is B. Set ProductCategory as the parent of ProductSubcategory and set ProductSubcategory as the parent of ProductName. For ProductSubcategory, click Hide if Name Equals Parent. Configuring a product hierarchy in a tabular model requires ordering levels from broadest to most specific and applying 'Hide if Name Equals Parent' at the intermediate level to suppress redundant nodes.

Build a tabular data model

Question

You need to configure a hierarchy for DimProduct that meets the technical requirements. What should you do?

Options

  • ASet ProductName as the parent of ProductSubCategory and set ProductSubcategory as the parent of ProductCategory. For ProductSubcategory, click Hide if Name Equals Parent.
  • BSet ProductCategory as the parent of ProductSubcategory and set ProductSubcategory as the parent of ProductName. For ProductSubcategory, click Hide if Name Equals Parent.
  • CSet ProductName as the parent of ProductSubcategory and set ProductSubcategory as the parent of ProductCategory. For ProductSubcategory, click Hide if Name Equals Parent.
  • DSet ProductCategory as the parent of ProductSubcategory and set ProductSubcategory as the parent of ProductName. For ProductCategory, click Hide if Name Equals Parent.

How the community answered

(51 responses)
  • A
    10% (5)
  • B
    82% (42)
  • C
    2% (1)
  • D
    6% (3)

Why each option

Configuring a product hierarchy in a tabular model requires ordering levels from broadest to most specific and applying 'Hide if Name Equals Parent' at the intermediate level to suppress redundant nodes.

ASet ProductName as the parent of ProductSubCategory and set ProductSubcategory as the parent of ProductCategory. For ProductSubcategory, click Hide if Name Equals Parent.

Placing ProductName as the top-level parent reverses the hierarchy so it drills up from specific to general rather than from general to specific, which is the wrong direction for a product hierarchy.

BSet ProductCategory as the parent of ProductSubcategory and set ProductSubcategory as the parent of ProductName. For ProductSubcategory, click Hide if Name Equals Parent.Correct

ProductCategory is the broadest classification and must be the top-level parent, with ProductSubcategory as its child and ProductName as the leaf level, forming the correct drill-down path. Applying 'Hide if Name Equals Parent' to ProductSubcategory suppresses subcategory nodes whose names duplicate the parent category name, avoiding redundant levels in the hierarchy browse experience.

CSet ProductName as the parent of ProductSubcategory and set ProductSubcategory as the parent of ProductCategory. For ProductSubcategory, click Hide if Name Equals Parent.

Identical to option A - it sets ProductName as the top-level parent, which inverts the intended category-to-product drill-down direction.

DSet ProductCategory as the parent of ProductSubcategory and set ProductSubcategory as the parent of ProductName. For ProductCategory, click Hide if Name Equals Parent.

Applies 'Hide if Name Equals Parent' to ProductCategory instead of ProductSubcategory, which does not suppress redundant subcategory nodes and is the wrong level for this setting.

Concept tested: Tabular model parent-child product hierarchy configuration

Source: https://learn.microsoft.com/en-us/power-bi/transform-model/desktop-create-and-manage-hierarchies

Topics

#SSAS hierarchy#Hide if Name Equals Parent#parent-child levels#DimProduct

Community Discussion

No community discussion yet for this question.

Sign up to join the discussion
Full 70-466 Practice