Documentation & Version Control Flashcards
7 cards from real DBT practice questions. Tap to flip, then mark Knew It or Still Learning โ missed cards come back until you master them.
Read the first 7 Documentation & Version Control flashcards as text
Which file should typically NOT be committed to a shared Git repository because it holds credentials?
Answer: profiles.yml
profiles.yml contains connection details and secrets, so it is kept outside version control.
Which directories are normally listed in a dbt project's .gitignore?
Answer: target/, dbt_packages/ and logs/
target, dbt_packages and logs are generated or installed artifacts and should not be tracked.
What does the selector `state:modified+` combined with `--state` select?
Answer: Modified nodes and everything downstream of them
state:modified+ compares against a prior manifest and includes changed nodes plus their descendants, enabling Slim CI.
In packages.yml, how do you pin a git-hosted package to a specific tag or commit?
Answer: revision:
The revision key accepts a branch, tag, or commit SHA for git packages.
What does `package-lock.yml` record in dbt 1.7 and later?
Answer: Exact resolved package versions installed by dbt deps
dbt deps writes package-lock.yml so installs are reproducible across environments.
In the dbt Cloud IDE, why must you create a new branch before editing a project whose default branch is main?
Answer: Main is read-only in the IDE
The IDE treats the default branch as read-only so changes flow through feature branches and pull requests.
Which Git practice best supports safe collaboration on a dbt project?
Answer: Feature branches merged through reviewed pull requests with CI
Branching with PR review and CI checks catches errors before they reach production.
How this page was made: written with AI tools. We have not yet matched this exam's facts to an official source, so confirm fees, dates and rules with the exam body. Not reviewed by a subject-matter expert. Editorial policy