What should be considered when updating configurations for AEM as a Cloud Service? (Choose three)

Question

Options

• AAlign configurations with specific run modes
• BTest updates in the production environment
• CUse local SDKs for initial validation
• DEnsure compatibility with dispatcher configurations
• EOptimize OSGi configurations for staging and production

• A
  81% (47)
• B
  5% (3)
• E
  14% (8)

Explanation

When updating configurations for AEM as a Cloud Service, run-mode alignment (A) is essential because environment-specific OSGi configs must be placed under correctly named folders (e.g., config.author, config.publish, config.dev) so they activate only in their intended environments. Local SDK validation (C) is a required best practice - Adobe's AEM SDK lets you verify configurations locally before any cloud deployment, catching errors early without consuming cloud pipeline resources. Dispatcher compatibility (D) matters because AEM as a Cloud Service bundles dispatcher configs within the project itself, and mismatches between application and dispatcher rules cause request-routing failures in real environments.

Why the distractors are wrong:

• B is wrong because testing directly in production violates safe deployment principles - AEM as a Cloud Service uses a pipeline promotion model (dev → stage → prod) precisely to prevent untested changes from reaching production.
• E is wrong because it duplicates the intent of option A but does so incompletely. Run modes already handle environment-specific config targeting (including staging and production); framing it as a separate "optimization" step is misleading and not a distinct best practice.

Memory tip: Think "RAD" - Run modes, ACM SDK (local validation), Dispatcher compatibility. These are the three "before you deploy" checkpoints that are unique to AEM Cloud's architecture.

No community discussion yet for this question.