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 content. What should a Business Practitioner recommend to the content authoring team?

The scenario describes managing content updates across multiple related websites ("multiple root branches") from a central source. This is the primary use case for Adobe Experience Manager's Multi-Site Manager (MSM) feature. A "blueprint" serves as the source, and "live copies" are the destination sites. The action to propagate changes from the blueprint to the live copies is called a "rollout." This process updates the authoring versions of the live copies, and the published content remains unchanged until the author explicitly activates the updated pages, thus meeting the requirement to not disturb the published content during maintenance.

A. Use Launches: Launches are designed for creating and managing future, time-based releases of content. While they isolate editing, they are more suited for major updates or campaigns, not typically for "normal maintenance."
C. Use live copy: A live copy is the destination of the content propagation; it is the object being managed, not the tool or process used to perform the update from the source.
D. Use Projects: AEM Projects are an organizational tool for managing workflows, tasks, and teams. While a content update task could be managed within a Project, it is not the feature that executes the content synchronization itself.

1. Adobe Experience Manager as a Cloud Service Documentation, "Multi-Site Manager Concepts": This document defines the core components. It states, "A blueprint configuration identifies an existing website that you want to use as the source for one or more live copy pages." and "A rollout is the central MSM action that synchronizes live copies with their source." This directly supports using a blueprint and the rollout action for propagating changes.

Source Reference: Adobe Experience Manager as a Cloud Service Documentation > User Guide > Sites > Administering > Multi-Site Manager > MSM Concepts.

2. Adobe Experience Manager as a Cloud Service Documentation, "Creating and Synchronizing Live Copies": This guide details the rollout process. It explains, "You can roll out blueprint page changes to a live copy page to synchronize the pages... A rollout can be triggered by an author (on a blueprint page) or by a system event (as configured by the rollout configuration)." This confirms that "rollout" is the recommended action for an author to promote changes from a blueprint.

Source Reference: Adobe Experience Manager as a Cloud Service Documentation > User Guide > Sites > Administering > Multi-Site Manager > Creating and Synchronizing Live Copies, Section: "Rolling Out Changes to a Live Copy".

3. Adobe Experience Manager as a Cloud Service Documentation, "Launches": This document clarifies the purpose of Launches. "Launches enable you to efficiently develop and publish a future release of one or more activated web pages." This positions Launches as a tool for future releases, which is distinct from the "normal maintenance" described in the question.

Source Reference: Adobe Experience Manager as a Cloud Service Documentation > User Guide > Sites > Authoring > Working with Page Content > Launches.