Download Microsoft.70-767.PrepAway.2019-07-20.68q.vcex

Download Exam

File Info

Exam Implementing a SQL Data Warehouse
Number 70-767
File Name Microsoft.70-767.PrepAway.2019-07-20.68q.vcex
Size 2 MB
Posted Jul 20, 2019
Download Microsoft.70-767.PrepAway.2019-07-20.68q.vcex

How to open VCEX & EXAM Files?

Files with VCEX & EXAM extensions can be opened by ProfExam Simulator.

Download
ProfExam Simulator

Purchase

Coupon: MASTEREXAM
With discount: 20%





Demo Questions

Question 1

Note: This question is part of a series of questions that present the same scenario. Each question in the series contains a unique solution that might meet the stated goals. Some question sets might have more than one correct solution, while others might not have a correct solution. 
After you answer a question in this section, you will NOT be able to return to it. As a result, these questions will not appear in the review screen. 
You have a data warehouse that stores information about products, sales, and orders for a manufacturing company. The instance contains a database that has two tables named SalesOrderHeader and SalesOrderDetail. SalesOrderHeader has 500,000 rows and SalesOrderDetail has 3,000,000 rows. 
Users report performance degradation when they run the following stored procedure:
  
  
You need to optimize performance. 
Solution: You run the following Transact-SQL statement:
  
  
Does the solution meet the goal?


  1. Yes
  2. No
Correct answer: B
Explanation:
Microsoft recommend against specifying 0 PERCENT or 0 ROWS in a CREATE STATISTICS..WITH SAMPLE statement. When 0 PERCENT or ROWS is specified, the statistics object is created but does not contain statistics data. References: https://docs.microsoft.com/en-us/sql/t-sql/statements/create-statistics-transact-sql
Microsoft recommend against specifying 0 PERCENT or 0 ROWS in a CREATE STATISTICS..WITH SAMPLE statement. When 0 PERCENT or ROWS is specified, the statistics object is created but does not contain statistics data. 
References: https://docs.microsoft.com/en-us/sql/t-sql/statements/create-statistics-transact-sql



Question 2

Note: This question is part of a series of questions that present the same scenario. Each question in the series contains a unique solution that might meet the stated goals. Some question sets might have more than one correct solution, while others might not have a correct solution. 
After you answer a question in this section, you will NOT be able to return to it. As a result, these questions will not appear in the review screen. 
You have the following line-of-business solutions:
  • ERP system 
  • Online WebStore 
  • Partner extranet 
One or more Microsoft SQL Server instances support each solution. Each solution has its own product catalog. You have an additional server that hosts SQL Server Integration Services (SSIS) and a data warehouse. You populate the data warehouse with data from each of the line-of-business solutions. The data warehouse does not store primary key values from the individual source tables. 
The database for each solution has a table named Products that stored product information. The Products table in each database uses a separate and unique key for product records. Each table shares a column named ReferenceNr between the databases. This column is used to create queries that involve more than once solution. 
You need to load data from the individual solutions into the data warehouse nightly. The following requirements must be met:
  • If a change is made to the ReferenceNr column in any of the sources, set the value of IsDisabled to True and create a new row in the Products table. 
  • If a row is deleted in any of the sources, set the value of IsDisabled to True in the data warehouse. 
Solution: Perform the following actions:
  • Enable the Change Tracking for the Product table in the source databases. 
  • Query the CHANGETABLE function from the sources for the updated rows. 
  • Set the IsDisabled column to True for the listed rows that have the old ReferenceNr value. 
  • Create a new row in the data warehouse Products table with the new ReferenceNr value. 
Does the solution meet the goal?


  1. Yes
  2. No
Correct answer: B
Explanation:
We must check for deleted rows, not just updates rows. References: https://www.timmitchell.net/post/2016/01/18/getting-started-with-change-tracking-in-sql-server/
We must check for deleted rows, not just updates rows. 
References: https://www.timmitchell.net/post/2016/01/18/getting-started-with-change-tracking-in-sql-server/



