Question 76

Your team runs a nightly Lakeflow Job named `nightly_sales_etl` that ingests data from an external REST API into a Delta table. The ingestion task occasionally fails because the upstream API returns transient HTTP 503 errors that resolve themselves within a minute or two. Currently the task has **no retry policy configured**, so a single 503 error fails the entire run and pages the on-call engineer. You must change the task configuration so that transient API failures are automatically tolerated, while still ensuring a genuinely broken task does not retry forever and a hung task is eventually killed. You add a retry policy to the task with the following intent: ```json { "task_key": "ingest_api_data", "max_retries": 3, "min_retry_interval_millis": 60000, "timeout_seconds": 1800, "notebook_task": { "notebook_path": "/Shared/etl/ingest_api_data" } } ``` Which statement correctly describes how Lakeflow Jobs applies this configuration when the task fails with a transient error?

• AThe task is restarted up to 3 times after a failure, the retry waits at least 60 seconds between the start of the failed run and the next retry, and the 30-minute `timeout_seconds` applies independently to each retry run.
• BThe task is restarted exactly once because `max_retries` is capped at 1 for notebook tasks, and the timeout applies only to the original run.
• CThe task retries indefinitely with exponential backoff because any value of `max_retries` greater than 0 enables continuous-mode backoff, and `timeout_seconds` is ignored.
• DThe retry policy is rejected at deployment because a task cannot define both `timeout_seconds` and `max_retries`; you must choose one or the other.