The Research and Development team has requested that capabilities be added to the database. The capabilities must meet the following requirements: - A device member must be able to have multiple capab

Adding an attribute hierarchy per capability to the customer dimension creates a fixed schema that requires development changes each quarter when new capabilities are introduced, violating the minimal maintenance requirement.

Creating a dedicated Capability Name dimension and configuring a many-to-many relationship in SSAS directly models the requirement that a device can have multiple capabilities and a capability can belong to multiple devices via an intermediate measure group. A separate dimension allows the R&D team to add new capability members to the data source each quarter without any model schema changes, minimizing development and maintenance effort.

A single attribute hierarchy named Capability Name on the customer dimension supports only a regular one-to-many relationship and cannot model the required many-to-many relationship between devices and capabilities.

Configuring a regular relationship between the Capability Name dimension and the fact table creates a one-to-many relationship, which cannot satisfy the requirement that a capability belongs to multiple device members.