A developer is tasked with building a complex new section for the Adobe Commerce Admin panel. The client wants a modern, highly interactive user interface and wants to ensure the extension is as decou

Question

Options

• AThe Admin UI SDK for out-of-process extensibility
• BExtending the Admin using only 'adminhtml' layout XML updates
• CUsing a PWA Studio application inside an Admin iframe
• DThe traditional UI Component framework with custom JavaScript

• A
  82% (27)
• B
  3% (1)
• C
  12% (4)
• D
  3% (1)

Explanation

Option A is correct because Adobe's Admin UI SDK was specifically designed for out-of-process extensibility - it allows developers to build self-contained React applications that are securely injected into the Admin panel via iframes with a postMessage communication bridge. This keeps extension code completely isolated from the Commerce core, making upgrades far safer and the architecture truly decoupled.

Option B (adminhtml layout XML) is wrong because this is the traditional in-process approach: it modifies Admin templates directly, tightly coupling the extension to core internals and making upgrades risky.

Option C (PWA Studio in an iframe) is wrong because PWA Studio targets the storefront (customer-facing), not the Admin panel - it's a completely different product surface and not designed for Admin extensibility.

Option D (UI Components + custom JS) is wrong because the legacy UI Component framework is also in-process and tightly coupled to the core, which is exactly what the client wants to avoid.

Memory tip: Think "SDK = Separate, Decoupled, Kotlin-free React" - the Admin UI SDK gives you a Separate React app that is Decoupled from core. The word "out-of-process" in the answer is the key phrase; whenever you see a question about decoupled, modern React-based Admin extensions, that phrase points directly to the Admin UI SDK.

No community discussion yet for this question.