Talend Data-Integration-Developer Exam Practice Test Instant Access

Question 1

Which characteristics distinguish Traces Debug from Java Debug?

Choose 2 answers

AAllow row-by-row inspection of data flows

BRequires a separate perspective

CRequire Java development experiences

DSupports breakpoints based on input data condition

Answer : A, D

Trace Debug and Java Debug are two modes that allow you to debug your jobs in Talend Studio. Trace Debug mode allows you to trace each row processed by your job components and see the values of each column in each row. 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.

The characteristics that distinguish Trace Debug from Java Debug are:

Trace Debug mode allows row-by-row inspection of data flows, while Java Debug mode does not. Data flows are the links that show 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. You can also use filters to display only the rows that match a condition or an expression. In Java Debug mode, you cannot see the data flow on each trace or inspect the values of each column for each row.

Trace Debug mode supports breakpoints based on input data condition, while Java Debug mode does not. Breakpoints are points where the execution of your job pauses and waits for your action. You can use breakpoints to inspect your data or debug your logic at specific points of your job execution. In Trace Debug mode, 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. In Java Debug mode, you can only set breakpoints on lines of code based on a condition or an expression that involves variables or expressions.

The characteristics that do not distinguish Trace Debug from Java Debug are:

Both modes require a separate perspective. A perspective is a set of views and editors that are arranged in a specific way to support a specific task. In Talend Studio, you can switch between different perspectives, such as Integration, Debug, Profiling, etc. To use Trace Debug mode, you need to switch to the Debug perspective by clicking on the Open Perspective button and selecting Debug. To use Java Debug mode, you need to switch to the Java perspective by clicking on the Open Perspective button and selecting Java.

Neither mode requires Java development experience. Although Java Debug mode allows you to debug your job code in Java or Perl, you do not need to have Java development experience to use it. You can use the graphical interface of Talend Studio to design your job components and properties without writing any code. You can also use the Code view to see the generated code of your job in Java or Perl and modify it if needed. However, you do not need to write any code from scratch or understand all the details of the code to use Java Debug mode.Reference:Talend Open Studio: Open-source ETL and Free Data Integration | Talend, [Trace Debug mode - 7.3], [Java Debug mode - 7.3]

Question 2

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

AMatch Model parameter field for fine of the inputs

BExpression field for a single column of the output

CExpression filter in the output table

DMatch Model parameter field for one of the main inputs

Answer : C

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.Reference:Talend Open Studio: Open-source ETL and Free Data Integration | Talend

Question 3

You have a tMap component configured with a single input row1 and three outputs: CA, NY, Rejects. The input row1 consists of two columns. Name and State, containing the following data:

All outputs map only the Name column from row1, but CA employs a filter expression, CA.equals(row1.state), while Ny employs a filter expression, NY. Equals(row1, State). All Rejects have no such configuration.

Under these conditions, how does data flow to the outputs?

ACA:Thomas Coolidge Andrew TyalorlNY;Calvin Adams;rejects;none

BCA:Thomas Coodge;Calvin Adams; rejects:Andrew Taylor

CCA:Thomas Coolidge;Ny:Calvin Adams;rejects:Thomas Coolidge, adrew taylor, Calvin Adame

DCA:Thomas Coolidge, Andrew Taylor;Ny:Calvin Adams; rejects:Thomas Coolidge, Andrew Taylor,Calvin Adams

Answer : B

The tMap component allows you to configure multiple outputs for your data transformation and mapping. You can apply filter expressions on each output to filter out the rows that meet certain criteria. For example, if you want to send only the rows that have CA as the state value to one output, you can use CA.equals(row1.state) as the filter expression for that output. The filter expression evaluates to true or false for each row, and only the rows that evaluate to true are sent to the output. In this case, only Thomas Coolidge and Andrew Taylor have CA as their state value, so they are sent to the CA output. Similarly, only Calvin Adams has NY as his state value, so he is sent to the NY output. The Rejects output has no filter expression, so it receives all the rows from the input by default. However, since there is a conflict between the CA and NY outputs and the Rejects output, only the rows that are not sent to any other output are sent to the Rejects output. In this case, there are no such rows, so the Rejects output receives no data.Reference:Talend Open Studio: Open-source ETL and Free Data Integration | Talend,

Question 4

What determines the name of the tMap output row that delivers join rejects?

AThe name is predetermined; it is always named Inner join Reject.

BThe name is determined by the output table you create to catch the rejects.

CThe name is configurable in the Component view of the tMap component

DThe name is determined by the input table, you create to generate the rejects.

Answer : B

The tMap component allows you to configure different types of joins between the main input and the lookup tables, such as inner join, left outer join, right outer join, etc. An inner join returns only the matching rows from both tables based on a join condition. If a row from the main input does not match any row from the lookup table, it is considered as an inner join reject. You can configure an output to collect these rejects by setting the Catch inner join reject option to true. The name of the output row that delivers the join rejects is determined by the output table you create to catch the rejects. You can name the output table as you wish, such as Rejects, Errors, etc.Reference:Talend Open Studio: Open-source ETL and Free Data Integration | Talend,

Question 5

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

Choose answers

AYou can use the up and down arrows to interchange the order of the Lookup tables.

BThy main input source is always placed on top and cannot be moved within the tMap component.

CThe main input source will always be placed on top by default hut ran be dragged to any position.

DThe order in which the input sources appear on the map does not matter, provided the joins are configured correctly.

Answer : A, B

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.Reference:Talend Open Studio: Open-source ETL and Free Data Integration | Talend, [tMap properties - 7.3]

Question 6

You have a tMap component whose main input provides the following data:

There is also a lookup table with the following data:

An inner join is configured between the State column of the main input with the State Code column of the lookup table.

What happens when the row containing the name Andrew laylor is processed?

AIf an output is configured to collect inner join rejects, the data flows to that output as well as the main output.

BIf an output is not configured to collect inner join rejects, an error condition is raises.

CIf an output is not configured to collect inner Join rejects, the data flows to the main output.

DIf an output is configured to collect inner join rejects, the data flows only to that output.

Answer : D

The tMap component allows you to perform data transformations and joins between multiple input sources and output targets. You can configure different types of joins between the main input and the lookup tables, such as inner join, left outer join, right outer join, etc. An inner join returns only the matching rows from both tables based on a join condition. If a row from the main input does not match any row from the lookup table, it is considered as an inner join reject. You can configure an output to collect these rejects by setting the Catch inner join reject option to true. If you do so, the data will flow only to that output and not to the main output. If you do not configure an output to collect the rejects, the data will be ignored and no error will be raised.Reference:Talend Open Studio: Open-source ETL and Free Data Integration | Talend, [tMap 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?

ASet the Property type to Repository and replace the credential1; in each component.

BSet the Property type to Built-in and set all the relevant properties manually.

CSet the Database file to Metadata

DSet the Property type, to Repository and use a common DB connection metadata

Answer : B

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.Reference:Talend Data Integration --- Software to Connect, Access, and Transform Data | Talend, [tDBInput properties - 7.3]

Talend Data Integration Certified Developer Exam Practice Test