Thanks Vassil. My question is more specific to the dynamic modules. In this case I had added a custom (dynamic) module with some content items.
After doing the site sync the second instance seemed to work without the updates to the DynamicModulesConfig. On the target server I could see the new content types and add them. Also I didn't not see any errors.
What would be the downside, or the effect of not having the updated config on the target server? It didn't appear that they were needed because after the sync everything seemed to work.
Part of my goal is to establish a best practice for development and deployment of new changes when a new dynamic module is required. How does this sound so far:
1. Add new module using module builder on staging server.
2. Add new content for dynamic content item on staging server.
3. Copy updated *.config files to all production servers.
4. Perform site sync of new dynamic content types (structure only) to production servers.
5. Perform site sync of new content items to production servers.
6. Restart production server instances.
In testing I only performed steps 1, 2, 4, 5 and the new content types & data appeared on the target servers with no issues or errors.
Are steps 3 & 6 required? And if so, why is it in my testing that it worked without it?