A customer that uses version 6.5 wants 10 have a text component with basic text editing features. The solution must require minimal effort cost and time to meet the deadline. Which approach should a…

Question

Options

• AUse Core Text Component
• BUse HTML Source Edit
• CUse Foundation Text Component
• DCreate a new Text Component

• A
  81% (25)
• B
  10% (3)
• C
  3% (1)
• D
  6% (2)

Explanation

Option A is correct because the AEM Core Text Component (WCM Core Components) ships production-ready in AEM 6.5 with built-in rich text editing capabilities - it requires zero custom development, just drop it on the page and configure via the dialog, perfectly satisfying the minimal effort and time constraints.

Why the distractors fail:

• B (HTML Source Edit) is a toggle within the RTE editor for writing raw markup, not a standalone component - it's a feature, not a solution, and demands technical HTML knowledge.
• C (Foundation Text Component) is the legacy/deprecated predecessor; while it still exists in 6.5, Adobe explicitly steers teams toward Core Components for new work, making it a suboptimal choice.
• D (Create a new Text Component) directly contradicts the constraint - custom component development is the highest-effort, highest-cost option of the four.

Memory tip: When an AEM question mentions "minimal effort + AEM 6.5 or later," default to Core Components - they are Adobe's modern, out-of-the-box standard. Reserve Foundation for legacy maintenance scenarios, and never build custom when a Core Component already exists.

No community discussion yet for this question.