How should the developer deploy this third party library onto AEM Cloud Service?

A customer wants to support translations on AEM Cloud Service environment. They have an existing third party vendor who will provide a pre-build package that must be deployed to AEM so it can be leveraged as port of the workflow process.

How should the developer deploy this third party library onto AEM Cloud Service?
A . Store the package as part of the customer code repository under the <url>file;$(mnven.multiModuleProjectDirectory)/install</url> folder and deploy it using Cloud Manager.
B . Get the third party library as AEM package form the translation vendor and directly install it to Production environment using CRX Package Manager.
C . Host the package in a remote public or private repository (password protected) and reference it as part of pon.xml so it is included as part of Cloud Manager deployment

View Answer

Answer: A

Explanation:

In Adobe Experience Manager (AEM) as a Cloud Service, deployments are handled through Cloud Manager, and all code, including third-party libraries, must be part of the versioned code repository. To deploy the third-party package provided by the vendor, it needs to be included as part of the AEM project’s codebase under the install folder within the repository:

The package should be stored in the <url>file;$(maven.multiModuleProjectDirectory)/install</url> directory.

Once stored, the deployment will be handled through Cloud Manager’s deployment pipeline. This ensures the third-party package is included in the standard deployment process and follows AEMaaCS’s immutable infrastructure model, which ensures that changes to environments are made only through deployments using Cloud Manager.

Option B is incorrect because installing a package directly to production via CRX Package Manager is not allowed in AEM as a Cloud Service. Option C would work for self-hosted AEM instances but not for AEMaaCS, where dependencies must be part of the Maven build.

For more information, refer to AEMaaCS deployment best practices and the Cloud Manager documentation.