How should the developer deploy the change to an AEM Cloud Service production environment?

A customer finds an Ul issue with component (/apps/<customer-project>/<component-name>) 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?
A . Fix the Ul issue as part of the customer code base and deploy the change to immutable repository using Cloud Manage’ pipeline
B . Due to the urgency of the request. Make the Ul fix directly to the component on AEM Production using CRXOE and then make same change to customer code bate
C . Fix the component on local AEM and create an AEM package for that specific component that can be deployed to Production using package Manager as a one-off urgent fix

View Answer

Answer: A

Explanation:

In AEM Cloud Service, the correct approach to making changes, even urgent ones, is to update the codebase and deploy it through the Cloud Manager pipeline. This ensures that the change is part of the version-controlled, immutable repository and follows best practices for deployment.

Immutable infrastructure: AEMaaCS does not allow direct modifications to production environments (e.g., via CRXDE Lite). All changes must be deployed through Cloud Manager, ensuring consistency and traceability.

Making changes directly on production via CRXDE or deploying one-off fixes using the Package Manager (Options B and C) violates AEMaaCS’s immutable infrastructure principle and is not supported.

Refer to Adobe Cloud Manager’s documentation for best practices on deploying urgent fixes in AEM as a Cloud Service.