When scheduling Structured Streaming jobs for production, which configuration automatically recovers from query failures and keeps costs low?
When scheduling Structured Streaming jobs for production, which configuration automatically recovers from query failures and keeps costs low?
To schedule Structured Streaming jobs for production with an automatic recovery from query failures while keeping costs low, you should use a new job cluster to ensure an isolated and streamlined environment, set retries to unlimited to handle and recover from any failures automatically, and limit maximum concurrent runs to 1 to avoid resource contention and ensure only one instance of the query runs at a time. This configuration efficiently manages resources and ensures the job's reliability and cost-effectiveness.
the answer given is correct: Maximum concurrent runs: Set to 1. There must be only one instance of each query concurrently active. Retries: Set to Unlimited. https://docs.databricks.com/en/structured-streaming/query-recovery.html
D. Cluster: New Job Cluster; Retries: Unlimited; Maximum Concurrent Runs: 1
D. Cluster: New Job Cluster; Retries: Unlimited; Maximum Concurrent Runs: 1
D is correct https://docs.databricks.com/en/structured-streaming/query-recovery.html
Correct Ans is D
D is correct
D is correct
D is correct