Question 770 A CI runner provides a bundle variable named `schema_name` through the environment instead of a CLI flag. Which environment variable naming convention does the CLI support? `SPARK_SQL_schema_name` `BUNDLE_VAR_schema_name` BUNDLE_SCHEMA_schema_name `JOB_TOKEN_schema_name` Explanation Correct Answer B:The BUNDLE_VAR_ prefix identifies an environment-provided bundle variable override. Incorrect Answers A:That string does not populate the Databricks bundle variable mechanism. C:The CLI consumes environment substitutions through BUNDLE_VAR_ followed by the declared variable name, not an arbitrary bundle-schema prefix. D:This is not the documented bundle-variable prefix.
Question 771 A repository defines identical job logic for two cloud workspaces. Which bundle configuration should differ between the dev and prod target deployments? The original Git commit hash within the source tree The meaning of the business columns The target workspace host and environment-specific resource settings Every SQL transformation function name Explanation Correct Answer C:Targets can direct a common codebase to different workspaces and apply local overrides. Incorrect Answers A:Environment selection need not mutate the contents of the approved source commit. B:Deployment targets do not change the conceptual data model. D:The same tested code should generally be promoted rather than rewritten per workspace.
Question 772 A production Lakeflow pipeline already exists with preserved state, and a team is adopting Declarative Automation Bundles without recreating that production pipeline. Which operation is relevant? Destroy the existing production pipeline before versioning it Edit production code without a source-controlled bundle Bind the bundle resource key to the existing remote resource ID before deployment Use `git status` to bind the existing pipeline Explanation Correct Answer C:Binding lets the bundle manage an existing resource rather than allocating an unrelated duplicate. Incorrect Answers A:Destruction can lose the resource and is unnecessary for supported resource adoption. B:Manual changes do not establish the desired declarative resource association. D:Git status reports local changes and does not link remote Databricks resources.
Question 773 A developer proposes running `databricks bundle destroy -t prod` merely to clear a validation warning. Why should the reviewer reject it? It automatically repairs source-code syntax errors That command can delete previously deployed production resources and artifacts It changes only local Git staging status It only prints the configured targets and cannot change resources Explanation Correct Answer B:Destroy is a destructive lifecycle operation, not a harmless validation reset. Incorrect Answers A:Removing deployed resources does not correct configuration syntax. C:The command acts against bundle-managed remote resources. D:Destroy can remove deployed assets and should not be treated as read-only.
Question 774 Before changing a regulated production job, a team wants to inspect the expected remote resource changes without directly running the workflow. What CLI capability helps? Use bundle planning or a reviewed deployment diff where supported Run `bundle destroy` against production Use `databricks bundle deploy -t prod` as the first step and inspect what it changed afterward Rely exclusively on the most recent deployed job settings without a proposed change preview Explanation Correct Answer A:Reviewing planned changes catches unintended resource updates before promotion. Incorrect Answers B:Destroy deletes resources rather than safely presenting planned updates. C:Deploy applies resource changes; the requirement calls for a plan or reviewed diff before mutating production resources. D:Current resource state does not disclose the changes that the candidate bundle would make to regulated production resources.
Question 775 A deployed bundle contains several similarly named jobs, and a release engineer needs to locate the exact resource keys and remote URLs. Which CLI feature is relevant? Only inspect Git author names Inspect a bundle summary for the selected target Rename the resources repeatedly Rebuild every job in the UI Explanation Correct Answer B:The summary identifies bundle resources and their deployment context. Incorrect Answers A:Git authors do not identify the deployed Databricks resource IDs. C:Renaming makes identification harder and may create resource drift. D:Manual recreation is unnecessary to find declared deployed resources.
Question 776 A bundle passes `databricks bundle validate`, but its notebook later fails because a third-party REST service is down. What does this illustrate? Validation guarantees every downstream API will be reachable Bundle configuration validation does not prove runtime external service availability A working bundle can never contain notebooks Passing validation means job permissions cannot fail at run time Explanation Correct Answer B:Validation checks the declared bundle configuration; it is not an end-to-end live integration test. Incorrect Answers A:External service conditions are outside static bundle configuration checks. C:Bundles can package and deploy notebooks and related workflow resources. D:Runtime privilege and credential issues can still occur after configuration validation.
Question 777 A developer edited a transformation notebook locally but did not commit it. The CI release builds from the approved Git commit. Why might production still run the earlier logic? All bundle deployments automatically read every developer's local files Table privileges automatically revert new source code The uncommitted local edit is not part of the approved Git commit The SQL optimizer always discards changed notebooks Explanation Correct Answer C:A commit-based pipeline consumes the committed source revision, not unsaved local workstation state. Incorrect Answers A:CI typically runs in its own checkout of the source revision. B:Authorization does not select a Git revision for deployment. D:Code revision selection happens before SQL optimization.
Question 778 A developer's local branch includes two commits, but the remote branch has a teammate's new commit. What should happen before pushing a reviewed combined change? Force-push over the teammate's commit without review Deploy unrelated production jobs instead of resolving Git history Fetch and integrate remote changes, resolve any conflicts, test, then push Delete the remote branch to make the push succeed Explanation Correct Answer C:Reconciling divergent history avoids overwriting teammates' work and preserves a reviewable result. Incorrect Answers A:Replacing the remote branch can discard work or bypass required review. B:Deployment cannot resolve the source-control divergence. D:Branch deletion loses the shared reference rather than reconciling development.
Question 779 Two feature branches modified the same notebook SQL filter in incompatible ways. A merge conflict is reported. What is the correct developer action? Reconcile the intended filter logic, test it, then commit the conflict resolution Delete the conflicting code block and use an empty filter Assume the most recently fetched version is always correct Leave conflict markers in the notebook and deploy Explanation Correct Answer A:A conflict requires a substantive choice about the merged code, not merely eliminating markers. Incorrect Answers B:Removing both versions without requirements review can break the transformation. C:Time of fetch does not establish which behavior meets the business rule. D:Conflict markers are not valid executable transformation logic.
Question 780 A production job has a known defect. An engineer fixes its deployed notebook directly, but the version-controlled bundle still contains the old code. What long-term problem is created? The production Delta data automatically becomes read-only All branch protections are automatically removed Git creates a permanent correct patch automatically Configuration and code drift that may be overwritten on the next controlled deployment Explanation Correct Answer D:The deployable source of truth no longer matches production, so the hotfix may be lost. Incorrect Answers A:Direct notebook edits do not inherently change table access mode. B:A manual notebook edit does not by itself delete repository branch rules. C:Direct remote edits are not automatically recorded in the approved Git repository.