What is the primary purpose of reviewing existing components during the design phase?

Question

Options

• ATo ensure alignment with AEM as a Cloud Service's architectural principles
• BTo reduce the number of content templates
• CTo configure dispatcher cache invalidation rules
• DTo prepare asset metadata for migration

• A
  92% (36)
• B
  3% (1)
• D
  5% (2)

Explanation

Reviewing existing components during the design phase ensures that new or customized components align with AEM as a Cloud Service's architectural principles - such as HTL (Sling Model patterns), Core Components usage, and cloud-ready practices - preventing costly rework later in development. Option B is wrong because component review doesn't target reducing content templates; template strategy is a separate concern. Option C is wrong because dispatcher cache invalidation is an infrastructure/operations concern, not a component design activity. Option D is wrong because asset metadata preparation belongs to the migration phase, not component design review.

Memory tip: Think "design = decisions" - the design phase is about making architectural decisions that keep your components cloud-compatible; everything else (cache rules, metadata, templates) happens in different phases or workstreams.

No community discussion yet for this question.