Talend Core Developer 시험 - Talend실제시험문제와 답 - 55문항

Question No : 1

Which type of task can be added to a plan in Talend Management Console?

A.Data services
B.Big Data tasks
C.Routes
D.Jobs

정답:
Explanation:
Comprehensive and Detailed
In Talend Management Console (TMC), a plan is a sequence of tasks executed in a defined order. The types of tasks that can be added to a plan include:
Jobs (Option D): Standard data integration tasks designed in Talend Studio.
Big Data tasks (Option B): Tasks involving big data processing.
Routes (Option C): Tasks related to messaging routes.
However, Data services (Option A) refer to web services and are not typically added as tasks within a plan.
Reference: Talend Management Console User Guide

Question No : 2

You created a Remote Engine in Talend Cloud and copied the Remote Engine key. You downloaded the Remote Engine script for your Linux system, and now you need to pair the engine manually.
Which options can you use to set the key? Choose 2 answers.

A.In Studio Talend Cloud preferences.
B.In the Remote Engine web service page.
C.In the key configuration file of the engine.
D.In the engine run script command line as a parameter.

정답:
Explanation:
Comprehensive and Detailed
To manually pair a Remote Engine with Talend Cloud, you can set the pairing key using the following methods:
In the Remote Engine web service page (Option B):
Access the Remote Engine's web interface, typically available at http://localhost:8043/configuration.
Enter the pairing key obtained from the Talend Management Console.
Click on PAIR REMOTE ENGINE to establish the connection.
In the key configuration file of the engine (Option C):
Locate the preauthorized.key.cfg file in the Remote Engine's etc directory.
Open the file and paste the pairing key into the remote.engine.pre.authorized.key parameter.
Save the changes and restart the Remote Engine to apply the configuration.
Why not other options?
Option A: Setting the pairing key in Talend Studio's preferences is not applicable for pairing a Remote Engine.
Option D: While it's technically possible to pass the pairing key as a parameter in the engine's run script, it's not the standard or recommended method.
Reference: Talend Remote Engine User Guide

Question No : 3

You implemented a Job in Talend Studio and need to execute it in Talend Cloud.
Which options can you use in Talend Management Console after publishing the Job to Talend Cloud? Choose 2 answers.

A.Add a task and then run the task.
B.Click the artifact name and then run the Job.
C.Select the corresponding task, configure the task, and then run the task.
D.Select the artifact name, add and configure a task, then run the task.

정답:
Explanation:
Comprehensive and Detailed
After publishing a Job from Talend Studio to Talend Cloud, you can execute it using the Talend Management Console (TMC) by following these steps:
Add a task and then run the task (Option A):
In TMC, navigate to the Management section and select Tasks.
Click on Add Task, choose the published artifact (your Job), configure necessary parameters, and save the task.
Once the task is created, you can run it manually or schedule it for execution.
Select the artifact name, add and configure a task, then run the task (Option D):
In TMC, go to the Artifacts section to view your published Jobs.
Select the desired artifact and click on Add Task.
Configure the task settings as needed and save it.
After creating the task, you can execute it immediately or set up a schedule.
Why not other options?
Option B: TMC does not support directly running a Job by clicking on the artifact name without first creating a task.
Option C: While you can select and configure an existing task, the initial step requires creating the task associated with the artifact.
Reference: Talend Management Console User Guide

Question No : 4

After enabling the Observability Metric Collector metric generation located in the \etc\org.talend.ipaas.rt.observability.cfg, which additional configurations should you apply? Choose 2 answers.

A.Schedule the metrics generation using CRON based trigger
B.Configure the time zone
C.Frequency
D.Lifetime

정답:
Explanation:
Comprehensive and Detailed
After enabling the Observability Metric Collector in Talend's configuration file (org.talend.ipaas.rt.observability.cfg), it's essential to set additional parameters to control the behavior of metric collection:
Frequency (Option C): Determines how often metrics are collected. Setting this ensures that data is gathered at appropriate intervals for monitoring needs.
Lifetime (Option D): Specifies how long the collected metrics are retained. This helps manage storage and ensures that outdated metrics are purged.
Configuring these parameters ensures that the metric collection aligns with organizational requirements for monitoring and performance analysis.
Reference: Talend Observability Configuration Guide

Question No : 5

Which component can be used to read a CSV file in an ESB Route?

A.tFileInputDelimited
B.cMap
C.cFileInputDelimited
D.cFile
E.tMap

정답:
Explanation:
Comprehensive and Detailed
In Talend's Enterprise Service Bus (ESB) routes, the appropriate component to read a CSV file is cFileInputDelimited. This component is specifically designed for Camel routes to handle delimited files like CSVs.
Reference: Talend ESB Components Documentation

Question No : 6

