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 3 Question 36 Discussion

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

You have two branches: Branch1 contains Job1, and Branch 2 contains Job 2. You want to copy Job1 to Branch 2 and preserve the change history when connecting Studio to Talend Administrator Center.

Which method should you use to preserve the change history?

Show Suggested Answer Hide Answer
Suggested Answer: A

To copy Job1 from Branch1 to Branch2 and preserve the change history when connecting Studio to Talend Administration Center, you need to use the Copy to branch option. This option allows you to copy a job or a folder from one branch to another branch in the same project without losing the version history. You can access this option by switching to Branch1, right-clicking on Job1 in the Repository tree view, and selecting Copy to branch. This will open a dialog box where you can select Branch2 as the target branch and confirm the copy operation.

You do not need to use the import items, create standard job, or paste over options. These options are not used to copy jobs between branches and preserve the change history. 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 paste over option is used to overwrite an existing job with another job that has been copied or cut from the same or another project.Reference:Talend Open Studio: Open-source ETL and Free Data Integration | Talend, [Copy to branch - 7.3]


Contribute your Thoughts:

Reynalda
2 months ago
Wait, is this a trick question? If I had to guess, I'd say Option C is the way to go. Gotta keep that change history intact, you know?
upvoted 0 times
...
Nobuko
2 months ago
Hmm, I was considering option B, but after reading the options again, C seems to be the most straightforward and effective way to preserve the change history. Nice one!
upvoted 0 times
Iluminada
1 months ago
Yeah, I agree. Option C seems like the most straightforward method.
upvoted 0 times
...
Herschel
1 months ago
Yeah, I agree. It seems like the most straightforward method to preserve the change history.
upvoted 0 times
...
Veronika
1 months ago
I think option C is the best choice here.
upvoted 0 times
...
Pearlie
1 months ago
I think option C is the best choice to preserve the change history.
upvoted 0 times
...
...
Laurel
2 months ago
Haha, option D is just asking for trouble. Pasting a job over another? That's a recipe for disaster! C is the way to go, no doubt.
upvoted 0 times
...
Lisandra
2 months ago
I'm not sure, but I think B) Switch to Branch 1, copy the Branch 1 job, switch to Branch 2, and paste the job into Branch 2 might be the right choice.
upvoted 0 times
...
Twana
2 months ago
I disagree, I believe the correct method is D) Switch to Branch 1, copy Job 1, switch to Branch 2, and paste Job 1 over Job 2.
upvoted 0 times
...
Kristin
2 months ago
I think the answer is A) Switch to Branch 1, right-click Job 1, select Copy to branch, and select Branch 2.
upvoted 0 times
...
Huey
2 months ago
I agree, Option C is the best choice here. Switching between the branches and copying the job properly will ensure the history is maintained.
upvoted 0 times
Marge
19 days ago
Copying the job properly is key to maintaining the change history when connecting Studio to Talend Administrator Center.
upvoted 0 times
...
Jerrod
20 days ago
Agreed, switching branches and pasting the job into Branch 2 will keep the history intact.
upvoted 0 times
...
Barney
22 days ago
I think copying the job from Branch 1 to Branch 2 is the best method to preserve the change history.
upvoted 0 times
...
Pansy
1 months ago
Option C is definitely the way to go. It's important to switch branches correctly.
upvoted 0 times
...
...
Claudio
2 months ago
Option C seems to be the way to go. Preserving the change history is crucial, and this method looks like it would do the trick.
upvoted 0 times
Edelmira
1 months ago
C) Yeah, preserving the change history is important, so option C seems like the best choice.
upvoted 0 times
...
Willodean
1 months ago
A) That could work too, but I think option C ensures the change history is preserved.
upvoted 0 times
...
Thad
1 months ago
B) But wouldn't it be easier to just switch to Branch 1, right-click Job 1, select Copy to branch, and select Branch 2?
upvoted 0 times
...
Sue
1 months ago
A) Switch to branch 1, copy the Branch 1 Job, switch to Branch 2, and paste the Job into Branch 2.
upvoted 0 times
...
...

Save Cancel