Question 3

Note: This question is part of a series of questions that present the same scenario. Each question in the series contains a unique solution that might meet the stated goals. Some question sets might have more than one correct solution, while others might not have a correct solution. 
After you answer a question in this section, you will NOT be able to return to it. As a result, these questions will not appear in the review screen. 
You have the following line-of-business solutions:
  • ERP system 
  • Online WebStore 
  • Partner extranet 
One or more Microsoft SQL Server instances support each solution. Each solution has its own product catalog. You have an additional server that hosts SQL Server Integration Services (SSIS) and a data warehouse. You populate the data warehouse with data from each of the line-of-business solutions. The data warehouse does not store primary key values from the individual source tables. 
The database for each solution has a table named Products that stored product information. The Products table in each database uses a separate and unique key for product records. Each table shares a column named ReferenceNr between the databases. This column is used to create queries that involve more than once solution. 
You need to load data from the individual solutions into the data warehouse nightly. The following requirements must be met:
  • If a change is made to the ReferenceNr column in any of the sources, set the value of IsDisabled to True and create a new row in the Products table. 
  • If a row is deleted in any of the sources, set the value of IsDisabled to True in the data warehouse. 
Solution: Perform the following actions:
  • Enable the Change Tracking feature for the Products table in the three source databases. 
  • Query the CHANGETABLE function from the sources for the deleted rows. 
  • Set the IsDIsabled column to True on the data warehouse Products table for the listed rows. 
Does the solution meet the goal?


  1. Yes
  2. No
Correct answer: B
Explanation:
We must check for updated rows, not just deleted rows. References: https://www.timmitchell.net/post/2016/01/18/getting-started-with-change-tracking-in-sql-server/
We must check for updated rows, not just deleted rows. 
References: https://www.timmitchell.net/post/2016/01/18/getting-started-with-change-tracking-in-sql-server/



Question 4

Note: This question is part of a series of questions that present the same scenario. Each question in the series contains a unique solution that might meet the stated goals. Some question sets might have more than one correct solution, while others might not have a correct solution. 
After you answer a question in this section, you will NOT be able to return to it. As a result, these questions will not appear in the review screen. 
You have the following line-of-business solutions:
  • ERP system 
  • Online WebStore 
  • Partner extranet 
One or more Microsoft SQL Server instances support each solution. Each solution has its own product catalog. You have an additional server that hosts SQL Server Integration Services (SSIS) and a data warehouse. You populate the data warehouse with data from each of the line-of-business solutions. The data warehouse does not store primary key values from the individual source tables. 
The database for each solution has a table named Products that stored product information. The Products table in each database uses a separate and unique key for product records. Each table shares a column named ReferenceNr between the databases. This column is used to create queries that involve more than once solution. 
You need to load data from the individual solutions into the data warehouse nightly. The following requirements must be met:
  • If a change is made to the ReferenceNr column in any of the sources, set the value of IsDisabled to True and create a new row in the Products table. 
  • If a row is deleted in any of the sources, set the value of IsDisabled to True in the data warehouse. 
Solution: Perform the following actions:
  • Enable the Change Tracking for the Product table in the source databases. 
  • Query the cdc.fn_cdc_get_all_changes_capture_dbo_products function from the sources for updated rows. 
  • Set the IsDisabled column to True for rows with the old ReferenceNr value. 
  • Create a new row in the data warehouse Products table with the new ReferenceNr value. 
Does the solution meet the goal?


  1. Yes
  2. No
Correct answer: B
Explanation:
We must also handle the deleted rows, not just the updated rows. References: https://solutioncenter.apexsql.com/enable-use-sql-server-change-data-capture/
We must also handle the deleted rows, not just the updated rows. 
References: https://solutioncenter.apexsql.com/enable-use-sql-server-change-data-capture/



Question 5