You are using a tRESTClient component to call a REST service.
Which advanced option should you use to convert the response from the server to the document type?

A.Convert Response To XML Document
B.Convert Response To JSON Document
C.Convert Response To DOM Document
D.Convert Response To HTML Document

정답:
Explanation:
Comprehensive and Detailed
In Talend Studio, the tRESTClient component includes an advanced setting called "Convert Response To DOM Document". When this option is selected, the response from the REST service is converted into a DOM (Document Object Model) document. This allows for structured processing of the response data within Talend workflows.
Reference: Talend Components Documentation

Question No : 7

Which HTTP methods are supported by tRESTRequest?

A.GET, POST, PUT, PATCH, and DELETE
B.POST, PATCH, and UPDATE
C.SELECT, INSERT, UPDATE, and DELETE
D.GET, POST, UPDATE, and DELETE

정답:
Explanation:
Comprehensive and Detailed
The tRESTRequest component in Talend Studio is designed to handle RESTful web service requests. It supports the following HTTP methods:
GET: Retrieves data from the server.
POST: Submits data to the server, often causing a change in state or side effects.
PUT: Replaces all current representations of the target resource with the request payload.
PATCH: Applies partial modifications to a resource.
DELETE: Removes the specified resource from the server.
Therefore, the correct answer is
A. GET, POST, PUT, PATCH, and DELETE.
Reference: Talend Components Documentation, HTTP Methods Overview

Question No : 8

You can initialize your component endpoint, API mappings, and documentation from your API definition.
Which API definitions are supported by tRESTRequest?

A.CSV definition file
B.XML definition file
C.WSDL file
D.OAS/Swagger 2.0 file

정답:
Explanation:
Comprehensive and Detailed
The tRESTRequest component supports OpenAPI Specification (OAS)/Swagger 2.0 for initializing component endpoints, API mappings, and documentation.
OAS/Swagger 2.0 file (Correct Answer - Option D):
tRESTRequest allows API-first development by importing a Swagger 2.0 (OAS) definition.
This enables automatic configuration of API endpoints, request parameters, and response structures.
Why not other options?
CSV definition file (Option A): Not a valid API definition format.
XML definition file (Option B): XML files are not standard for REST API definitions.
WSDL file (Option C): WSDL is used for SOAP-based web services, not REST.
Reference: Talend API Development Guide, Talend REST Component Documentation

Question No : 9

What is the default port for the REST Endpoint when using tRESTRequest in Talend Studio?

A.5040
B.5070
C.8040
D.8090

정답:
Explanation:
Comprehensive and Detailed
The default REST endpoint port for tRESTRequest in Talend Studio is 8090.
Port 8090 (Correct Answer - Option D):
When running a REST service inside Talend Studio, the default listening port is 8090.
This can be changed in the component settings if required.
Other port options explained:
5040 & 5070: Not default ports used for Talend REST services.
8040: Used in Talend Runtime, not in Studio.
Reference: Talend Studio User Guide, Talend ESB REST Service Configuration

Question No : 10

How can you create REST API metadata in Talend Studio? Choose 2 answers.

A.Create it manually in Talend Studio.
B.Import it from Talend API Designer.
C.Import it from a JSON file.
D.Import it from Talend API Tester.

정답:
Explanation:
Comprehensive and Detailed
In Talend Studio, REST API metadata can be created using the following methods:
Create it manually in Talend Studio (Option A):
Users can define REST API metadata within Talend Studio by manually specifying API structure, endpoints, HTTP methods, and parameters.
This method provides full control over the API metadata but requires manual configuration.
Import it from Talend API Designer (Option B):
If an API has been designed using Talend API Designer, it can be imported into Talend Studio.
This enables reusing the API design directly without manual recreation.
Why not other options?
Option C (Import from JSON file): Talend Studio does not support direct import of REST API metadata from generic JSON files.
Option D (Import from Talend API Tester): Talend API Tester is used for testing APIs but does not provide an option to import API definitions into Talend Studio.
Reference: Talend Studio User Guide, Talend API Development Documentation

Question No : 11

You have a MySQL table named customers with columns named id, name, address, and country. You need to retrieve records that have a specific country based on a variable.
Which steps should you use to achieve this?

A.Use a tDBInput component with a context variable in the SQL query.
B.Use a tDBInput component and link it to a tMatchGroup component.
C.Use a tDBInput component with a Run if trigger.
D.Use a tDBInput component and link it to a tFilterColumns component.

