Which steps are required when provisioning AEM as a Cloud Service environments? (Choose two)

Question

Options

• ASetting up development, stage, and production environments
• BValidating dispatcher configurations manually
• CConfiguring user permissions across all environments
• DDeploying updates directly to the production environment
• EConfiguring asset microservices

• A
  75% (38)
• B
  6% (3)
• C
  4% (2)
• D
  16% (8)

Explanation

When provisioning AEM as a Cloud Service, setting up the three-tier environment structure (dev, stage, prod) is fundamental - Cloud Manager automatically provisions these tiers and they form the backbone of the deployment pipeline. Configuring asset microservices is also required because AEM as a Cloud Service replaces traditional workflow-based asset processing with cloud-native Asset Compute microservices, which must be set up during provisioning.

Why the distractors are wrong:

• B is incorrect because dispatcher configuration validation is handled automatically by Cloud Manager's CI/CD pipeline - manual validation is not a provisioning step.
• C is incorrect because user permission configuration is an ongoing administrative task, not a required provisioning step.
• D is incorrect because AEM as a Cloud Service explicitly prohibits direct deployments to production; all changes must flow through the pipeline (dev → stage → prod) via Cloud Manager.

Memory tip: Think "A-E = Architecture + Engine" - you provision the environment Architecture (the three tiers) and the processing Engine (asset microservices). If an option suggests bypassing the pipeline (D) or doing something manually that's automated (B), it's wrong for a cloud-native service.

No community discussion yet for this question.