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 #21
How do you create an empty Joblet?
- A . Create an empty Job, then export it as a Joblet by right-clicking it in the Repository.
- B . Create an empty Jon and use the file menu to save it as Joblet.
- C . Right-click Joblet Designs the Repository and select Create Joblet.
- D . Right-clicking a space in the Designer and select refactor to Joblect.
Correct Answer: C
C
Explanation:
To create an empty Joblet, you need to right-click on the Joblet Designs node in the Repository tree view and select Create Joblet option. This will open a dialog box where you can enter the name and description of your Joblet and select an icon for it. You can then design your Joblet by adding components and links to it in the Designer workspace.
You cannot create an empty Joblet by creating an empty job, then exporting it as a Joblet by right-clicking it in the Repository, creating an empty job and using the file menu to save it as Joblet, or right-clicking a space in the Designer and selecting refactor to Joblet. 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]
C
Explanation:
To create an empty Joblet, you need to right-click on the Joblet Designs node in the Repository tree view and select Create Joblet option. This will open a dialog box where you can enter the name and description of your Joblet and select an icon for it. You can then design your Joblet by adding components and links to it in the Designer workspace.
You cannot create an empty Joblet by creating an empty job, then exporting it as a Joblet by right-clicking it in the Repository, creating an empty job and using the file menu to save it as Joblet, or right-clicking a space in the Designer and selecting refactor to Joblet. 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 #22
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
- A . Observing the execution time in the Code view.
- B . Heading the time stamps from the execution console in the Run view.
- C . Comparing time stamp in Trace Debug mode.
- D . Observing the execution times that annotate the flows in the Designer.
Correct Answer: B, D
B, D
Explanation:
To identify execution times to verify the effectiveness of your changes, you can use one of these methods:
Reading the time stamps from the execution console in the Run view. This method allows you to see the start and end time of each subjob and component in your job, as well as the total execution time of the job. You can also see the number of rows processed by each component and the status of the job (success or failure).
Observing the execution times that annotate the flows in the Designer. This method allows you to see the execution time of each flow (main, lookup, reject, etc.) between components in your job. You can also see the number of rows processed by each flow and the throughput (rows per second) of
each flow.
You cannot use these methods to identify execution times:
Observing the execution time in the Code view. This method does not show you the execution time of your job or its components, but only the generated code of your job in Java or Perl. The Code view is useful for debugging or customizing your code, but not for measuring performance.
Comparing time stamps in Trace Debug mode. This method does not show you the execution time of your job or its components, but only the values of each column for each row processed by your job. The Trace Debug mode is useful for tracing data quality or transformation issues, but not for measuring performance.
Reference: Talend Open Studio: Open-source ETL and Free Data Integration | Talend, [Run view – 7.3], [Designer – 7.3], [Code view – 7.3], [Trace Debug mode – 7.3]
B, D
Explanation:
To identify execution times to verify the effectiveness of your changes, you can use one of these methods:
Reading the time stamps from the execution console in the Run view. This method allows you to see the start and end time of each subjob and component in your job, as well as the total execution time of the job. You can also see the number of rows processed by each component and the status of the job (success or failure).
Observing the execution times that annotate the flows in the Designer. This method allows you to see the execution time of each flow (main, lookup, reject, etc.) between components in your job. You can also see the number of rows processed by each flow and the throughput (rows per second) of
each flow.
You cannot use these methods to identify execution times:
Observing the execution time in the Code view. This method does not show you the execution time of your job or its components, but only the generated code of your job in Java or Perl. The Code view is useful for debugging or customizing your code, but not for measuring performance.
Comparing time stamps in Trace Debug mode. This method does not show you the execution time of your job or its components, but only the values of each column for each row processed by your job. The Trace Debug mode is useful for tracing data quality or transformation issues, but not for measuring performance.
Reference: Talend Open Studio: Open-source ETL and Free Data Integration | Talend, [Run view – 7.3], [Designer – 7.3], [Code view – 7.3], [Trace Debug mode – 7.3]
Question #23
You need to set up a server in your Talend environment that enables several members of your team to collaborate on a project.
Which application must you enable before working on a remote project?
- A . Git or SVN server instance must be running.
- B . Talent Administration Center instance must be running with the team members and project configured.
- C . Git or SVN client must be installed on each developed workstation.
- D . Talend admission Center service must be running on each development workstation.
Correct Answer: A, B
A, B
Explanation:
To set up a server in your Talend environment that enables several members of your team to collaborate on a project, you need to enable two applications before working on a remote project: Git or SVN server instance and Talend Administration Center instance. These applications are used to manage version control and collaboration for your project.
Git or SVN server instance is a server application that allows you to store and track changes of your project files using a version control system. Git and SVN are two popular version control systems that are supported by Talend Studio. You need to have a Git or SVN server instance running and accessible by your team members before working on a remote project. You also need to have a Git or SVN client installed on each development workstation to connect to the server and perform version control operations.
Talend Administration Center is a web-based application that allows you to manage users, projects, tasks, execution servers, and licenses for your Talend environment. You need to have a Talend Administration Center instance running and accessible by your team members before working on a remote project. You also need to configure the team members and project settings in Talend Administration Center to grant access and permissions for your project.
Reference: Talend Open Studio: Open-source ETL and Free Data Integration | Talend, [Version control – 7.3], [Talend Administration Center – 7.3]
A, B
Explanation:
To set up a server in your Talend environment that enables several members of your team to collaborate on a project, you need to enable two applications before working on a remote project: Git or SVN server instance and Talend Administration Center instance. These applications are used to manage version control and collaboration for your project.
Git or SVN server instance is a server application that allows you to store and track changes of your project files using a version control system. Git and SVN are two popular version control systems that are supported by Talend Studio. You need to have a Git or SVN server instance running and accessible by your team members before working on a remote project. You also need to have a Git or SVN client installed on each development workstation to connect to the server and perform version control operations.
Talend Administration Center is a web-based application that allows you to manage users, projects, tasks, execution servers, and licenses for your Talend environment. You need to have a Talend Administration Center instance running and accessible by your team members before working on a remote project. You also need to configure the team members and project settings in Talend Administration Center to grant access and permissions for your project.
Reference: Talend Open Studio: Open-source ETL and Free Data Integration | Talend, [Version control – 7.3], [Talend Administration Center – 7.3]
Question #24
Which Action on table operations are supported by a tMysqlOutput component? Choose 3 answers.
- A . Drop table
- B . Drop table if exists and create
- C . Replace
- D . Create table if does not exist
- E . Create table
Correct Answer: B, D, E
B, D, E
Explanation:
Comprehensive and Detailed
The tMysqlOutput component in Talend provides several actions on tables to manage data output operations effectively. The supported actions include:
Drop Table if Exists and Create (Option B):
This action checks if the specified table exists in the database. If it does, the table is dropped and a new one is created. This ensures that the table is recreated fresh for the data load.
Create Table if Does Not Exist (Option D):
This action checks if the specified table exists in the database. If it does not exist, the table is created.
If it already exists, no action is taken, and the existing table is used.
Create Table (Option E):
This action attempts to create the specified table in the database. If the table already exists, an error will occur unless handled appropriately.
These actions provide flexibility in managing database tables during data integration processes, allowing for dynamic table creation and management based on the Job’s requirements.
Reference: Talend Components Reference Guide, Talend Database Output Components Documentation
B, D, E
Explanation:
Comprehensive and Detailed
The tMysqlOutput component in Talend provides several actions on tables to manage data output operations effectively. The supported actions include:
Drop Table if Exists and Create (Option B):
This action checks if the specified table exists in the database. If it does, the table is dropped and a new one is created. This ensures that the table is recreated fresh for the data load.
Create Table if Does Not Exist (Option D):
This action checks if the specified table exists in the database. If it does not exist, the table is created.
If it already exists, no action is taken, and the existing table is used.
Create Table (Option E):
This action attempts to create the specified table in the database. If the table already exists, an error will occur unless handled appropriately.
These actions provide flexibility in managing database tables during data integration processes, allowing for dynamic table creation and management based on the Job’s requirements.
Reference: Talend Components Reference Guide, Talend Database Output Components Documentation
Question #25
You need to share a connection between multiple database components in a Studio Job.
Which component should you use?
- A . tDBOutput
- B . tDBRun
- C . tDBCommit
- D . tDBConnection
Correct Answer: D
D
Explanation:
Comprehensive and Detailed
In Talend, when multiple components need to share the same database connection, the tDBConnection component is used.
tDBConnection (Correct Answer – Option D):
This component establishes a database connection that can be reused by multiple database components (such as tDBInput, tDBOutput, and tDBRow) within the same Job.
Reduces redundant connection creation, improving performance and efficiency.
To use it, other database components must set "Use an existing connection" in their configuration.
Why not other options?
tDBOutput (Option A): Used for writing data to a database but does not manage shared connections.
tDBRun (Option B): Used to execute a subJob but does not handle database connections.
tDBCommit (Option C): Used for committing transactions, but it requires a shared connection (which tDBConnection provides).
Reference: Talend Studio User Guide, Talend Database Connection Management
D
Explanation:
Comprehensive and Detailed
In Talend, when multiple components need to share the same database connection, the tDBConnection component is used.
tDBConnection (Correct Answer – Option D):
This component establishes a database connection that can be reused by multiple database components (such as tDBInput, tDBOutput, and tDBRow) within the same Job.
Reduces redundant connection creation, improving performance and efficiency.
To use it, other database components must set "Use an existing connection" in their configuration.
Why not other options?
tDBOutput (Option A): Used for writing data to a database but does not manage shared connections.
tDBRun (Option B): Used to execute a subJob but does not handle database connections.
tDBCommit (Option C): Used for committing transactions, but it requires a shared connection (which tDBConnection provides).
Reference: Talend Studio User Guide, Talend Database Connection Management
Question #26
Which HTTP methods are supported by tRESTRequest?
- A . GET, POST, PUT, PATCH, and DELETE
- B . POST, PATCH, and UPDATE
- C . SELECT, INSERT, UPDATE, and DELETE
- D . GET, POST, UPDATE, and DELETE
Correct Answer: A
A
Explanation:
Comprehensive and Detailed
The tRESTRequest component in Talend Studio is designed to handle RESTful web service requests. It supports the following HTTP methods:
GET: Retrieves data from the server.
POST: Submits data to the server, often causing a change in state or side effects.
PUT: Replaces all current representations of the target resource with the request payload.
PATCH: Applies partial modifications to a resource.
DELETE: Removes the specified resource from the server.
Therefore, the correct answer is
A
Explanation:
Comprehensive and Detailed
The tRESTRequest component in Talend Studio is designed to handle RESTful web service requests. It supports the following HTTP methods:
GET: Retrieves data from the server.
POST: Submits data to the server, often causing a change in state or side effects.
PUT: Replaces all current representations of the target resource with the request payload.
PATCH: Applies partial modifications to a resource.
DELETE: Removes the specified resource from the server.
Therefore, the correct answer is
Question #27
Where do you access the option to create a Joblet from an existing Job?
- A . Selecting the File menu.
- B . Selecting the desired components and right-clicking.
- C . Adding a Joblet component to the Designer.
- D . Right-clicking the I oh in the Repository
Correct Answer: B
B
Explanation:
To create a Joblet from an existing Job, you can follow these steps:
Open the Job that you want to create a Joblet from.
Select the components that you want to include in the Joblet.
Right-click on the selected components and select Create Joblet from the context menu.
In the Create Joblet dialog box, enter a name and description for the Joblet.
Click Finish to create the Joblet.
Reference: Talend Open Studio User Guide: Creating a Joblet from a Job: https://help.talend.com/r/en-US/8.0/studio-user-guide/creating-joblet-from-job
B
Explanation:
To create a Joblet from an existing Job, you can follow these steps:
Open the Job that you want to create a Joblet from.
Select the components that you want to include in the Joblet.
Right-click on the selected components and select Create Joblet from the context menu.
In the Create Joblet dialog box, enter a name and description for the Joblet.
Click Finish to create the Joblet.
Reference: Talend Open Studio User Guide: Creating a Joblet from a Job: https://help.talend.com/r/en-US/8.0/studio-user-guide/creating-joblet-from-job
Question #28
Which locations allow you to view a dataset in Talend Cloud Data Preparation? Choose 3 answers.
- A . Data preparation overview
- B . Dataset properties
- C . Dataset overview
- D . Dataset patterns
- E . Dataset sample
Correct Answer: C, D, E
C, D, E
Explanation:
Comprehensive and Detailed
In Talend Cloud Data Preparation, users can view and interact with datasets through various interfaces:
Dataset overview (Option C):
Provides a general summary of the dataset, including metadata, quality metrics, and other pertinent information.
Dataset patterns (Option D):
Displays recurring patterns within the dataset, helping users understand data distributions and identify anomalies.
Dataset sample (Option E):
Allows users to view a sample of the dataset’s records, facilitating data exploration and preparation tasks.
Why not other options?
Option A: "Data preparation overview" is not a standard feature or terminology within Talend Cloud Data Preparation.
Option B: "Dataset properties" typically refers to metadata and configuration settings, not the data content itself.
Reference: Talend Cloud Data Preparation User Guide
C, D, E
Explanation:
Comprehensive and Detailed
In Talend Cloud Data Preparation, users can view and interact with datasets through various interfaces:
Dataset overview (Option C):
Provides a general summary of the dataset, including metadata, quality metrics, and other pertinent information.
Dataset patterns (Option D):
Displays recurring patterns within the dataset, helping users understand data distributions and identify anomalies.
Dataset sample (Option E):
Allows users to view a sample of the dataset’s records, facilitating data exploration and preparation tasks.
Why not other options?
Option A: "Data preparation overview" is not a standard feature or terminology within Talend Cloud Data Preparation.
Option B: "Dataset properties" typically refers to metadata and configuration settings, not the data content itself.
Reference: Talend Cloud Data Preparation User Guide
Question #29
Where can you specify the remote JobServer to execute a Job?
- A . Job settings section of the Project Settings windows
- B . Extra tab in the Job view
- C . Run/Debug section in the Preference window
- D . Target Exec tab in the Run view
Correct Answer: D
D
Explanation:
To specify the remote JobServer to execute a job, you need to use the Target Exec tab in the Run view of Talend Studio. The Run view allows you to configure and execute your job from Talend Studio. The Target Exec tab allows you to select whether you want to run your job locally or remotely on a JobServer. A JobServer is a server application that allows you to execute jobs remotely from Talend Studio or Talend Administration Center. To run your job on a remote JobServer, you need to select Remote Jobserver option from the drop-down menu and select or add a JobServer connection from the list.
You do not need to use Job settings section of Project Settings window, Extra tab in Job view, or Run/Debug section in Preferences window. These windows are not used to specify remote JobServer execution. The Job settings section of Project Settings window is used to configure general settings for your jobs, such as versioning, statistics, logs, etc. The Extra tab in Job view is used to configure extra features for your job, such as implicit context load, tStatCatcher, tLogCatcher, etc. The Run/Debug section in Preferences window is used to configure run/debug settings for your Talend Studio, such as JVM arguments, execution mode, etc.
Reference: Talend Open Studio: Open-source ETL and Free Data Integration | Talend, [Run view – 7.3], [Project Settings – 7.3], [Job view – 7.3], [Preferences – 7.3]
D
Explanation:
To specify the remote JobServer to execute a job, you need to use the Target Exec tab in the Run view of Talend Studio. The Run view allows you to configure and execute your job from Talend Studio. The Target Exec tab allows you to select whether you want to run your job locally or remotely on a JobServer. A JobServer is a server application that allows you to execute jobs remotely from Talend Studio or Talend Administration Center. To run your job on a remote JobServer, you need to select Remote Jobserver option from the drop-down menu and select or add a JobServer connection from the list.
You do not need to use Job settings section of Project Settings window, Extra tab in Job view, or Run/Debug section in Preferences window. These windows are not used to specify remote JobServer execution. The Job settings section of Project Settings window is used to configure general settings for your jobs, such as versioning, statistics, logs, etc. The Extra tab in Job view is used to configure extra features for your job, such as implicit context load, tStatCatcher, tLogCatcher, etc. The Run/Debug section in Preferences window is used to configure run/debug settings for your Talend Studio, such as JVM arguments, execution mode, etc.
Reference: Talend Open Studio: Open-source ETL and Free Data Integration | Talend, [Run view – 7.3], [Project Settings – 7.3], [Job view – 7.3], [Preferences – 7.3]
Question #30
You want to create a generic schema using a schema defined in a Talend component in the Repository view.
How can you accomplish this?
- A . By right-clicking the component and selecting the Generic schema option.
- B . On the Advanced settings tab of the Component view.
- C . In the Repository, by right-clicking Generic schemas.
- D . In the Schema Editor window for the component.
Correct Answer: C
C
Explanation:
To create a generic schema from a schema defined in a Talend component, follow these steps:
Open the Repository View:
In Talend Studio, navigate to the Repository panel, typically located on the left side of the interface.
Locate the ‘Generic schemas’ Node:
Within the Repository, expand the ‘Metadata’ section to find the ‘Generic schemas’ node.
Initiate the Generic Schema Creation Process:
Right-click on ‘Generic schemas’ and select ‘Create generic schema’ from the context menu.
Define the Schema Properties:
In the schema creation wizard that appears, provide the necessary properties such as ‘Name’ and ‘Description’ for the new generic schema.
Set Up the Schema Structure:
Define the schema structure by adding columns and specifying their data types as required.
Finalize the Schema Creation:
Click ‘Finish’ to complete the creation process. The new generic schema will now be available under the ‘Generic schemas’ node in the Repository.
This method allows you to create a reusable generic schema that can be applied across multiple components and Jobs within Talend Studio.
Reference: Talend Official Documentation, Talend Studio User Guide
C
Explanation:
To create a generic schema from a schema defined in a Talend component, follow these steps:
Open the Repository View:
In Talend Studio, navigate to the Repository panel, typically located on the left side of the interface.
Locate the ‘Generic schemas’ Node:
Within the Repository, expand the ‘Metadata’ section to find the ‘Generic schemas’ node.
Initiate the Generic Schema Creation Process:
Right-click on ‘Generic schemas’ and select ‘Create generic schema’ from the context menu.
Define the Schema Properties:
In the schema creation wizard that appears, provide the necessary properties such as ‘Name’ and ‘Description’ for the new generic schema.
Set Up the Schema Structure:
Define the schema structure by adding columns and specifying their data types as required.
Finalize the Schema Creation:
Click ‘Finish’ to complete the creation process. The new generic schema will now be available under the ‘Generic schemas’ node in the Repository.
This method allows you to create a reusable generic schema that can be applied across multiple components and Jobs within Talend Studio.
Reference: Talend Official Documentation, Talend Studio User Guide