AD0-E408 · Question #102
Which composer should be used to make design choices without requiring direct editing of the code?
The correct answer is C. Visual Experience. Visual Experience Composer (C) is correct because it provides a WYSIWYG (what-you-see-is-what-you-get) interface that lets users make design and layout changes by pointing and clicking on page elements - no code editing required. It abstracts away the underlying code, making it a
Question
Which composer should be used to make design choices without requiring direct editing of the code?
Options
- AData Platform
- BForm Based
- CVisual Experience
- DPage Composer
How the community answered
(31 responses)- A6% (2)
- B3% (1)
- C90% (28)
Explanation
Visual Experience Composer (C) is correct because it provides a WYSIWYG (what-you-see-is-what-you-get) interface that lets users make design and layout changes by pointing and clicking on page elements - no code editing required. It abstracts away the underlying code, making it accessible to non-developers who need to modify visual presentation.
Why the distractors are wrong:
- A. Data Platform - focused on data management, ingestion, and analytics pipelines, not visual design decisions.
- B. Form Based - relies on structured input fields and configuration forms, which still require understanding of properties and settings rather than direct visual manipulation.
- D. Page Composer - a more technical tool typically used for structural page customization; it may involve direct property editing or code-level configuration.
Memory tip: The word Visual is the giveaway - if you're making design choices by seeing and interacting with the interface rather than touching code, think Visual Experience Composer. Associate "Visual = No Code Needed."
Topics
Community Discussion
No community discussion yet for this question.