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 #31
User A shared a connection with User B. User B used the shared connection and created Dataset_1. User A stops sharing the connection with User B.
Which statement is true about access to Dataset_1?
- A . User B has limited access to Dataset_1.
- B . User B has no access to Dataset_1.
- C . User A has full access to Dataset_1.
- D . User B has full access to Dataset_1.
Correct Answer: D
D
Explanation:
Comprehensive and Detailed
In Talend Cloud Data Inventory, when a user creates a dataset using a shared connection, the following applies:
User B has full access to Dataset_1 (Option D):
Once User B creates Dataset_1 using the shared connection, they become the owner of that dataset. Even if User A later revokes access to the connection, User B retains full access to Dataset_1. The dataset’s accessibility is independent of the connection’s sharing status after its creation.
Why not other options?
Option A: User B’s access to Dataset_1 is not limited; they have full ownership and control.
Option B: Revoking the connection does not remove User B’s access to datasets they have already created.
Option C: User A’s access to Dataset_1 depends on the sharing settings applied by User B; by default, User A does not have access unless granted.
Reference: Talend Cloud Data Inventory User Guide
D
Explanation:
Comprehensive and Detailed
In Talend Cloud Data Inventory, when a user creates a dataset using a shared connection, the following applies:
User B has full access to Dataset_1 (Option D):
Once User B creates Dataset_1 using the shared connection, they become the owner of that dataset. Even if User A later revokes access to the connection, User B retains full access to Dataset_1. The dataset’s accessibility is independent of the connection’s sharing status after its creation.
Why not other options?
Option A: User B’s access to Dataset_1 is not limited; they have full ownership and control.
Option B: Revoking the connection does not remove User B’s access to datasets they have already created.
Option C: User A’s access to Dataset_1 depends on the sharing settings applied by User B; by default, User A does not have access unless granted.
Reference: Talend Cloud Data Inventory User Guide
Question #32
Which methods can you use to name an output row in a tMap component? Choose 3 answers.
- A . Click the name of the table in the Map Editor window and edit it.
- B . Assign the name when defining a new output table in the Map Editor window.
- C . Select the output row, then open the Component view and click the View tab.
- D . Assign the name when connecting a new output component.
- E . Double-click the output row in the Designer and enter a new name.
Correct Answer: A, B, D
A, B, D
Explanation:
In a tMap component, naming an output row correctly helps in managing data flow efficiently.
The correct methods are:
A, B, D
Explanation:
In a tMap component, naming an output row correctly helps in managing data flow efficiently.
The correct methods are:
Question #33
Which method allows you to execute the compiled Job Talend Studio?
- A . Click the Export button in the Edit Properties window.
- B . Right-click the Job in the Repository and select Build Job
- C . Right-click the Job in the Repository and select Export items.
- D . Select Save As on the main File menu
Correct Answer: B
B
Explanation:
To execute the compiled job outside Talend Studio, you need to right-click on the job in the Repository tree view and select Build Job option. This 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 click the Export button in the Edit Properties window, right-click on the job in the Repository and select Export items, or select Save As on the main File menu. These options are not used to execute the compiled job outside Talend Studio. The Export button in the Edit Properties window is used to export your job properties as an XML file. The Export items option is used to export your items (such as jobs, metadata, routines, etc.) as an archive file that can be imported into another project or workspace. The Save As option is used to save a copy of your job with a different name or location.
Reference: Talend Open Studio: Open-source ETL and Free Data Integration | Talend, [Build Job – 7.3]
B
Explanation:
To execute the compiled job outside Talend Studio, you need to right-click on the job in the Repository tree view and select Build Job option. This 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 click the Export button in the Edit Properties window, right-click on the job in the Repository and select Export items, or select Save As on the main File menu. These options are not used to execute the compiled job outside Talend Studio. The Export button in the Edit Properties window is used to export your job properties as an XML file. The Export items option is used to export your items (such as jobs, metadata, routines, etc.) as an archive file that can be imported into another project or workspace. The Save As option is used to save a copy of your job with a different name or location.
Reference: Talend Open Studio: Open-source ETL and Free Data Integration | Talend, [Build Job – 7.3]
Question #34
Which statements are true about the execution logs of a task running on a Remote Engine? Choose 2 answers.
- A . Logs are stored in the file system of the server where the Remote Engine is running.
- B . Logs are stored in an H2 database hosted on the server where the Remote Engine is running.
- C . Logs can be downloaded from Talend Management Console.
- D . Logs are stored in Parquet format on the server where the Remote Engine is running.
Correct Answer: A, C
A, C
Explanation:
Comprehensive and Detailed
When a task executes on a Talend Remote Engine, the execution logs are handled as follows:
Logs are stored in the file system of the server where the Remote Engine is running (Option A):
The Remote Engine writes execution logs to its local file system, typically in plain text or log formats. These logs provide detailed information about the task’s execution and are essential for troubleshooting and monitoring.
Logs can be downloaded from Talend Management Console (Option C):
Talend Management Console (TMC) aggregates execution logs from Remote Engines, allowing users to access and download them directly through the TMC interface. This centralized access simplifies monitoring and debugging across multiple environments.
Why not other options?
Option B: While some components of Talend may use H2 databases for internal purposes, execution logs are not typically stored in an H2 database on the Remote Engine server.
Option D: Execution logs are generally stored in plain text or standard log formats, not in Parquet format. Parquet is a columnar storage file format commonly used for efficient data processing, not for logging purposes.
Reference: Talend Remote Engine User Guide, Talend Management Console User Guide
A, C
Explanation:
Comprehensive and Detailed
When a task executes on a Talend Remote Engine, the execution logs are handled as follows:
Logs are stored in the file system of the server where the Remote Engine is running (Option A):
The Remote Engine writes execution logs to its local file system, typically in plain text or log formats. These logs provide detailed information about the task’s execution and are essential for troubleshooting and monitoring.
Logs can be downloaded from Talend Management Console (Option C):
Talend Management Console (TMC) aggregates execution logs from Remote Engines, allowing users to access and download them directly through the TMC interface. This centralized access simplifies monitoring and debugging across multiple environments.
Why not other options?
Option B: While some components of Talend may use H2 databases for internal purposes, execution logs are not typically stored in an H2 database on the Remote Engine server.
Option D: Execution logs are generally stored in plain text or standard log formats, not in Parquet format. Parquet is a columnar storage file format commonly used for efficient data processing, not for logging purposes.
Reference: Talend Remote Engine User Guide, Talend Management Console User Guide
Question #35
Which methods can you use to specify the schema in a tFileInputDelimited component? Choose 3 answers.
- A . Add the component, open the Component view, select the Built-in schema type, then click the Edit schema button.
- B . Drag a generic schema metadata item onto the Designer.
- C . Add the component, then drag and drop a generic schema metadata item onto the component.
- D . Add the schema to the component using the Schema Editor.
- E . Drag a File delimited metadata item from the Repository onto the design workspace.
Correct Answer: A, C, E
A, C, E
Explanation:
In Talend Studio, there are multiple methods to specify the schema for a tFileInputDelimited component. The three primary approaches include:
A, C, E
Explanation:
In Talend Studio, there are multiple methods to specify the schema for a tFileInputDelimited component. The three primary approaches include:
Question #36
What is the default port for the REST Endpoint when using tRESTRequest in Talend Studio?
- A . 5040
- B . 5070
- C . 8040
- D . 8090
Correct Answer: D
D
Explanation:
Comprehensive and Detailed
The default REST endpoint port for tRESTRequest in Talend Studio is 8090.
Port 8090 (Correct Answer – Option D):
When running a REST service inside Talend Studio, the default listening port is 8090.
This can be changed in the component settings if required.
Other port options explained:
5040 & 5070: Not default ports used for Talend REST services.
8040: Used in Talend Runtime, not in Studio.
Reference: Talend Studio User Guide, Talend ESB REST Service Configuration
D
Explanation:
Comprehensive and Detailed
The default REST endpoint port for tRESTRequest in Talend Studio is 8090.
Port 8090 (Correct Answer – Option D):
When running a REST service inside Talend Studio, the default listening port is 8090.
This can be changed in the component settings if required.
Other port options explained:
5040 & 5070: Not default ports used for Talend REST services.
8040: Used in Talend Runtime, not in Studio.
Reference: Talend Studio User Guide, Talend ESB REST Service Configuration
Question #37
Which concepts are a part of Pipeline Designer? Choose 3 answers.
- A . Context variables
- B . Preparations
- C . Connection
- D . Dataset
- E . Processor
Correct Answer: C, D, E
C, D, E
Explanation:
Comprehensive and Detailed
Talend’s Pipeline Designer is a tool that enables users to design and execute data integration workflows. Key components of Pipeline Designer include:
Connection (Option C):
Defines the link between Pipeline Designer and various data sources or destinations, specifying how to access and interact with external systems.
Dataset (Option D):
Represents the structured data that flows through the pipeline, serving as the input or output of various processing steps.
Processor (Option E):
Performs specific operations on the data within the pipeline, such as transformations, aggregations, or filtering, to achieve the desired data processing outcomes.
Why not other options?
Option A: While context variables are used in Talend Studio for parameterizing jobs, they are not a primary concept in Pipeline Designer.
Option B: "Preparations" refer to data transformation sequences in Talend Data Preparation, not directly in Pipeline Designer.
Reference: Talend Pipeline Designer User Guide
C, D, E
Explanation:
Comprehensive and Detailed
Talend’s Pipeline Designer is a tool that enables users to design and execute data integration workflows. Key components of Pipeline Designer include:
Connection (Option C):
Defines the link between Pipeline Designer and various data sources or destinations, specifying how to access and interact with external systems.
Dataset (Option D):
Represents the structured data that flows through the pipeline, serving as the input or output of various processing steps.
Processor (Option E):
Performs specific operations on the data within the pipeline, such as transformations, aggregations, or filtering, to achieve the desired data processing outcomes.
Why not other options?
Option A: While context variables are used in Talend Studio for parameterizing jobs, they are not a primary concept in Pipeline Designer.
Option B: "Preparations" refer to data transformation sequences in Talend Data Preparation, not directly in Pipeline Designer.
Reference: Talend Pipeline Designer User Guide
Question #38
You designing a Job that can run in two contexts, Test and Production. You want to run it as a standalone job outside Talend Studio.
How do you accomplish this?
- A . Build the Job with the Context scripts option selected in the Build Job windows. Before running the Job, edit the script according to the context in which want to run the job.
- B . Set the desired context as the default, then build the Job. Rebuild the Job if you need to run it in a different context.
- C . Build the Job with the Context scripts option selected in the Build Job windows. You will be prompted for the context.
- D . Build the Job with the desired context selected in the Build Job windows. Build a separate copy if you need to run the Job in a different context.
Correct Answer: D
D
Explanation:
To design a job that can run in two contexts, Test and Production, and run it as a standalone job outside Talend Studio, you need to do the following steps:
Define the context variables and values for each context in the Contexts tab of your job. A context variable is a variable that can store a value that can be changed at runtime or between different contexts. You can use context variables to parameterize the properties or expressions of your job components.
Build the job with the desired context selected in the Build Job window. 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 need to select the context that you want to use for your job execution from the drop-down menu.
Extract the content of the archive file that contains your job executable files and libraries. 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.
If you need to run the job in a different context, you need to build a separate copy of the job with the other context selected in the Build Job window. You cannot change the context of an already built job
without rebuilding it.
You do not need to build the job with the Context scripts option selected in the Build Job window, edit the script according to the context in which you want to run the job, set the desired context as the default, rebuild the job if you need to run it in a different context, or be prompted for the context. 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], [Contexts – 7.3]
D
Explanation:
To design a job that can run in two contexts, Test and Production, and run it as a standalone job outside Talend Studio, you need to do the following steps:
Define the context variables and values for each context in the Contexts tab of your job. A context variable is a variable that can store a value that can be changed at runtime or between different contexts. You can use context variables to parameterize the properties or expressions of your job components.
Build the job with the desired context selected in the Build Job window. 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 need to select the context that you want to use for your job execution from the drop-down menu.
Extract the content of the archive file that contains your job executable files and libraries. 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.
If you need to run the job in a different context, you need to build a separate copy of the job with the other context selected in the Build Job window. You cannot change the context of an already built job
without rebuilding it.
You do not need to build the job with the Context scripts option selected in the Build Job window, edit the script according to the context in which you want to run the job, set the desired context as the default, rebuild the job if you need to run it in a different context, or be prompted for the context. 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], [Contexts – 7.3]
Question #39
Which statement describes a Data Preparation recipe?
- A . Dataset designed specifically for export
- B . Set of functions applied to a dataset
- C . List of semantic types associated with a dataset
- D . Datasets created for external applications
Correct Answer: B
B
Explanation:
Comprehensive and Detailed
In Talend Cloud Data Preparation, a recipe refers to a sequence of data transformation steps applied to a dataset. These steps can include actions like filtering, cleansing, enriching, and formatting data to prepare it for analysis or reporting. The recipe ensures that the same transformations can be consistently reapplied to the dataset or similar datasets, promoting data consistency and efficiency.
Why not other options?
Option A: A recipe is not a dataset itself but a set of transformation instructions applied to a dataset.
Option C: While semantic types are important, a recipe encompasses more than just listing them; it involves actionable transformations.
Option D: Recipes are not datasets but are applied to datasets to achieve desired transformations.
Reference: Talend Cloud Data Preparation User Guide
B
Explanation:
Comprehensive and Detailed
In Talend Cloud Data Preparation, a recipe refers to a sequence of data transformation steps applied to a dataset. These steps can include actions like filtering, cleansing, enriching, and formatting data to prepare it for analysis or reporting. The recipe ensures that the same transformations can be consistently reapplied to the dataset or similar datasets, promoting data consistency and efficiency.
Why not other options?
Option A: A recipe is not a dataset itself but a set of transformation instructions applied to a dataset.
Option C: While semantic types are important, a recipe encompasses more than just listing them; it involves actionable transformations.
Option D: Recipes are not datasets but are applied to datasets to achieve desired transformations.
Reference: Talend Cloud Data Preparation User Guide
Question #40
How can you create REST API metadata in Talend Studio? Choose 2 answers.
- A . Create it manually in Talend Studio.
- B . Import it from Talend API Designer.
- C . Import it from a JSON file.
- D . Import it from Talend API Tester.
Correct Answer: A, B
A, B
Explanation:
Comprehensive and Detailed
In Talend Studio, REST API metadata can be created using the following methods:
Create it manually in Talend Studio (Option A):
Users can define REST API metadata within Talend Studio by manually specifying API structure, endpoints, HTTP methods, and parameters.
This method provides full control over the API metadata but requires manual configuration.
Import it from Talend API Designer (Option B):
If an API has been designed using Talend API Designer, it can be imported into Talend Studio.
This enables reusing the API design directly without manual recreation.
Why not other options?
Option C (Import from JSON file): Talend Studio does not support direct import of REST API metadata from generic JSON files.
Option D (Import from Talend API Tester): Talend API Tester is used for testing APIs but does not provide an option to import API definitions into Talend Studio.
Reference: Talend Studio User Guide, Talend API Development Documentation
A, B
Explanation:
Comprehensive and Detailed
In Talend Studio, REST API metadata can be created using the following methods:
Create it manually in Talend Studio (Option A):
Users can define REST API metadata within Talend Studio by manually specifying API structure, endpoints, HTTP methods, and parameters.
This method provides full control over the API metadata but requires manual configuration.
Import it from Talend API Designer (Option B):
If an API has been designed using Talend API Designer, it can be imported into Talend Studio.
This enables reusing the API design directly without manual recreation.
Why not other options?
Option C (Import from JSON file): Talend Studio does not support direct import of REST API metadata from generic JSON files.
Option D (Import from Talend API Tester): Talend API Tester is used for testing APIs but does not provide an option to import API definitions into Talend Studio.
Reference: Talend Studio User Guide, Talend API Development Documentation