MENU
A data engineer needs to capture pipeline settings from an existing in the workspace, and use them to create and version a JSON file to create a new pipeline.
Which command should the data engineer enter in a web terminal configured with the Databricks CLI?
Suggested Answer: A
Get Premium Databricks Certified Data Engineer Professional Questions
as Interactive Web-Based Practice Test or PDF
Real Exam Format
Detailed Explanations
Instant Access
Get Your Practice Test
The Databricks CLI provides a way to automate interactions with Databricks services. When dealing with pipelines, you can use the databricks pipelines get --pipeline-id command to capture the settings of an existing pipeline in JSON format. This JSON can then be modified by removing the pipeline_id to prevent conflicts and renaming the pipeline to create a new pipeline. The modified JSON file can then be used with the databricks pipelines create command to create a new pipeline with those settings.
Databricks Documentation on CLI for Pipelines: Databricks CLI - Pipelines
44 comments · newest first
WY
Wynell
10 months ago
Not sure about option D, seems a bit complicated.
HE
Helene
11 months ago
Wait, can you really just rename the pipeline like that?
MI
Michel
11 months ago
Definitely A, it’s the most straightforward.
VI
Viola
11 months ago
Nah, I’d go with option C instead.
JU
Judy
11 months ago
I think option A is the right way to go!
TA
Tatum
12 months ago
I thought we could use the alone command to create a copy, but that doesn't sound right now. I should have reviewed the JSON commands more thoroughly.
NA
Nana
12 months ago
I feel like option D might be the right choice since it mentions getting specs for all pipelines, but I’m a bit confused about how to parse the results.
JE
Jerry
12 months ago
I remember practicing a similar question where we had to retrieve pipeline settings, but I can't recall if we used a reset command or something else.
LE
Leslie
1 year ago
I think we need to use the get command to capture the settings, but I'm not sure if we have to rename the pipeline or just modify it directly.
TU
Tu
1 year ago
Option D looks interesting, but I'm not sure how reliable it would be to parse the list of pipelines to get the specs. Seems like there could be some edge cases there. I'd probably stick with A or C to be on the safe side.
LY
Lyda
1 year ago
I think option C is the way to go. Using the "alone" command to create a copy of the existing pipeline, then getting the JSON definition and saving it to git seems like a good way to version the pipeline settings.
CE
Cecily
1 year ago
Hmm, I'm a bit confused by the question. Do we need to stop the existing pipeline first before creating a new one? Option B mentions stopping the existing pipeline, but I'm not sure if that's necessary.
RE
Reid
1 year ago
This seems straightforward - I'd go with option A. Capture the settings for the existing pipeline, remove the pipeline ID, and use that to create a new pipeline.
LA
Lashawna
1 year ago
I think one advantage is that they let different projects use different versions of the same libraries without conflicts.
HE
Hershel
2 years ago
D) that's a clever approach, but it seems a bit overkill. Why not just use the get command like in A)? Less steps, you know?
LO
Lorrine
2 years ago
C) I think A) is the way to go. It's simpler and more efficient.
TA
Tawanna
2 years ago
A) Stop the existing pipeline; use the returned settings in a reset command
WI
Wilda
2 years ago
D) Yeah, I see your point. A) does seem more straightforward and less complicated.
JE
Jesus
2 years ago
A) Use the get command to capture the settings for the existing pipeline; remove the pipeline_id and rename the pipeline; use this in a create command
RO
Robt
2 years ago
B) stopping the existing pipeline and resetting it? That's not what the question is asking for. We need to create a new pipeline, not modify the existing one.
JE
Jenise
2 years ago
C) is interesting, but I don't think creating a copy of an existing pipeline is what the question is asking for. We need to create a new pipeline based on the existing one.
DA
Darrel
2 years ago
A) seems like the right approach to me. Capturing the settings and creating a new versioned pipeline sounds like the task at hand.
KA
Kaitlyn
2 years ago
D) Use list pipelines to get the specs for all pipelines; get the pipeline spec from the return results parse and use this to create a pipeline.
TH
Theodora
2 years ago
B) Stop the existing pipeline; use the returned settings in a reset command.
ST
Stefania
2 years ago
A) seems like the right approach to me. Capturing the settings and creating a new versioned pipeline sounds like the task at hand.
KA
Kayleigh
2 years ago
I'm feeling option A is the way to go. Can't go wrong with a good old get and create command combo.
MA
Matilda
2 years ago
I'm not sure, but I think option C could also work by creating a copy of an existing pipeline.
MA
Margot
2 years ago
Haha, option C is like the data engineer is trying to clone a pipeline. Gotta love those 'alone' commands!
CA
Carmela
2 years ago
Option B is weird. Why would the data engineer need to stop the existing pipeline? That doesn't seem necessary for this task.
SE
Sean
2 years ago
User3: Option D seems like the right approach, using the list pipelines command to get the specs.
GL
Gladis
2 years ago
User2: I agree, it's better to focus on capturing the settings and creating the JSON file.
TH
Thaddeus
2 years ago
Option B does seem unnecessary. It's not mentioned in the question.
JO
Josephine
2 years ago
I agree with Meghan, using list pipelines to get the specs for all pipelines makes sense.
MA
Marcos
2 years ago
Option D doesn't make sense to me. Why would the data engineer need to list all pipelines and parse the specs when they just need to capture the settings for a specific pipeline?
GA
Galen
2 years ago
User 4: Option D does seem a bit unnecessary for this task, listing all pipelines and parsing specs is overkill.
CH
Charisse
2 years ago
User 3: Option C also sounds like a good option, creating a copy of the existing pipeline and saving the JSON to git.
EL
Elza
2 years ago
User 2: I agree, using the get command to capture the settings for the existing pipeline makes sense.
JO
Jolanda
2 years ago
Option A seems like the most straightforward approach.
ME
Meghan
2 years ago
I think the correct command is D.
LY
Lynette
2 years ago
I think option A is the correct answer. The data engineer needs to capture the pipeline settings, remove the pipeline ID, and use them to create a new pipeline.
AL
Alline
2 years ago
Let's go with option A then, it seems like the most logical choice.
RE
Reta
2 years ago
Option A sounds like the right approach for this task.
LA
Lamar
2 years ago
I agree, capturing the settings and using them to create a new pipeline makes sense.
CO
Coral
2 years ago
I think option A is the correct answer.