Databricks-DE-Assoc Working with Lakeflow Jobs Practice Question
A data engineer needs to pass the execution date to a job task dynamically. Which feature should they use?
⚠ Common exam trap
Candidates often confuse task parameters with cluster-level environment variables or hardcoded notebook widgets, failing to use the native job task configuration feature.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Defining job parameters in the task configuration.
Using Job Parameters allows engineers to inject dynamic values into tasks at runtime. This capability is crucial for backfilling data or running incremental pipelines where the processing logic depends on specific dates or data partitions. By parameterizing tasks, engineers create reusable jobs that can handle varying datasets without requiring manual code changes, thereby improving the maintainability and scalability of the entire data pipeline architecture.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Hardcoding the date in the notebook.
Why it's wrong here
Hardcoding values creates technical debt and prevents reuse. It forces the engineer to modify the source code every time a different date range needs processing, which is error-prone and violates best practices for building robust, automated data platforms that should handle dynamic inputs natively through configuration parameters.
- ✓
Defining job parameters in the task configuration.
Why this is correct
Task-level parameters allow values to be passed to notebooks or scripts at execution time. These parameters can be referenced within the code using standard widget APIs or environment variable lookups, providing a clean and programmatic way to inject dynamic information into the task execution without altering the underlying logic.
- ✗
Creating a new cluster for each date.
Why it's wrong here
Creating new clusters for every execution is an inefficient use of resources and incurs unnecessary overhead. Cluster management should be decoupled from job parameterization. The correct approach is to use a static or job cluster and pass the specific date as a parameter to the existing task.
- ✗
Using global workspace variables.
Why it's wrong here
Workspace variables are not a standard feature for passing dynamic run-time data between job executions. Job parameters are the intended mechanism for injecting context-specific information into a task, whereas global workspace settings would not provide the isolation and granularity required for concurrent or historical data processing runs.
About these practice questions
One of 276 original Databricks-DE-Assoc practice questions on Courseiva, each with a full explanation and wrong-answer analysis — not exam dumps or protected exam content. Learn why practice questions differ from exam dumps →
JA
Written and reviewed by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
Last reviewed September 2026 · checked against the official Databricks exam blueprint
This Databricks-DE-Assoc practice question is part of Courseiva's free Databricks certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the Databricks-DE-Assoc exam.