You need to implement the product dimension. What should you do?

Building a dimension from a view that joins source tables at query time defers join processing until query execution, adding overhead and reducing performance compared to a pre-materialized dimension table.

This option creates a dimension table but likely omits required attributes or uses an incomplete key structure, making it an insufficient definition for a fully specified product dimension.

Creating a dedicated product dimension table directly in the data warehouse with the required product attributes follows the star schema dimensional modeling standard. A physical table pre-joins any necessary source data, providing optimal query performance and a stable, reusable structure for the SSAS cube to reference. Placing the dimension in the data warehouse layer ensures consistency across multiple cubes or reporting tools that consume the same data.

Creating a named query inside the cube embeds join logic in the SSAS layer rather than the data warehouse, violating separation of concerns and complicating future maintenance.