AD0-E117 · Question #32
A client wants to change how they publish their content. Refer to the following client business requirements: - The client has a seasonal business that has significant content changes across their…
The correct answer is B. Use the Manage Publication with scheduling value set to the season change over date when. Note on this question: Based on AEM best practices, option D (Launches) appears to be the more accurate correct answer for this scenario - the stated answer of B may reflect a question error or truncated answer choices. Here's the full breakdown: Why D (Launches) best fits all…
Question
A client wants to change how they publish their content. Refer to the following client business requirements:
- The client has a seasonal business that has significant content changes across their site that
need to be rolled out at once based on the season change over date.
- The content authors need to be able to work one season in advance of publish dates to ensure
that all changes can be completed on time.
- The content authors need a way to indicate that all the seasonal changes are ready. If the
content changes are not completed, then the pages should not get published.
- The content authors need the ability to modify the current live pages without rolling back
changes for a future content rollout. What approach should the Architect recommend?
Options
- AUse the Versioning feature when editing a page to toggle and publish changes when ready.
- BUse the Manage Publication with scheduling value set to the season change over date when
- CCreate a Project inside of AEM for each new season and create a task for notifying that changes
- DUse Launches inside of AEM for each new season and use the production ready flag to show
How the community answered
(28 responses)- A4% (1)
- B82% (23)
- C11% (3)
- D4% (1)
Explanation
Note on this question: Based on AEM best practices, option D (Launches) appears to be the more accurate correct answer for this scenario - the stated answer of B may reflect a question error or truncated answer choices. Here's the full breakdown:
Why D (Launches) best fits all requirements: AEM Launches create a parallel copy of the site's page tree, allowing authors to prepare an entire season's worth of content changes in isolation while the live site remains fully editable. The production ready flag on a Launch signals that all content is finalized, and only flagged Launches get promoted - satisfying the "don't publish if incomplete" requirement. This is the only option that natively handles all four business requirements simultaneously.
Why the other options fall short:
- A (Versioning): Versioning tracks page history for rollback purposes, not for coordinating future bulk releases - it has no scheduling or readiness-gating mechanism.
- B (Manage Publication with scheduling): Scheduling publication works for known future dates but doesn't provide an isolated authoring workspace, so authors editing "future" pages would risk affecting the live experience - failing requirement 4.
- C (Projects/Tasks): AEM Projects manage workflows and task assignments but don't provide a parallel content workspace or a mechanism to gate publication based on completeness.
Memory tip: Think of Launches as a "staging branch" for content - just like a Git feature branch lets developers work ahead without touching production, a Launch lets content authors work a season ahead without touching the live site.
If this appeared on an Adobe AEM exam, flag option D as the expected answer for this scenario.
Topics
Community Discussion
No community discussion yet for this question.