70-466 · Question #153
A production SQL Server Analysis Services (SSAS) cube is processed daily. The users query products by using a hierarchy named Products from a dimension named Product. The DimProduct table in the data
The correct answer is B. Relate the Subcategory and Category attributes directly to the Product attribute.. When a SSAS dimension is sourced from a single denormalized table, attribute relationships should be defined directly to the key attribute rather than chained, to avoid data integrity violations during processing.
Question
- Product
- Subcategory
- Category
Options
- ADelete the Products hierarchy.
- BRelate the Subcategory and Category attributes directly to the Product attribute.
- CRemove the duplicate data from the DimProduct table.
- DRemove the Subcategory attribute.
How the community answered
(60 responses)- A5% (3)
- B83% (50)
- C10% (6)
- D2% (1)
Why each option
When a SSAS dimension is sourced from a single denormalized table, attribute relationships should be defined directly to the key attribute rather than chained, to avoid data integrity violations during processing.
Deleting the Products user-defined hierarchy removes navigation capability for users but does not fix the underlying attribute relationship problem causing processing or aggregation issues.
Because DimProduct is a single denormalized table where SubcategoryKey and CategoryKey both exist at the product row level, both Subcategory and Category should be related directly to the Product key attribute. The chained relationship (Product -> Subcategory -> Category) imposes a strict many-to-one constraint between Subcategory and Category that may be violated in the flat table, causing processing errors or incorrect aggregations. Relating them directly to Product removes this rigid dependency.
The table structure is intentionally denormalized for SSAS consumption; removing duplicate data would restructure the source table unnecessarily and would not resolve the attribute relationship design issue in the cube.
Removing the Subcategory attribute eliminates useful business context and is not required - the attribute can remain as long as its relationship to the key attribute is correctly defined.
Concept tested: SSAS dimension attribute relationship design for denormalized tables
Source: https://learn.microsoft.com/en-us/analysis-services/multidimensional-models/attribute-relationships-define
Topics
Community Discussion
No community discussion yet for this question.