What should be reviewed when validating existing components against AEM as a Cloud Service? (Choose two)

Question

Options

• ACode dependencies for deprecated APIs
• BCustom dispatcher configurations
• CEditable template compatibility
• DIntegration with asset microservices

• A
  80% (32)
• B
  15% (6)
• D
  5% (2)

Explanation

When migrating to AEM as a Cloud Service, validating code dependencies for deprecated APIs (A) is critical because Cloud Service runs on a continuously updated codebase that removes or replaces APIs present in older AEM 6.x versions - the Cloud Readiness Analyzer tool specifically flags these violations. Editable template compatibility (C) must also be reviewed because components often rely on template structure, policies, and content inheritance that may behave differently or require restructuring under Cloud Service's stricter template framework.

B (Custom dispatcher configurations) is incorrect in this context because dispatcher setup is an infrastructure/deployment concern, not a component-level validation - it's handled separately through the Cloud Manager pipeline. D (Integration with asset microservices) is a new capability you configure for asset processing pipelines, not something you validate existing UI/page components against.

Memory tip: Think "AC - App Code" - the two things you audit at the application code level are your API calls (deprecated?) and your Components' template dependencies. Dispatcher and microservices live outside component code, so they belong to separate checklists.

No community discussion yet for this question.