A custom AEM application has a run time dependency to a third party OSGi bundle that is NOT included in out-of-the-box AEM. The third party dependency needs to be available for multiple applications and be upgraded separately from the custom AEM application.
How should a developer make sure that the bundle is installed on all environments?
A. Add the dependency to the third party bundle in the pom.xml of the project bundle.
B. Embed the third party bundle in the bundle that depends on it.
C. Embed the bundle in a content package to have it automatically deployed.
D. Declare the dependency correctly using a link to the OSGi Bundle Repository (OBR).
|
Download Printable PDF. VALID exam to help you PASS. |
 |
c
C is the correct answer
D, because of “… The third party dependency needs to be available for multiple applications and be upgraded separately from the custom AEM application” and
Ref: https://felix.apache.org/documentation/subprojects/apache-felix-osgi-bundle-repository.html
Third party dependencies will generally be made available in content package form. In cases where OSGi bundles are already available, we will simply package those bundles into a package. In cases where an OSGi bundle is not available, we will wrap dependencies into OSGi bundles and then make a content package available for easy deployment.
Answer is C
Usually, we don’t have 3rd party lib wrapped in the package. Wrapping it in the build process but it’s overkill as you need to have artificial module just for this case. So D will do the job but as numerous drawbacks: is not scalable, we expose internal dependency to the whole OSGi subsystem.
The usual practice is to embed it in the bundle manifest and deploy with our bundle. B Is correct.
Errata: not D will do the job but C.
Finally correct is B.
D
https://adobe-consulting-services.github.io/acs-aem-commons/pages/thirdparty.html
Answer is C
C is correct Answer