I understand that you have an external source, and AEM needs to deliver the content based on that source. And as that source can receive changes at any time, these changes need to be reflected on the content generated by AEM as well. A few questions:Is there any personalization on top of that conten...

Check the documentation at https://experienceleague.adobe.com/en/docs/experience-manager-cloud-service/content/implementing/content-delivery/cdn#point-to-point-CDN

My personal opinion on that, is that if you need to invalidate CDN and dispatcher caches on a regular basis, you are doing something wrong, or caching was an afterthought in your whole content strategy. Normally the default AEM dispatcher invalidation plus a TTL-based invalidation should be sufficie...

The easiest way is probably to check on the DNS level. For example www.adobe.com $ host www.adobe.com www.adobe.com is an alias for stls.adobe.com-cn.edgesuite.net.stls.adobe.com-cn.edgesuite.net is an alias for stls.adobe.com-cn.edgesuite.net.globalredir.akadns.net.stls.adobe.com-cn.edgesuite.net.g...

The default GET servlet has an OSGI configuration how many nodes are serialized via this mechanism; IIRC it's value is 100 nodes, and you can adapt it.  This value is just a DOS prevention, so if you have prevented this functionality from being used on publish (the documentation strongly suggests no...

In that case you should think how you want to use the MSM relations, and how the MSM rollouts will be done. Also about local changes, which are overriding MSM inheritance.(You should also do the math and think about if the MSM is the right tool here. Rollouts can be costly/performance-intense, and i...

At first sight I would agree to your structure. But there are several unknowns, which can influence this. A few thoughts: ACLs?Content reuse (same offer over stores of multiple brands), you might think about using CF/XFs for it. Also about asset reuse.Do you plan to use the MSM or the language copy ...

I assume that it can take a lot of time, but it should not have failed. How did you determine that it failed?

regarding the naming: yes, it's quite inconsistent. Replication = publishing. And if you take away the replication privilege from a user, then this user is not able to replicate directly; instead AEM will invoke this workflow.

Have you tried to create a content package of that path, and then replicate the package?  Installing that package might definitely take a while, so I am not sure if that is acceptable.