A large retail customer is building their ecommerce platform on AEM. Several third-party vendors sell products through their site. Those vendors need to review and verify the content close to producti

Question

Options

• AGive third-party vendors access to the Author Server
• BUse the Preview Capabilities of AEM Author Server
• CExport content as PDF and share with the vendors
• DAdd a Publish (preview) Server and provide access

• A
  16% (10)
• B
  5% (3)
• C
  6% (4)
• D
  73% (47)

Explanation

Adding a dedicated Publish (Preview) Server creates an isolated, production-like tier in AEM's architecture (Author → Preview → Publish) where vendors can review fully rendered content without any authoring privileges or exposure to the live site - this is the standard AEM pattern for pre-production stakeholder sign-off.

Why the distractors fail:

• A (Author Server access) - The Author environment is where content is created and managed; granting vendors access here is overly permissive, exposes internal workflows, and risks accidental content modification.
• B (AEM Author Preview capabilities) - Author's built-in preview renders pages within the authoring context; it's not a true isolated environment and doesn't represent actual publish-tier rendering or infrastructure.
• C (Export as PDF) - PDFs can't represent interactive ecommerce experiences (carousels, pricing, CTAs) and introduce manual overhead; this is not a scalable or accurate review mechanism.

Memory tip: Think of AEM's three-tier architecture as a runway - Author is backstage, Preview Publish is the dress rehearsal, and Publish is the live show. Vendors belong in the dress rehearsal, never backstage.

No community discussion yet for this question.