Home / DE Professional practice test / Developing Code for Data Processing using Python and SQL / Question

Databricks Data Engineer Professional · free practice question

A data engineering team has a monorepo containing multiple Databricks Asset Bundle projects for different product domains. Each project has its own…

Exam-style question on Developing Code for Data Processing using Python and SQL from the free DE Professional practice test, with the answer and a full explanation below.

Updated November 16, 2026

Developing Code for Data Processing using Python and SQL Medium

A data engineering team has a monorepo containing multiple Databricks Asset Bundle projects for different product domains. Each project has its own databricks.yml. The CI/CD pipeline runs on GitHub Actions. On every pull request, the team wants to: (1) validate the bundle YAML schema, (2) run Python unit tests, and (3) prevent deployment if validation or tests fail. On merge to main, the CD step must deploy to the prod target. A new engineer is asked to write the GitHub Actions workflow YAML steps. Which sequence of CLI commands in the CI job correctly implements all three requirements?

  1. Adatabricks bundle plan -t prod to validate configuration and preview changes, then pytest tests/ to run unit tests. If either fails, the GitHub Actions job exits with a non-zero code, blocking the PR merge. No deployment command is included in the CI job.
  2. Bdatabricks bundle validate to check the bundle configuration, then pytest tests/ to run unit tests. If either exits with a non-zero code, the CI job fails and the merge is blocked. The CD job runs databricks bundle deploy -t prod on merge to main.
  3. Cdatabricks bundle deploy --dry-run -t staging to simulate a staging deployment as the validation step, then python -m unittest discover to run tests. The dry-run flag stops resources from being created, so the step is safe to run on each PR.
  4. Ddatabricks bundle check -t prod to verify workspace permissions, then databricks bundle test to run the bundle's built-in test suite, then pytest tests/ to run custom unit tests. A failure in one of the three steps blocks the PR merge.
  5. Edatabricks bundle lint to check code style, databricks bundle validate -t prod to validate schema against the production target, and pytest tests/ to run unit tests. The -t prod flag is needed here, as the YAML schema differs between targets.
Answer & explanation

Correct answer: B

WHY B: databricks bundle validate is the purpose-built command for schema and config validation: it checks YAML syntax, schema compliance, variable references, and file existence, and it does not require a -t flag for basic schema validation. pytest tests/ is the standard Python unit testing invocation. Both commands return non-zero exit codes on failure, which GitHub Actions treats as job failure, blocking the merge. databricks bundle deploy -t prod in the CD job is the correct production deployment command.

WHY NOT A: databricks bundle plan is a valid DAB CLI command (available with the direct deployment engine) that previews deployment changes without making them, similar to Terraform's plan. However, it requires workspace connectivity and is scoped to deployment previews, not YAML schema validation. databricks bundle validate is the purpose-built command for CI schema checking.

WHY NOT C: databricks bundle deploy --dry-run is not a valid DAB flag; there is no dry-run mode in the DAB CLI, so this step cannot serve as validation.

WHY NOT D: databricks bundle check and databricks bundle test are not valid DAB commands, so two of the three steps would fail to run at all.

WHY NOT E: databricks bundle lint is not a valid DAB command. databricks bundle validate does not require a -t flag, and the YAML schema does not differ between targets.

Take the full DE Professional practice test free →

Would you pass today?

This question is one of 60 in the free, timed Databricks Data Engineer Professional practice test. Take it and get a section-by-section score.

Start the free test →