nerdexam
Microsoft

DP-300 · Question #1

Case Study 1 - Litware, Inc Overview Litware, Inc. is a renewable energy company that has a main office in Boston. The main office hosts a sales department and the primary datacenter for the…

The correct answer is C. sys.dm_exec_requests F. sys.dm_tran_locks. SalesSQLDb1 experiences performance issues that are likely due to out-of-date statistics and frequent blocking queries. Seeing a Count of All Active SQL Server Wait Types. Sometimes we're trying to diagnose a problem and we want to know if we're seeing a large number of wait…

Submitted by hassan_iq· Mar 6, 2026Incident & Event Response

Question

Case Study 1 - Litware, Inc Overview Litware, Inc. is a renewable energy company that has a main office in Boston. The main office hosts a sales department and the primary datacenter for the company. Physical Locations Existing Environment Litware has a manufacturing office and a research office is separate locations near Boston. Each office has its own datacenter and internet connection. The manufacturing and research datacenters connect to the primary datacenter by using a VPN. Network Environment The primary datacenter has an ExpressRoute connection that uses both Microsoft peering and private peering. The private peering connects to an Azure virtual network named HubVNet. Identity Environment Litware has a hybrid Azure Active Directory (Azure AD) deployment that uses a domain named litwareinc.com. All Azure subscriptions are associated to the litwareinc.com Azure AD tenant. Database Environment The sales department has the following database workload: An on-premises named SERVER1 hosts an instance of Microsoft SQL Server 2012 and two 1- TB databases. A logical server named SalesSrv01A contains a geo-replicated Azure SQL database named SalesSQLDb1. SalesSQLDb1 is in an elastic pool named SalesSQLDb1Pool. SalesSQLDb1 uses database firewall rules and contained database users. An application named SalesSQLDb1App1 uses SalesSQLDb1. The manufacturing office contains two on-premises SQL Server 2016 servers named SERVER2 and SERVER3. The servers are nodes in the same Always On availability group. The availability group contains a database named ManufacturingSQLDb1 Database administrators have two Azure virtual machines in HubVnet named VM1 and VM2 that run Windows Server 2019 and are used to manage all the Azure databases. Licensing Agreement Litware is a Microsoft Volume Licensing customer that has License Mobility through Software Assurance. Current Problems SalesSQLDb1 experiences performance issues that are likely due to out-of-date statistics and frequent blocking queries. Requirements Planned Changes Litware plans to implement the following changes: Implement 30 new databases in Azure, which will be used by time-sensitive manufacturing apps that have varying usage patterns. Each database will be approximately 20 GB. Create a new Azure SQL database named ResearchDB1 on a logical server named ResearchSrv01. ResearchDB1 will contain Personally Identifiable Information (PII) data. Develop an app named ResearchApp1 that will be used by the research department to populate and access ResearchDB1. Migrate ManufacturingSQLDb1 to the Azure virtual machine platform. Migrate the SERVER1 databases to the Azure SQL Database platform. Technical Requirements Litware identifies the following technical requirements: Maintenance tasks must be automated. The 30 new databases must scale automatically. The use of an on-premises infrastructure must be minimized. Azure Hybrid Use Benefits must be leveraged for Azure SQL Database deployments. All SQL Server and Azure SQL Database metrics related to CPU and storage usage and limits must be analyzed by using Azure built-in functionality. Security and Compliance Requirements Litware identifies the following security and compliance requirements: Store encryption keys in Azure Key Vault. Retain backups of the PII data for two months. Encrypt the PII data at rest, in transit, and in use. Use the principle of least privilege whenever possible. Authenticate database users by using Active Directory credentials. Protect Azure SQL Database instances by using database-level firewall rules. Ensure that all databases hosted in Azure are accessible from VM1 and VM2 without relying on public endpoints. Business Requirements Litware identifies the following business requirements: Meet an SLA of 99.99% availability for all Azure deployments. Minimize downtime during the migration of the SERVER1 databases. Use the Azure Hybrid Use Benefits when migrating workloads to Azure. Once all requirements are met, minimize costs whenever possible. You need to identify the cause of the performance issues on SalesSQLDb1. Which two dynamic management views should you use? Each correct answer presents part of the solution. NOTE: Each correct selection is worth one point.

Options

  • Asys.dm_pdw_nodes_tran_locks
  • Bsys.dm_exec_compute_node_errors
  • Csys.dm_exec_requests
  • Dsys.dm_cdc_errors
  • Esys.dm_pdw_nodes_os_wait_stats
  • Fsys.dm_tran_locks

How the community answered

(43 responses)
  • A
    5% (2)
  • B
    5% (2)
  • C
    56% (24)
  • D
    23% (10)
  • E
    12% (5)

Explanation

SalesSQLDb1 experiences performance issues that are likely due to out-of-date statistics and frequent blocking queries. Seeing a Count of All Active SQL Server Wait Types. Sometimes we're trying to diagnose a problem and we want to know if we're seeing a large number of wait types occurring. We can do this using sys.dm_exec_requests because the current wait type being experienced is presented. Therefore, if we filter out any background or sleeping tasks, we can get a picture of what the waits are for active requests and we can also see if we have a problem. Here's the query: SELECT COALESCE(wait_type, 'None') AS wait_type, COUNT(*) AS Total FROM sys.dm_exec_requests - WHERE NOT status IN ('Background', 'Sleeping') GROUP BY wait_type ORDER BY Total DESC; Here is an example of the query output: We see that we have two LCK_M_S wait types. This is the wait type we get when we have requests waiting on obtaining a shared lock. We can then query along with sys.dm_tran_locks to determine what types of locks these active requests were trying to obtain: SELECT L.request_session_id, L.resource_type,L.resource_subtype, L.request_mode, FROM sys.dm_tran_locks AS L JOIN sys.dm_exec_requests AS DER ON L.request_session_id = DER.session_id WHERE DER.wait_type = 'LCK_M_S'; Not A: Azure SQL database does not have sys.dm_pdw_nodes_tran_locks. Not E: Azure SQL database does not have sys.dm_pdw_nodes_os_wait_stats. sysdmexecrequests/

Community Discussion

No community discussion yet for this question.

Sign up to join the discussion
Full DP-300 Practice