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?
A.
A parent-child hierarchy
B.
A sparse hierarchy
C.
A ragged hierarchy
D.
A balanced hierarchy
Answer:
C: Ragged hierachy
http://iman77.blogspot.com.es/2009/09/handling-raggedunbalanced-hierarchies.html
I agree.
this is an interesting one. ragged and parent child both create unbalanced hierarchies. The key difference between them is that parent child is self referencing and the balanced or unbalanced result is due to the self referencing constraints of the data. A ragged hierarchy is user defined and generally created to display attributes that don’t naturally have a relationship to each other.
Given that the question doesn’t indicate that it the dimension is self referencing I agree that it is ragged.
It tries to trick you by indicating it is an employee table to naturally people think org chart/parent child.
@dust – nice description. I agree “C” ragged
I disagree, the question does indicate the dimension is self referencing;
“Each level must be associated with an attribute in the employee dimension table.”
‘A’
ragged or parent child???
I think it is A.