Talend TALEND-TDICD Online Practice Questions and Exam Preparation

Talend TALEND-TDICD Online Questions & Answers

• Question 41:

  Which statements ate true about a tWarn component?

  Choose 2 answers

  A. Used alongside a tLogCatcher in order for the log data collected to be encapsulated and passed on to the output defined.
  B. Used only in conjunction with the log4j feature.
  C. Used to trigger a warning often caught by the tLogCatcher component for an exhaustive log.
  D. Used only in conjunction with a iLogCatcher component.
  A. Used alongside a tLogCatcher in order for the log data collected to be encapsulated and passed on to the output defined.
  C. Used to trigger a warning often caught by the tLogCatcher component for an exhaustive log.

  ---

  Explanation

  The tWarn component is used to trigger a warning message that can be caught by the tLogCatcher component for an exhaustive log. The tLogCatcher component is a component that collects the log data generated by the tWarn, tDie, and Java Exception components and passes it on to the output defined. The tWarn component can be used alongside a tLogCatcher component in order for the log data collected to be encapsulated and passed on to the output defined. The tWarn component can also be used independently of the tLogCatcher component, but in that case, the warning message will only be displayed in the console. The tWarn component is not used only in conjunction with the log4j feature, nor only in conjunction with a tLogCatcher component. The log4j feature is a logging framework that allows you to customize the logging level, format, and destination of your log messages. You can enable or disable the log4j feature in Talend Studio by checking or unchecking the Use log4j option in the Preferences menu. The tLogCatcher component can catch log data from other components besides the tWarn component, such as the tDie and Java Exception components.

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

• Question 42:

  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

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

  Which Action on table operations are supported by a tMysqlOutput component?

  Choose 3 answers

  A. Drop table if exists andcreate
  B. Create table
  C. Replace
  D. Drop table
  E. Create table if does not exists
  A. Drop table if exists andcreate
  B. Create table
  E. Create table if does not exists

  ---

  Explanation

  The tMysqlOutput component is used to write data into a MySQL database table. The Action on table parameter of this component allows you to specify what operation to perform on the table before loading data into it. The Action on table

  parameter supports the following operations:

  Drop table if exists and create: This operation drops the table if it already exists in the database and creates a new one with the same name and structure as defined in the schema.

  Create table: This operation creates a new table in the database with the name and structure as defined in the schema. If a table with the same name already exists, an error will be raised.

  Create table if does not exist: This operation creates a new table in the database with the name and structure as defined in the schema only if there is no table with the same name already existing in the database. If a table with the same

  name already exists, no action will be taken.

  The Action on table parameter does not support the following operations:

  Replace: This is not an operation on the table, but on the data. The Replace parameter of the tMysqlOutput component allows you to specify whether to replace existing rows in the table with new rows based on a key attribute or to insert new

  rows only.

  Drop table: This is not an operation on the table, but on the database. The Drop table parameter of the tMysqlConnection component allows you to specify whether to drop the table after closing the connection or not.

  References: Talend

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

• Question 44:

  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

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

  Which statement is true about the Sync columns button on the Basic settings tab of the Component view? Choose 2 answers

  A. Retrieves and synchronizes the output file schema with the input file schema for tFileOutputed limited.
  B. Retrieves the schema of the current component to match the Next component
  C. Retrieves the schema from the input component connected in the lob.
  D. Retrieves and synchronizes the output schema with the input schema for tJavaRow.
  C. Retrieves the schema from the input component connected in the lob.
  D. Retrieves and synchronizes the output schema with the input schema for tJavaRow.

  ---

  Explanation

  The Sync columns button on the Basic settings tab of the Component view retrieves the schema from the input component connected in the Job and synchronizes it with the current component's schema. This button is available for most of the components that have an input and an output schema, such as tJavaRow, tMap, tFileOutputDelimited, etc. However, this button does not retrieve and synchronize the output file schema with the input file schema for tFileOutputDelimited, as this component only has one output schema.

• Question 46:

  Which statements are true about Use or register ashared DB Connection option in Talend Studio?

  Choose 3 answers

  A. Compatible with the Use an independent process to run subJob option of tKunJob component
  B. Compatible tobesnared between parent and childJobs
  C. Compatiblewith The Use dynamicjob option of TRunJob component
  D. Incompatible with the Use an independent process to run subJob option of tRunJob component
  E. Incompatible with the Use dynamic job option of tRunJob component
  B. Compatible tobesnared between parent and childJobs
  D. Incompatible with the Use an independent process to run subJob option of tRunJob component
  E. Incompatible with the Use dynamic job option of tRunJob component

  ---

  Explanation

  The Use or register a shared DB Connection option in Talend Studio is an option that allows you to share a single database connection between multiple components in a job or between parent and child jobs. This option can improve the performance and efficiency of your job by avoiding opening and closing multiple connections to the same database. The Use or register a shared DB Connection option is compatible with the following scenarios: Sharing a connection between parent and child jobs. You can use this option to pass a database connection from a parent job to a child job that is called by a tRunJob component. This way, you do not need to create a new connection in the child job, but reuse the existing one from the parent job. Sharing a connection between components in the same subjob. You can use this option to register a database connection in one component (such as tMysqlConnection) and use it in other components (such as tMysqlInput or tMysqlOutput) in the same subjob. This way, you do not need to configure each component with the same connection properties, but use a shared one. The Use or register a shared DB Connection option is incompatible with the following scenarios: Using an independent process to run subjob option of tRunJob component. This option allows you to run a child job in a separate JVM process from the parent job. This option is not compatible with sharing a database connection, because each JVM process has its own memory space and cannot access the objects of another process. Using dynamic job option of tRunJob component. This option allows you to call a child job dynamically based on a context variable that contains the name of the child job. This option is not compatible with sharing a database connection, because dynamic jobs are loaded at runtime and cannot access the metadata of other jobs.

  References: Talend Open Studio: Open-source ETL and Free Data Integration | Talend, [Use or register a shared DB Connection - 7.3], [tRunJob properties - 7.3]

• Question 47:

  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 thesame context variable of the Jobin which it is used.
  B. A Joblet uses the same context variables of the Job in which it is used, unlinke 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 thesame context variable of the Jobin which it is used.

  ---

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

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

• Question 48:

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

  A. The name is predetermined; it is always named Innerjoin Reject.
  B. The name is determined by the output table you create to catch the rejects.
  C. The name is configurable in the Component view of the tMapcomponent
  D. The name is determined by the input table, you create to generate the rejects.
  B. The name is determined by the output table you create to catch the rejects.

  ---

  Explanation

  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.

  References: Talend Open Studio:

  Open-source ETL and Free Data Integration | Talend,

• Question 49:

  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

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

  How are contexts defined?

  A. They are automatically defined by the types of components used in the Job.
  B. Talend Studio defines a default context, and you can define more as needed.
  C. You must define the contexts
  D. In addition to a default context, Talend Studio defines a list of standard contexts you can use in your Ions.
  C. You must define the contexts

  ---

  Explanation

  Contexts are a way of defining different sets of values for variables that are used in a job. For example, you can define a context for testing and another context for production, with different values for the database connection parameters, file paths, etc. You can then switch between the contexts easily without modifying the job design. Contexts are not automatically defined by the types of components used in the job, nor by Talend Studio. You must define the contexts yourself in the Contexts tab of your job. You can also create context groups in the Repository and reuse them in multiple jobs.

  References: Talend Data Integration -- Software to Connect, Access, and Transform Data | Talend,