A customer finds an Ul issue with component (/apps//) on AEM page It needs to be fixed urgently to avoid miscommunication. The developer has been asked to urgently make the change in AEM production. How should the developer deploy the change to an AEM Cloud Service production environment?

AEM as a Cloud Service enforces a strict, immutable architecture for code deployment to ensure stability and consistency. The /apps directory, where custom component code resides, is part of the immutable repository. Consequently, any changes to code, regardless of urgency, must be committed to the project's Git repository and deployed through the mandatory Cloud Manager CI/CD pipeline. This process builds the code, runs automated quality and security checks, and then deploys the updated container image to the production environment. Direct modifications on production instances are not possible.

B: The /apps directory on AEM Cloud Service production environments is immutable. Direct modifications using tools like CRXDE Lite are technically impossible as it is a read-only view. C: Deploying code packages via Package Manager to production is not supported in AEM as a Cloud Service. All code deployments must be managed exclusively through the Cloud Manager pipeline.

1. Adobe Experience Manager as a Cloud Service Documentation, "Development Guidelines": This document explicitly states, "The immutable content partition contains /libs and /apps. Any changes in this area of the repository are not persisted after a pod is recycled... On AEM as a Cloud Service, code is deployed to a given environment as a whole... This means that one-off content packages or code fixes are not supported." This directly supports option A and refutes options B and C.

Source: Adobe Experience League. (n.d.). Development Guidelines. Adobe. Retrieved from https://experienceleague.adobe.com/docs/experience-manager-cloud-service/implementing/developing/development-guidelines.html

2. Adobe Experience Manager as a Cloud Service Documentation, "CI/CD & Development Workflow": This source clarifies the deployment process: "Code deployment to AEM as a Cloud Service can only be done through Cloud Manager. Code is checked out from a customer-managed git repository and built and deployed by Cloud Manager." This reinforces that the Cloud Manager pipeline is the sole deployment mechanism.

Source: Adobe Experience League. (n.d.). CI/CD & Development Workflow. Adobe. Retrieved from https://experienceleague.adobe.com/docs/experience-manager-cloud-service/implementing/using-cloud-manager/ci-cd-and-development-workflow.html

3. Adobe Experience Manager as a Cloud Service Documentation, "Introduction to AEM as a Cloud Service": This document outlines the fundamental architectural principles, including the separation of code and content. It notes that the AEM image contains the code and is immutable, while content is stored separately. This architectural design prevents direct code modifications on live instances.

Source: Adobe Experience League. (n.d.). Introduction to AEM as a Cloud Service. Adobe. Retrieved from https://experienceleague.adobe.com/docs/experience-manager-cloud-service/overview/introduction.html (Section: Architecture)