Deal of The Day! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Talend Exam Data-Integration-Developer Topic 7 Question 25 Discussion

Actual exam question for Talend's Data-Integration-Developer exam
Question #: 25
Topic #: 7
[All Data-Integration-Developer Questions]

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?

Show Suggested Answer Hide Answer
Suggested Answer: A, B, E

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


Contribute your Thoughts:

Xenia
2 months ago
You know, I heard that Talend Studio runs on a magical unicorn server, so any option should work. Let's just go with the one that makes the most glitter.
upvoted 0 times
...
Joaquin
2 months ago
Hmm, I'm torn between B and D. Maybe I should just flip a coin and hope for the best.
upvoted 0 times
Jeffrey
13 days ago
Maybe you can try flipping a coin, but I would recommend going with option D for better compatibility.
upvoted 0 times
...
Rickie
17 days ago
I would suggest choosing option D. It's better to have separate packages for each platform.
upvoted 0 times
...
Chauncey
1 months ago
I think you should go with option B. It's the safest bet.
upvoted 0 times
...
...
Zona
2 months ago
Ha! I bet the correct answer is C. Configuring the job properties is the key to making it work across platforms.
upvoted 0 times
Glendora
1 months ago
Building one package for each platform could also work, but it might be more work.
upvoted 0 times
...
Ashlyn
1 months ago
I think selecting Build Job because Jobs are runnable on all platforms might be the best option.
upvoted 0 times
...
Lili
2 months ago
Configuring the job properties is definitely important for cross-platform compatibility.
upvoted 0 times
...
...
Harrison
2 months ago
Option B sounds good to me. Specifying All for the Shell launcher option should make the job runnable on both platforms, right?
upvoted 0 times
Ashton
24 days ago
I agree. It's important to configure the Shell launcher option properly for cross-platform compatibility.
upvoted 0 times
...
Sherly
1 months ago
That's correct. It's the best option to ensure the job runs successfully on both platforms.
upvoted 0 times
...
Hector
2 months ago
Yes, selecting All for the Shell launcher option will make the job runnable on both Linux and Windows.
upvoted 0 times
...
...
An
2 months ago
I think option D is the way to go. Building one package for each platform ensures that the job will run seamlessly on both Linux and Windows.
upvoted 0 times
James
26 days ago
D) Build one package for each platform.
upvoted 0 times
...
Ocie
29 days ago
C) Configure the Job properties building the Job.
upvoted 0 times
...
Carline
1 months ago
B) Specify All for the Shell launcher option in the Build Job windows.
upvoted 0 times
...
Dong
2 months ago
A) Select Build Job because Jobs are runnable on all platforms
upvoted 0 times
...
...
Anthony
3 months ago
I'm not sure, but maybe configuring the Job properties could also work.
upvoted 0 times
...
Mozell
3 months ago
I agree with Shelton, building separate packages for each platform seems like the best option.
upvoted 0 times
...
Shelton
3 months ago
I think we should build one package for each platform.
upvoted 0 times
...

Save Cancel