Why user generated content is stored in separate node structure and not in the same content node as page

Referring to AEM 6.0 structure, can you add your thoughts on which of the below would an advantage for storing UGC separately (I came across this question) ?

A) Better cache-ability of the page
B) Simplified permissions
C) Better moderation of content

C

dwalling wrote...

One reason: ACLs on the pages are typically different than ACLs on the UGC itself. Typically UGC can be edited by the original poster as well as privileged users, whereas the corresponding pages cannot.

Second, the page nodes are always stored in JCR and only forward replicated. For UGC nodes, in AEM 6.1 and beyond the UGC nodes are stored in a configured SRP "common store". In AEM 6.0 and earlier, UGC nodes were reverse replicated to author and then forward replicated to other publish nodes in the farm. Because the UGC nodes are handled differently than page nodes, it is convenient to have them in separate structures.

 

Referring to AEM 6.0 structure, can you add your thoughts on which of the below would an advantage for storing UGC separately (I came across this question) ?

A) Better cache-ability of the page
B) Simplified permissions
C) Better moderation of content

Also from the security point, it helps in storing separately. To further improve that from AEM 6.x version it is recommended to store UGC on a separate cloud storage shared across publish instance which will avoid reverse replication