정답:
Explanation:
Comprehensive and Detailed
To filter records based on a specific country dynamically, the best approach is using a tDBInput component with a context variable in the SQL query (Option A).
Step-by-Step Process:
Define a Context Variable:
In the Context Variables section of Talend Studio, create a new variable (context.country) and set its value dynamically.
Configure tDBInput:
Drag and drop the tDBInput component onto the Designer.
Set up the database connection using either Built-in or Repository mode.
In the Query field, write:
SELECT id, name, address, country FROM customers WHERE country = '" + context.country + "'
Execute the Job:
The Job will retrieve only those records where the country column matches the value of the context variable.
The value of context.country can be modified at runtime, making the query dynamic.
Why not other options?
tMatchGroup (Option B): Used for record deduplication, not filtering.
Run if Trigger (Option C): Controls execution flow but does not filter records inside tDBInput.
tFilterColumns (Option D): Removes unwanted columns but does not filter records based on conditions.
Reference: Talend Database Components Guide, Talend SQL Query Optimization

Question No : 12

You need to share a connection between multiple database components in a Studio Job.
Which component should you use?

A.tDBOutput
B.tDBRun
C.tDBCommit
D.tDBConnection

정답:
Explanation:
Comprehensive and Detailed
In Talend, when multiple components need to share the same database connection, the tDBConnection component is used.
tDBConnection (Correct Answer - Option D):
This component establishes a database connection that can be reused by multiple database components (such as tDBInput, tDBOutput, and tDBRow) within the same Job.
Reduces redundant connection creation, improving performance and efficiency.
To use it, other database components must set "Use an existing connection" in their configuration.
Why not other options?
tDBOutput (Option A): Used for writing data to a database but does not manage shared connections.
tDBRun (Option B): Used to execute a subJob but does not handle database connections.
tDBCommit (Option C): Used for committing transactions, but it requires a shared connection (which tDBConnection provides).
Reference: Talend Studio User Guide, Talend Database Connection Management

Question No : 13

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

정답:
Explanation:
Comprehensive and Detailed
When multiple Jobs require connections to the same database server but with different credentials, the recommended approach is:
Set the Property Type to Built-in and Set All the Relevant Properties Manually (Option C):
In each tDBInput component, set the 'Property Type' to 'Built-in.'
Manually enter the connection details, including the specific username and password required for that particular Job.
This approach ensures that each Job uses its own set of credentials, maintaining the necessary security and access controls.
Reference: Talend Studio User Guide, Talend Database Components Documentation

Question No : 14

Which Action on table operations are supported by a tMysqlOutput component? Choose 3 answers.

A.Drop table
B.Drop table if exists and create
C.Replace
D.Create table if does not exist
E.Create table

정답:
Explanation:
Comprehensive and Detailed
The tMysqlOutput component in Talend provides several actions on tables to manage data output operations effectively. The supported actions include:
Drop Table if Exists and Create (Option B):
This action checks if the specified table exists in the database. If it does, the table is dropped and a new one is created. This ensures that the table is recreated fresh for the data load.
Create Table if Does Not Exist (Option D):
This action checks if the specified table exists in the database. If it does not exist, the table is created.
If it already exists, no action is taken, and the existing table is used.
Create Table (Option E):
This action attempts to create the specified table in the database. If the table already exists, an error will occur unless handled appropriately.
These actions provide flexibility in managing database tables during data integration processes, allowing for dynamic table creation and management based on the Job's requirements.
Reference: Talend Components Reference Guide, Talend Database Output Components Documentation

Question No : 15

You need to create a centralized metadata connection to a 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 tCreateTable component to create a table in the database.
B.Add a tMap component to handle and convert Db Types.
C.Create Db Connections metadata to describe the database connection.
D.Drag the Db Connections metadata onto the Designer to read from the database component.
E.Retrieve the schemas from the database connection.

정답:
Explanation:
Comprehensive and Detailed
To establish a centralized metadata connection to a database server in Talend Studio, follow these steps before constructing a Job that reads from the database:
Create Db Connections Metadata to Describe the Database Connection (Option C):
In the Repository panel, right-click on "Metadata" and select "Create connection."
Fill in the necessary details such as database type, host, port, database name, username, and password.
Test the connection to ensure it is configured correctly.
Save the connection metadata for reuse across multiple Jobs.
Retrieve the Schemas from the Database Connection (Option E):
After creating the database connection metadata, expand it to view the available schemas.
Retrieve the required schemas by importing the table structures.
This step ensures that the schema definitions are centralized and can be reused in different Jobs.
Drag the Db Connections Metadata onto the Designer to Read from the Database Component (Option D):
In the Repository, locate the previously created database connection metadata.
Drag and drop the desired table or schema onto the Designer workspace.
Talend Studio will automatically create the appropriate input component (e.g., tDBInput) configured with the connection and schema details.
By following these steps, you ensure a centralized and consistent approach to managing database connections and schemas, promoting reusability and reducing configuration errors.
Reference: Talend Studio User Guide, Talend Metadata Management Documentation

Talend Talend Core Developer 시험