During the implementation of a public-facing website based on AEM as a Cloud Service, the customer raises an additional requirement to have a commenting functionality for end users implemented on…

Question

Options

• ASave comments in JCR and leverage Sling Distribution to synchronize comments between
• BIntegrate a third-party solution to store comments externally
• CUse MongoDB as provided with AEM as a Cloud Service to store the comments
• DSave comments in JCR and leverage reverse replication to synchronize comments via author

• A
  10% (5)
• B
  6% (3)
• C
  59% (29)
• D
  24% (12)

Explanation

MongoDB is correct (C) because AEM as a Cloud Service provides MongoDB as a cloud-native, scalable persistence layer specifically suited for user-generated content (UGC) like comments. Since AEMaaCS publish instances are stateless and ephemeral, writing UGC directly to the JCR on publish is fundamentally unsound - any content stored there will not survive instance recycling.

Why the distractors fail:

• A - Sling Distribution handles author-to-publish content propagation; it was not designed as a synchronization mechanism for UGC flowing in the other direction, and it won't scale reliably across ephemeral publish pods.
• D - Reverse replication (publish → author sync) was a legacy AEM 6.x feature that is not available in AEM as a Cloud Service - the cloud architecture simply doesn't support it.
• B - While integrating a third-party service is a valid pattern, MongoDB is already provided within AEMaaCS specifically for this use case (via the MSRP - MongoDB Storage Resource Provider for AEM Communities), making a separate external solution redundant and less integrated.

Memory tip: Associate "cloud publish = stateless = no JCR writes for UGC." When JCR is off the table, eliminate A and D immediately (both rely on JCR + a replication mechanism). Between B and C, remember MongoDB is included - you don't need to go outside AEM.

No community discussion yet for this question.