A customer is preparing for holiday sales and needs to update the live site at exactly midnight local time, without any manual intervention. All changes are already done on the author instance…

Question

Options

• AAEM Translations
• BManage Publication
• CQuick Publish
• DLaunches
• EMuIti-Site-Manager

• A
  5% (3)
• B
  82% (45)
• C
  11% (6)
• E
  2% (1)

Explanation

Manage Publication (B) and Launches (D) together solve both requirements: unattended deployment and exact scheduling.

• Launches (D) lets the team stage an entire set of changes in a parallel "launch" copy of the site, completely isolated from the live experience until it's ready. It is the right tool for preparing a large batch of holiday content in advance.
• Manage Publication (B) provides the scheduling mechanism - you can target a precise date/time for activation, so the launch goes live at exactly midnight with no one clicking a button.

Why the distractors fail:

• Quick Publish (C) pushes content live immediately - there is no scheduler, so someone would have to be awake at midnight to trigger it manually.
• AEM Translations (A) is a localization workflow for converting content into other languages; it has nothing to do with publish scheduling.
• Multi-Site-Manager (E) manages inheritance relationships between a blueprint site and its live copies across regions/brands; it does not schedule deployments.

Memory tip: Think of it as a two-step rocket launch - Launches is the payload (all your prepared changes sitting on the pad), and Manage Publication is the countdown timer that fires it automatically at T-midnight. You need both the payload and the timer for an unattended, on-schedule liftoff.

No community discussion yet for this question.