Courseiva

DP-203 Practice Question: Secure, monitor, and optimize data storage and data processing

You need to monitor the performance of an Azure Data Factory pipeline that copies data from an on-premises SQL Server to Azure Blob Storage. The pipeline runs on a self-hosted integration runtime. Which metric is most important to monitor to ensure the self-hosted IR is not a bottleneck?

⚠ Common exam trap

DP-203 often tests the distinction between pipeline-level metrics (duration, data read/written) and IR-specific metrics (queue depth, CPU); candidates may pick duration as a proxy for IR performance.

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

✓

Queue depth for the self-hosted IR

The self-hosted integration runtime (IR) queue depth metric indicates the number of activities waiting to be processed by the IR. A consistently high or increasing queue depth signals that the IR cannot keep up with the workload, making it a bottleneck. Monitoring this metric allows proactive scaling or optimization.

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

  • ✗

    Pipeline duration metric

    Why it's wrong here

    Pipeline duration is an end-to-end outcome affected by source, network and sink, so it cannot isolate the self-hosted IR as the constraint. It is tempting because slow runs prompt investigation, and would be the right metric when reporting overall SLA performance rather than attributing delay to integration runtime resources.

  • ✓

    Queue depth for the self-hosted IR

    Why this is correct

    Queue depth measures pending requests awaiting a free self-hosted integration runtime node, so a rising value directly signals the IR cannot keep pace with copy activity demand. This exposes the bottleneck constraint, whereas CPU or memory alone may not reflect queued work.

  • ✗

    Number of active connections to the IR

    Why it's wrong here

    Active connection counts reflect concurrent sessions, not the self-hosted IR node's CPU, memory or queue saturation that actually causes a bottleneck. They are tempting because connection limits matter for gateway throughput, and would be the correct metric when diagnosing connectivity exhaustion rather than runtime resource pressure.

  • ✗

    Data read and data written metrics for the pipeline

    Why it's wrong here

    Data read and written metrics describe throughput volume, not whether the self-hosted IR's CPU, memory or concurrent-job capacity is saturated. They are tempting because they reveal pipeline load, and would be the right choice when sizing source or sink throughput rather than diagnosing integration runtime resource contention.

Quick reference

Azure Blob Storage Tier Comparison

TierStorage CostRetrieval CostLatencyUse Case
HotHighestLowestImmediateActive data, frequent reads
CoolLowerHigherImmediateData accessed < once / month
ColdLower stillHigherImmediateData accessed < once / quarter
ArchiveLowestHighest + rehydration delayHoursLong-term compliance retention

Go deeper

Related to this question

About these practice questions

This DP-203 question is part of Courseiva's 509-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam dumps. Learn why practice questions differ from exam dumps →

How Courseiva writes practice questions · Editorial policy

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-203 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-203 exam.