Note: This question is part of a series of questions that present the same scenario. Each question in the series contains a unique solution that might meet the stated goals. Some question sets might have more than one correct solution, while others might not have a correct solution. 
After you answer a question in this section, you will NOT be able to return to it. As a result, these questions will not appear in the review screen. 
You are developing a Microsoft SQL Server Integration Services (SSIS) projects. The project consists of several packages that load data warehouse tables. 
You need to extend the control flow design for each package to use the following control flow while minimizing development efforts and maintenance:
  
  
Solution: You add the control flow to a script task. You add an instance of the script task to the storage account in Microsoft Azure.
Does the solution meet the goal?


  1. Yes
  2. No
Correct answer: B
Explanation:
A package consists of a control flow and, optionally, one or more data flows. You create the control flow in a package by using the Control Flow tab in SSIS Designer. References: https://docs.microsoft.com/en-us/sql/integration-services/control-flow/control-flow
A package consists of a control flow and, optionally, one or more data flows. You create the control flow in a package by using the Control Flow tab in SSIS Designer. 
References: https://docs.microsoft.com/en-us/sql/integration-services/control-flow/control-flow



Question 6

Note: This question is part of a series of questions that present the same scenario. Each question in the series contains a unique solution that might meet the stated goals. Some question sets might have more than one correct solution, while others might not have a correct solution. 
After you answer a question in this section, you will NOT be able to return to it. As a result, these questions will not appear in the review screen. 
You are developing a Microsoft SQL Server Integration Services (SSIS) projects. The project consists of several packages that load data warehouse tables. 
You need to extend the control flow design for each package to use the following control flow while minimizing development efforts and maintenance:
  
  
Solution: You add the control flow to a control flow package part. You add an instance of the control flow package part to each data warehouse load package.
Does the solution meet the goal?


  1. Yes
  2. No
Correct answer: A
Explanation:
A package consists of a control flow and, optionally, one or more data flows. You create the control flow in a package by using the Control Flow tab in SSIS Designer. References: https://docs.microsoft.com/en-us/sql/integration-services/control-flow/control-flow
A package consists of a control flow and, optionally, one or more data flows. You create the control flow in a package by using the Control Flow tab in SSIS Designer. 
References: https://docs.microsoft.com/en-us/sql/integration-services/control-flow/control-flow



Question 7

Note: This question is part of a series of questions that use the same scenario. For your convenience, the scenario is repeated in each question. Each question presents a different goal and answer choices, but the text of the scenario is exactly the same in each question in this series. 
You have a Microsoft SQL Server data warehouse instance that supports several client applications. 
The data warehouse includes the following tables: Dimension.SalesTerritory, Dimension.Customer, Dimension.Date, Fact.Ticket, and Fact.Order. The Dimension.SalesTerritory and Dimension.Customer tables are frequently updated. The Fact.Order table is optimized for weekly reporting, but the company wants to change it to daily. The Fact.Order table is loaded by using an ETL process. Indexes have been added to the table over time, but the presence of these indexes slows data loading. 
All data in the data warehouse is stored on a shared SAN. All tables are in a database named DB1. You have a second database named DB2 that contains copies of production data for a development environment. The data warehouse has grown and the cost of storage has increased. Data older than one year is accessed infrequently and is considered historical. 
You have the following requirements:
  • Implement table partitioning to improve the manageability of the data warehouse and to avoid the need to repopulate all transactional data each night. Use a partitioning strategy that is as granular as possible. 
  • Partition the Fact.Order table and retain a total of seven years of data. 
  • Partition the Fact.Ticket table and retain seven years of data. At the end of each month, the partition structure must apply a sliding window strategy to ensure that a new partition is available for the upcoming month, and that the oldest month of data is archived and removed. 
  • Optimize data loading for the Dimension.SalesTerritory, Dimension.Customer, and Dimension.Date tables. 
  • Incrementally load all tables in the database and ensure that all incremental changes are processed. 
  • Maximize the performance during the data loading process for the Fact.Order partition. 
  • Ensure that historical data remains online and available for querying. 
  • Reduce ongoing storage costs while maintaining query performance for current data. 
