A Business Practitioner needs to deactivate content that Is published In production. Where should the deactivation workflow be initiated?

Question

Options

• AOn the dispatcher
• BOn the author
• COn the CDN
• DOn the publish

• A
  6% (1)
• B
  88% (15)
• C
  6% (1)

Explanation

In AEM (Adobe Experience Manager), the Author environment is the control center for all content lifecycle operations, including activation and deactivation. Initiating a deactivation workflow on Author triggers a replication action that removes (unpublishes) the content from the Publish instance - this is the correct and only supported workflow path.

Why the distractors are wrong:

• A (Dispatcher): The Dispatcher is a caching/load-balancing layer; it serves cached responses but has no workflow engine or content management capabilities.
• C (CDN): The CDN is even further upstream for delivery acceleration - it has no awareness of CMS content workflows.
• D (Publish): The Publish instance serves live content to end users but is not meant for business practitioners to log into and manage workflows; it receives instructions from Author via replication.

Memory tip: Think of Author as the "source of truth and command." Content only flows from Author - both going live (activate) and going dark (deactivate) must be commanded from Author. If it affects what users see on Publish, Author initiates it.

No community discussion yet for this question.