更新されたのは2024年04月試験エンジンはData-Integration-Developer無料お試しサンプルが365日更新されます
試験合格保証Data-Integration-Developer試験には正確な問題解答付き！
質問 # 26
Where can you simultaneously define primary keys for the Update and Delete operations in a tMysqlOutput component?
- A. Advanced settings view, select the Use hint options check box
- B. Advanced settings view, select the Use field options check box
- C. Advanced settings view, select the Additional columns options check box
- D. Basic settings view, select the Use field options check box
正解：B
解説：
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]
質問 # 27
You created a Job to process a customer database. Next, you want to debug the Job using Traces Debug and pause the execution when it encounters any records for customers residing in the state of California.
- A. Open the Debug Run tab of the Run view and click Traces Debug.
- B. Right-click the trace on the output of the input component and select Show Breakpoint Setup.
- C. Right-click the trace on the output of the input component and select Add Breakpoint.
- D. Add a breakpoint in the Advanced Settings tab of the Run view.
正解：B
解説：
Explanation
To debug a job using Trace Debug mode and pause the execution when it encounters any records for customers residing in the state of California, you need to right-click on the trace on the output of the input component and select Show Breakpoint Setup option. 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. A trace is a link that shows the data flow between components in your job design workspace.
The Show Breakpoint Setup option allows you to set a breakpoint on a trace based on a condition or an expression. A breakpoint is a point 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. You can access this option by right-clicking on a trace on your job design workspace and selecting Show Breakpoint Setup. This will open a dialog box where you can enter a condition or an expression for your breakpoint.
For example, if you want to pause your job execution when it encounters any records for customers residing in the state of California, you can enter this condition for your breakpoint:
row1.state == "CA"
This will make your job stop at the trace where this condition is met and show you the values of each column for that row.
You do not need to add a breakpoint in Advanced settings tab of Run view, open Debug Run tab of Run view and click Trace Debug button, or right-click on trace on output of input component and select Add Breakpoint option. These options are not used to set breakpoints based on conditions or expressions. The Advanced settings tab of Run view is used to configure advanced settings for your job execution, such as JVM arguments, statistics parameters, implicit context load parameters, etc. The Debug Run tab of Runview is used to access Trace Debug mode, but not to set breakpoints. The Add Breakpoint option is used to add a simple breakpoint on a trace without any condition or expression. References: Talend Open Studio: Open-source ETL and Free Data Integration | Talend, [Trace Debug mode - 7.3], [Breakpoints - 7.3]
質問 # 28
You are building a Job to run outsode Talend Studio that must run on both Linux and Windows.
Which action should you take when building the Job?
- A. Build one package for each platform.
- B. Configure the Job properties building the Job.
- C. Specify All for the Shell launcher option in the Build Job windows.
- D. Select Build Job because Jobs are runnable on all platforms
正解：C
解説：
Explanation
To build a job to run outside Talend Studio that must run on both Linux and Windows, you need to select Build Job because jobs are runnable on all platforms. The Build Job 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 specify All for the Shell launcher option in the Build Job window, configure the job properties before building the job, or build one package for each platform. These methods are not necessary or available in Talend Studio and may cause errors or unexpected results. References: Talend Open Studio:
Open-source ETL and Free Data Integration | Talend, [Build Job - 7.3]
質問 # 29
Which methods car you use to specify the schema in a tFilelnputDelimited component?
Choose 3 answers
- A. Drag a generic schema metadata item onto the Designer.
- B. Add the component then drag and drop a generic schema metadata item onto the component.
- C. Drag a File delimited metadata item from the Repository onto the design workspace.
- D. Add the component, open the Component view, select the Built-in schema type, then click the Edit schema button.
- E. Add the schema to the component using the Schema Editor
正解：B、C、D
解説：
Explanation
The methods that you can use to specify the schema in a tFileInputDelimited component are:
Add the component then drag and drop a generic schema metadata item onto the component. This method allows you to reuse an existing schema that is stored in the Metadata section of the Repository.
A generic schema is a schema that is not associated with any specific file format or connection type.
You can create a generic schema by right-clicking on Generic Schema in the Repository and selecting Create Generic Schema.
Drag a File delimited metadata item from the Repository onto the design workspace. This method allows you to create a new tFileInputDelimited component with a predefined schema that is based on a specific delimited file. A File delimited metadata item is a metadata item that contains information about a delimited file, such as its path, format, encoding, field separator, etc. You can create a File delimited metadata item by right-clicking on File delimited in the Repository and selecting Create File delimited.
Add the component, open the Component view, select the Built-in schema type, then click the Edit schema button. This method allows you to create a custom schema for the tFileInputDelimited component within the Component view. A built-in schema is a schema that is defined locally for a specific component and cannot be reused by other components. You can edit a built-in schema by clicking on the Edit schema button in the Basic settings tab of the Component view.
質問 # 30
A colleague has exported a Data Integration Job to run outside Talend Studio.
How do you run the Job?
- A. Extract the contents of the archive and run the batch file and shell script.
- B. Install the Job and start the resulting service.
- C. Extract the files from the archive and run the JAR file.
- D. Extract the content of the archive and run the batch file or the shell script.
正解：D
解説：
Explanation
To run a job that has been exported by a colleague to run outside Talend Studio, you need to extract the content of the archive and run the batch file or the shell script. The archive file contains all the files and libraries required to run the job independently from Talend Studio on any platform that supports Java. The archive file also contains two executable files: a batch file (.bat) for Windows platforms and a shell script (.sh) for Linux platforms. You need to run the appropriate file for your platform by double-clicking on it or using a command line tool. This will launch the job and display its output in a console window.
You do not need to extract the contents of the archive and run both the batch file and shell script, install the job and start the resulting service, or extract the files from the archive and run the JAR file. These methods are not correct or available in Talend Studio and may cause errors or unexpected results. References: Talend Open Studio: Open-source ETL and Free Data Integration | Talend, [Build Job - 7.3]
質問 # 31
You need to set up a server in your Talend environment that enables several members of your team to collaborate on a project.
Which application must you enable before working on a remote project?
- A. Talent Administration Center instance must be running with the team members and project configured.
- B. Talend admission Center service must be running on each development workstation.
- C. Git or SVN client must be installed on each developed workstation.
- D. Git or SVN server instance must be running.
正解：A、D
解説：
Explanation
To set up a server in your Talend environment that enables several members of your team to collaborate on a project, you need to enable two applications before working on a remote project: Git or SVN server instance and Talend Administration Center instance. These applications are used to manage version control and collaboration for your project.
Git or SVN server instance is a server application that allows you to store and track changes of your project files using a version control system. Git and SVN are two popular version control systems that are supported by Talend Studio. You need to have a Git or SVN server instance running and accessible by your team members before working on a remote project. You also need to have a Git or SVN client installed on each development workstation to connect to the server and perform version control operations.
Talend Administration Center is a web-based application that allows you to manage users, projects, tasks, execution servers, and licenses for your Talend environment. You need to have a Talend Administration Center instance running and accessible by your team members before working on a remote project. You also need to configure the team members and project settings in Talend Administration Center to grant access and permissions for your project. References: Talend Open Studio: Open-source ETL and Free Data Integration | Talend, [Version control - 7.3], [Talend Administration Center - 7.3]
質問 # 32
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. Navigate to @ Referenced project, @ project_ref, Job Designs, Standard, then select testJob.
- B. Right-click Job Designs and click import items.
- C. Navigate to Metadata, @ project ref, Job Designs, Standard, then select testJob.
- D. Right-click Job Designs, click Crete Standard Job, and enter testJob as the Job name.
正解：A
解説：
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]
質問 # 33
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. Denoting a milestone in the lifecycle of a project
- C. Denoting major or minor releases.
- D. Fixing hugs or enhancements.
正解：B
解説：
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.
References:
Talend Best Practices Guide:
https://help.talend.com/r/en-US/8.0/software-dev-lifecycle-best-practices-guide/branching-merging-and-ta Git documentation on tags: https://git-scm.com/docs/git-tag
質問 # 34
You need to calculate the total number of rows in an input file using a tMlelnputDelimited component.
Which code should you use in a tJava component to write a nb-line variable?
- A. Int nb_line=(integer)globalMap.put(''tFileInputDelimited_1_NB_LINE'')
- B. Int nb_line-(String)globalMap.put(''tFileInputDelimited_1_NB_LINE'')
- C. Int nb_line-(integer)globalMap.put(''tFileInputDelimited_1_NB_LINE'')
- D. Int nb.line-(integer)globalMap.put(''tFileInputDelimited_1_NB_LINE'')
正解：D
解説：
Explanation
You need to use the following code in a tJava component to write a nb_line variable:
int nb_line = (Integer)globalMap.get("tFileInputDelimited_1_NB_LINE");
This code retrieves the value of the global variable tFileInputDelimited_1_NB_LINE, which stores the number of rows processed by the tFileInputDelimited component, and assigns it to an integer variable named nb_line.
You can then use this variable to print or manipulate the number of rows in your Job. Note that you need to use globalMap.get, not globalMap.put, to access the value of a global variable.
質問 # 35
Where can you specify the remote JobServer to execute a Job?
- A. Target Exec tab in the Run view
- B. Run/Debug section in the Preference window
- C. Extra tab in the Job view
- D. Job settings section of the Project Settings windows
正解：A
解説：
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]
質問 # 36
Which options can you use to add a Joblet to your talend Job?
Choose 3 answers
- A. Type the Joblet name on the Studio canvas, then select if from the Palette drop-down menu.
- B. Right-click the Joblet from Palette and select the Add option.
- C. Drag the Joblet from Palette to the design workspace.
- D. Use a tRunJob component and select the Joblet from the drop-down menu.
- E. Drag theJobket from the Repository tree view to designer canvas.
正解：A、C、E
解説：
Explanation
To add a Joblet to your Talend Job, you can use one of these options:
Type the Joblet name on the Studio canvas, then select it from the Palette drop-down menu. This will create a Joblet container on your canvas that contains all the components and links of your Joblet.
Drag the Joblet from Repository tree view to designer canvas. This will also create a Joblet container on your canvas that contains all components and links of your Joblet.
Drag Joblet from Palette to design workspace. This will open a dialog box where you can select an existing Joblet from Repository or create a new one.
You cannot use a tRunJob component and select Joblet from drop-down menu, nor right-click Joblet from Palette and select Add option. 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]
質問 # 37
You have a MySQL table named customers with column named id, address, and country.You need to retrieve records that have a specific based on a variable.
Which steps should you use to achieve this?
- A. Use a tDBInput component with a Run fi trigger.
- B. Use a tDBInput component and link it to a tFilterColumns component.
- C. Use a tDBInput component and link to a tMatchGroup component.
- D. Use a tDBInput component with a context variable in the SQL query.
正解：D
解説：
Explanation
To retrieve records that have a specific value based on a variable, you can use a tDBInput component with a context variable in the SQL query. A context variable is a variable that can store a value that can be changed at runtime or between different contexts. A context variable can be used in various components to parameterize their properties or expressions. A tDBInput component is used to read data from a database table by executing an SQL query. You can use a context variable in the SQL query to filter the records based on a dynamic value.
For example, if you have a context variable named country that stores the value of the country you want to filter by, you can use it in the SQL query of the tDBInput component as follows:
SELECT id, address, country FROM customers WHERE country = 'context.country' This will retrieve only the records that have the same value as the context variable country in the country column.
You do not need to use a Run if trigger, a tMatchGroup component, or a tFilterColumns component to achieve this. A Run if trigger is used to execute a subjob conditionally based on a logical expression. A tMatchGroup component is used to group similar records based on matching rules and output them as master or duplicate records. A tFilterColumns component is used to select or remove columns from an input flow based on a list of column names. References: Talend Open Studio: Open-source ETL and Free Data Integration | Talend,
[Contexts - 7.3], [tDBInput properties - 7.3], [Run if properties - 7.3], [tMatchGroup properties - 7.3],
[tFilterColumns properties - 7.3]
質問 # 38
Which capabilities does Traces Debugprovide?
Choose 2 answers
- A. Breaking when an input column fulfills a condition
- B. Breaking on a selected line of code
- C. Filtering which data is propagated by a flow
- D. Advancing one column at a time
- E. Advancing one row at a time
正解：A、E
解説：
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]
質問 # 39
Where do you access the option to create a Joblet from an existing Job?
- A. Right-clicking the I oh in the Repository
- B. Adding a Joblet component to the Designer.
- C. Selecting the desired components and right-clicking.
- D. Selecting the File menu.
正解：C
解説：
Explanation
To create a Joblet from an existing Job, you can follow these steps:
Open the Job that you want to create a Joblet from.
Select the components that you want to include in the Joblet.
Right-click on the selected components and select Create Joblet from the context menu.
In the Create Joblet dialog box, enter a name and description for the Joblet.
Click Finish to create the Joblet.
References:
Talend Open Studio User Guide: Creating a Joblet from a Job:
https://help.talend.com/r/en-US/8.0/studio-user-guide/creating-joblet-from-job
質問 # 40
What determines the name of the tMap output row that delivers join rejects?
- A. The name is determined by the input table, you create to generate the rejects.
- B. The name is predetermined; it is always named Innerjoin Reject.
- C. The name is configurable in the Component view of the tMapcomponent
- D. The name is determined by the output table you create to catch the rejects.
正解：D
解説：
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,
質問 # 41
......
Talend Data-Integration-Developer 認定試験の出題範囲：
| トピック | 出題範囲 |
|---|---|
| トピック 1 |
|
| トピック 2 |
|
| トピック 3 |
|
| トピック 4 |
|
| トピック 5 |
|
試験問題はData-Integration-Developer最新版を提供するのはテストエンジン：https://jp.fast2test.com/Data-Integration-Developer-premium-file.html