You are not permitted to make changes to the client applications. 
You need to implement the data partitioning strategy. 
How should you partition the Fact.Order table? 


  1. Create 17,520 partitions.
  2. Use a granularity of two days.
  3. Create 2,557 partitions.
  4. Create 730 partitions.
Correct answer: C
Explanation:
We create on partition for each day, which means that a granularity of one day is used. 7 years times 365 days is 2,555. Make that 2,557 to provide for leap years. From scenario: Partition the Fact.Order table and retain a total of seven years of data.The Fact.Order table is optimized for weekly reporting, but the company wants to change it to daily. Maximize the performance during the data loading process for the Fact.Order partition. Reference: https://docs.microsoft.com/en-us/azure/sql-data-warehouse/sql-data-warehouse-tables-partition
We create on partition for each day, which means that a granularity of one day is used. 7 years times 365 days is 2,555. Make that 2,557 to provide for leap years. 
From scenario: Partition the Fact.Order table and retain a total of seven years of data.
The Fact.Order table is optimized for weekly reporting, but the company wants to change it to daily. 
Maximize the performance during the data loading process for the Fact.Order partition. 
Reference: https://docs.microsoft.com/en-us/azure/sql-data-warehouse/sql-data-warehouse-tables-partition



Question 8

Note: This question is part of a series of questions that use the same scenario. For your convenience, the scenario is repeated in each question. Each question presents a different goal and answer choices, but the text of the scenario is exactly the same in each question in this series. 
You have a Microsoft SQL Server data warehouse instance that supports several client applications. 
The data warehouse includes the following tables: Dimension.SalesTerritory, Dimension.Customer, Dimension.Date, Fact.Ticket, and Fact.Order. The Dimension.SalesTerritory and Dimension.Customer tables are frequently updated. The Fact.Order table is optimized for weekly reporting, but the company wants to change it to daily. The Fact.Order table is loaded by using an ETL process. Indexes have been added to the table over time, but the presence of these indexes slows data loading. 
All data in the data warehouse is stored on a shared SAN. All tables are in a database named DB1. You have a second database named DB2 that contains copies of production data for a development environment. The data warehouse has grown and the cost of storage has increased. Data older than one year is accessed infrequently and is considered historical. 
You have the following requirements:
  • Implement table partitioning to improve the manageability of the data warehouse and to avoid the need to repopulate all transactional data each night. Use a partitioning strategy that is as granular as possible. 
  • Partition the Fact.Order table and retain a total of seven years of data. 
  • Partition the Fact.Ticket table and retain seven years of data. At the end of each month, the partition structure must apply a sliding window strategy to ensure that a new partition is available for the upcoming month, and that the oldest month of data is archived and removed. 
  • Optimize data loading for the Dimension.SalesTerritory, Dimension.Customer, and Dimension.Date tables. 
  • Incrementally load all tables in the database and ensure that all incremental changes are processed. 
  • Maximize the performance during the data loading process for the Fact.Order partition. 
  • Ensure that historical data remains online and available for querying. 
  • Reduce ongoing storage costs while maintaining query performance for current data. 
You are not permitted to make changes to the client applications. 
You need to optimize the storage for the data warehouse. 
What change should you make?


  1. Partition the Fact.Order table, and move historical data to new filegroups on lower-cost storage.
  2. Create new tables on lower-cost storage, move the historical data to the new tables, and then shrink the database.
  3. Remove the historical data from the database to leave available space for new data.
  4. Move historical data to new tables on lower-cost storage.
  5. Implement row compression for the Fact.Order table.
  6. Move the index for the Fact.Order table to lower-cost storage.
