Orphaned entities during Configuration as Code tenant migration

Dynatrace Configuration as Code (CaC) allows for the definition of monitoring settings, dashboards, and alerting profiles via YAML files to enable repeatable environment deployments. When utilizing a GitOps workflow to synchronize a "golden" environment state across multiple tenants, the tool relies on the Dynatrace API to map the desired state to the actual environment.

A challenge arises when importing these configurations into a target environment with a different tenant ID. Because certain entities rely on unique identifiers, there is uncertainty regarding how the tool handles ID mapping during the synchronization process to prevent the creation of duplicate or orphaned entities.

Technical Constraints

• Dependency on API-driven synchronization for YAML state.
• Requirement for consistent entity mapping across distinct tenant IDs.

How does the Configuration as Code tool resolve unique identifier conflicts when applying exported YAML to a new tenant? What is the documented behavior for preventing orphaned entities during this migration?