During implementation, you identify that existing configurations are not compatible with AEM as a Cloud Service run modes. What should you do?

Question

Options

• ADeploy the configurations directly to the staging environment
• BUpdate OSGi configurations and validate them in a local SDK environment
• CIgnore the incompatible configurations and proceed with the deployment
• DRefactor workflows to bypass run mode dependencies

• A
  4% (2)
• B
  80% (39)
• C
  10% (5)
• D
  6% (3)

Explanation

Option B is correct because AEM as a Cloud Service has strict run mode constraints - configurations must be validated against the Cloud Service SDK locally before deployment to ensure compatibility, catching errors early without risking broken environments. The local SDK mirrors the Cloud Service runtime, making it the proper place to test and fix OSGi configuration issues tied to run modes like author, publish, or dev.

Why the distractors fail:

• A - Deploying incompatible configurations directly to staging propagates the problem into a shared environment, wasting pipeline runs and potentially blocking other teams.
• C - Ignoring incompatible configurations will cause runtime failures in Cloud Service environments where those run modes are enforced, not optional.
• D - Refactoring workflows to bypass run mode dependencies treats the symptom, not the cause; the OSGi configs themselves need to be corrected, not routed around.

Memory tip: Think "local before cloud" - in AEM as a Cloud Service, the SDK is your safety net. Any config change touching run modes should be validated locally first, just like you'd test code before committing.

No community discussion yet for this question.