AD0-E124: Adobe Experience Manager DevOps Engineer ExpertDemo

By Adobe · Question Mode

QuestionQ20

Performance Optimization and Troubleshooting

A DevOps engineer gets monitoring-system notifications that a bundle is stuck in the installed state.

A new version of an OSGi bundle was recently deployed. All author and publish instances are affected. Manually starting the bundle does not resolve the problem.

What is preventing the OSGi bundle from activating?

  • A At least one OSGi component throws an exception during activation.
  • B At least one OSGi component reference is unsatisfied.
  • C At least one OSGi bundle marked as a dependency is not available in the instances.
  • D At least one OSGi component has ConfigurationPolicy set to "required" and no configuration is provided.
Explanation

An OSGi bundle must resolve its mandatory dependencies before it can start. If a required dependency bundle is unavailable, its required package wiring cannot be resolved and the bundle remains in the INSTALLED state; manually starting it cannot bypass that requirement. Component reference satisfaction and ConfigurationPolicy=REQUIRE govern Declarative Services component activation, not whether the bundle itself resolves.

Learn more

Community Discussion

No comments yet. Be the first to start the discussion!