From which runmode tier does the OSGi configuration folder "config.preview" inherit its values?

Question

Options

• ADev runmode
• BAuthor runmode
• CStage runmode
• DPublish runmode

• A
  4% (1)
• B
  12% (3)
• C
  4% (1)
• D
  80% (20)

Explanation

In AEM's OSGi configuration hierarchy, config.preview inherits its values from the publish runmode tier because "preview" is architecturally a publish-side service - it runs the same publish runtime but serves content to a restricted audience before full release. Any configuration defined in config.publish flows down to config.preview unless explicitly overridden in the preview-specific folder.

Why the distractors are wrong:

• A (Dev): Dev is a local development runmode entirely separate from the publish/preview tier; it has no inheritance relationship with preview.
• B (Author): Author and publish/preview are opposite sides of the AEM architecture (content creation vs. delivery); preview has no connection to author configs.
• C (Stage): "Stage" is not a standard AEM runmode tier in the OSGi config inheritance chain - it's an environment concept, not a config folder ancestor.

Memory tip: Think of preview as "publish with a velvet rope" - it's a publish instance that gatekeeps content, so it naturally inherits from config.publish. If you remember that preview is a publish tier, the inheritance direction becomes obvious.

No community discussion yet for this question.