Courseiva
Question 362 of 760
Develop data processinghardMultiple ChoiceObjective-mapped

Optimize Azure Synapse Data Flow Performance

You are designing a data processing pipeline in Azure Synapse Analytics that uses a mapping data flow with Azure Integration Runtime (IR). The pipeline runs slowly and you notice that the IR's data movement is limited by the number of cores. Which configuration should you adjust to improve performance?

Quick Answer

The answer is to increase the 'Data Flow Compute Type' and 'Core Count' in the Azure IR settings. This is correct because mapping data flows in Azure Synapse run on a Spark cluster managed by the Azure Integration Runtime, and when data movement is bottlenecked by limited cores, scaling up the compute resources directly boosts parallel processing throughput. On the DP-203 exam, this scenario tests your understanding of how to optimize Azure Synapse data flow performance by tuning the IR’s compute profile, often appearing as a performance troubleshooting question where candidates mistakenly adjust TTL or batch size instead of core count. A common trap is confusing the IR’s general data movement limits with the dedicated Spark compute settings for data flows. Remember the memory tip: “More cores, more flow” — when your pipeline crawls, check the IR’s core count first.

⚠ Common exam trap

Test-takers frequently confuse the 'Number of partitions' setting (which controls data parallelism within the flow) with the Azure IR's core count (which controls the Spark cluster's overall compute capacity), leading them to pick D instead of B.

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

Increase the 'Data Flow Compute Type' and 'Core Count' in the Azure IR settings.

The Azure Integration Runtime (IR) for mapping data flows uses a Spark cluster, and its performance is directly tied to the compute resources allocated. By increasing the 'Data Flow Compute Type' (e.g., from General Purpose to Memory Optimized) and the 'Core Count' (e.g., from 4 to 8 or 16 cores), you provide more parallel processing power, which directly addresses the core-limited data movement bottleneck.

Answer analysis

Option-by-option breakdown

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

  • Enable staging for the copy activity within the data flow.

    Why it's wrong here

    Staging is for copy activities, not for improving data flow performance.

  • Increase the 'Data Flow Compute Type' and 'Core Count' in the Azure IR settings.

    Why this is correct

    These settings directly allocate more resources to mapping data flows.

  • Use a Self-Hosted IR instead of Azure IR for data flows.

    Why it's wrong here

    Self-Hosted IR is for on-premises data, not for increasing performance.

  • Increase the 'Number of partitions' in the source transformation.

    Why it's wrong here

    Partitioning helps parallelism but still limited by IR cores.

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

Same concept, more angles

1 more way this is tested on DP-203

These questions test the same concept from different angles. Work through them to make sure you can recognise it however the exam phrases it.

Variation 1. You are monitoring an Azure Synapse Analytics pipeline that runs daily. The pipeline uses a data flow to transform data. You notice that the data flow is slow and consumes a lot of compute resources. Which action can you take to optimize performance?

easy
  • A.Use a staging table to load data before transformation
  • B.Increase the batch size in the data flow
  • C.Use PolyBase to load data into the dedicated SQL pool
  • D.Partition the data flow by a key column

Why D: Partitioning the data flow by a key column (Option D) enables parallel processing across multiple compute nodes, reducing data shuffling and improving throughput. In Azure Synapse data flows, partitioning distributes the workload evenly, which directly addresses the slow performance and high resource consumption observed in the pipeline.

Last reviewed: Jun 24, 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.