A developer is working on an AEM project for ABC Company. Which approach should the developer adopt to define specific build configurations for Cloud Service deployment?

Question

Options

• ACreate a separate configuration file specific to Cloud Service.
• BUtilize AEM SDK Developer Tools to configure build settings locally.
• CManually edit POM file for build configurations.
• DUse environment variables defined by AEM Cloud Service in the POM file.

• A
  19% (5)
• B
  70% (19)
• C
  4% (1)
• D
  7% (2)

Explanation

Option B is correct because the AEM SDK Developer Tools are specifically designed to mirror the Cloud Service runtime environment locally, allowing developers to configure and validate build settings in a context that replicates what Cloud Service expects - ensuring compatibility before deployment.

Why the distractors are wrong:

• A is tempting but too vague - AEM Cloud Service uses run modes and Maven profiles for environment-specific config, not a generic "separate configuration file." Creating arbitrary config files doesn't guarantee Cloud Service compatibility.
• C is partially valid in practice (POM files do hold build config), but manually editing them without using the SDK tooling misses the structured, SDK-guided approach Adobe recommends for Cloud Service compatibility.
• D mixes up two real concepts - environment variables in Cloud Manager are for runtime OSGi config, not for defining build configurations in the POM file.

Memory tip: Think "SDK = Safe Development Kit for Cloud Service" - when the question is about building for Cloud Service, the answer will point back to the AEM SDK tools, since they're Adobe's official mechanism to ensure local builds align with the Cloud runtime. If you see "local configuration that targets Cloud Service," default to SDK Developer Tools.

No community discussion yet for this question.