The answer is to add additional TempDB data files equal to the number of vCores, which is 16. This directly addresses PAGELATCH_EX contention in TempDB for Azure SQL Database, a bottleneck caused by many concurrent transactions fighting over the same allocation pages—like PFS, GAM, and SGAM—within a single data file. By adding multiple data files, each file gets its own set of allocation structures, distributing the write load and dramatically reducing page latch waits. On the DP-300 exam, this scenario tests your understanding of TempDB configuration best practices for high-concurrency, Business Critical workloads; a common trap is to add too few files or to increase file size instead. Remember the memory tip: “Match your vCores to your TempDB files for high-concurrency piles.”
DP-300 Practice Question: Monitor, configure, and optimize database resources
This DP-300 practice question tests your understanding of monitor, configure, and optimize database resources. This is a configuration task: choose the command set that satisfies every stated requirement. Small differences — like 'secret' vs 'password' or 'transport input ssh' vs 'all' — change whether the answer is correct. After answering, compare your reasoning against the explanation and wrong-answer breakdown below. Once you have made your selection, read the full explanation to reinforce the concept and understand why each distractor is designed to mislead on exam day.
You are the database administrator for an Azure SQL Database used by a financial trading application. The database is in the Business Critical service tier with 16 vCores. The application executes thousands of small, high-frequency transactions per second. Recently, the application's response time has increased, and you observe high PAGELATCH_EX waits in sys.dm_os_waiting_tasks. The database is 500 GB with a single data file (tempdb.mdf) and a single log file (tempdb_log.ldf). TempDB is configured with the default settings. You need to reduce PAGELATCH_EX contention in TempDB. What should you do?
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Add additional TempDB data files equal to the number of vCores (16).
PAGELATCH_EX contention in TempDB is typically caused by allocation page contention when many concurrent transactions compete for the same system page (e.g., PFS, GAM, SGAM). In Azure SQL Database Business Critical tier, adding multiple TempDB data files equal to the number of vCores (16) reduces contention by distributing allocations across files, each with its own allocation structures. This is a proven best practice for high-concurrency workloads like financial trading applications.
Key principle: Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
✓
Add additional TempDB data files equal to the number of vCores (16).
Why this is correct
Multiple data files reduce allocation contention on SGAM and PFS pages, which cause PAGELATCH_EX waits.
Related concept
Read the scenario before looking for a memorised answer.
✗
Move TempDB to Azure Premium Storage for better IO latency.
Why it's wrong here
Premium Storage improves IO but does not address page latch contention caused by concurrent allocations.
✗
Increase the database service tier to 24 vCores.
Why it's wrong here
More vCores may increase concurrency and worsen contention without addressing the root cause.
✗
Increase the initial size of the TempDB data file to 100 GB.
Why it's wrong here
Increasing file size does not reduce contention; it only reduces file growth events.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates often confuse PAGELATCH_EX (allocation page contention) with PAGEIOLATCH_EX (IO-related waits) and incorrectly choose storage or tier upgrades instead of the file-count solution.
Detailed technical explanation
How to think about this question
TempDB uses PFS (Page Free Space), GAM (Global Allocation Map), and SGAM (Shared Global Allocation Map) pages to track space usage. With a single data file, every concurrent transaction must serialize access to these pages, causing PAGELATCH_EX waits. Adding multiple data files (ideally 1:1 with vCores) creates separate allocation structures per file, allowing parallel allocations and dramatically reducing contention. In Azure SQL Database, the Business Critical tier uses local SSD storage, so IO latency is already low; the fix is purely structural.
KKey Concepts to Remember
Read the scenario before looking for a memorised answer.
Find the constraint that changes the correct option.
Eliminate answers that are true in general but not in this case.
TExam Day Tips
→Watch for words such as best, first, most likely and least administrative effort.
→Review why wrong options are wrong, not only why the correct option is correct.
Key takeaway
Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Real-world example
How this comes up in practice
A media company stores terabytes of video archives that are accessed once a year for audit purposes. Moving these objects to a cold storage tier (Azure Archive, S3 Glacier, or Google Nearline) costs a fraction of hot storage. Questions like this test whether you understand storage tiers, access frequency tradeoffs, and retrieval latency requirements.
Related glossary terms
Concepts from this question explained
These glossary pages explain the core terms tested in this DP-300 question in full detail.
Monitor, configure, and optimize database resources — This question tests Monitor, configure, and optimize database resources — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: Add additional TempDB data files equal to the number of vCores (16). — PAGELATCH_EX contention in TempDB is typically caused by allocation page contention when many concurrent transactions compete for the same system page (e.g., PFS, GAM, SGAM). In Azure SQL Database Business Critical tier, adding multiple TempDB data files equal to the number of vCores (16) reduces contention by distributing allocations across files, each with its own allocation structures. This is a proven best practice for high-concurrency workloads like financial trading applications.
What should I do if I get this DP-300 question wrong?
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
What is the key concept behind this question?
Read the scenario before looking for a memorised answer.
About these practice questions
Courseiva creates original exam-style practice questions with explanations and wrong-answer analysis. It does not publish real exam questions, exam dumps, or protected exam content. Learn why practice questions differ from exam dumps →
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
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.
Question Discussion
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
Sign in to join the discussion.