Which configuration update is essential to align with AEM as a Cloud Service run modes?

Question

Options

• AContent taxonomy adjustments
• BDispatcher flush rules optimization
• CRefactoring custom workflows
• DUpdating OSGi configurations based on run modes

• A
  4% (1)
• B
  7% (2)
• C
  11% (3)
• D
  78% (21)

Explanation

Updating OSGi configurations based on run modes (D) is essential because AEM as a Cloud Service uses environment-specific run modes (author, publish, dev, stage, prod) to activate different OSGi config files - misconfigured or missing run-mode-specific configs are a leading cause of failures when migrating to AEMaaCS.

Why the others are wrong:

• A (Content taxonomy) - taxonomy is a content modeling concern, not a run mode alignment issue.
• B (Dispatcher flush rules) - Dispatcher configuration matters for caching, but flush rules are not tied to run mode configuration alignment.
• C (Custom workflows) - workflow refactoring may be needed for AEMaaCS compatibility, but it's unrelated to run mode configuration.

Memory tip: Think of run modes as "environment switches" - OSGi configs are the only config type in AEM that activates/deactivates based on which switch is flipped, making them the essential thing to align when targeting AEMaaCS environments.

No community discussion yet for this question.