I would say if the data is not complex and you are not handling any DQ checks in the pipeline the go for a regular databricks workflow and save it as delta table since you are refreshing the data every 1 month and it is not streaming workload.

thanks for the replay.

I also plan to orchestrated it all from airflow and I prefer not to use  databricks workflow. I know dlt work on dlt pipeline I am not sure if and how it should be done.

so you suggest saving in s3  and then create table in uc pointing on s3?

thanks 

I think if you are registering the table in UC and using delta live table you cannot create an external table in s3. It should be a managed table. DLT, by design, works with managed tables in Unity Catalog.

I meant for my use case maybe it's better to simply save in uc instead of using dlt .what do you think?

Yes if your other tables are external. Then no point going for DLT and managed table. You can just write to s3 and register the table in UC.