It is pretty easy to create a complex landscape to handle transports in your SAP Cloud Integration/CPI landscape.
Here you can see what kinds of considerations you can have when setting up he landscape.
In the video we talk about some of the a good transport process.
Composite landscapes
This is the way you configure the landscape. The reason is that we create what we call binary landscapes behind. This allows you to transport between two tenants.
On the composite landscape you can configure
Name of the different tenants in the landscape
Approval setup and deployment
Name replacements for the objects iflows etc. Here you can add or remove prefixes
External configuration replacement where you can inserts hosts that needs to be replaced between two systems
Allow and deny rules are probably more related to PI transports
Webhook to send events if different events happens like transport created or imported.
Virtual Tenants/Agents
Is a way for you to reuse one tenant for both Dev and Test? Your transport will work the same but where it will be possible to add pre or post fixes to the objects.