Question 350 A Git folder shows a clean working tree but the production deployment is missing the latest merged changes. What should be checked? Inspect only the developer folder branch and ignore the CI checkout ref Assume a clean local Git worktree proves the CI runner checked out the intended commit Only the number of source rows in bronze The CI workflow's selected commit/ref and target deployment status Explanation Correct Answer D:A clean local tree does not prove production has deployed the latest reviewed revision. Incorrect Answers A:A clean local folder does not show which commit was selected and deployed by the production CI runner. B:A clean local checkout does not identify the revision actually selected and deployed by another automation runner. C:Data volume cannot establish which Git revision was deployed.
Question 351 A production job requires different credentials from development. Which bundle design preserves one codebase without exposing passwords? Use one shared admin password in every environment Environment-specific identity/secret references supplied outside source-controlled plaintext Hardcode each password in the bundle YAML committed to Git Disable all authentication in production Explanation Correct Answer B:Targets can reference approved environment resources while sensitive values remain protected. Incorrect Answers A:Common privileged credentials broaden blast radius and weaken isolation. C:Plaintext credentials in version control can be exposed and are hard to rotate safely. D:Removing authentication is unsafe and generally invalid.
Question 352 A declarative bundle includes a schedule and a job definition, but the first deployment to test accidentally enables production-style frequent execution. What should be separated? The Git commit author names Target-specific schedule or pause settings for test versus prod Use a production schedule in every target and rely on reviewers not to launch the test job All table schemas into one ungoverned namespace Explanation Correct Answer B:Environment overrides can keep test resources from running on production cadence. Incorrect Answers A:Authorship metadata does not set schedules. C:The deployment should isolate schedule behavior by target; identical active schedules can start unintended test workloads. D:Schema consolidation is not the solution to target-specific execution cadence.
Question 353 An engineer wants a CI check that refuses to deploy if a bundle references a nonexistent job task dependency. Which control is appropriate? Only rerun git status Deploy first and only inspect errors after production runs Run bundle validate and fail on invalid resource references Only run COUNT(*) on a source table Explanation Correct Answer C:Validation can catch malformed bundle resource graphs before the target is modified. Incorrect Answers A:Git status reports local file changes, not configuration reference validity. B:Post-deployment discovery risks affecting live workloads. D:Data counts cannot validate a job DAG resource reference.
Question 354 A project manages several Lakeflow Jobs and one pipeline as one deployable unit. Which bundle capability is central? Place all assets in a raw CSV file Declare multiple workspace resources in the bundle configuration Grant SELECT to all workspace users Use one manual notebook run as the sole deployment record Explanation Correct Answer B:A bundle can package related job and pipeline resources for consistent environment promotion. Incorrect Answers A:CSV data storage is not a declarative job/pipeline resource definition. C:Broad data access is not necessary for bundling job resources. D:Manual execution does not define or deploy the complete resource set.
Question 355 A developer uses an unreviewed local branch to deploy directly to production. What CI/CD safeguard is most relevant? Require an approved protected-branch or release revision for prod deployment Require production deployment tokens but permit use from any unreviewed feature branch Run YAML validation on every feature branch but allow direct production deployments without review Only change job parameter names Explanation Correct Answer A:A protected promotion gate ties production to reviewed, tested source revisions. Incorrect Answers B:A deploy token controls authentication, but without a protected source/ref policy an unreviewed change can still reach production. C:Syntax validation helps catch malformed configuration but cannot substitute for a reviewed, approved release source. D:Parameter naming does not establish source approval provenance.
Question 356 A job bundle is deployed to dev, but a reviewer cannot tell which Git commit produced that deployment. Which metadata would improve auditability? Capture the source commit identifier and selected bundle target in release evidence Record only the semantic version label without the resolved source commit Only record the table owner email Only record the number of cluster workers Explanation Correct Answer A:A commit-to-target link makes deployed configuration traceable to a reviewed code revision. Incorrect Answers B:A mutable release label by itself does not reliably identify the exact Git revision that produced the deployment. C:Ownership is not a deployment commit identity. D:Worker count does not establish Git provenance.
Question 357 An engineer updates a bundle job definition but forgets to push the branch before CI runs against the remote repository. What can happen? Unity Catalog revokes production table grants CI may deploy the older remote revision instead of the local unpushed change All deployed jobs are destroyed by Git status CI always reads every developer's local disk automatically Explanation Correct Answer B:The remote pipeline operates on commits available to it, not unseen local edits. Incorrect Answers A:A missing Git push does not inherently modify catalog permissions. C:Local Git status does not delete remote resources. D:Remote runners generally cannot access an unpushed workstation working tree.
Question 358 A bundle deployment should be tested in staging before production. The configuration has a staging and prod target. What sequence supports the gate? Disable all tests because bundle syntax is valid Validate and deploy to staging, test behavior, then deploy approved revision to prod Deploy to prod first and validate after user impact Create a new untracked copy of the notebook for prod Explanation Correct Answer B:Promoting the same tested source revision across targets reduces configuration surprises. Incorrect Answers A:Configuration validity does not prove application behavior. C:This reverses the intended staging quality boundary. D:Untracked copies undermine reproducible version promotion.
Question 359 A development repository has multiple contributors changing the same notebook. Which Git practice reduces accidental overwrites when merging? Use one shared credential with no attribution Let everyone force-push the production main branch Use branches, pull requests and conflict review Discard local edits whenever another developer commits Explanation Correct Answer C:A reviewed merge resolves competing edits rather than silently replacing work. Incorrect Answers A:Shared identities obscure authorship and do not solve merge conflicts. B:Force-pushing shared history can overwrite others' changes. D:Unconditionally dropping work is not proper collaborative conflict resolution.
Question 360 A deployment pipeline runs a shell command to apply a bundle, but the CLI is authenticated to the wrong workspace. Which guard should be added? Run bundle deploy while trusting the CLI's default active profile Check the target name but not the actual authenticated CLI workspace host Only rename the deployment script Check the authenticated profile/host against the selected bundle target Explanation Correct Answer D:Credential environment and target host must match before applying workspace changes. Incorrect Answers A:A default profile may point to the wrong host; the runner should verify host/profile against its selected target before changing resources. B:The same target label can be applied while a CLI profile points at a different workspace; both effective host and target must be checked. C:Script renaming does not change the authenticated workspace endpoint.