A customer wants to simplify and automate publishing press pages and defines the following flows: What should the Architect recommend?

Question

Exhibits

Options

• ACreate a custom workflow
• BAdvise the customer to use Launches
• CImplement a Sling event listener that triggers on page creation
• DConfigure MSM with the "Activate on Blueprint activation" option

• A
  17% (8)
• B
  71% (34)
• C
  4% (2)
• D
  8% (4)

Explanation

Launches is AEM's out-of-the-box feature purpose-built for preparing and scheduling future content (like press releases) in a parallel staging environment, then promoting it to production with minimal effort - making it the ideal fit for "simplify and automate."

Why the distractors are wrong:

• A (Custom workflow): Adds unnecessary development complexity; "simplify" is the key word here - a custom workflow works against that goal.
• C (Sling event listener): A low-level, code-heavy approach that fires on page creation, not on a content-readiness lifecycle - it's the wrong trigger for press publishing scenarios.
• D (MSM "Activate on Blueprint activation"): MSM is for replicating content across sites/regions, not for scheduling staged content releases; it solves a different problem entirely.

Memory tip: Think of Launches = press launches. The name is a deliberate hint - it's the tool editors use to "launch" campaigns and press pages at the right moment, with no custom code required.

No community discussion yet for this question.