When deploying updates to AEM as a Cloud Service, what should be prioritized?

Question

Options

• AImmediate deployment in the production environment
• BDeployment through the Cloud Manager pipeline to staging first
• CManual migration of updated content
• DDirect dispatcher rule updates without testing

• A
  2% (1)
• B
  91% (41)
• C
  2% (1)
• D
  4% (2)

Explanation

Deploying through Cloud Manager's pipeline to staging first (B) is the correct approach because AEM as a Cloud Service enforces a structured CI/CD pipeline - updates must pass automated quality gates, security scans, and functional tests in a staging environment before reaching production, ensuring stability and reducing risk.

Why the distractors are wrong:

• A skips staging validation entirely, violating AEM Cloud Service's mandatory pipeline process and risking production instability.
• C manual content migration is unrelated to code/configuration deployments and doesn't reflect how Cloud Manager operates.
• D dispatcher rule changes still require pipeline validation; bypassing testing can break caching, routing, or security filters in production.

Memory tip: Think of Cloud Manager as a "gatekeeper" - nothing reaches production without first surviving the staging checkpoint. The phrase "Stage before Prod" captures the core rule for AEM as a Cloud Service deployments.

No community discussion yet for this question.