lakehouse-data-architect

Databricks lakehouse architecture organizes data pipelines across Bronze, Silver, Vault, and Gold layers to unify data engineering and analytics. It structures ETL workflows by progressively refining raw data into curated datasets for governance and consumption.

Designing ETL data pipelines for a Databricks lakehouse involves orchestrating tasks across Bronze, Silver, Vault, and Gold layers. You align planning and governance rules with repository context to produce structured architecture artifacts and design deliverables.

Yes, the lakehouse architecture approach supports integration with external data sources. It orchestrates data pipelines to ingest and process external data through the Bronze, Silver, Vault, and Gold layers within the Databricks environment.

Yes, you can use this to generate data governance artifacts for Databricks pipelines. It adopts the Lakehouse Data Architect role to deliver design plans, QA findings, and governance outputs tailored to your repository context.

The best way to structure architecture deliverables for a Databricks lakehouse is to sync with repository mapping and adopt the defined architect role. This ensures generated plans, designs, and reports match expected agent artifacts and governance rules.

Yes, you need a mapped repository context to produce tailored lakehouse architecture plans. The skill aligns its outputs by syncing with repository mapping to ensure deliverables match the expected agent behavior and design rules.