You are using seeds in your dbt project for static data lookups. During a dbt seed run, you encounter an error indicating a duplicate primary key value. What are the likely consequences?

After configuring a dbt package, you notice its models depend on a source table absent from your warehouse. How do you typically address this?

You've created a complex lineage macro, and you want to include unit tests for the macro logic itself. How might you approach this?

Your dbt models create tables, but you notice a consistent "_dbt" suffix appended to all table names. Where does this likely originate from, and how could you modify it?

You maintain a large dbt project with various reporting models that source data from a set of core business tables. These core tables often include columns with sensitive information. What technique could ensure compliance and maintainability when restricting access to this data?