In the Visual Experience Composer (VEC), what considerations should a Target Business Practitioner be aware of when using the "Layout" options such as "Rearrange" and "Move"?

Question

Options

• AThe Move option automatically adjusts other elements to accommodate the moved element.
• BElements are allowed to be moved outside their parent containers without any restrictions.
• CCertain actions like Rearrange and Move may exhibit inconsistent behavior if lazy loading occurs.
• DClick-tracking functions smoothly with rearranged and moved items.

• A
  18% (10)
• B
  7% (4)
• C
  72% (41)
• D
  4% (2)

Explanation

Option C is correct because the VEC applies modifications to the DOM at page load, but lazy-loaded elements may not exist in the DOM at that moment. When "Rearrange" or "Move" targets an element that loads asynchronously afterward, the action either fails silently or produces unpredictable results, since the DOM structure Target expected has changed.

Why the distractors are wrong:

• A is false - The Move option repositions the selected element only; it does not automatically reflow or adjust surrounding elements, which can cause overlapping or broken layouts.
• B is false - VEC does restrict movement outside parent containers; you cannot freely drag elements across arbitrary DOM boundaries without limitations.
• D is false - This is actually another known problem: click-tracking selectors are tied to the element's original DOM position, so rearranging or moving elements can break click-tracking rather than leave it unaffected.

Memory tip: Tie C to the phrase "lazy page, lazy results" - lazy loading delays elements from entering the DOM, so any VEC layout action that depends on those elements being present will behave inconsistently. If the element isn't there yet, Target can't reliably move it.

No community discussion yet for this question.