Talend Talend Core Developer Practice Exams
Last updated on Oct 21,2026- Exam Code: Talend Core Developer
- Exam Name: Talend Core Certified Developer Exam
- Certification Provider: Talend
- Latest update: Oct 21,2026
Question #11
You are using a tRESTClient component to call a REST service.
Which advanced option should you use to convert the response from the server to the document type?
- A . Convert Response To XML Document
- B . Convert Response To JSON Document
- C . Convert Response To DOM Document
- D . Convert Response To HTML Document
Correct Answer: C
C
Explanation:
Comprehensive and Detailed
In Talend Studio, the tRESTClient component includes an advanced setting called "Convert Response To DOM Document". When this option is selected, the response from the REST service is converted into a DOM (Document Object Model) document. This allows for structured processing of the response data within Talend workflows.
Reference: Talend Components Documentation
C
Explanation:
Comprehensive and Detailed
In Talend Studio, the tRESTClient component includes an advanced setting called "Convert Response To DOM Document". When this option is selected, the response from the REST service is converted into a DOM (Document Object Model) document. This allows for structured processing of the response data within Talend workflows.
Reference: Talend Components Documentation
Question #12
You are building a Job to run outsode Talend Studio that must run on both Linux and Windows.
Which action should you take when building the Job?
- A . Select Build Job because Jobs are runnable on all platforms
- B . Specify All for the Shell launcher option in the Build Job windows.
- C . Configure the Job properties building the Job.
- D . Build one package for each platform.
Correct Answer: B
B
Explanation:
To build a job to run outside Talend Studio that must run on both Linux and Windows, you need to select Build Job because jobs are runnable on all platforms. The Build Job option allows you to export your job as an executable file that can be run independently from Talend Studio on any platform that supports Java. You can access this option by right-clicking on your job in the Repository tree view and selecting Build Job. This will open a dialog box where you can configure the build settings, such as destination folder, archive name, context, etc.
You do not need to specify All for the Shell launcher option in the Build Job window, configure the job
properties before building the job, or build one package for each platform. These methods are not necessary or available in Talend Studio and may cause errors or unexpected results.
Reference: Talend Open Studio: Open-source ETL and Free Data Integration | Talend, [Build Job – 7.3]
B
Explanation:
To build a job to run outside Talend Studio that must run on both Linux and Windows, you need to select Build Job because jobs are runnable on all platforms. The Build Job option allows you to export your job as an executable file that can be run independently from Talend Studio on any platform that supports Java. You can access this option by right-clicking on your job in the Repository tree view and selecting Build Job. This will open a dialog box where you can configure the build settings, such as destination folder, archive name, context, etc.
You do not need to specify All for the Shell launcher option in the Build Job window, configure the job
properties before building the job, or build one package for each platform. These methods are not necessary or available in Talend Studio and may cause errors or unexpected results.
Reference: Talend Open Studio: Open-source ETL and Free Data Integration | Talend, [Build Job – 7.3]
Question #13
After enabling the Observability Metric Collector metric generation located in the etcorg.talend.ipaas.rt.observability.cfg, which additional configurations should you apply? Choose 2 answers.
- A . Schedule the metrics generation using CRON based trigger
- B . Configure the time zone
- C . Frequency
- D . Lifetime
Correct Answer: C, D
C, D
Explanation:
Comprehensive and Detailed
After enabling the Observability Metric Collector in Talend’s configuration file (org.talend.ipaas.rt.observability.cfg), it’s essential to set additional parameters to control the behavior of metric collection:
Frequency (Option C): Determines how often metrics are collected. Setting this ensures that data is gathered at appropriate intervals for monitoring needs.
Lifetime (Option D): Specifies how long the collected metrics are retained. This helps manage storage and ensures that outdated metrics are purged.
Configuring these parameters ensures that the metric collection aligns with organizational requirements for monitoring and performance analysis.
Reference: Talend Observability Configuration Guide
C, D
Explanation:
Comprehensive and Detailed
After enabling the Observability Metric Collector in Talend’s configuration file (org.talend.ipaas.rt.observability.cfg), it’s essential to set additional parameters to control the behavior of metric collection:
Frequency (Option C): Determines how often metrics are collected. Setting this ensures that data is gathered at appropriate intervals for monitoring needs.
Lifetime (Option D): Specifies how long the collected metrics are retained. This helps manage storage and ensures that outdated metrics are purged.
Configuring these parameters ensures that the metric collection aligns with organizational requirements for monitoring and performance analysis.
Reference: Talend Observability Configuration Guide
Question #14
What are the key capabilities of Talend Cloud Data Preparation that improve data quality and accessibility?
Choose 2 answers
- A . Standardize data
- B . Cleanse data
- C . Transform
- D . Discover
Correct Answer: A, B
A, B
Explanation:
A, B
Explanation:
Question #15
You have a MySQL table named customers with columns named id, name, address, and country. You need to retrieve records that have a specific country based on a variable.
Which steps should you use to achieve this?
- A . Use a tDBInput component with a context variable in the SQL query.
- B . Use a tDBInput component and link it to a tMatchGroup component.
- C . Use a tDBInput component with a Run if trigger.
- D . Use a tDBInput component and link it to a tFilterColumns component.
Correct Answer: A
A
Explanation:
Comprehensive and Detailed
To filter records based on a specific country dynamically, the best approach is using a tDBInput component with a context variable in the SQL query (Option A).
Step-by-Step Process:
Define a Context Variable:
In the Context Variables section of Talend Studio, create a new variable (context.country) and set its value dynamically.
Configure tDBInput:
Drag and drop the tDBInput component onto the Designer.
Set up the database connection using either Built-in or Repository mode.
In the Query field, write:
SELECT id, name, address, country FROM customers WHERE country = ‘" + context.country + "’
Execute the Job:
The Job will retrieve only those records where the country column matches the value of the context variable.
The value of context.country can be modified at runtime, making the query dynamic.
Why not other options?
tMatchGroup (Option B): Used for record deduplication, not filtering.
Run if Trigger (Option C): Controls execution flow but does not filter records inside tDBInput.
tFilterColumns (Option D): Removes unwanted columns but does not filter records based on conditions.
Reference: Talend Database Components Guide, Talend SQL Query Optimization
A
Explanation:
Comprehensive and Detailed
To filter records based on a specific country dynamically, the best approach is using a tDBInput component with a context variable in the SQL query (Option A).
Step-by-Step Process:
Define a Context Variable:
In the Context Variables section of Talend Studio, create a new variable (context.country) and set its value dynamically.
Configure tDBInput:
Drag and drop the tDBInput component onto the Designer.
Set up the database connection using either Built-in or Repository mode.
In the Query field, write:
SELECT id, name, address, country FROM customers WHERE country = ‘" + context.country + "’
Execute the Job:
The Job will retrieve only those records where the country column matches the value of the context variable.
The value of context.country can be modified at runtime, making the query dynamic.
Why not other options?
tMatchGroup (Option B): Used for record deduplication, not filtering.
Run if Trigger (Option C): Controls execution flow but does not filter records inside tDBInput.
tFilterColumns (Option D): Removes unwanted columns but does not filter records based on conditions.
Reference: Talend Database Components Guide, Talend SQL Query Optimization
Question #16
You need to call a different Job within a Job you are developing.
Which mechanism allows you to pass the parameters to the lob you want to call?
- A . Context parameters
- B . File
- C . CommandLine options
- D . Java Function paramters
Correct Answer: A
A
Explanation:
To call a different job within a job you are developing, you can use the tRunJob component. This component allows you to execute another job as a subjob within a parent job. To pass the parameters to the job you want to call, you can use the context parameters. Context parameters are variables that can store values that can be changed at runtime or between different contexts. You can define context parameters in the Contexts tab of your job and assign them values for each context. You can also pass context parameters from the parent job to the child job by using the Context Param tab of the tRunJob component. This way, you can parameterize the properties or expressions of the child job with the values from the parent job.
You do not need to use a file, command line options, or Java function parameters to pass parameters to a different job. These methods are not supported by Talend Studio and may cause errors or unexpected results.
Reference: Talend Open Studio: Open-source ETL and Free Data Integration | Talend, [tRunJob properties – 7.3], [Contexts – 7.3]
A
Explanation:
To call a different job within a job you are developing, you can use the tRunJob component. This component allows you to execute another job as a subjob within a parent job. To pass the parameters to the job you want to call, you can use the context parameters. Context parameters are variables that can store values that can be changed at runtime or between different contexts. You can define context parameters in the Contexts tab of your job and assign them values for each context. You can also pass context parameters from the parent job to the child job by using the Context Param tab of the tRunJob component. This way, you can parameterize the properties or expressions of the child job with the values from the parent job.
You do not need to use a file, command line options, or Java function parameters to pass parameters to a different job. These methods are not supported by Talend Studio and may cause errors or unexpected results.
Reference: Talend Open Studio: Open-source ETL and Free Data Integration | Talend, [tRunJob properties – 7.3], [Contexts – 7.3]
Question #17
You created a Job to process a customer database. Next, you want to debug the Job using Traces
Debug and pause the execution when it encounters any records for customers residing in the state of California.
- A . Add a breakpoint in the Advanced Settings tab of the Run view.
- B . Open the Debug Run tab of the Run view and click Traces Debug.
- C . Right-click the trace on the output of the input component and select Add Breakpoint.
- D . Right-click the trace on the output of the input component and select Show Breakpoint Setup.
Correct Answer: D
D
Explanation:
To debug a job using Trace Debug mode and pause the execution when it encounters any records for customers residing in the state of California, you need to right-click on the trace on the output of the input component and select Show Breakpoint Setup option. Trace Debug mode is a feature that allows you to trace each row processed by your job components and see the values of each column in each row. You can access this mode by opening the Debug Run tab of the Run view and clicking on Trace Debug button. A trace is a link that shows the data flow between components in your job design workspace.
The Show Breakpoint Setup option allows you to set a breakpoint on a trace based on a condition or an expression. A breakpoint is a point where the execution of your job pauses and waits for your action. You can use breakpoints to inspect your data or debug your logic at specific points of your job execution. You can access this option by right-clicking on a trace on your job design workspace and selecting Show Breakpoint Setup. This will open a dialog box where you can enter a condition or an expression for your breakpoint.
For example, if you want to pause your job execution when it encounters any records for customers residing in the state of California, you can enter this condition for your breakpoint:
row1.state == “CA”
This will make your job stop at the trace where this condition is met and show you the values of each column for that row.
You do not need to add a breakpoint in Advanced settings tab of Run view, open Debug Run tab of Run view and click Trace Debug button, or right-click on trace on output of input component and select Add Breakpoint option. These options are not used to set breakpoints based on conditions or expressions. The Advanced settings tab of Run view is used to configure advanced settings for your job execution, such as JVM arguments, statistics parameters, implicit context load parameters, etc. The Debug Run tab of Run view is used to access Trace Debug mode, but not to set breakpoints. The Add Breakpoint option is used to add a simple breakpoint on a trace without any condition or expression.
Reference: Talend Open Studio: Open-source ETL and Free Data Integration | Talend, [Trace Debug mode – 7.3], [Breakpoints – 7.3]
D
Explanation:
To debug a job using Trace Debug mode and pause the execution when it encounters any records for customers residing in the state of California, you need to right-click on the trace on the output of the input component and select Show Breakpoint Setup option. Trace Debug mode is a feature that allows you to trace each row processed by your job components and see the values of each column in each row. You can access this mode by opening the Debug Run tab of the Run view and clicking on Trace Debug button. A trace is a link that shows the data flow between components in your job design workspace.
The Show Breakpoint Setup option allows you to set a breakpoint on a trace based on a condition or an expression. A breakpoint is a point where the execution of your job pauses and waits for your action. You can use breakpoints to inspect your data or debug your logic at specific points of your job execution. You can access this option by right-clicking on a trace on your job design workspace and selecting Show Breakpoint Setup. This will open a dialog box where you can enter a condition or an expression for your breakpoint.
For example, if you want to pause your job execution when it encounters any records for customers residing in the state of California, you can enter this condition for your breakpoint:
row1.state == “CA”
This will make your job stop at the trace where this condition is met and show you the values of each column for that row.
You do not need to add a breakpoint in Advanced settings tab of Run view, open Debug Run tab of Run view and click Trace Debug button, or right-click on trace on output of input component and select Add Breakpoint option. These options are not used to set breakpoints based on conditions or expressions. The Advanced settings tab of Run view is used to configure advanced settings for your job execution, such as JVM arguments, statistics parameters, implicit context load parameters, etc. The Debug Run tab of Run view is used to access Trace Debug mode, but not to set breakpoints. The Add Breakpoint option is used to add a simple breakpoint on a trace without any condition or expression.
Reference: Talend Open Studio: Open-source ETL and Free Data Integration | Talend, [Trace Debug mode – 7.3], [Breakpoints – 7.3]
Question #18
A colleague has exported a Data Integration Job to run outside Talend Studio.
How do you run the Job?
- A . Extract the contents of the archive and run the batch file and shell script.
- B . Extract the content of the archive and run the batch file or the shell script.
- C . Install the Job and start the resulting service.
- D . Extract the files from the archive and run the JAR file.
Correct Answer: B
B
Explanation:
To run a job that has been exported by a colleague to run outside Talend Studio, you need to extract the content of the archive and run the batch file or the shell script. The archive file contains all the files and libraries required to run the job independently from Talend Studio on any platform that supports Java. The archive file also contains two executable files: a batch file (.bat) for Windows platforms and a shell script (.sh) for Linux platforms. You need to run the appropriate file for your platform by double-clicking on it or using a command line tool. This will launch the job and display its output in a console window.
You do not need to extract the contents of the archive and run both the batch file and shell script, install the job and start the resulting service, or extract the files from the archive and run the JAR file. These methods are not correct or available in Talend Studio and may cause errors or unexpected results.
Reference: Talend Open Studio: Open-source ETL and Free Data Integration | Talend, [Build Job – 7.3]
B
Explanation:
To run a job that has been exported by a colleague to run outside Talend Studio, you need to extract the content of the archive and run the batch file or the shell script. The archive file contains all the files and libraries required to run the job independently from Talend Studio on any platform that supports Java. The archive file also contains two executable files: a batch file (.bat) for Windows platforms and a shell script (.sh) for Linux platforms. You need to run the appropriate file for your platform by double-clicking on it or using a command line tool. This will launch the job and display its output in a console window.
You do not need to extract the contents of the archive and run both the batch file and shell script, install the job and start the resulting service, or extract the files from the archive and run the JAR file. These methods are not correct or available in Talend Studio and may cause errors or unexpected results.
Reference: Talend Open Studio: Open-source ETL and Free Data Integration | Talend, [Build Job – 7.3]
Question #19
Which actions can you perform in the configuration panel in Pipeline Designer? Choose 2 answers.
- A . Modify processor values.
- B . Display and update dataset connections.
- C . Preview changes made by processors.
- D . Select the settings for a pipeline export.
Correct Answer: A, B
A, B
Explanation:
Comprehensive and Detailed
In Talend Pipeline Designer, the configuration panel provides options for managing and modifying the settings of components within a pipeline.
Modify processor values (Option A):
Users can adjust values for processors such as filters, joins, transformations, and aggregations within the configuration panel.
This helps fine-tune data processing rules directly in the pipeline.
Display and update dataset connections (Option B):
The configuration panel allows users to change dataset connections, updating the source or target locations of data.
Users can modify database credentials, file paths, or API endpoints as needed.
Why not other options?
Option C: The ability to preview changes made by processors is handled in the preview panel, not the configuration panel.
Option D: Pipeline export settings are managed separately in the export settings menu, not in the configuration panel.
Reference: Talend Pipeline Designer User Guide
A, B
Explanation:
Comprehensive and Detailed
In Talend Pipeline Designer, the configuration panel provides options for managing and modifying the settings of components within a pipeline.
Modify processor values (Option A):
Users can adjust values for processors such as filters, joins, transformations, and aggregations within the configuration panel.
This helps fine-tune data processing rules directly in the pipeline.
Display and update dataset connections (Option B):
The configuration panel allows users to change dataset connections, updating the source or target locations of data.
Users can modify database credentials, file paths, or API endpoints as needed.
Why not other options?
Option C: The ability to preview changes made by processors is handled in the preview panel, not the configuration panel.
Option D: Pipeline export settings are managed separately in the export settings menu, not in the configuration panel.
Reference: Talend Pipeline Designer User Guide
Question #20
You implemented a Job in Talend Studio and need to execute it in Talend Cloud.
Which options can you use in Talend Management Console after publishing the Job to Talend Cloud? Choose 2 answers.
- A . Add a task and then run the task.
- B . Click the artifact name and then run the Job.
- C . Select the corresponding task, configure the task, and then run the task.
- D . Select the artifact name, add and configure a task, then run the task.
Correct Answer: A, D
A, D
Explanation:
Comprehensive and Detailed
After publishing a Job from Talend Studio to Talend Cloud, you can execute it using the Talend Management Console (TMC) by following these steps:
Add a task and then run the task (Option A):
In TMC, navigate to the Management section and select Tasks.
Click on Add Task, choose the published artifact (your Job), configure necessary parameters, and save the task.
Once the task is created, you can run it manually or schedule it for execution.
Select the artifact name, add and configure a task, then run the task (Option D):
In TMC, go to the Artifacts section to view your published Jobs.
Select the desired artifact and click on Add Task.
Configure the task settings as needed and save it.
After creating the task, you can execute it immediately or set up a schedule.
Why not other options?
Option B: TMC does not support directly running a Job by clicking on the artifact name without first creating a task.
Option C: While you can select and configure an existing task, the initial step requires creating the task associated with the artifact.
Reference: Talend Management Console User Guide
A, D
Explanation:
Comprehensive and Detailed
After publishing a Job from Talend Studio to Talend Cloud, you can execute it using the Talend Management Console (TMC) by following these steps:
Add a task and then run the task (Option A):
In TMC, navigate to the Management section and select Tasks.
Click on Add Task, choose the published artifact (your Job), configure necessary parameters, and save the task.
Once the task is created, you can run it manually or schedule it for execution.
Select the artifact name, add and configure a task, then run the task (Option D):
In TMC, go to the Artifacts section to view your published Jobs.
Select the desired artifact and click on Add Task.
Configure the task settings as needed and save it.
After creating the task, you can execute it immediately or set up a schedule.
Why not other options?
Option B: TMC does not support directly running a Job by clicking on the artifact name without first creating a task.
Option C: While you can select and configure an existing task, the initial step requires creating the task associated with the artifact.
Reference: Talend Management Console User Guide