Option B uses the @hourly cron expression, a convenient way to schedule tasks to run every hour in Airflow. Option A specifies a specific time within the cron syntax

Addressing skewed data requires a multi-pronged approach. Salting randomizes data distribution within partitions, custom partitioners ensure balanced distribution of skewed values, and broadcasting avoids redundant data transfers on shuffled stages.

Option A is correct because it properly uses the JDBC format with all the necessary options including the URL, database table, and user credentials.

Each worker node runs an executor responsible for receiving tasks from the driver, fetching data from storage, and performing computations on assigned partitions.

While option D might be desirable if both approaches are applicable, storing sensitive data in code is insecure (option D)