Microsoft 70-463 Exam Questions

Question 6 of 218

You are designing a data warehouse for a software distribution business that stores sales by software title. It stores sales targets by software category. Software titles are classified into subcategories and categories. Each software title is included in only a single software subcategory, and each subcategory is included in only a single category. The data warehouse will be a data source for an Analysis Services cube.
The data warehouse contains two fact tables:
✑ factSales, used to record daily sales by software title
✑ factTarget, used to record the monthly sales targets by software category
Reports must be developed against the warehouse that reports sales by software title, category and subcategory, and sales targets.
You need to design the software title dimension. The solution should use as few tables as possible while supporting all the requirements.
What should you do?

Create three software tables, dimSoftware, dimSoftwareCategory, and dimSoftwareSubcategory and a fourth bridge table that joins software titles to their appropriate category and subcategory table records with foreign key constraints. Direct the cube developer to use key granularity attributes.

Create three software tables, dimSoftware, dimSoftwareCategory, and dimSoftwareSubcategory. Connect factSales to all three tables and connect factTarget to dimSoftwareCategory with foreign key constraints. Direct the cube developer to use key granularity attributes.

Create one table, dimSoftware, which contains Software Detail, Category, and Subcategory columns. Connect factSales to dimSoftware with a foreign key constraint. Direct the cube developer to use a non-key granularity attribute for factTarget.

Create two tables, dimSoftware and dimSoftwareCategory. Connect factSales to dimSoftware and factTarget to dimSoftwareCategory with foreign key

Correct Answer: C

Question 7 of 218

You are designing a data warehouse hosted on SQL Azure. The data warehouse currently includes the dimUser and dimDistrict dimension tables and the factSales fact table. The dimUser table contains records for each user permitted to run reports against the warehouse; and the dimDistrict table contains information about sales districts.
The system is accessed by users from certain districts, as well as by area supervisors and users from the corporate headquarters.
You need to design a table structure to ensure that certain users can see sales data for only certain districts. Some users must be permitted to see sales data from multiple districts.
What should you do?

Add a district column to the dimUser table.

Partition the factSales table on the district column.

Create a userDistrict table that contains primary key columns from the dimUser and dimDistrict tables.

For each district, create a view of the factSales table that includes a WHERE clause for the district.

Correct Answer: C

Question 8 of 218

You are reviewing the design of a customer dimension table in an existing data warehouse hosted on SQL Azure.
The current dimension design does not allow the retention of historical changes to customer attributes such as Postcode.
You need to redesign the dimension to enable the full historical reporting of changes to multiple customer attributes including Postcode.
What should you do?

Add StartDate and EndDate columns to the customer dimension.

Add an IsCurrent column to the customer dimension.

Enable Snapshot Isolation on the data warehouse.

Add CurrentValue and PreviousValue columns to the customer dimension.

Correct Answer: A

Question 9 of 218

You are implementing the indexing strategy for a fact table in a data warehouse. The fact table is named Quotes. The table has no indexes and consists of seven columns:
✑ [ID]
✑ [QuoteDate]
✑ [Open]
✑ [Close]
✑ [High]
✑ [Low]
✑ [Volume]
Each of the following queries must be able to use a columnstore index:
✑ SELECT AVG ([Close]) AS [AverageClose] FROMQuotes WHERE [QuoteDate] BETWEEN '20100101' AND '20101231'.
✑ SELECT AVG([High] - [Low]) AS [AverageRange] FROM Quotes WHERE [QuoteDate] BETWEEN '20100101' AND '20101231'.
SELECT SUM([Volume]) AS [SumVolume] FROM Quotes WHERE [QuoteDate] BETWEEN '20100101' AND '20101231'.

You need to ensure that the indexing strategy meets the requirements. The strategy must also minimize the number and size of the indexes.
What should you do?

Create one columnstore index that contains [ID], [Close], [High], [Low], [Volume], and [QuoteDate].

Create three coiumnstore indexes:One containing [QuoteDate] and [Close]One containing [QuoteDate], [High], and [Low]One containing [QuoteDate] and [Volume]

Create one columnstore index that contains [QuoteDate], [Close], [High], [Low], and [Volume].

Create two columnstore indexes:One containing [ID], [QuoteDate], [Volume], and [Close]One containing [ID], [QuoteDate], [High], and [Low]

Correct Answer: C

Question 10 of 218

You are designing an enterprise star schema that will consolidate data from three independent data marts. One of the data marts is hosted on SQL Azure.
Most of the dimensions have the same structure and content. However, the geography dimension is slightly different in each data mart.
You need to design a consolidated dimensional structure that will be easy to maintain while ensuring that all dimensional data from the three original solutions is represented.
What should you do?

Create a junk dimension for the geography dimension.

Implement change data capture.

Create a conformed dimension for the geography dimension.

Create three geography dimensions.

Correct Answer: C