You need to create the calculation for SalespersonName. What should you do? (Each Answer presents a complete solution. Choose all that apply.)

A SQL Server computed column is evaluated at query time and, unless marked PERSISTED, cannot be indexed efficiently; the scenario's correct approach requires a stored, ETL-populated column rather than a formula-driven computed column.

Adding a new physical column directly to the DimSalesperson table and populating it via ETL creates a persistent, stored SalespersonName value that is available to all reports and models without per-query computation.

Configuring the model's Salesperson table to be based on a custom query modifies the model binding layer rather than defining the derivation at the data warehouse source, which is the required level of change.

Adding a DAX calculated column to the SSAS tabular model defines SalespersonName only within the model layer and does not place the derivation in the data warehouse where it can be shared across all consumers.

Creating a data warehouse view with a derived column - such as concatenating FirstName and LastName - encapsulates the transformation at the source layer without altering the base table, and the tabular model can bind to that view as its data source.

A DAX calculated column in the model is a model-layer transformation that duplicates the logic per model rather than centralizing the derivation at the data warehouse source as required.