Identifying Data Write Duration in Synapse Mapping Data Flows
Short answer
B the sink processing time
Question
Key Takeaways
The question tests knowledge of mapping data flow execution metrics; the trap is confusing total pipeline time or transformation time with the specific sink write latency.
To measure the time taken to write data to a destination like Azure Synapse Dedicated SQL Pool, use the Sink Processing Time metric. Community consensus confirms this is the definitive metric for I/O and write operation duration.
Common mistake: Selecting 'transformation processing time' (C), which measures CPU-intensive transformations before data reaches the final destination, not the actual write operation.
Expert Analysis
Why the Answer Is Correct
The Sink Processing Time metric specifically captures the duration required to commit data to the target system. In Azure Synapse mapping data flows, the sink is the final stage where data exits the flow engine into the destination store, such as Pool1.
Why the Other Options Are Wrong
Rows written (A) is a count metric, not a temporal one. Transformation processing time (C) measures the time spent on operations like joins or aggregations within the flow, excluding the final write. Post-processing time (D) typically refers to cleanup or metadata operations after the main write, which is negligible compared to the actual I/O write time.
Community Comment Notes
Comment [1] clarifies that Sink Processing Time includes both transformation time and I/O time for that specific sink component, making it the comprehensive measure for the write phase. Comments [2] and [3] reinforce that 'sink' equals 'destination', directly linking the metric to the write operation against Pool1.
Exam Strategy
When asked about writing to a database or file system in data flows, immediately look for 'Sink' related metrics. Distinguish between data movement (sink) and data manipulation (transformations).
Community Votes
100% of anonymous learners picked answer B. Votes are pick records left by other test-takers — they are not the verified answer.
Discussion 4 contributions
Compiled from public community threads and reader submissions, lightly edited for clarity. Handles and vote tallies are shown as recorded, and comments reflect the views of individual contributors.
From public community threads 4
-
jongert 👍 4Correct: Each transformation stage includes a total time for that stage to complete with each partition execution time totaled together. When you select the Sink, you see "Sink Processing Time". This time includes the total of the transformation time plus the I/O time it took to write your data to your destination store. The difference between the Sink Processing Time and the total of the transformation is the I/O time to write the data. https://learn.microsoft.com/en-us/azure/data-factory/concepts-data-flow-monitoring#total-sink-processing-time-vs-transformation-processing-time
-
evangelist 👍 2 Answered BSink processing time: This metric measures the time taken to write the data to the sink, which in this case is Pool1. It directly answers the question about how long the write operation takes.
-
imatheushenrique 👍 2 Answered BB. the sink processing time the sink represents the final destination where data is written. Sink processing time measures how long it takes to write the data to the destination (Pool1).
-
efeee333 👍 1 Answered Bcorrect
Reader comments & corrections
No reader corrections yet — spotted an error or have a note? Share it below.