A team is preparing to deploy an updated website to AEM as a Cloud Service. What sequence should they follow to ensure a seamless deployment?

Question

Options

• ADeploy updates directly to production and monitor logs
• BUse Cloud Manager to build, test, and deploy to staging first, then promote to production
• CUpdate dispatcher rules and deploy directly to production without testing
• DDeploy updates to preview and staging simultaneously

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

Explanation

Option B is correct because AEM as a Cloud Service uses Cloud Manager as the mandatory CI/CD pipeline - it's the only supported way to build, test, and promote code through environments. The proper flow is: build → test → deploy to staging → verify → promote to production, ensuring quality gates are passed before users are impacted.

• A is wrong because deploying directly to production skips all safety gates and risks live site breakage with no rollback safety net.
• C is wrong because updating dispatcher rules without testing is dangerous, and direct production deploys bypass Cloud Manager entirely - which isn't supported in AEMaaCS.
• D is wrong because preview and staging serve different purposes; simultaneous deployment skips the staged validation process and breaks the promotion chain.

Memory tip: Think of Cloud Manager as the only on-ramp to production in AEMaaCS - there are no side roads. The flow always goes: build → staging → production, never sideways or straight to production.

No community discussion yet for this question.