TALEND-CORE-DEVELOPER practice question 8 of 15

You are building a complex Job and want to explore different options for optimizing execution times using parallelism. How can you identify execution times to verify the effectiveness of your changes? Choose 2 answers

Full set: 55 questions
Answer options
A: Observing the execution time in the Code view.
B: Heading the time stamps from the execution console in the Run view. Correct answer
C: Comparing time stamp in Trace Debug mode.
D: Observing the execution times that annotate the flows in the Designer. Correct answer
Correct Answer:
B. Heading the time stamps from the execution console in the Run view.; D. Observing the execution times that annotate the flows in the Designer.
Explanation

To measure the impact of parallelization you must activate statistics when you run the Job.
• The Run view console then prints start/end time-stamps for each component, letting you read total run time (B).
• When statistics are on, Talend Studio overlays every connection in the Designer with execution metrics (rows, duration, rows/s), so you can visually compare times between successive runs (D).

Why Incorrect

A. Code view only shows the generated Java; it contains no runtime metrics or timestamps.
C. Trace Debug streams data row-by-row for functional debugging; it does not summarise or compare execution durations needed for performance tuning.

References

1. Talend Studio User Guide 8.0

“Viewing statistics of your Job”

section 12.2.1

pp. 657-659 – explains how Run console displays timestamps.

2. Talend Studio User Guide 8.0

“Displaying execution statistics on connections”

section 12.2.2

pp. 660-662 – describes duration and throughput annotations in Designer.

Scroll to Top