DP-300 Practice Question: Monitor, configure, and optimize database resources
Your Azure SQL Database is configured with the Hyperscale service tier. You observe increased redo log latency. Which resource is most likely the bottleneck?
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
✓
Log service throughput
In Hyperscale, the log service is a separate component that handles redo; high latency there directly affects redo speed. Option A is wrong because compute node CPU affects query processing, not redo latency specifically. Option C is wrong because page servers handle data reads, not redo. Option D is wrong because storage IO is distributed and rarely the bottleneck for redo in Hyperscale.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Compute node CPU
Why it's wrong here
Compute node CPU executes queries; redo latency arises from log write throughput, not processor contention. It is tempting because CPU is the usual suspect for slow Azure SQL performance, and would be correct if the symptom were query execution time rather than log redo delay.
- ✓
Log service throughput
Why this is correct
Hyperscale offloads log processing to dedicated log service compute nodes, so redo log latency scales with log service throughput rather than primary compute. Increased redo latency therefore points to that log service throughput as the bottleneck.
- ✗
Page server IO
Why it's wrong here
Page servers serve data pages to compute nodes; they do not host the transaction log, so their IO cannot drive redo latency. It is tempting because page server IO is a genuine Hyperscale bottleneck, and would be the answer when read-intensive workloads show slow page fetches rather than delayed log writes.
- ✗
Remote storage IOPS
Why it's wrong here
Remote storage holds data pages, not the transaction log, so its IOPS do not govern redo latency. It is tempting because Hyperscale separates storage from compute, and would be correct when page reads or writes against remote storage are the observed slow operation.
Go deeper
Related to this question
Learn chapter
Implementing High Availability for Azure SQL Databases
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 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.