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
Mail Us support@pass4success.com
Location US
Mob_nav_barsMENU

Databricks Certified Data Engineer Professional Exam - Topic 3 Question 8 Discussion

Actual exam question for Databricks's Databricks Certified Data Engineer Professional exam
Question #: 8
Topic #: 3
[All Databricks Certified Data Engineer Professional Questions]

Which REST API call can be used to review the notebooks configured to run as tasks in a multi-task job?

Show Suggested Answer Hide Answer
Suggested Answer: C

The provided MERGE statement is a classic implementation of a Type 2 SCD in a data warehousing context. In this approach, historical data is preserved by keeping old records (marking them as not current) and adding new records for changes. Specifically, when a match is found and there's a change in the address, the existing record in the customers table is updated to mark it as no longer current (current = false), and an end date is assigned (end_date = staged_updates.effective_date). A new record for the customer is then inserted with the updated information, marked as current. This method ensures that the full history of changes to customer information is maintained in the table, allowing for time-based analysis of customer data. Reference: Databricks documentation on implementing SCDs using Delta Lake and the MERGE statement (https://docs.databricks.com/delta/delta-update.html#upsert-into-a-table-using-merge).


by Alison at Apr 23, 2024, 08:58 PM

Limited Time Offer

25%

Off

Get Premium Databricks Certified Data Engineer Professional Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

0/2000 characters
Submit Cancel
Lisha
6 months ago
Yeah, /jobs/runs/get is the way to go!
upvoted 0 times
...
Lauran
6 months ago
Wait, can you really use /jobs/runs/get-output for that?
upvoted 0 times
...
Eulah
6 months ago
Pretty sure it's not /jobs/get.
upvoted 0 times
...
Estrella
7 months ago
I thought it was /jobs/runs/list?
upvoted 0 times
...
Elfrieda
7 months ago
It's definitely /jobs/runs/get!
upvoted 0 times
...
Leota
7 months ago
I’m leaning towards B since it mentions getting output, but I’m not confident if that’s what they mean by reviewing notebooks.
upvoted 0 times
...
Malcolm
7 months ago
I feel like E could be relevant too, but it seems more about listing jobs rather than reviewing specific notebooks.
upvoted 0 times
...
Florinda
7 months ago
I remember practicing a question similar to this, and I think C was the one that dealt with getting job details.
upvoted 0 times
...
Juan
8 months ago
I think the answer might be A, but I'm not entirely sure if that's the right endpoint for reviewing notebooks.
upvoted 0 times
...
Lenora
8 months ago
I'm a bit stuck on this one. I know the question is about reviewing the notebooks in a multi-task job, but I'm not sure which API call would be the best fit. I might need to review my notes on the different job-related endpoints.
upvoted 0 times
...
Dorothy
8 months ago
I'm confident that the answer is C. The "/jobs/runs/get" endpoint seems to be the most relevant one for retrieving information about the individual runs within a multi-task job, which would include the configured notebooks.
upvoted 0 times
...
Nu
8 months ago
Okay, let me think this through. The question is asking about reviewing the notebooks configured to run as tasks in a multi-task job, so I'm guessing the answer has to do with retrieving information about the job runs, not just the job itself.
upvoted 0 times
...
Cordell
8 months ago
Hmm, I'm a bit unsure about this one. The options seem to be related to jobs and runs, but I'm not sure which one specifically deals with reviewing the notebooks in a multi-task job.
upvoted 0 times
...
Fabiola
8 months ago
This looks like a straightforward REST API question. I think I can narrow it down based on the keywords "notebooks", "tasks", and "multi-task job".
upvoted 0 times
...
Soledad
8 months ago
The checks-effects-interactions pattern sounds familiar, but I'm not sure if it's required for all external calls or just certain situations. I'll need to think this through carefully.
upvoted 0 times
...
Arthur
8 months ago
Okay, I've got a strategy for this. I'll carefully read through the options and think about what the Scrum Guide says about handling a cancelled Sprint.
upvoted 0 times
...
Shenika
8 months ago
I feel pretty confident about this. Configuring basic budgeting in Dynamics 365 is a common task, so I'll apply my knowledge of the standard setup process to identify the correct sequence of actions.
upvoted 0 times
...
Keith
8 months ago
I think B is true since data warehouses do help with integrating data from multiple sources, but I'm hesitant about the exact wording.
upvoted 0 times
...
Val
1 year ago
Trick question! The real answer is F. /jobs/runs/get-notebook-output, because who doesn't love a hidden option?
upvoted 0 times
Lizbeth
11 months ago
Hmm, maybe it's D) /jobs/get
upvoted 0 times
...
Shelton
11 months ago
Actually, I'm pretty sure it's E) /jobs/list
upvoted 0 times
...
Helene
11 months ago
No, I believe it's C) /jobs/runs/get
upvoted 0 times
...
Alline
11 months ago
I think the answer is A) /jobs/runs/list
upvoted 0 times
...
...
Felix
1 year ago
Wait, is this a trick question? I bet the real answer is A. /jobs/runs/list, because that's the only one that mentions 'runs' which sounds like what we need.
upvoted 0 times
...
Jospeh
1 year ago
Haha, this is easy! It's clearly E. /jobs/list, because you need to list all the jobs to see the notebooks, duh.
upvoted 0 times
Reed
11 months ago
I think you're right. C) /jobs/runs/get makes more sense for reviewing the notebooks in a multi-task job.
upvoted 0 times
...
Antione
11 months ago
Oh, I see. Thanks for clarifying. I thought it was E) /jobs/list because you need to list all the jobs first.
upvoted 0 times
...
Josphine
12 months ago
No, it's actually C) /jobs/runs/get. That's the one you need to review the notebooks configured to run as tasks in a multi-task job.
upvoted 0 times
...
...
Noble
1 year ago
I'm pretty sure it's C. /jobs/runs/get, since that's the only one that mentions getting the output of a job run.
upvoted 0 times
Lou
11 months ago
I agree with you, it's C) /jobs/runs/get to review the notebooks configured to run as tasks.
upvoted 0 times
...
Rosina
12 months ago
I believe it's D) /jobs/get, to get details about the job itself.
upvoted 0 times
...
Felicia
1 year ago
I think it might be A) /jobs/runs/list, to list all the job runs.
upvoted 0 times
...
...
Carlene
1 year ago
The correct answer is obviously D. /jobs/get, that's the only one that mentions getting the job details, which would include the configured notebooks.
upvoted 0 times
Marilynn
1 year ago
You're right, D) /jobs/get makes sense for reviewing the notebooks configured in a job
upvoted 0 times
...
Margurite
1 year ago
Actually, I'm pretty sure it's D) /jobs/get
upvoted 0 times
...
Louisa
1 year ago
No, I believe it's C) /jobs/runs/get
upvoted 0 times
...
Charlena
1 year ago
I think the answer is A) /jobs/runs/list
upvoted 0 times
...
...
Sherita
1 year ago
Why do you think that?
upvoted 0 times
...
Anglea
1 year ago
I disagree, I believe the correct answer is C) /jobs/runs/get
upvoted 0 times
...
Sherita
1 year ago
I think the answer is A) /jobs/runs/list
upvoted 0 times
...

Save Cancel