You need to configure a hierarchy for DimProduct that meets the technical requirements

###BeginCaseStudy###
Case Study: 1
Tailspin Toys

Background
Tailspin Toys is a multinational company that manufactures toys. Tailspin Toys has offices in
five regions worldwide. The company sells toys at various retail stores. The company also
sells toys directly to consumers through a web site.
The company has the following departments:
• Sales
• Distribution
• Manufacturing
Each department has an office in each region.
The fiscal calendar of Tailspin Toys runs from June to May.
The network contains a server farm that has Microsoft SharePoint Server 2013 installed.
Existing Environment
Current Database Environment
Each department uses SharePoint team sites for internal collaboration.
All manufacturing information is stored in a relational database named Manufacturing. All
sales information is stored in a relational database named Sales.
Tailspin Toys deploys SQL Server Analysis Services (SSAS) and configures SSAS to use
tabular models. SSAS will be used for all sales reports.
Tailspin Toys deploys a SQL Server Reporting Services (SSRS) instance in SharePoint
mode.
Sales Database
A database named Sales contains two tables named FactSales and DimProduct. FactSales
contains the following columns:
• SalesID
• Total Due
• OrderDate
DimProduct contains the following columns:
• ProductID
• ProductName
• ProductCategory
• ProductSubcategory
The Sales database contains information about the products. Most of the products have a
category and a subcategory. Certain products only have a category.
A sample from DimProduct is shown in the following table.

Requirements
Security Requirements

Tailspin Toys identifies the following security requirement:
• Sales department users must be allowed to view the sales transactions from their
region only.
• Sales department users must be able to view the contents of the manufacturing
reports.
• Manufacturing department users must be able to create new manufacturing reports.
• Third-party and custom solutions must NOT be deployed to the reporting server.
• Sales department users must NOT be able to create new manufacturing reports.
Planned Reporting Implementation
The manufacturing department plans to use the SSRS instance for its reports. The
manufacturing department also plans to make its reports accessible from SharePoint. All
manufacturing reports will use an existing database named Manufacturing.
Reporting Requirements
Tailspin Toys identifies the following reporting requirements:
• All reports must contain the company logo and a header that contains the date and the
time that the report was executed.
• All reports must be created by using the SQL Server Data Tools.
Manufacturing report
You plan to create a report named Manufacturinglssues.rdl. The report has the following
requirements:
• Manufacturing department managers must be able to view product issues by product
type, manufacturing plant location, and error type.
• The manufacturing department managers must be able to change views by choosing
options from drop-down lists.
Sales reports
You plan to create a sales report named RegionalSales.rdl. The report has the following
requirements:
• Users must be able to view the report by using a web browser. By default,
subcategories and product details must be hidden when using the browser.
• Users must be able to subscribe to receive the report by email. The report must be sent
by email as a PDF attachment.
You plan to create a quarterly sales report named QuarterSales.rdl. The report must display
sales data by fiscal quarter.
Technical Requirements
Tailspin Toys identifies the following technical requirements:
• Products in the DimProduct table that do NOT have a subcategory must use the
category value as the subcategory value.
• SSRS must NOT connect to databases more frequently than once every 30 minutes.
• Sales department users must be able to use Microsoft Excel to browse tabular data.
###EndCaseStudy###

You need to configure a hierarchy for DimProduct that meets the technical requirements.
What should you do?

A.
Set ProductName as the parent of ProductSubCategory and set ProductSubcategory as
the parent of ProductCategory. For ProductSubcategory, click Hide if Name Equals Parent.

B.
Set ProductCategory as the parent of ProductSubCategory and set ProductSubcategory
as the parent of ProductName. For ProductSubcategory, click Hide if Name Equals Parent.

C.
Set ProductName as the parent of ProductSubcategory and set ProductSubCategory as
the parent of ProductCategory. For ProductCategory, click Hide if Name Equals Parent.

D.
Set ProductCategory as the parent of ProductSubcategory and set ProductSubCategory
as the parent of ProductName. For ProductCategory, click Hide if Name Equals Parent.