You're refactoring a complex SQL query into a dbt model. You notice that the model's output has significantly fewer rows than expected. Which of the following are potential causes?

• A. Your model has accidental WHERE conditions that are too restrictive.
• B. There may be a LIMIT statement leftover from development.
• C. An incorrect materialization setting on the model.
• D. Upstream data has quality issues with null values or unexpected joins.

(Multiple Select)

• A. Manually examine the compiled SQL files.
• B. Use the dbt debug command.
• C. dbt test
• D. Write a custom Python script to parse dbt models.
• E. ref() and source() functions
• F. Jinja templating
• G. dbt docs
• H. Snapshots
• I. Inspect the manifest.json file.

You've implemented a macro to standardize descriptions across a set of models. After updating the macro and regenerating docs, the changes don't seem to be reflected. What could be the cause?

• A. The documentation generator is caching the old version of the macro.
• B. The macro might only be applied to specific model types.
• C. Changes to macros sometimes require a full re-compilation of all models for the updates to take effect in the documentation.
• D. Your macro implementation has a subtle logic error.

You're getting inconsistent errors when adding new models in your dbt_project.yml. You suspect typos or indentation issues. How can you proactively improve this situation?

• A. Write tests covering various aspects of dbt_project.yml to proactively catch errors.
• B. Set up a pre-commit hook that runs a YAML validation script before committing changes.
• C. All of the above.
• D. Use a code editor or IDE with YAML-specific linting and auto-formatting support.

Which of the following scenarios might warrant you using the --no-compile flag with dbt docs generate? When you have syntax errors in your dbt models that would prevent compilation.

• A. When you want to quickly preview documentation changes without triggering a full model build.
• B. recompilation.
• C. When your CI/CD pipeline requires you to generate documentation as a separate step from model compilation.
• D. When you're deploying documentation updates to a production environment and want to minimize risks associated with model