DP-300 Practice Question: Monitor, configure, and optimize database resources
You are managing an Azure SQL Database that uses the Business Critical service tier. You need to ensure that the database can handle a sudden increase in transaction log write throughput without experiencing log write waits. Which factor should you primarily consider?
⚠ Common exam trap
The trap here is assuming that database size or read replicas affect log write throughput, when in fact it is solely determined by vCore count in Business Critical.
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
✓
The number of vCores allocated to the database.
In the Business Critical service tier, the maximum transaction log write throughput is directly proportional to the number of vCores allocated to the database. To handle increased log write throughput, you should scale up the number of vCores. Other factors such as database size, read replicas, and backup storage redundancy do not affect the log write rate limit.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
The configured backup storage redundancy.
Why it's wrong here
Backup storage redundancy options (e.g., locally redundant, zone-redundant) affect durability and availability of backups, but they do not impact the transaction log write throughput. The log write rate is a function of the compute resources, not the backup storage configuration.
- ✓
The number of vCores allocated to the database.
Why this is correct
In the Business Critical tier, the transaction log write throughput is primarily determined by the number of vCores. Each vCore provides a certain log write rate, and the total log throughput scales linearly with the number of vCores. Therefore, increasing vCores directly increases the maximum log write rate.
- ✗
The number of read replicas configured.
Why it's wrong here
Read replicas in Business Critical are used for read scale-out and do not influence the transaction log write throughput of the primary. The log write rate is determined by the primary's compute resources. Adding read replicas does not increase the primary's log write capacity.
- ✗
The size of the database in gigabytes.
Why it's wrong here
Database size does not directly affect the maximum transaction log write throughput. In Business Critical, log throughput is tied to compute resources, not storage size. While larger databases may have more transactions, the log rate limit is independent of the allocated storage size.
Go deeper
Related to this question
Learn chapter
Managing Environment Configurations and Resource Governance
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.
About these practice questions
Courseiva writes every DP-300 question from scratch — 574 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 →
JA
Written and reviewed by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
Last reviewed September 2026 · checked against the official Microsoft exam blueprint
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.