An Adobe Experience Manager architect is asked to configure run mode for their UAT environment. Which configuration will work for the environment?

The correct configuration is /apps//osgiconfig/config.uat.author/.cfg.json in the ui.apps project. This structure adheres to the standard AEM project conventions for OSGi configurations. The path /apps//... is managed by the ui.apps module. The folder naming convention config.. (e.g., config.uat.author) is the correct syntax for applying configurations to an instance where multiple run modes are active. Finally, the .cfg.json extension is the required format for JSON-based OSGi configurations to be recognized by the JCR Installer. This configuration would correctly apply to an author instance within the UAT environment.

A. The ui.config project is designated for repository paths under /apps/system/config, not /apps//.... This option incorrectly places an application-specific path within the ui.config project's scope.
C. The file extension .json is incorrect. For the OSGi installer to process the file as a configuration, it must have the .cfg.json extension. A file with a .json extension will be ignored.

1. Adobe Experience Manager as a Cloud Service Documentation, "OSGi for AEM as a Cloud Service": This document outlines the recommended project structure. It specifies that the ui.config project contains mutable configurations under /apps/system/config., while the ui.apps project contains immutable application code and configurations under /apps/. This supports why option A is incorrect and option B's location in ui.apps is valid.

Reference Section: "OSGi Configurations" and "Immutable versus Mutable Content".

2. Adobe Experience Manager as a Cloud Service Documentation, "Deploying to AEM as a Cloud Service": This guide details the structure of AEM projects. It confirms that OSGi configurations are part of the code packages (ui.apps and ui.config) and explains their respective JCR paths.

Reference Section: "Project Structure".

3. Apache Sling Documentation, "OSGi Installer": This documentation specifies the file formats and naming conventions recognized by the OSGi installer, which AEM uses. It explicitly states that JSON-formatted configurations must use the .cfg.json extension. This directly invalidates option C.

Reference Section: "Providing OSGi Configurations".