Question 840 of 846
Monitor and optimize data storage and processinghardMultiple SelectObjective-mapped

Quick Answer

The answer is Data Integration Unit (DIU) Consumption, Pipeline Succeeded Rerun Count, and Pipeline Failed Rerun Count. DIU Consumption is the primary metric for measuring the compute resources consumed during an activity, where a sustained high value relative to your pipeline’s baseline directly indicates a bottleneck in data movement or transformation throughput. Pipeline Succeeded Rerun Count and Pipeline Failed Rerun Count are critical because a high number of reruns—especially successful ones after failures—signals that the pipeline is repeatedly retrying due to throttling, resource contention, or transient errors, which degrades overall performance. On the DP-203 exam, this tests your ability to correlate Azure Monitor metrics with specific Data Factory performance issues; a common trap is focusing only on DIU Consumption while ignoring rerun counts, which reveal retry-induced latency. Remember the mnemonic “DIU for load, Reruns for pain”—DIU tells you how hard the system is working, while rerun metrics tell you where it’s failing and retrying, pinpointing the bottleneck.

DP-203 Practice Question: Monitor and optimize data storage and processing

This DP-203 practice question tests your understanding of monitor and optimize data storage and processing. The scenario asks you to isolate a root cause — eliminate options that address a different problem before choosing. 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.

Which THREE metrics from Azure Monitor should be used to diagnose performance bottlenecks in an Azure Data Factory pipeline?

Question 1hardmulti select
Full question →

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

Pipeline Succeeded Rerun Count

Pipeline Succeeded Rerun Count (A) is correct because a high number of reruns indicates that the pipeline is repeatedly failing and retrying, which directly points to a performance bottleneck such as resource contention or throttling. This metric helps identify pipelines that are not completing successfully on the first attempt, signaling underlying issues that degrade throughput.

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.

  • Pipeline Succeeded Rerun Count

    Why this is correct

    High rerun count indicates failures and potential bottlenecks.

    Related concept

    Read the scenario before looking for a memorised answer.

  • Blob Capacity

    Why it's wrong here

    Storage metric, not pipeline performance.

  • Activity Duration

    Why this is correct

    Directly measures execution time of each activity.

    Related concept

    Read the scenario before looking for a memorised answer.

  • SQL Pool DWU Used

    Why it's wrong here

    Metric for Synapse SQL pool, not ADF.

  • Data Integration Unit (DIU) Consumption

    Why this is correct

    Indicates if copy activity is resource constrained.

    Related concept

    Read the scenario before looking for a memorised answer.

Common exam traps

Common exam trap: answer the scenario, not the keyword

The trap here is that candidates often confuse storage-level metrics (like Blob Capacity) or data warehouse metrics (like DWU Used) with pipeline-specific performance indicators, but the question explicitly asks for metrics that diagnose bottlenecks in the pipeline execution itself, not in downstream storage or compute services.

Detailed technical explanation

How to think about this question

Activity Duration (C) measures the time taken for each individual activity within a pipeline, allowing you to pinpoint which specific step (e.g., Copy, Lookup, Stored Procedure) is causing the delay. Data Integration Unit (DIU) Consumption (E) reflects the compute resources allocated to a Copy activity; if DIU consumption is consistently low while data volumes are high, it suggests the source or sink is throttling the operation, limiting parallelism. Under the hood, Azure Monitor collects these metrics via the Azure Data Factory diagnostic settings, emitting them as platform metrics with a 1-minute granularity.

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.

What to study next

Got this wrong? Here's your next step.

Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.

Related practice questions

Related DP-203 practice-question pages

Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.

Practice this exam

Start a free DP-203 practice session

Short sessions build daily habit. Longer sessions build exam-day stamina. Try a timed session to simulate real conditions.

FAQ

Questions learners often ask

What does this DP-203 question test?

Monitor and optimize data storage and processing — This question tests Monitor and optimize data storage and processing — Read the scenario before looking for a memorised answer..

What is the correct answer to this question?

The correct answer is: Pipeline Succeeded Rerun Count — Pipeline Succeeded Rerun Count (A) is correct because a high number of reruns indicates that the pipeline is repeatedly failing and retrying, which directly points to a performance bottleneck such as resource contention or throttling. This metric helps identify pipelines that are not completing successfully on the first attempt, signaling underlying issues that degrade throughput.

What should I do if I get this DP-203 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 →

How Courseiva writes practice questions · Editorial policy

Last reviewed: Jun 11, 2026

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.

Loading comments…

Sign in to join the discussion.

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.