How to Analyze Deadlock Graphs in Azure SQL Database
Your Azure SQL Database is experiencing deadlocks. You have enabled deadlock graphs in the extended events session. After capturing a deadlock, you need to analyze it to determine which queries are involved. What should you use?
Quick Answer
The answer is to open the deadlock graph file (.xdl) in SQL Server Management Studio (SSMS). SSMS renders the deadlock graph as a visual diagram showing the two competing processes, the resources they hold or request, and the SQL statements involved, making it straightforward to analyze deadlock graphs in Azure SQL Database. On the Microsoft Azure Database Administrator Associate DP-300 exam, this question tests your understanding of deadlock capture tools—extended events collect the raw .xdl file, but only SSMS can display the graphic layout. A common trap is confusing deadlock graphs with dynamic management views like sys.dm_exec_requests, which show current blocking but not historical deadlock details. Remember the memory tip: "XDL = eXecute DeadLock visualization in SSMS."
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Open the deadlock graph file in SQL Server Management Studio (SSMS).
To analyze a deadlock graph captured via extended events, you should open the .xdl file in SQL Server Management Studio (SSMS), which provides a graphical representation of the deadlock, showing the processes involved, the resources, and the queries. Option B is correct. Option A is incorrect because sys.dm_exec_requests with a blocking filter shows current blocking, not historical deadlock details. Option C is incorrect because Azure Monitor for SQL provides metrics but not the detailed deadlock graph. Option D is incorrect because Query Store tracks query performance over time but does not capture deadlock events or graphs.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Query sys.dm_exec_requests with a filter on blocking.
Why it's wrong here
Shows current blocking, not past deadlocks.
- ✓
Open the deadlock graph file in SQL Server Management Studio (SSMS).
Why this is correct
SSMS can display deadlock graphs captured via extended events.
- ✗
Azure Monitor for SQL and view deadlock metrics.
Why it's wrong here
Azure Monitor for SQL shows deadlock count but not the graph.
- ✗
Query Store and review the regressed queries.
Why it's wrong here
Query Store does not capture deadlock events.
Go deeper
Related to this question
Learn chapter
Overview of Azure Data Platform Options
Key term
Azure SQL Performance Tuning
Azure SQL Performance Tuning is the process of optimizing the speed and efficiency of queries and database operations in Microsoft Azure SQL Database or SQL Managed Instance to reduce latency and improve throughput.
Key term
Query Store
Query Store is a built-in SQL Server feature that captures and stores a history of query execution plans and performance data for easy monitoring and troubleshooting.
About these practice questions
Courseiva writes every DP-300 question from scratch — 906 in total, each with an explanation and a wrong-answer breakdown. None are copied from real exams or dumps. Learn why practice questions differ from exam dumps →
Same concept, more angles
1 more way this is tested on DP-300
These questions test the same concept from different angles. Work through them to make sure you can recognise it however the exam phrases it.
Variation 1. Your SQL Server is experiencing deadlocks. You enable trace flag 1222 to capture deadlock graphs in the error log. Where can you retrieve the deadlock information?
medium- A.sys.dm_exec_sessions
- B.sys.query_store_query_text
- C.sys.dm_exec_requests
- ✓ D.The SQL Server error log, viewable using sp_readerrorlog.
Why D: Trace flag 1222 writes deadlock information to the SQL Server error log. This log can be read using sp_readerrorlog, xp_readerrorlog, or the Log File Viewer in SQL Server Management Studio. Option D refers to this error log, though retrieving it via sp_readerrorlog is the direct method; the original mention of sys.messages and sys.fn_get_audit_file is incorrect and replaced.
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
This DP-300 practice question is part of Courseiva's free Microsoft certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the DP-300 exam.