Download Implementing a Data Warehouse with Microsoft SQL Server 2012-2014.70-463.PracticeTest.2019-02-14.144q.vcex

Vendor: Microsoft
Exam Code: 70-463
Exam Name: Implementing a Data Warehouse with Microsoft SQL Server 2012/2014
Date: Feb 14, 2019
File Size: 1 MB

How to open VCEX files?

Files with VCEX extension can be opened by ProfExam Simulator.

Purchase
Coupon: EXAM_HUB

Discount: 20%

Demo Questions

Question 1
You develop a SQL Server Integration Services (SSIS) package that imports SQL Azure data into a data warehouse every night. 
The SQL Azure data contains many misspellings and variations of abbreviations. To import the data, a developer used the Fuzzy Lookup transformation to choose the closest-matching string from a reference table of allowed values. The number of rows in the reference table is very large. 
If no acceptable match is found, the Fuzzy Lookup transformation passes a null value. 
The current setting for the Fuzzy Lookup similarity threshold is 0.50. 
Many values are incorrectly matched. 
You need to ensure that more accurate matches are made by the Fuzzy Lookup transformation without degrading performance. 
What should you do?
  1. Change the Exhaustive property to True.
  2. Change the similarity threshold to 0.55.
  3. Change the similarity threshold to 0.40.
  4. Increase the maximum number of matches per lookup.
Correct answer: B
Explanation:
References: http://msdn.microsoft.com/en-us/library/ms137786.aspx
References: http://msdn.microsoft.com/en-us/library/ms137786.aspx
Question 2
You install a SQL Server 2012 database engine instance on a production server. A month later, you install SQL Server 2012 Integration Services (SSIS). 
You must develop an SSIS project and deploy it to the server by using the Project Deployment model. 
Operations Log records that are outside the configured retention period must be cleaned automatically. 
You need to create the SSIS catalog on the production server and ensure that the operations log cleaning requirement is met. 
What should you do? (Each correct answer presents part of the solution. Choose all that apply.)
  1. Enable XP Command Shell.
  2. Enable CLR Integration.
  3. Enable OLE Automation.
  4. Start the SQL Server Browser service.
  5. Enable Cross Database Ownership Chaining
  6. Start the SQL Server Agent service
  7. Enable Ad Hoc Remote Queries.
Correct answer: BF
Explanation:
B: To create the SSISDB catalog in SQL Server Management StudioOpen SQL Server Management Studio. Connect to the SQL Server Database Engine. In Object Explorer, expand the server node, right-click the Integration Services Catalogs node, and then click Create Catalog. Click Enable CLR Integration. The catalog uses CLR stored procedures. Etc. F: SSIS projects, packages, parameters, environments, and operational history are all stored in the SSISDB database so if you have hundreds of SSIS packages or packages that run every few minutes you could see how the database storing all the historical information would grow exponentially.Also included when you enable this feature is a SQL Server Agent Job called SSIS Server Maintenance job:    References: http://msdn.microsoft.com/en-us/library/gg471509(v=sql.110).aspxhttps://www.mssqltips.com/sqlservertip/3307/managing-the-size-of-the-sql-server-ssis-catalog-database/
B: To create the SSISDB catalog in SQL Server Management Studio
  1. Open SQL Server Management Studio. 
  2. Connect to the SQL Server Database Engine. 
  3. In Object Explorer, expand the server node, right-click the Integration Services Catalogs node, and then click Create Catalog. 
  4. Click Enable CLR Integration. 
The catalog uses CLR stored procedures. 
Etc. 
F: SSIS projects, packages, parameters, environments, and operational history are all stored in the SSISDB database so if you have hundreds of SSIS packages or packages that run every few minutes you could see how the database storing all the historical information would grow exponentially.
Also included when you enable this feature is a SQL Server Agent Job called SSIS Server Maintenance job:
  
References: 
http://msdn.microsoft.com/en-us/library/gg471509(v=sql.110).aspx
https://www.mssqltips.com/sqlservertip/3307/managing-the-size-of-the-sql-server-ssis-catalog-database/
Question 3
A SQL Server Integration Services (SSIS) package on a computer is failing periodically in production. The package was created less than one year ago and was deployed to the SSIS catalog. 
Sometimes the package is started on a SQL Agent schedule; sometimes the package is started manually by an SSIS developer by using the Object Explorer in SQL Server Management Studio. 
You need to identify the authenticated user responsible for starting the package each time it failed in the past. 
Where can you find this information?
  1. the SQL Server Log
  2. the SSISDB.[catalog].[executions] view
  3. the SSISDB.[catalog].[event_messages] view
  4. the SQL Agent Job History
  5. the SQL Agent Error Log
Correct answer: B
Question 4
You maintain a SQL Server Integration Services (SSIS) package. The package was developed by using SQL Server 2008 Business Intelligence Development Studio (BIDS). 
The package includes custom scripts that must be upgraded. 
You need to upgrade the package to SQL Server 2012. 
Which tool should you use?
  1. SSIS Upgrade Wizard in SQL Server 2008 BIDS
  2. SSIS Upgrade Wizard in SQL Server Data Tools
  3. SQL Server DTExecUI utility (dtexecui.exe)
  4. SQL Server dtexec utility (dtexec.exe)
  5. SQL Server Integration Services Deployment Wizard
