Hi @Dali1 ,

When you deploy with Asset Bundles, DABk keeps track of what’s already been deployed and what has changed. That means:

• it only updates what needs updating,

• detects drift between your desired state and the workspace,

• lets you generate plans/diffs,

• and reduces deployment errors.

It you've worked with Terraform is the same concept (in fact, under the hood DABs are using terraform).  

SDK calls by themselves are stateless: if you run the same API calls over and over, you’re responsible for tracking what exists or changed - this becomes complex as your pipelines grow.