โ† All DBT Flashcard Decks

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
  1. Which artifact produced by `dbt docs generate` holds column data types and table statistics gathered from the warehouse?

    Answer: catalog.json

    catalog.json is built by introspecting the warehouse, while manifest.json describes the project's parsed resources.

  2. What is the default port used by `dbt docs serve`?

    Answer: 8080

    dbt docs serve hosts the documentation site on port 8080 unless --port is specified.

  3. Which syntax correctly defines a reusable doc block in a .md file?

    Answer: {% docs order_status %} ... {% enddocs %}

    Doc blocks are wrapped in {% docs name %} and {% enddocs %} and later referenced with the doc() function.

  4. How do you reference a doc block named order_status inside a YAML description?

    Answer: description: '{{ doc("order_status") }}'

    The doc() Jinja function pulls in the content of a named doc block.

  5. Which config pushes model and column descriptions into the warehouse as comments?

    Answer: persist_docs

    persist_docs with relation and/or columns set to true writes descriptions to the database objects.

  6. What is the purpose of an exposure in dbt?

    Answer: Documenting a downstream use of models such as a dashboard

    Exposures declare downstream consumers like dashboards or ML apps so they show up in the DAG and docs.

  7. What does the `--no-compile` flag do with `dbt docs generate`?

    Answer: Skips compiling the project before generating docs

    --no-compile reuses the existing manifest rather than recompiling the project before building the catalog.

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