A customer wants to migrate their AEM environment from an on-premise infrastructure to a public cloud to improve performance. The customer currently hosts many assets (images, videos, documents) in th

Question

Options

• AMove to a shared datastore and enable binary less replication
• BSet up Connected Assets to share the DAM assets in the sites
• CSet up a horizontally scalable AEM environment on MongoDB
• DRun online revision cleanup before moving to the new storage format

• A
  4% (1)
• B
  4% (1)
• C
  13% (3)
• D
  79% (19)

Explanation

Running online revision cleanup before migration is the correct architect action because AEM's Oak repository accumulates stale revision data over time, and compacting it first reduces the dataset size, ensures a cleaner migration, and prevents carrying unnecessary overhead into the new cloud storage format - this is a documented Adobe best practice before any Oak datastore migration.

Why the distractors are wrong:

• A - Binary-less replication with a shared datastore is a valid AEM optimization, but it's an ongoing configuration concern, not a pre-migration step; it doesn't address the actual process of moving the repository to cloud storage.
• B - Connected Assets is for federating assets between separate AEM Sites and AEM Assets deployments; the scenario describes a single AEM environment being lifted and shifted, not a split architecture.
• C - MongoDB (DocumentNodeStore) is not the recommended storage for cloud AEM deployments; Adobe's recommended path is AEM as a Cloud Service using Segment Store/Blob Store, and "horizontally scalable on MongoDB" is an outdated or niche pattern, not a migration best practice.

Memory tip: Think "declutter before you move." Just as you'd get rid of junk before moving homes, you run revision cleanup to compact the Oak repository and remove accumulated garbage before moving to a new storage format - smaller payload, cleaner migration.

No community discussion yet for this question.