An author plans to change the source pages that occur as a result of normal maintenance. The author will handle multiple root branches and promote the content without disturbing the published…

Question

Options

• AUse Launches
• BUse the rollout option on a blueprint
• CUse live copy
• DUse Projects

• A
  3% (1)
• B
  70% (26)
• C
  8% (3)
• D
  19% (7)

Explanation

Rolling out from a blueprint is the correct approach because AEM's Multi-Site Manager (MSM) is designed exactly for this scenario: when a blueprint (source) is updated during maintenance, the rollout action propagates those changes to all connected live copies (the multiple root branches) in a controlled, configurable way - allowing authors to push updates without immediately disturbing published content.

Why the distractors are wrong:

• A (Launches): Launches are for staging future content changes (e.g., a campaign going live on a specific date), not for propagating source-page maintenance across multiple inherited branches.
• C (Live copy): A live copy is a relationship (the copy itself), not an action - it describes the structure MSM creates, not the mechanism for pushing changes.
• D (Projects): Projects are a workflow/task-management feature for team collaboration; they have no role in content propagation across site branches.

Memory tip: Think of it as a franchise model - the blueprint is corporate headquarters, and live copies are the franchise locations. When HQ (blueprint) updates its standards, rollout is how those updates are "shipped" to all locations (branches) without closing any store (disturbing published content).

No community discussion yet for this question.