A client wants to automate deployments for their AEM as a Cloud Service environments. Which tools and processes should you recommend?

Question

Options

• AManual deployment scripts with dispatcher configurations
• BAdobe I/O CLI for environment management and Cloud Manager pipelines for CI/CD
• CDirect production deployment using legacy processes
• DManual approval workflows for all environments

• A
  13% (2)
• B
  81% (13)
• D
  6% (1)

Explanation

Option B is correct because AEM as a Cloud Service is designed to work natively with Adobe Cloud Manager for CI/CD pipelines, and the Adobe I/O CLI provides the command-line interface for managing environments, triggering deployments, and integrating with DevOps workflows - these are Adobe's officially supported automation tools for AEMaaCS.

A is wrong because manual deployment scripts bypass Cloud Manager entirely; AEMaaCS does not support traditional dispatcher configuration management outside of Cloud Manager's pipeline-driven approach. C is wrong because AEMaaCS explicitly prohibits direct production deployments - all code must flow through Cloud Manager pipelines, and "legacy processes" are incompatible with the cloud-native architecture. D is wrong because while approval gates can exist within pipelines, requiring manual approval for all environments defeats the purpose of CI/CD automation and is not a recommended practice.

Memory tip: Think "Adobe tools for Adobe cloud" - when AEMaaCS automation is the topic, the answer will always involve Cloud Manager (the deployment engine) and Adobe I/O CLI (the control interface), never manual scripts or legacy methods.

No community discussion yet for this question.