Talend TALEND-TDICD Online Practice Questions and Exam Preparation

Talend TALEND-TDICD Online Questions & Answers

• Question 1:

  Which file should you edit to enable SSL for a JobServer?

  A. Conf/TalendJobServer.properties
  B. Conf/TalendServer.properties
  C. Conf/server.xml
  D. Jsl_stati64.ini
  A. Conf/TalendJobServer.properties

  ---

  explanation:

  Explanation

  To enable SSL for a JobServer, you need to edit the conf/TalendJobServer.properties file. A JobServer is a server application that allows you to execute jobs remotely from Talend Studio or Talend Administration Center. The conf/ TalendJobServer.properties file contains various configuration parameters for your JobServer, such as port number, log level, security options, etc. To enable SSL for your JobServer, you need to set the ssl parameter to true and provide the path and password of your keystore file that contains your SSL certificate. You do not need to edit conf/TalendServer.properties, conf/server.xml, or jsl_static64.ini files. These files are not related to JobServer configuration or SSL settings. The conf/TalendServer.properties file is used to configure Talend Administration Centersettings, such as database connection, LDAP authentication, email notification, etc. The conf/server.xml file is used to configure Tomcat server settings, such as connectors, realms, valves, etc. The jsl_static64.ini file is used to configure Java Service Launcher settings, such as service name, description, startup type, etc.

  References: Talend Open Studio: Open-source ETL and Free Data Integration | Talend, [Configuring Talend JobServer - 7.3], [Configuring Talend Administration Center - 7.3], [Configuring Tomcat - 7.3], [Installing Java Service Launcher - 7.3]

• Question 2:

  Which capabilities does Traces Debugprovide?

  Choose 2 answers

  A. Filtering which data is propagated by a flow
  B. Advancing one column at a time
  C. Breaking on a selected line of code
  D. Breaking when an input column fulfills a condition
  E. Advancing one row at a time
  D. Breaking when an input column fulfills a condition
  E. Advancing one row at a time

  ---

  explanation:

  Explanation

  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. The capabilities that Trace Debug mode provides are: Breaking when an input column fulfills a condition. You can set breakpoints on traces based on a condition or an expression that involves input data columns. For example, you can set a breakpoint to pause your job when a customer name contains a certain string or when a product price exceeds a certain value. To set a breakpoint based on a condition, you need to right-click on a trace on your jobdesign workspace and select Show Breakpoint Setup option. This will open a dialog box where you can enter a condition or an expression for your breakpoint. Advancing one row at a time. You can advance the execution of your job one row at a time by using the Step Over button in the toolbar of the Run view. This will allow you to see how each row is processed by your job components and how it affects the output data. The capabilities that Trace Debug mode does not provide are: Filtering which data is propagated by a flow. You cannot filter which data is propagated by a flow in Trace Debug mode. A flow is a link that shows the data transfer between components in your job design workspace. In Trace Debug mode, you can see the data flow on each trace and inspect the values of each column for each row processed by your job. However, you cannot change which rows are propagated by a flow based on a condition or an expression. Advancing one column at a time. You cannot advance the execution of your job one column at a time in Trace Debug mode. You can only advance the execution of your job one row at a time by using the Step Over button in the toolbar of the Run view. This will allow you to see how each row is processed by your job components and how it affects the output data. However, you cannot see how each column is processed by your job components and how it affects the output data. Breaking on a selected line of code. You cannot break on a selected line of code in Trace Debug mode. You can only break on a trace based on a condition or an expression that involves input data columns. To break on a selected line of code, you need to use Java Debug mode. Java Debug mode allows you to debug your job code in Java or Perl and see the values of each variable or expression in your code. You can access this mode by switching to the Java perspective and clicking on the Debug button in the toolbar of the Code view.

  References: Talend Open Studio: Open-source ETL and Free Data Integration | Talend, [Trace Debug mode

  -7.3], [Java Debug mode - 7.3]

• Question 3:

  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 Branch1, copy lob 1, switch to Branch 2, and paste Job 1 over Job 2.
  A. Switch to Branch 1, right-click Job 1, select Copy to branch, and select Branch 2.

  ---

  explanation:

  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 branchoption. 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.

  References: Talend Open Studio: Open-source ETL and Free Data Integration | Talend, [Copy to branch - 7.3]

• Question 4:

  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.
  C. Right-click Joblet Designs the Repository and select Create Joblet.

  ---

  explanation:

  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 whereyou 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.

  References: Talend Open Studio: Open-source ETL and Free Data Integration | Talend, [Joblets - 7.3]

• Question 5:

  In the tMap component, where do you set up a filter on the input fields?

  A. Match Model parameter field for fine of the inputs
  B. Expression field for a single column of the output
  C. Expression filter in the output table
  D. Match Model parameter field for one of the main inputs
  C. Expression filter in the output table

  ---

  explanation:

  Explanation

  The tMap component allows you to set up a filter on the input fields by using the Expression filter in the output table. The Expression filter is a field where you can enter a logical expression that evaluates to true or false for each input row. For example, if you want to filter out the rows that have null values in a certain column, you can use row1.column != null as the expression filter for that output. The expression filter applies to all the input fields of the row, not just a single column. You cannot set up a filter on the input fields by using the Match Model parameter field for one of the inputs or outputs, as this field is used to define how to match rows between different inputs or outputs based on a key attribute.

  References: Talend Open Studio: Open-source ETL and Free Data Integration | Talend

