A developer was instructed to disable plugins in their Adobe Commerce system. Which .xml file and parameter combination can perform the action?

Question

Options

• APlugins can be disabled using di.xml and by setting "disabled" parameter to "true" in plugin
• BPlugins can be disabled using events.xml and by setting "disabled" parameter to "true" in plugin
• CPlugins can be disabled using events.xml and by setting "enabled" parameter to "false" in plugin
• DPlugins can be disabled using config.xml and by setting "active" parameter to "false" in plugin

• A
  79% (15)
• B
  5% (1)
• C
  5% (1)
• D
  11% (2)

Explanation

Option A is correct because Adobe Commerce uses di.xml (Dependency Injection configuration) as the central file for registering and configuring plugins (interceptors), and the disabled="true" attribute on a <plugin> node is the proper way to deactivate one - including overriding a plugin defined in a third-party module.

Why the distractors are wrong:

• B & C both reference events.xml, which handles event observers, not plugins - a completely different extension mechanism.
• D references config.xml, which stores default system configuration values (like store settings), not dependency injection or plugin declarations. There is also no active parameter for plugins.

Memory tip: Think DI = di.xml. Plugins are a dependency injection feature, so they live in di.xml. The attribute mirrors plain English - you're "disabling" it, so the parameter is disabled="true", not enabled="false".

No community discussion yet for this question.