An AEM Sites implementation is migrating from on-premise to AEM as a Cloud Service. Previously, the application was deployed in a single package for both code and access policy nodes. After initial…

Question

Options

• AUpdate package metadata to use MergePreserve for handling access policy nodes
• BMove access policy nodes to a dedicated package and install manually
• CRefactor access policy nodes to Apache Sling JCR Repoinit scripts in the same package
• DDocument permissions and request the Customer Success Engineer to configure

• A
  74% (20)
• B
  4% (1)
• C
  15% (4)
• D
  7% (2)

Explanation

In AEM as a Cloud Service, the package's ac-handling metadata property controls how Access Control List (ACL) nodes are processed during deployment. Setting this to MergePreserve ensures the package's access policy nodes are merged with existing system-level permissions rather than overwriting or ignoring them - which is critical in ACS where the cloud runtime pre-configures certain permissions that must not be destroyed.

Option B is wrong because AEM as a Cloud Service does not support ad-hoc manual package installation via the Package Manager UI; all deployments must flow through Cloud Manager pipelines. Option C (Repoinit) is a valid long-term best practice, but it requires significant refactoring and is not the targeted fix for an existing package deployment issue - the question asks for the corrective change to the current approach. Option D is never a valid architectural solution; delegating configuration to a CSE is neither scalable nor repeatable.

Memory tip: Think "Cloud = don't overwrite what the system owns." MergePreserve = Merge your policies in, Preserve what's already there - the safe handshake between your app's ACLs and the cloud platform's system permissions.

No community discussion yet for this question.