Comprehensive Explanation

Adobe Experience Manager as a Cloud Service separates application code from mutable repository content through a defined content-package architecture.

Immutable code packages must declare their package type as application . This designation identifies packages containing application definitions, components, configuration resources, and other code-related repository structures.

The property is configured within the FileVault Package Maven Plugin configuration:

< packageType > application < /packageType >

In a typical AEM Project Archetype implementation, the ui.apps module contains immutable application resources under /apps , while the ui.content module contains mutable content resources.

Option B is incorrect because content identifies packages containing mutable repository content, commonly associated with paths such as /content and /conf .

Option C is incorrect because container packages organize and distribute other packages. The corresponding container package generally acts as an aggregation mechanism rather than representing an individual immutable application package.

This separation is particularly important in AEM as a Cloud Service because application code is deployed through Cloud Manager pipelines using an immutable infrastructure model.

Adobe explicitly requires code packages to use the application package type, while mutable content packages use content .

Official Adobe Reference: AEM Project Structure — Package Types and Immutable Code Packages.