SalesSQLDb1 experiences performance issues that are likely due to out-of-date statistics and

frequent blocking queries.

A: Use sys.dm_pdw_nodes_tran_locks instead of sys.dm_tran_locks from Azure Synapse Analytics

(SQL Data Warehouse) or Parallel Data Warehouse

E: Example:

The following query will show blocking information.

SELECT

t1.resource_type,

t1.resource_database_id,

t1.resource_associated_entity

_id, t1.request_mode,

t1.request_session_id,

t2.blocking_session_id

FROM sys.dm_tran_locks as t1

INNER JOIN sys.dm_os_waiting_tasks as t2

ON t1.lock_owner_address = t2.resource_address

Note: Depending on the system you’re working with you can access these wait statistics from one of

three locations:

sys.dm_os_wait_stats: for SQL Server
sys.dm_db_wait_stats: for Azure SQL Database
sys.dm_pdw_nodes_os_wait_stats: for Azure SQL Data Warehouse
F: sys.dm_tran_locks returns information about currently active lock manager resources in SQL
Server 2019 (15.x). Each row represents a currently active request to the lock manager for a lock that
has been granted or is waiting to be granted.
Instead use sys.dm_pdw_nodes_tran_locks.

Incorrect Answers:

Scenario: Business Requirements

Litware identifies business requirements include: meet an SLA of 99.99% availability for all Azure

deployments.

Box 1: Cloud witness

If you have a Failover Cluster deployment, where all nodes can reach the internet (by extension of

Azure), it is recommended that you configure a Cloud Witness as your quorum witness resource.

Box 2: Azure Basic Load Balancer

Microsoft guarantees that a Load Balanced Endpoint using Azure Standard Load Balancer, serving two

or more Healthy Virtual Machine Instances, will be available 99.99% of the time.

Note: There are two main options for setting up your listener: external (public) or internal. The
external (public) listener uses an internet facing load balancer and is associated with a public Virtual
IP (VIP) that is accessible over the internet. An internal listener uses an internal load balancer and
only supports clients within the same Virtual Network.

Box 1: The server, the elastic pool, and the database
Senario:
SalesSQLDb1 is in an elastic pool named SalesSQLDb1Pool.
Litware technical requirements include: 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
Box 2: Azure Event hubs
Scenario: Migrate ManufacturingSQLDb1 to the Azure virtual machine platform.
Event hubs are able to handle custom metrics.
Incorrect Answers:
Azure Log Analytics
Azure metric and log data are sent to Azure Monitor Logs, previously known as Azure Log Analytics,
directly by Azure. Azure SQL Analytics is a cloud only monitoring solution supporting streaming of
diagnostics telemetry for all of your Azure SQL databases.
However, because Azure SQL Analytics does not use agents to connect to Azure Monitor, it does not
support monitoring of SQL Server hosted on-premises or in virtual machines.

Scenario: Authenticate database users by using Active Directory credentials.
Which three 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.
The configuration steps include the following procedures to configure and use Azure Active Directory
authentication. Create and populate Azure AD.
Optional: Associate or change the active directory that is currently associated with your Azure
Subscription.
Create an Azure Active Directory administrator. (Step 1)
Configure your client computers.
Create contained database users in your database mapped to Azure AD identities. (Step 2)
Connect to your database by using Azure AD identities. (Step 3)