Answer-first summary for fast verification
Answer: Three new jobs named "Ingest new data" will be defined in the workspace, but no jobs will be executed.
The Databricks REST API endpoint 2.0/jobs/create is used to define a new job configuration in the workspace. Each call to this endpoint with the provided JSON creates a new job named 'Ingest new data' but does not automatically execute it. Since the workload is executed three times, three new job configurations are created. However, without a schedule or manual trigger, none of these jobs will run. The existing_cluster_id specifies an existing cluster for the job to use when it runs, but the job must be triggered to do so. Therefore, the correct outcome is that three new jobs are defined in the workspace, but none are executed.
Author: LeetQuiz Editorial Team
Ultimate access to all questions.
A junior data engineer has configured a workload that posts the following JSON to the Databricks REST API endpoint 2.0/jobs/create:
{
"name": "Ingest new data",
"existing_cluster_id": "6015-954420-peace720",
"notebook_task": {
"notebook_path": "/Prod/ingest.py"
}
}
{
"name": "Ingest new data",
"existing_cluster_id": "6015-954420-peace720",
"notebook_task": {
"notebook_path": "/Prod/ingest.py"
}
}
Assuming that all configurations and referenced resources are available, what would be the result of executing this workload three times?
A
Three new jobs named "Ingest new data" will be defined in the workspace, and they will each run once daily.
B
The logic defined in the referenced notebook will be executed three times on new clusters with the configurations of the provided cluster ID.
C
Three new jobs named "Ingest new data" will be defined in the workspace, but no jobs will be executed.
D
One new job named "Ingest new data" will be defined in the workspace, but it will not be executed.
E
The logic defined in the referenced notebook will be executed three times on the referenced existing all purpose cluster.
No comments yet.