Talend TALEND-TDICD Online Practice Questions and Exam Preparation

Talend TALEND-TDICD Online Questions & Answers

• Question 1:

  You have a Job that uses a tFileInputDelimited component to extract data from an input file. You built a spate subjob, called W, to handle the condition when the input file is empty.

  Which condition syntax is correct for the Run if connection?

  A. ((Integer)globalMap.get(`'tFieldInputDelimited_1NB_LINES''))=0
  B. ((Integer)globalMap.get(`'tFieldInputDelimited_1NB_LINES''))--0
  C. ((Integer)globalMap.get(`'tFieldInputDelimited_1NB_LINES''))-0
  D. ((Integer)globalMap.get(`'tFieldInputDelimited_1NB_LINES''))===0
  C. ((Integer)globalMap.get(`'tFieldInputDelimited_1NB_LINES''))-0

  ---

  Explanation

  To reference the value of a context variable you defined, you can use the syntax context.variable_name, where variable_name is the name of the context variable. For example, if you have a context variable named path, you can reference its value by using context.path. You do not need to specify the context name (such as test or prod) or use parentheses or brackets around the variable name.

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

• Question 2:

  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

  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 3:

  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.
  D. Navigate to @ Referenced project, @ project_ref, Job Designs, Standard, then select testJob.

  ---

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

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

• Question 4:

  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
  D. Target Exec tab in the Run view

  ---

  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.

  References: 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 5:

  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

  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 6:

  Which section in Talend Studio allows you to graphically connect components in a Job to run a dataflow process?

  A. Design workspace
  B. Component view
  C. Repository
  D. Code
  A. Design workspace

  ---

  Explanation

  The design workspace in Talend Studio allows the user to graphically connect components in a Job to run a dataflow process. The design workspace is the main area where the user can design the data integration logic by dragging and dropping components from the palette and linking them with connectors. The design workspace also shows the schema of each component, which defines the structure and type of the data.

• Question 7:

  Using the following input file format as an example:

  

  Which tFileinputDelimted component parameters should you configure to parse the input file correctly? Choose 3 answers

  A. Limit
  B. Schema
  C. Field separator
  D. Footer
  E. Header
  B. Schema
  C. Field separator
  E. Header

  ---

  Explanation

  Using the following input file format as an example:

  Name, Phone Abraham Smith, 510-555-5555 ... Steven Doe, 613-555-5555

  The tFileInputDelimited component parameters that you should configure to parse the input file correctly are Schema, Field separator, and Header. The Schema parameter defines the structure and type of the data in the input file. You can

  use a built-in schema or a repository schema to specify the columns and their properties. The Field separator parameter defines the character that separates each field in a row of data. In this case, it is a comma (,). The Header parameter

  defines the number of rows to be skipped at the beginning of the file. In this case, it is 1, as the first row contains the column names.

• Question 8:

  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
  B. Right-click the Job in the Repository and select Build Job

  ---

  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.

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

• Question 9:

  You need to create a centralized metadata connection to database server for an application.

  Which steps should you take before building a Job that reads from that database?

  Choose 3 answers

  A. Add a tMap component handle and convert DB Types.
  B. Retrieve schemas from the database connection.
  C. Drag the Db Connection metadata into the Designer to read from the database component.
  D. Create DB Connections metadata to describe the database connection.
  E. Add a tCreatTable component to create a table in the database.
  B. Retrieve schemas from the database connection.
  C. Drag the Db Connection metadata into the Designer to read from the database component.
  D. Create DB Connections metadata to describe the database connection.

  ---

  Explanation

  To create a centralized metadata connection to a database server for an application, you need to take the following steps before building a job that reads from that database:

  Create DB Connections metadata to describe the database connection. You can do this by right-clicking on the DB Connections node in the Repository and selecting Create Connection. You can then enter the connection details, such as

  host, port, database, username, password, etc., and test the connection. Retrieve schemas from the database connection. You can do this by expanding the DB Connections node in the Repository and right-clicking on the connection you

  created. You can then select Retrieve Schema and choose the tables or views you want to import as metadata schemas. You can also edit or customize the schemas as needed.

  Drag the DB Connection metadata into the Designer to read from the database component. You can do this by dragging the connection or a specific schema from the Repository to the Designer workspace. This will automatically create a

  database input component (such as tMysqlInput) that is configured with the connection and schema properties. You can then use this component to read data from the database in your job.

  You do not need to add a tMap component to handle and convert DB Types, nor a tCreateTable component to create a table in the database. These components are not required for reading data from an existing database, but they can be

  used for other purposes, such as transforming or writing data.

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

• Question 10:

  Which exceptions car be caught using tLogCatcher?

  Choose 3 answers

  A. tWarn
  B. tDie
  C. Java Exception
  D. OnbubjobError Exception
  E. tAssertCatcher
  A. tWarn
  B. tDie
  C. Java Exception

  ---

  Explanation

  The tLogCatcher component can catch exceptions from three types of components: tWarn, tDie, and Java Exception. The tWarn component is used to trigger a warning message that can be caught by the tLogCatcher component for an exhaustive log. The tDie component is used to stop the execution of a job or a subjob and return an error code that can be caught by the tLogCatcher component for an exhaustive log. The Java Exception component is used to handle any Java exception that occurs during the execution of a job or a subjob and pass it to the tLogCatcher component for an exhaustive log. The tLogCatcher component cannot catch exceptions from other types of components, such as OnSubjobError Exception or tAssertCatcher. The OnSubjobError Exception is a trigger that is activated when an error occurs in a subjob and can be used to perform some actions after the error, such as sending an email or logging a message. The tAssertCatcher component is a component that collects the assert data generated by the tAssert component and passes it on to the output defined. The tAssert component is used to verify if a condition is true or false and generate an assert data accordingly.

  References: Talend Open Studio: Open-source ETL and Free Data Integration | Talend, [tLogCatcher properties - 7.3], [tWarn properties - 7.3], [tDie properties - 7.3], [Java Exception properties

  - 7.3], [OnSubjobError properties - 7.3], [tAssertCatcher properties - 7.3], [tAssert properties - 7.3]