nerdexam
Adobe

AD0-E117 · Question #33

A news agency editor wants to publish news articles to an intermediate Publish (preview) instance for internal review before publishing the article to production Publish instance. Which two steps…

The correct answer is B. Create a reverse replication agent on preview server C. Create a separate live copy to preview content. In AEM (Adobe Experience Manager) architecture, setting up a preview-before-production pipeline requires two things: an isolated content space for preview and a mechanism for that preview instance to participate in the replication chain. Option C (Live Copy) creates a separate…

Design and Architecture

Question

A news agency editor wants to publish news articles to an intermediate Publish (preview) instance for internal review before publishing the article to production Publish instance. Which two steps should the Architect recommend? (Choose two.)

Options

  • ACreate a closed user group (CUG) for editors
  • BCreate a reverse replication agent on preview server
  • CCreate a separate live copy to preview content
  • DSet up a new replication agent for preview server
  • ECreate a custom publish workflow

How the community answered

(31 responses)
  • A
    29% (9)
  • B
    42% (13)
  • D
    10% (3)
  • E
    19% (6)

Explanation

In AEM (Adobe Experience Manager) architecture, setting up a preview-before-production pipeline requires two things: an isolated content space for preview and a mechanism for that preview instance to participate in the replication chain. Option C (Live Copy) creates a separate, manageable content branch on the preview server that mirrors production content but remains independently reviewable - keeping preview and production content cleanly separated. Option B (reverse replication agent on preview) equips the preview Publish instance with the ability to initiate replication outward (toward production), enabling the "approved on preview → promote to production" flow that the editorial workflow requires.

Why the distractors fail:

  • A (CUG): Closed User Groups control who can view content - they do nothing to create a staging pipeline between server instances.
  • D (new replication agent for preview): A standard forward replication agent on the Author pushes content to preview but doesn't give preview any ability to promote content onward to production - it only solves half the problem.
  • E (custom publish workflow): A custom workflow adds unnecessary complexity and isn't the recommended architectural pattern; the native Live Copy + reverse replication combination handles this natively.

Memory tip: Think of it as two directions - C (Live Copy) creates the landing zone for preview content, and B (reverse replication) gives preview a voice to push content forward once approved. "Receive via Live Copy, promote via reverse replication."

Topics

#AEM Replication#Live Copies#Preview Publishing#Content Workflow

Community Discussion

No community discussion yet for this question.

Full AD0-E117 Practice