Correct answer: A
Explanation:
Create the load staging table in the same filegroup as the partition you are loading. Create the unload staging table in the same filegroup as the partition you are deleting. From scenario: The data warehouse has grown and the cost of storage has increased. Data older than one year is accessed infrequently and is considered historical. References: https://blogs.msdn.microsoft.com/sqlcat/2013/09/16/top-10-best-practices-for-building-a-large-scale-relational-data-warehouse/
Create the load staging table in the same filegroup as the partition you are loading. 
Create the unload staging table in the same filegroup as the partition you are deleting. 
From scenario: The data warehouse has grown and the cost of storage has increased. Data older than one year is accessed infrequently and is considered historical. 
References: https://blogs.msdn.microsoft.com/sqlcat/2013/09/16/top-10-best-practices-for-building-a-large-scale-relational-data-warehouse/



Question 9

You deploy a Microsoft Azure SQL Data Warehouse instance. The instance must be available eight hours each day. 
You need to pause Azure resources when they are not in use to reduce costs. 
What will be the impact of pausing resources? To answer, select the appropriate options in the answer area. 
NOTE: Each correct selection is worth one point.


Correct answer: To work with this question, an Exam Simulator is required.
Explanation:
To save costs, you can pause and resume compute resources on-demand. For example, if you won't be using the database during the night and on weekends, you can pause it during those times, and resume it during the day. You won't be charged for DWUs while the database is paused. When you pause a database:Compute and memory resources are returned to the pool of available resources in the data center Data Warehouse Unit (DWU) costs are zero for the duration of the pause. Data storage is not affected and your data stays intact. SQL Data Warehouse cancels all running or queued operations. When you resume a database:SQL Data Warehouse acquires compute and memory resources for your DWU setting. Compute charges for your DWUs resume. Your data will be available. You will need to restart your workload queries. References: https://docs.microsoft.com/en-us/azure/sql-data-warehouse/sql-data-warehouse-manage-compute-rest-api
To save costs, you can pause and resume compute resources on-demand. For example, if you won't be using the database during the night and on weekends, you can pause it during those times, and resume it during the day. You won't be charged for DWUs while the database is paused. 
When you pause a database:
Compute and memory resources are returned to the pool of available resources in the data center 
Data Warehouse Unit (DWU) costs are zero for the duration of the pause. 
Data storage is not affected and your data stays intact. 
SQL Data Warehouse cancels all running or queued operations. 
When you resume a database:
SQL Data Warehouse acquires compute and memory resources for your DWU setting. 
Compute charges for your DWUs resume. 
Your data will be available. 
You will need to restart your workload queries. 
References: https://docs.microsoft.com/en-us/azure/sql-data-warehouse/sql-data-warehouse-manage-compute-rest-api



Question 10

Note: This question is part of a series of questions that use the same or similar answer choices. An answer choice may be correct for more than one question in the series. Each question is independent of the other questions in this series. Information and details provided in a question apply only to that question. 
You are a database administrator for an e-commerce company that runs an online store. The company has three databases as described in the following table. 
  
  
You plan to load at least one million rows of data each night from DB1 into the OnlineOrder table. You must load data into the correct partitions using a parallel process. 
You create 24 Data Flow tasks. You must place the tasks into a component to allow parallel load. After all of the load processes compete, the process must proceed to the next task. 
You need to load the data for the OnlineOrder table. 
What should you use?


  1. Lookup transformation
  2. Merge transformation
  3. Merge Join transformation
  4. MERGE statement
  5. Union All transformation
  6. Balanced Data Distributor transformation
  7. Sequential container
  8. Foreach Loop container
Correct answer: H
Explanation:
The Parallel Loop Task is an SSIS Control Flow task, which can execute multiple iterations of the standard Foreach Loop Container concurrently. References: http://www.cozyroc.com/ssis/parallel-loop-task
The Parallel Loop Task is an SSIS Control Flow task, which can execute multiple iterations of the standard Foreach Loop Container concurrently. 
References: http://www.cozyroc.com/ssis/parallel-loop-task









CONNECT US

Facebook

Twitter

PROFEXAM WITH A 20% DISCOUNT

You can buy ProfExam with a 20% discount!

Get Now!


HOW TO OPEN VCEX FILES

Use ProfExam Simulator to open VCEX files