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 #51
Which operations can you perform using a tMap component? Choose 3 answers.
- A . Map data using filters, constraints, and simple explicit joins.
- B . Perform full outer joins.
- C . Transform data from single or multiple sources to single or multiple destinations.
- D . Load single lookup tables only.
- E . Reject data using inner join rejections.
Correct Answer: A, B, C
A, B, C
Explanation:
Comprehensive and Detailed
The tMap component in Talend allows for various data transformation and mapping operations. The correct operations include:
A, B, C
Explanation:
Comprehensive and Detailed
The tMap component in Talend allows for various data transformation and mapping operations. The correct operations include:
Question #52
You built multiple Jobs in Studio, each uses its own tDBInput component to connect to a common
database server, but they all use different credentials.
How should you configure the tDBInput components?
- A . Set the Property type to Repository and use a common DB connection metadata.
- B . Set the Property type to Repository and replace the credentials in each component.
- C . Set the Property type to Built-in and set all the relevant properties manually.
- D . Set the Database field to Metadata.
Correct Answer: C
C
Explanation:
Comprehensive and Detailed
When multiple Jobs require connections to the same database server but with different credentials, the recommended approach is:
Set the Property Type to Built-in and Set All the Relevant Properties Manually (Option C):
In each tDBInput component, set the ‘Property Type’ to ‘Built-in.’
Manually enter the connection details, including the specific username and password required for that particular Job.
This approach ensures that each Job uses its own set of credentials, maintaining the necessary security and access controls.
Reference: Talend Studio User Guide, Talend Database Components Documentation
C
Explanation:
Comprehensive and Detailed
When multiple Jobs require connections to the same database server but with different credentials, the recommended approach is:
Set the Property Type to Built-in and Set All the Relevant Properties Manually (Option C):
In each tDBInput component, set the ‘Property Type’ to ‘Built-in.’
Manually enter the connection details, including the specific username and password required for that particular Job.
This approach ensures that each Job uses its own set of credentials, maintaining the necessary security and access controls.
Reference: Talend Studio User Guide, Talend Database Components Documentation
Question #53
Which statements are true when comparing a Joblet to a tRunJob component? Choose 3 answers
- A . The performance of tRunJob component is better than running an equivalent Job using a Joblet.
- B . A Joblet uses the same context variables of the Job in which it is used, unlinke a tRunJob component.
- C . The performance of a Joblet if better than running an equivalent Job using a tRunJob component.
- D . Building a Joblet typically requires the use of generic input, and trigger component.
- E . The nested Job called by a tRunJob component cannot use the same context variable of the Job in which it is used.
Correct Answer: B, D, E
B, D, E
Explanation:
A Joblet is a reusable piece of a job that can be used in multiple jobs as a single component. A tRunJob component is a component that allows you to call another job as a subjob within a parent job.
When comparing a Joblet to a tRunJob component, these statements are true:
A Joblet uses the same context variables of the job in which it is used, unlike a tRunJob component. A context variable is a variable that can store a value that can be changed at runtime or between different contexts. A Joblet inherits the context variables from the job that contains it and does not have its own context variables. A tRunJob component can pass context variables from the parent job to the child job, or use a specific context for the child job.
Building a Joblet typically requires the use of generic input and trigger components. 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 trigger 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 nested job called by a tRunJob component cannot use the same context variables of the job in which it is used. A nested job is a job that is called by another job using a tRunJob component. A nested job can have its own context variables or receive context variables from its parent job, but it cannot use the same context variables as its parent job. This means that if you have two context variables with the same name in both jobs, they will be treated as separate variables and will not share values.
These statements are false when comparing a Joblet to a tRunJob component:
The performance of tRunJob component is better than running an equivalent job using a Joblet. The performance of a Joblet is better than running an equivalent job using a tRunJob component. This is because a Joblet is integrated into the main code of the job and does not require launching another JVM process or loading another metadata object like a tRunJob component does.
Reference: Talend Open Studio: Open-source ETL and Free Data Integration | Talend, [Joblets – 7.3], [tRunJob properties – 7.3], [Contexts – 7.3]
B, D, E
Explanation:
A Joblet is a reusable piece of a job that can be used in multiple jobs as a single component. A tRunJob component is a component that allows you to call another job as a subjob within a parent job.
When comparing a Joblet to a tRunJob component, these statements are true:
A Joblet uses the same context variables of the job in which it is used, unlike a tRunJob component. A context variable is a variable that can store a value that can be changed at runtime or between different contexts. A Joblet inherits the context variables from the job that contains it and does not have its own context variables. A tRunJob component can pass context variables from the parent job to the child job, or use a specific context for the child job.
Building a Joblet typically requires the use of generic input and trigger components. 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 trigger 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 nested job called by a tRunJob component cannot use the same context variables of the job in which it is used. A nested job is a job that is called by another job using a tRunJob component. A nested job can have its own context variables or receive context variables from its parent job, but it cannot use the same context variables as its parent job. This means that if you have two context variables with the same name in both jobs, they will be treated as separate variables and will not share values.
These statements are false when comparing a Joblet to a tRunJob component:
The performance of tRunJob component is better than running an equivalent job using a Joblet. The performance of a Joblet is better than running an equivalent job using a tRunJob component. This is because a Joblet is integrated into the main code of the job and does not require launching another JVM process or loading another metadata object like a tRunJob component does.
Reference: Talend Open Studio: Open-source ETL and Free Data Integration | Talend, [Joblets – 7.3], [tRunJob properties – 7.3], [Contexts – 7.3]
Question #54
Which action should you perform to calculate the overall Trust Score™ for multiple customer datasets?
- A . Review the rating of selected datasets in the group tab.
- B . Use the search bar to filter the customer datasets, and the score will automatically update.
- C . Mark the datasets in the dataset list, and the score updates in the detailed view.
- D . Use the search bar to filter the customer datasets and manually calculate the score.
Correct Answer: B
B
Explanation:
Comprehensive and Detailed
To calculate the overall Trust Score™ for multiple customer datasets:
Use the search bar to filter the customer datasets, and the score will automatically update (Option B):
Filtering datasets using the search functionality aggregates the Trust Scores of the selected datasets, providing an overall score for the group.
Why not other options?
Option A: Reviewing individual ratings does not provide an aggregated Trust Score™.
Option C: Marking datasets does not trigger an automatic update of the aggregated score.
Option D: Manual calculation is unnecessary as the system provides automatic aggregation upon filtering.
Reference: Talend Cloud Data Inventory User Guide
B
Explanation:
Comprehensive and Detailed
To calculate the overall Trust Score™ for multiple customer datasets:
Use the search bar to filter the customer datasets, and the score will automatically update (Option B):
Filtering datasets using the search functionality aggregates the Trust Scores of the selected datasets, providing an overall score for the group.
Why not other options?
Option A: Reviewing individual ratings does not provide an aggregated Trust Score™.
Option C: Marking datasets does not trigger an automatic update of the aggregated score.
Option D: Manual calculation is unnecessary as the system provides automatic aggregation upon filtering.
Reference: Talend Cloud Data Inventory User Guide
Question #54
Which action should you perform to calculate the overall Trust Score™ for multiple customer datasets?
- A . Review the rating of selected datasets in the group tab.
- B . Use the search bar to filter the customer datasets, and the score will automatically update.
- C . Mark the datasets in the dataset list, and the score updates in the detailed view.
- D . Use the search bar to filter the customer datasets and manually calculate the score.
Correct Answer: B
B
Explanation:
Comprehensive and Detailed
To calculate the overall Trust Score™ for multiple customer datasets:
Use the search bar to filter the customer datasets, and the score will automatically update (Option B):
Filtering datasets using the search functionality aggregates the Trust Scores of the selected datasets, providing an overall score for the group.
Why not other options?
Option A: Reviewing individual ratings does not provide an aggregated Trust Score™.
Option C: Marking datasets does not trigger an automatic update of the aggregated score.
Option D: Manual calculation is unnecessary as the system provides automatic aggregation upon filtering.
Reference: Talend Cloud Data Inventory User Guide
B
Explanation:
Comprehensive and Detailed
To calculate the overall Trust Score™ for multiple customer datasets:
Use the search bar to filter the customer datasets, and the score will automatically update (Option B):
Filtering datasets using the search functionality aggregates the Trust Scores of the selected datasets, providing an overall score for the group.
Why not other options?
Option A: Reviewing individual ratings does not provide an aggregated Trust Score™.
Option C: Marking datasets does not trigger an automatic update of the aggregated score.
Option D: Manual calculation is unnecessary as the system provides automatic aggregation upon filtering.
Reference: Talend Cloud Data Inventory User Guide
Question #56
You are collaborating on a project with other developers using talend best practices.
When should you use a tag?
- A . Capturing snapshot of a codebase that requires ongoing maintenance.
- B . Fixing hugs or enhancements.
- C . Denoting major or minor releases.
- D . Denoting a milestone in the lifecycle of a project
Correct Answer: D
D
Explanation:
Tags are used to mark specific points in the development lifecycle of a project. This can be done for a variety of reasons, such as:
To mark the completion of a major feature or release
To mark the start of a new development phase (e.g., QA, production)
To mark a known good state of the codebase (e.g., before a risky change)
Tags can be used to create branches, which can then be used to develop and test new features or bug fixes. They can also be used to deploy the codebase to different environments (e.g., development, staging, production).
Examples of when to use a tag:
When you are ready to release a new version of your application to production.
When you have completed a major feature or milestone in the development of your application.
Before making a risky change to your codebase, such as a database migration or refactoring.
When you need to deploy your application to a different environment, such as staging or production.
Benefits of using tags:
Tags can help you to keep track of the different versions of your codebase.
Tags can help you to roll back to a previous version of your codebase if necessary.
Tags can help you to deploy your codebase to different environments.
Tags can help you to collaborate with other developers more effectively.
Reference: Talend Best Practices Guide: https://help.talend.com/r/en-US/8.0/software-dev-lifecycle-best-practices-guide/branching-merging-and-tagging
Git documentation on tags: https://git-scm.com/docs/git-tag
D
Explanation:
Tags are used to mark specific points in the development lifecycle of a project. This can be done for a variety of reasons, such as:
To mark the completion of a major feature or release
To mark the start of a new development phase (e.g., QA, production)
To mark a known good state of the codebase (e.g., before a risky change)
Tags can be used to create branches, which can then be used to develop and test new features or bug fixes. They can also be used to deploy the codebase to different environments (e.g., development, staging, production).
Examples of when to use a tag:
When you are ready to release a new version of your application to production.
When you have completed a major feature or milestone in the development of your application.
Before making a risky change to your codebase, such as a database migration or refactoring.
When you need to deploy your application to a different environment, such as staging or production.
Benefits of using tags:
Tags can help you to keep track of the different versions of your codebase.
Tags can help you to roll back to a previous version of your codebase if necessary.
Tags can help you to deploy your codebase to different environments.
Tags can help you to collaborate with other developers more effectively.
Reference: Talend Best Practices Guide: https://help.talend.com/r/en-US/8.0/software-dev-lifecycle-best-practices-guide/branching-merging-and-tagging
Git documentation on tags: https://git-scm.com/docs/git-tag