nerdexam
Microsoft

70-466 · Question #148

You are developing a SQL Server Analysis Services (SSAS) cube. You must create a four-level hierarchy for the employee dimension. Each level must be associated with an attribute in the employee dimens

The correct answer is C. A ragged hierarchy. When a hierarchy has members that do not have values at every level, a ragged hierarchy is the correct design choice to suppress logically missing members from reporting tools.

Build an analysis services database

Question

You are developing a SQL Server Analysis Services (SSAS) cube. You must create a four-level hierarchy for the employee dimension. Each level must be associated with an attribute in the employee dimension table. Two thirds of the dimension data contain values for all four attributes. The remainder of the dimension data contains values for the first three of the four attributes only. You need to create the hierarchy so that logically missing members will not be shown by the reporting tool. Which type of hierarchy should you create?

Exhibit

70-466 question #148 exhibit

Options

  • AA parent-child hierarchy
  • BA sparse hierarchy
  • CA ragged hierarchy
  • DA balanced hierarchy

How the community answered

(23 responses)
  • A
    4% (1)
  • C
    91% (21)
  • D
    4% (1)

Why each option

When a hierarchy has members that do not have values at every level, a ragged hierarchy is the correct design choice to suppress logically missing members from reporting tools.

AA parent-child hierarchy

A parent-child hierarchy is used for recursive self-referencing relationships (like employee-manager), not for fixed-level hierarchies with unequal depth.

BA sparse hierarchy

Sparse is not a standard SSAS hierarchy type - sparsity refers to empty cells in the cube data space, not to missing levels in a dimension hierarchy.

CA ragged hierarchyCorrect

A ragged hierarchy is specifically designed for dimensions where members do not have a uniform depth across all branches - exactly the scenario where one third of members have only three of four levels populated. SSAS provides the HideMemberIf property on ragged hierarchies to suppress logically missing members so they do not appear in reporting tools.

DA balanced hierarchy

A balanced hierarchy requires that all members at every branch share the same depth, which contradicts the scenario where one third of members only have three levels.

Concept tested: SSAS ragged hierarchy with HideMemberIf

Source: https://learn.microsoft.com/en-us/analysis-services/multidimensional-models/dimension-attribute-properties-reference

Topics

#ragged hierarchy#missing members#dimension design#SSAS hierarchy types

Community Discussion

No community discussion yet for this question.

Full 70-466 Practice