Adobe Experience Manager uses the OSGi framework to provide a modular runtime environment in which individual bundles supply services and application functionality.
The OSGi bundle lifecycle defines several distinct runtime states, including INSTALLED, RESOLVED, STARTING, ACTIVE, STOPPING, and UNINSTALLED.
When a bundle is initially installed, it enters the INSTALLED state. At this point, the framework has registered the bundle, but its dependencies may not yet have been successfully resolved.
Once the OSGi framework resolves the bundle's required packages and dependencies, the bundle can transition to RESOLVED.
When activation begins, the framework enters the STARTING state. During this stage, the bundle's activation lifecycle executes, subject to the applicable OSGi activation policy.
After successful activation, the bundle enters the ACTIVE state and can provide its registered services for consumption.
Adobe's OSGi API reference explicitly distinguishes RESOLVED bundles, which are capable of starting, from ACTIVE bundles, which are running.
Option A incorrectly introduces STOPPING at the beginning. Options C and D also place lifecycle states in an invalid sequence for the normal installation and activation process.
Official Adobe references:
Adobe AEM API Documentation — OSGi Bundle Interface and Lifecycle States
Submit