Correct answer: B
Explanation:
Use the SSIS Package Upgrade Wizard to upgrade SQL Server 2005 Integration Services (SSIS) packages and SQL Server 2008 Integration Services (SSIS) packages to the package format for the current (2012) release of SQL Server Integration Services.
Use the SSIS Package Upgrade Wizard to upgrade SQL Server 2005 Integration Services (SSIS) packages and SQL Server 2008 Integration Services (SSIS) packages to the package format for the current (2012) release of SQL Server Integration Services.
Question 5
You are reviewing the design of an existing fact table named factSales, which is loaded from a SQL Azure database by a SQL Server Integration Services (SSIS) package each day. The fact table has approximately 1 billion rows and is dimensioned by product, sales date, and sales time of day. 
  
The database administrator is concerned about the growth of the database. Users report poor reporting performance against this database. Reporting requirements have recently changed and the only remaining report that uses this fact table reports sales by product name, sale month, and sale year. No other reports will be created against this table. 
You need to reduce the report processing time and minimize the growth of the database. 
What should you do?
  1. Partition the table by product type.
  2. Create a view over the fact table to aggregate sales by month.
  3. Change the granularity of the fact table to month.
  4. Create an indexed view over the fact table to aggregate sales by month.
Correct answer: C
Question 6
You are designing a data warehouse with two fact tables. The first table contains sales per month and the second table contains orders per day. 
Referential integrity must be enforced declaratively. 
You need to design a solution that can join a single time dimension to both fact tables. 
What should you do?
  1. Create a time mapping table.
  2. Change the level of granularity in both fact tables to be the same.
  3. Merge the fact tables.
  4. Create a view on the sales table.
Correct answer: B
Explanation:
Microsoft SQL Server Analysis Services, a time dimension is a dimension type whose attributes represent time periods, such as years, semesters, quarters, months, and days. The periods in a time dimension provide time-based levels of granularity for analysis and reporting. The attributes are organized in hierarchies, and the granularity of the time dimension is determined largely by the business and reporting requirements for historical data References: https://docs.microsoft.com/en-us/sql/analysis-services/multidimensional-models/database-dimensions-create-a-date-type-dimension
Microsoft SQL Server Analysis Services, a time dimension is a dimension type whose attributes represent time periods, such as years, semesters, quarters, months, and days. The periods in a time dimension provide time-based levels of granularity for analysis and reporting. The attributes are organized in hierarchies, and the granularity of the time dimension is determined largely by the business and reporting requirements for historical data 
References: https://docs.microsoft.com/en-us/sql/analysis-services/multidimensional-models/database-dimensions-create-a-date-type-dimension
Question 7
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?
  1. 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.
  2. 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.
  3. 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.
  4. Create two tables, dimSoftware and dimSoftwareCategory. Connect factSales to dimSoftware and factTarget to dimSoftwareCategory with foreign key constraints. Direct the cube developer to use key granularity attributes.
Correct answer: C
Question 8
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?
  1. Add a district column to the dimUser table.
  2. Partition the factSales table on the district column.
  3. Create a userDistrict table that contains primary key columns from the dimUser and dimDistrict tables.
  4. For each district, create a view of the factSales table that includes a WHERE clause for the district.
Correct answer: C
Question 9
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?
  1. Add StartDate and EndDate columns to the customer dimension.
  2. Add an IsCurrent column to the customer dimension.
  3. Enable Snapshot Isolation on the data warehouse.
  4. Add CurrentValue and PreviousValue columns to the customer dimension.
Correct answer: A
Explanation:
Adding a start and end date will give you this ability as when a record is inserted and given a start and end date, you’ll have the ability to determine when they were active therefore giving you a retention of historical changes
Adding a start and end date will give you this ability as when a record is inserted and given a start and end date, you’ll have the ability to determine when they were active therefore giving you a retention of historical changes
Question 10
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?
  1. Create one columnstore index that contains [ID], [Close], [High], [Low], [Volume], and [QuoteDate].
  2. Create three columnstore indexes:One containing [QuoteDate] and [Close]One containing [QuoteDate], [High], and [Low]One containing [QuoteDate] and [Volume]
  3. Create one columnstore index that contains [QuoteDate], [Close], [High], [Low], and [Volume].
  4. Create two columnstore indexes:One containing [ID], [QuoteDate], [Volume], and [Close]One containing [ID], [QuoteDate], [High], and [Low]
Correct answer: C
Explanation:
References: http://msdn.microsoft.com/en-us/library/gg492088.aspxhttp://msdn.microsoft.com/en-us/library/gg492153.aspx
References: http://msdn.microsoft.com/en-us/library/gg492088.aspx
http://msdn.microsoft.com/en-us/library/gg492153.aspx
HOW TO OPEN VCE FILES

Use VCE Exam Simulator to open VCE files
Avanaset

HOW TO OPEN VCEX AND EXAM FILES

Use ProfExam Simulator to open VCEX and EXAM files
ProfExam Screen

ProfExam
ProfExam at a 20% markdown

You have the opportunity to purchase ProfExam at a 20% reduced price

Get Now!