You design a Business Intelligence (BI) solution by using SQL Server 2008. You design a SQL Server 2008 Analysis Services (SSAS) solution by using SQL Server 2008. The solution uses a source database that contains a table named Customer. The Customer table has multiple columns.
You have read-only access to the database.
You plan to reduce the number of columns in the Customer table. You need to split the Customer table to be distributed across multiple table definitions.

What should you do?

A.
Create multiple data sources for the SSAS solution.

B.
Create multiple named queries for the SSAS solution.

C.
Create multiple data source views for the SSAS solution.

D.
Create multiple database views for the source database.

Explanation:
Tip: “across multiple table” = “named queries”

http://technet.microsoft.com/en-us/library/ms175683.aspx
Defining Named Queries in a Data Source View (Analysis Services)
A named query is a SQL expression represented as a table. In a named query, you can specify an SQL expression to select rows and columns returned from one or more tables in one or more data sources. A named query is like any other table in a data source view with rows and relationships, except that the named query is based on an expression.
A named query lets you extend the relational schema of existing tables in a data source view without modifying the underlying data source. For example, a series of named queries can be used to split up a complex dimension table into smaller, simpler dimension tables for use in database dimensions. A named query can also be used to join multiple database tables from one or more data sources into a single data source view table.
When you create a named query, you specify a name, the SQL query returning the columns and data for the table, and optionally, a description of the named query. The SQL expression can refer to other tables in the data source view. After the named query is defined, the SQL query in a named query is sent to the provider for the data source and validated as a whole. If the provider does not find any errors in the SQL query, the column is added to the table.
Tables and columns referenced in the SQL query should not be qualified or should be qualified by the table name only. For example, to refer to the SaleAmount column in a table, SaleAmount or Sales.SaleAmount is valid, but dbo.Sales.SaleAmount generates an error.