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 #41
You create a Job consisting of two subJobs, A and
B. You added Joblet C with the intension of running it between A and B.
What are the minimum requirements to orchestrate this? (Choose Two)
- A . Add TRIGGER_INPUT and TRIGGER_OUTPUT components into A.
- B . Link A, B and C using On Subject Ok triggers.
- C . Add TRIGGER_INPUT and TRIGGER_OUTPUT components into B.
- D . Add TRIGGER_INPUT and TRIGGER_OUTPUT components into C
Correct Answer: B, D
B, D
Explanation:
To create a job consisting of two subjobs, A and B, and add a Joblet C with the intention of running it between A and B, you need to do the following steps:
Design subjob A by adding components and links to it in the Designer workspace.
Add a Start component to mark the beginning of subjob B and link it to subjob A using an OnSubjobOk trigger.
Design subjob B by adding components and links to it after the Start component in the Designer workspace.
Add a tJobletTriggerInput component to your Joblet C design and link it to other components in your Joblet using data flows or triggers.
Add a tJobletTriggerOutput component to your Joblet C design and link it to other components in your Joblet using data flows or triggers.
Drag your Joblet C from the Repository tree view to the Designer workspace between subjob A and subjob B.
Link your Joblet C to subjob A using an OnComponentOk trigger from the last component of subjob A to the tJobletTriggerInput component of your Joblet C.
Link your Joblet C to subjob B using an OnComponentOk trigger from the tJobletTriggerOutput component of your Joblet C to the Start component of subjob B.
The minimum requirements to orchestrate this are adding TRIGGER_INPUT and TRIGGER_OUTPUT components into C and linking A, B, and C using OnSubjobOk triggers. These are generic components that allow you to define triggers for your Joblet without depending on specific components. You do not need to add TRIGGER_INPUT and TRIGGER_OUTPUT components into A or B, as these are regular subjobs that can use any type of components or triggers.
Reference: Talend Open Studio: Open-source ETL and Free Data Integration | Talend, [tJobletTriggerInput properties – 7.3], [tJobletTriggerOutput properties – 7.3], [Joblets – 7.3], [Triggers – 7.3]
B, D
Explanation:
To create a job consisting of two subjobs, A and B, and add a Joblet C with the intention of running it between A and B, you need to do the following steps:
Design subjob A by adding components and links to it in the Designer workspace.
Add a Start component to mark the beginning of subjob B and link it to subjob A using an OnSubjobOk trigger.
Design subjob B by adding components and links to it after the Start component in the Designer workspace.
Add a tJobletTriggerInput component to your Joblet C design and link it to other components in your Joblet using data flows or triggers.
Add a tJobletTriggerOutput component to your Joblet C design and link it to other components in your Joblet using data flows or triggers.
Drag your Joblet C from the Repository tree view to the Designer workspace between subjob A and subjob B.
Link your Joblet C to subjob A using an OnComponentOk trigger from the last component of subjob A to the tJobletTriggerInput component of your Joblet C.
Link your Joblet C to subjob B using an OnComponentOk trigger from the tJobletTriggerOutput component of your Joblet C to the Start component of subjob B.
The minimum requirements to orchestrate this are adding TRIGGER_INPUT and TRIGGER_OUTPUT components into C and linking A, B, and C using OnSubjobOk triggers. These are generic components that allow you to define triggers for your Joblet without depending on specific components. You do not need to add TRIGGER_INPUT and TRIGGER_OUTPUT components into A or B, as these are regular subjobs that can use any type of components or triggers.
Reference: Talend Open Studio: Open-source ETL and Free Data Integration | Talend, [tJobletTriggerInput properties – 7.3], [tJobletTriggerOutput properties – 7.3], [Joblets – 7.3], [Triggers – 7.3]
Question #42
You have two branches: Branch1 contains Job1, and Branch 2 contains Job 2. You want to copy Job1 to Branch 2 and preserve the change history when connecting Studio to Talend Administrator Center.
Which method should you use to preserve the change history?
- A . Switch to Branch 1, right-click Job 1, select Copy to branch, and select Branch 2.
- B . Switch to Branch 1, copy the Branch 1 job, switch to Branch 2, and paste the job into Branch 2.
- C . Switch to branch 1, copy the Branch 1 Job, switch to Branch 2, and paste the Job into Branch 2.
- D . Switch to Branch 1, copy lob 1, switch to Branch 2, and paste Job 1 over Job 2.
Correct Answer: A
A
Explanation:
To copy Job1 from Branch1 to Branch2 and preserve the change history when connecting Studio to Talend Administration Center, you need to use the Copy to branch option. This option allows you to copy a job or a folder from one branch to another branch in the same project without losing the version history. You can access this option by switching to Branch1, right-clicking on Job1 in the Repository tree view, and selecting Copy to branch. This will open a dialog box where you can select Branch2 as the target branch and confirm the copy operation.
You do not need to use the import items, create standard job, or paste over options. These options are not used to copy jobs between branches and preserve the change history. The import items option is used to import items (such as jobs, metadata, routines, etc.) from an archive file that can be exported from another project or workspace. The create standard job option is used to create a new job with a name and a description. The paste over option is used to overwrite an existing job with another job that has been copied or cut from the same or another project.
Reference: Talend Open Studio: Open-source ETL and Free Data Integration | Talend, [Copy to branch – 7.3]
A
Explanation:
To copy Job1 from Branch1 to Branch2 and preserve the change history when connecting Studio to Talend Administration Center, you need to use the Copy to branch option. This option allows you to copy a job or a folder from one branch to another branch in the same project without losing the version history. You can access this option by switching to Branch1, right-clicking on Job1 in the Repository tree view, and selecting Copy to branch. This will open a dialog box where you can select Branch2 as the target branch and confirm the copy operation.
You do not need to use the import items, create standard job, or paste over options. These options are not used to copy jobs between branches and preserve the change history. The import items option is used to import items (such as jobs, metadata, routines, etc.) from an archive file that can be exported from another project or workspace. The create standard job option is used to create a new job with a name and a description. The paste over option is used to overwrite an existing job with another job that has been copied or cut from the same or another project.
Reference: Talend Open Studio: Open-source ETL and Free Data Integration | Talend, [Copy to branch – 7.3]
Question #43
Which type of task can be added to a plan in Talend Management Console?
- A . Data services
- B . Big Data tasks
- C . Routes
- D . Jobs
Correct Answer: D
D
Explanation:
Comprehensive and Detailed
In Talend Management Console (TMC), a plan is a sequence of tasks executed in a defined order. The types of tasks that can be added to a plan include:
Jobs (Option D): Standard data integration tasks designed in Talend Studio.
Big Data tasks (Option B): Tasks involving big data processing.
Routes (Option C): Tasks related to messaging routes.
However, Data services (Option A) refer to web services and are not typically added as tasks within a plan.
Reference: Talend Management Console User Guide
D
Explanation:
Comprehensive and Detailed
In Talend Management Console (TMC), a plan is a sequence of tasks executed in a defined order. The types of tasks that can be added to a plan include:
Jobs (Option D): Standard data integration tasks designed in Talend Studio.
Big Data tasks (Option B): Tasks involving big data processing.
Routes (Option C): Tasks related to messaging routes.
However, Data services (Option A) refer to web services and are not typically added as tasks within a plan.
Reference: Talend Management Console User Guide
Question #44
How many sample dataset records and rows can be displayed in Talend Cloud Data Preparation?
- A . All the available records
- B . 10,000
- C . 1,000
- D . 5,000
Correct Answer: B
B
Explanation:
Comprehensive and Detailed
In Talend Cloud Data Preparation, the platform is designed to handle large datasets efficiently by displaying a sample of the data to the user. By default, Talend Cloud Data Preparation can display up to 10,000 records from a dataset. This sampling approach ensures that users can interact with and analyze their data without performance issues that might arise from loading an entire large dataset into memory. Users have the option to view the first 10,000 records (Head sample) or 10,000 randomly selected records (Random sample) to get a representative understanding of the dataset’s content.
Reference: Talend Cloud Data Inventory User Guide
B
Explanation:
Comprehensive and Detailed
In Talend Cloud Data Preparation, the platform is designed to handle large datasets efficiently by displaying a sample of the data to the user. By default, Talend Cloud Data Preparation can display up to 10,000 records from a dataset. This sampling approach ensures that users can interact with and analyze their data without performance issues that might arise from loading an entire large dataset into memory. Users have the option to view the first 10,000 records (Head sample) or 10,000 randomly selected records (Random sample) to get a representative understanding of the dataset’s content.
Reference: Talend Cloud Data Inventory User Guide
Question #45
Which component can be used to read a CSV file in an ESB Route?
- A . tFileInputDelimited
- B . cMap
- C . cFileInputDelimited
- D . cFile
- E . tMap
Correct Answer: C
C
Explanation:
Comprehensive and Detailed
In Talend’s Enterprise Service Bus (ESB) routes, the appropriate component to read a CSV file is cFileInputDelimited. This component is specifically designed for Camel routes to handle delimited files like CSVs.
Reference: Talend ESB Components Documentation
C
Explanation:
Comprehensive and Detailed
In Talend’s Enterprise Service Bus (ESB) routes, the appropriate component to read a CSV file is cFileInputDelimited. This component is specifically designed for Camel routes to handle delimited files like CSVs.
Reference: Talend ESB Components Documentation
Question #46
What are the key capabilities of Talend Cloud Data Preparation that improve data quality and accessibility? Choose 3 answers.
- A . Discover
- B . Format data
- C . Cleanse data
- D . Transform
- E . Standardize data
Correct Answer: C, D, E
C, D, E
Explanation:
Comprehensive and Detailed
Talend Cloud Data Preparation enhances data quality and accessibility through:
Cleanse data (Option C):
Identifying and correcting inaccuracies or inconsistencies to ensure data integrity.
Transform (Option D):
Modifying data structures or values to meet specific requirements or formats.
Standardize data (Option E):
Ensuring uniformity in data presentation and format, facilitating consistency across datasets.
Why not other options?
Option A: Discovery is typically associated with data profiling, not preparation.
Option B: Formatting is a subset of transformation and standardization processes.
Reference: Talend Cloud Data Preparation User Guide
C, D, E
Explanation:
Comprehensive and Detailed
Talend Cloud Data Preparation enhances data quality and accessibility through:
Cleanse data (Option C):
Identifying and correcting inaccuracies or inconsistencies to ensure data integrity.
Transform (Option D):
Modifying data structures or values to meet specific requirements or formats.
Standardize data (Option E):
Ensuring uniformity in data presentation and format, facilitating consistency across datasets.
Why not other options?
Option A: Discovery is typically associated with data profiling, not preparation.
Option B: Formatting is a subset of transformation and standardization processes.
Reference: Talend Cloud Data Preparation User Guide
Question #47
You need a list of all customers whose first name contains "Tom" and who are older than 18.
Which processor should be used?
- A . Join
- B . Aggregate
- C . Filter
- D . Data sampling
Correct Answer: C
C
Explanation:
Comprehensive and Detailed
To filter customer records based on first name containing "Tom" and age greater than 18, the Filter processor is the correct choice.
Filter (Option C) C Correct Answer
The Filter processor allows users to set conditional rules to extract only the required data.
Users can specify conditions such as:
first_name CONTAINS "Tom"
AND
age > 18
This ensures that only relevant records are included in the output.
Why not other options?
Option A (Join): Used to combine data from multiple datasets based on a key field, not for filtering.
Option B (Aggregate): Used for summarizing data, such as calculating counts, sums, or averages.
Option D (Data Sampling): Used to select a random subset of data, not for filtering based on conditions.
Reference: Talend Pipeline Designer User Guide
C
Explanation:
Comprehensive and Detailed
To filter customer records based on first name containing "Tom" and age greater than 18, the Filter processor is the correct choice.
Filter (Option C) C Correct Answer
The Filter processor allows users to set conditional rules to extract only the required data.
Users can specify conditions such as:
first_name CONTAINS "Tom"
AND
age > 18
This ensures that only relevant records are included in the output.
Why not other options?
Option A (Join): Used to combine data from multiple datasets based on a key field, not for filtering.
Option B (Aggregate): Used for summarizing data, such as calculating counts, sums, or averages.
Option D (Data Sampling): Used to select a random subset of data, not for filtering based on conditions.
Reference: Talend Pipeline Designer User Guide
Question #48
In Talend Studio, you have access to a references project named project_ref. You need to reuse a Job named testJob from the project_ref in your main Job.
- A . Right-click Job Designs and click import items.
- B . Navigate to Metadata, @ project ref, Job Designs, Standard, then select testJob.
- C . Right-click Job Designs, click Crete Standard Job, and enter testJob as the Job name.
- D . Navigate to @ Referenced project, @ project_ref, Job Designs, Standard, then select testJob.
Correct Answer: D
D
Explanation:
To reuse a job named testJob from a referenced project named project_ref in your main job, you need to navigate to @Referenced project, @project_ref, Job Designs, Standard, then select testJob. A referenced project is a project that can be accessed from another project in read-only mode. You can add a referenced project to your main project by using the Project Settings window in Talend Studio. You can then browse the items (such as jobs, metadata, routines, etc.) of the referenced project in the Repository tree view under the @Referenced project node. You can drag and drop any item from the referenced project to your main job design workspace.
You do not need to use import items, create standard job, or navigate to Metadata options. These options are not used to reuse jobs from referenced projects. The import items option is used to import items (such as jobs, metadata, routines, etc.) from an archive file that can be exported from another project or workspace. The create standard job option is used to create a new job with a name and a description. The Metadata node in the Repository tree view is used to store and manage metadata definitions for various data sources (such as databases, files, web services, etc.).
Reference: Talend Open Studio: Open-source ETL and Free Data Integration | Talend, [Referenced projects – 7.3]
D
Explanation:
To reuse a job named testJob from a referenced project named project_ref in your main job, you need to navigate to @Referenced project, @project_ref, Job Designs, Standard, then select testJob. A referenced project is a project that can be accessed from another project in read-only mode. You can add a referenced project to your main project by using the Project Settings window in Talend Studio. You can then browse the items (such as jobs, metadata, routines, etc.) of the referenced project in the Repository tree view under the @Referenced project node. You can drag and drop any item from the referenced project to your main job design workspace.
You do not need to use import items, create standard job, or navigate to Metadata options. These options are not used to reuse jobs from referenced projects. The import items option is used to import items (such as jobs, metadata, routines, etc.) from an archive file that can be exported from another project or workspace. The create standard job option is used to create a new job with a name and a description. The Metadata node in the Repository tree view is used to store and manage metadata definitions for various data sources (such as databases, files, web services, etc.).
Reference: Talend Open Studio: Open-source ETL and Free Data Integration | Talend, [Referenced projects – 7.3]
Question #49
Which options can you use to add a Joblet to your talend Job?
Choose 3 answers
- A . Use a tRunJob component and select the Joblet from the drop-down menu.
- B . Type the Joblet name on the Studio canvas, then select if from the Palette drop-down menu.
- C . Right-click the Joblet from Palette and select the Add option.
- D . Drag the Jobket from the Repository tree view to designer canvas.
- E . Drag the Joblet from Palette to the design workspace.
Correct Answer: B, D, E
B, D, E
Explanation:
To add a Joblet to your Talend Job, you can use one of these options:
Type the Joblet name on the Studio canvas, then select it from the Palette drop-down menu. This will create a Joblet container on your canvas that contains all the components and links of your Joblet.
Drag the Joblet from Repository tree view to designer canvas. This will also create a Joblet container on your canvas that contains all components and links of your Joblet.
Drag Joblet from Palette to design workspace. This will open a dialog box where you can select an existing Joblet from Repository or create a new one.
You cannot use a tRunJob component and select Joblet from drop-down menu, nor right-click Joblet from Palette and select Add option. These methods are not available in Talend Studio and may cause errors or unexpected results.
Reference: Talend Open Studio: Open-source ETL and Free Data Integration | Talend, [Joblets – 7.3]
B, D, E
Explanation:
To add a Joblet to your Talend Job, you can use one of these options:
Type the Joblet name on the Studio canvas, then select it from the Palette drop-down menu. This will create a Joblet container on your canvas that contains all the components and links of your Joblet.
Drag the Joblet from Repository tree view to designer canvas. This will also create a Joblet container on your canvas that contains all components and links of your Joblet.
Drag Joblet from Palette to design workspace. This will open a dialog box where you can select an existing Joblet from Repository or create a new one.
You cannot use a tRunJob component and select Joblet from drop-down menu, nor right-click Joblet from Palette and select Add option. These methods are not available in Talend Studio and may cause errors or unexpected results.
Reference: Talend Open Studio: Open-source ETL and Free Data Integration | Talend, [Joblets – 7.3]
Question #50
What is the generic Input component used for in a Joblet design?
- A . Triggering a Joblet
- B . Triggering a subJob
- C . Carrying data into a Joblet
- D . Carrying data into a subJob
Correct Answer: C
C
Explanation:
The generic Input component used for in a Joblet design is the tJobletInput component. This component is used to carry data into a Joblet from another component in the job that contains the Joblet. A Joblet is a reusable piece of a job that can be used in multiple jobs as a single component. A Joblet can have one or more input and output flows that connect it with other components in a job. To create these flows, you need to use generic input and output components, such as tJobletInput, tJobletOutput, tJobletTriggerInput, and tJobletTriggerOutput. These components allow you to define schemas and triggers for your Joblet without depending on specific components.
The tJobletInput component is not used for triggering a Joblet, triggering a subjob, or carrying data into a subjob. These are different concepts and functionalities in Talend Studio. A trigger is a link that activates a subjob or a component based on a condition or an event. A subjob is a part of a job that consists of one or more components connected by data flows or triggers. A subjob can be triggered by another subjob using triggers such as OnSubjobOk, OnSubjobError, Run if, etc. A subjob can also carry data into another subjob using data flows such as main, lookup, reject, etc.
Reference: Talend Open Studio: Open-source ETL and Free Data Integration | Talend, [tJobletInput properties – 7.3], [Joblets – 7.3], [Triggers – 7.3]
C
Explanation:
The generic Input component used for in a Joblet design is the tJobletInput component. This component is used to carry data into a Joblet from another component in the job that contains the Joblet. A Joblet is a reusable piece of a job that can be used in multiple jobs as a single component. A Joblet can have one or more input and output flows that connect it with other components in a job. To create these flows, you need to use generic input and output components, such as tJobletInput, tJobletOutput, tJobletTriggerInput, and tJobletTriggerOutput. These components allow you to define schemas and triggers for your Joblet without depending on specific components.
The tJobletInput component is not used for triggering a Joblet, triggering a subjob, or carrying data into a subjob. These are different concepts and functionalities in Talend Studio. A trigger is a link that activates a subjob or a component based on a condition or an event. A subjob is a part of a job that consists of one or more components connected by data flows or triggers. A subjob can be triggered by another subjob using triggers such as OnSubjobOk, OnSubjobError, Run if, etc. A subjob can also carry data into another subjob using data flows such as main, lookup, reject, etc.
Reference: Talend Open Studio: Open-source ETL and Free Data Integration | Talend, [tJobletInput properties – 7.3], [Joblets – 7.3], [Triggers – 7.3]