You have an Azure Synapse Analytics dedicated SQL pool named Pool1 and a database named DB1. DB1 contains a fact table named Table.You need to identify the extent of the data skew in Table1.What should you do in Synapse Studio?
Answer(s): A
First connect to Pool1, not the built-in serverless pool, then use sys.dm_pdw_nodes_db_partition_stats to analyze any skewness in the data.
https://docs.microsoft.com/en-us/azure/synapse-analytics/sql-data-warehouse/cheat-sheet
You have an Azure Synapse Analytics dedicated SQL pool.You run PDW_SHOWSPACEUSED('dbo.FactInternetSales'); and get the results shown in the following table.Which statement accurately describes the dbo.FactInternetSales table?
Answer(s): D
The rows per distribution can vary up to 10% without a noticeable impact on performance. Here the distribution varies more than 10%. It is skewed.Note: SHOWSPACEUSED displays the number of rows, disk space reserved, and disk space used for a specific table, or for all tables in a Azure Synapse Analytics or Parallel Data Warehouse database.This is a very quick and simple way to see the number of table rows that are stored in each of the 60 distributions of your database. Remember that for the most balanced performance, the rows in your distributed table should be spread evenly across all the distributions.ROUND_ROBIN distributed tables should not be skewed. Data is distributed evenly across the nodes by design.
https://docs.microsoft.com/en-us/azure/synapse-analytics/sql-data-warehouse/sql-data-warehouse-tables- distribute https://github.com/rgl/azure-content/blob/master/articles/sql-data-warehouse/sql-data-warehouse-manage- distributed-data-skew.md
DRAG DROP (Drag and Drop is not supported)You have an Azure SQL managed instance named SQLMI1 that has Resource Governor enabled and is used by two apps named App1 and App2.You need to configure SQLMI1 to limit the CPU and memory resources that can be allocated to App1.Which four actions should you perform in sequence? To answer, move the appropriate actions from the list of actions to the answer area and arrange them in the correct order.Select and Place:
https://docs.microsoft.com/en-us/sql/relational-databases/resource-governor/resource-governor?view=sql- server-ver15https://docs.microsoft.com/en-us/sql/relational-databases/resource-governor/create-and-test-a-classifier-user- defined-function?view=sql-server-ver15
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 SQL Server 2019 on an Azure virtual machine.You are troubleshooting performance issues for a query in a SQL Server instance.To gather more information, you query sys.dm_exec_requests and discover that the wait type is PAGELATCH_UP and the wait_resource is 2:3:905856.You need to improve system performance.Solution: You shrink the transaction log file.Does this meet the goal?
Answer(s): B
You should instead reduce the use of table variables and temporary tables.Or you could create additional tempdb files.Note: The following operations use tempdb extensively:* Repetitive create-and-drop operation of temporary tables (local or global).* Table variables that use tempdb for storage.* Etc.
https://docs.microsoft.com/en-US/troubleshoot/sql/performance/recommendations-reduce-allocation- contention
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 SQL Server 2019 on an Azure virtual machine.You are troubleshooting performance issues for a query in a SQL Server instance.To gather more information, you query sys.dm_exec_requests and discover that the wait type is PAGELATCH_UP and the wait_resource is 2:3:905856.You need to improve system performance.Solution: You change the data file for the master database to autogrow by 10 percent.Does this meet the goal?
You should instead reduce the use of table variables and temporary tables.Or you could create additional tempdb filesNote: The following operations use tempdb extensively:* Repetitive create-and-drop operation of temporary tables (local or global).* Table variables that use tempdb for storage.* Etc.
Post your Comments and Discuss Microsoft DP-300 exam prep with other Community members:
Our website is free, but we have to fight against AI bots and content theft. We're sorry for the inconvenience caused by these security measures. You can access the rest of the DP-300 content, but please register or login to continue.