A client has multiple projects that need to be merged into a single deployable package for AEM as a Cloud Service. What steps should be taken to ensure a successful implementation?

Question

Options

• ADeploy each project individually to the production environment
• BConsolidate folder structures, standardize naming conventions, and test in a staging environment
• CAutomate dispatcher cache invalidation before merging projects
• DCreate separate pipelines for each project in Adobe Cloud Manager

• A
  15% (7)
• B
  72% (34)
• C
  9% (4)
• D
  4% (2)

Explanation

Option B is correct because merging multiple projects into a single deployable package for AEM as a Cloud Service requires careful structural alignment - consolidating folder structures prevents path conflicts, standardizing naming conventions avoids content/code collisions, and validating in a staging environment catches integration issues before they reach production.

Why the distractors are wrong:

• A defeats the purpose - deploying each project individually doesn't produce a single unified package and risks environment inconsistencies.
• C is a red herring - dispatcher cache invalidation is an operational concern unrelated to the package merge/build process.
• D is the opposite of the goal - separate pipelines fragment deployment rather than consolidating it into one deliverable.

Memory tip: Think "CST" - Consolidate, Standardize, Test. Merging projects is a structural problem first, so you fix the structure before you ever touch a pipeline or production environment.

No community discussion yet for this question.