Answer-first summary for fast verification
Answer: The job named `test_api` will be created and scheduled to trigger daily at 8:00 AM Brisbane time.
The `2.0/jobs/create` endpoint of the Databricks REST API allows for both the creation and scheduling of jobs. Once a schedule is set, the job will automatically trigger at the specified time. In this scenario, the job is scheduled to trigger daily at 8:00 AM according to the Brisbane, Australia timezone. The Cron expression provided uses Quartz syntax, which supports scheduling down to the second. For more information, refer to the documentation on scheduling jobs with the Databricks REST API.
Author: LeetQuiz Editorial Team
Ultimate access to all questions.
No comments yet.
A data engineer submits the following JSON to the 2.0/jobs/create endpoint of the Databricks REST API:
{
"name": "test_api",
"existing_cluster_id": "1198-132537-dht25rtr",
"notebook_task": {
"notebook_path": "/example.py"
},
"schedule": {
"quartz_cron_expression": "0 0 8 * * ?",
"timezone_id": "Australia/Brisbane"
}
}
{
"name": "test_api",
"existing_cluster_id": "1198-132537-dht25rtr",
"notebook_task": {
"notebook_path": "/example.py"
},
"schedule": {
"quartz_cron_expression": "0 0 8 * * ?",
"timezone_id": "Australia/Brisbane"
}
}
Assuming the cluster 1198-132537-dht25rtr exists, what will be the expected outcome?
A
The job named test_api will be created and scheduled to trigger daily at 8:00 AM Brisbane time.
B
The job will not be created because the 2.0/jobs/create endpoint does not support job scheduling.
C
The job named test_api will be created and scheduled to trigger on the 8th day of each month.
D
The job will be created but will not trigger due to an invalid Cron expression.
E
The job named test_api will be created but can only be triggered manually via the Jobs UI.