How is the effective configuration determined when multiple configurations for the same PID are applicable based on runmodes?

Question

Options

• ARandom selection
• BConfiguration with the lowest number of matching runmodes
• CAlphabetical order
• DConfiguration with the highest number of matching runmodes

• A
  8% (4)
• B
  2% (1)
• C
  2% (1)
• D
  89% (47)

Explanation

When multiple OSGi configurations match the current runmodes in AEM, the system uses specificity to resolve the conflict - the configuration with the highest number of matching runmodes wins because it is the most precisely targeted to the current environment. For example, a config scoped to author.dev (2 runmodes) overrides one scoped to just author (1 runmode) when both runmodes are active.

Why the distractors fail:

• A (Random) - AEM's config resolution is fully deterministic, never random.
• B (Lowest matching runmodes) - This is the opposite of the rule; fewest matches = least specific = lowest priority.
• C (Alphabetical) - Alphabetical ordering plays no role in runmode-based config resolution.

Memory tip: Think of it like CSS specificity - the more specific selector (more runmode conditions) wins, just as a more specific CSS rule overrides a general one.

No community discussion yet for this question.