• Question 6:

  Where can you simultaneously define primary keys for the Update and Delete operations in a tMysqlOutput component?

  A. Basic settings view, select the Use field options check box
  B. Advanced settings view, select the Additional columns options check box
  C. Advanced settings view, select the Use field options check box
  D. Advanced settings view, select the Use hint options check box
  C. Advanced settings view, select the Use field options check box

  ---

  explanation:

  Explanation

  The tMysqlOutput component is used to write data into a MySQL database table. The Update and Delete operations are used to modify or remove existing rows in the table based on a primary key. To define the primary key for these operations, you need to use the Use field options check box in the Advanced settings view of the component. This will enable you to specify which columns are used as keys for each operation. You can also define other options for each column, such as nullable, length, precision, etc. The Use field options check box is not available in the Basic settings view of the component. The Additional columns options check box and the Use hint options check box are used for other purposes, such as adding extra columns or hints to the SQL query, and they do not affect the primary key definition.

  References: Talend Open Studio: Open-source ETL and Free Data Integration | Talend, [tMysqlOutput properties - 7.3]

• Question 7:

  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 replace the credential1; in each component.
  B. Set the Property type to Built-in and set all the relevant properties manually.
  C. Set the Database file to Metadata
  D. Set the Property type, to Repository and use a common DB connection metadata
  B. Set the Property type to Built-in and set all the relevant properties manually.

  ---

  explanation:

  Explanation

  The tDBInput component allows you to configure the connection properties either by using a built-in mode or by using a repository mode. The built-in mode lets you set all the relevant properties manually, such as host, port, database, username, password, etc. The repository mode lets you reuse an existing connection metadata that is stored in the repository. If you have multiple jobs that use different credentials to connect to a common database server, you should use the built-in mode and set the properties for each job individually. This way, you can avoid creating multiple connection metadata in the repository and maintain them separately.

  References: Talend Data Integration -- Software to Connect, Access, and Transform Data | Talend, [tDBInput properties - 7.3]

• Question 8:

  Which templates allow you to create ready-to-run Jobs in Talend Studio?

  Choose2answers

  A. TabletoTable
  B. FileToDatabase.
  C. TahleToFile
  D. JobletToFile
  A. TabletoTable
  C. TahleToFile

  ---

  explanation:

  Explanation

  Talend Studio provides templates that allow you to create ready-to-run Jobs for common scenarios, such as Table to Table, File to Database, Table to File, etc. You can access these templates from the Repository > Job Designs > Create Job from Template menu. Joblet to File is not a valid template name.

• Question 9:

  You have two Talend Jobs. Job A need to call Job

  B. After Job B is complete, processed data stored in the tBufferOutput buffer memory must be transferred back to Job A.

  How can you achieve this requirement?

  A. Select the Transmit whole context in the basic settings of the tRunJob when calling Job B from Job A.
  C. Select the Propagate the child result to output schema in Advanced settings of the tRunJob when calling Job B from Job
  D. Select the Propagate the child result to output schema in the Basicsettings of the tRunJob when calling B from Job A.
  C. Select the Propagate the child result to output schema in Advanced settings of the tRunJob when calling Job B from Job

  ---

  explanation:

  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. To transfer processed data stored in the tBufferOutput buffer memory back to the parent job, you need to select the Propagate the child result to output schema option in the Advanced settings of the tRunJob component. This option allows you to retrieve the data from the tBufferOutput component of the child job and send it to an output row of the parent job. The tBufferOutput component is used to store data in memory without writing it to disk or database. You can use this component to optimize the performance and memory usage of your job. You do not need to select the Transmit whole context option in either Basic or Advanced settings of the tRunJob component. This option allows you to pass all the context parameters from the parent job to the child job without specifying them individually. This option does not affect the data transfer from the tBufferOutput component. You also do not need to select the Propagate the child result to output schema option in Basic settings of the tRunJob component, as this option is only available in Advanced settings.

  References: Talend Open Studio: Open-source ETL and Free Data Integration | Talend, [tRunJob properties - 7.3], [tBufferOutput properties - 7.3], [Contexts - 7.3]

• Question 10:

  Which statements are true about configuring the input sources of a tMap component?

  Choose answers

  A. You can use the up and down arrows to interchange the order of the Lookup tables.
  B. Thy main input source is always placed on topand cannot be moved within the tMap component.
  C. The main input source will always be placed on top by default hut ran be dragged to any position.
  D. The order in which the input sources appear on the map does not matter, provided the joins are configured correctly.
  A. You can use the up and down arrows to interchange the order of the Lookup tables.
  B. Thy main input source is always placed on topand cannot be moved within the tMap component.

  ---

  explanation:

  Explanation

  The tMap component allows you to configure multiple input sources for your data transformation and mapping. The main input source is always placed on top of the tMap component and cannot be moved within it. The main input source provides the data flow that drives the processing of the tMap component. The lookup tables are placed below the main input source and can be reordered by using the up and down arrows on the toolbar. The order in which the lookup tables appear on the tMap component does not affect the functionality of the joins, as long as they are configured correctly with the appropriate join conditions and expressions.

  References: Talend Open Studio: Open- source ETL and Free Data Integration | Talend, [tMap properties - 7.3]