Free Adobe AD0-E137 Practice Exam with Questions & Answers | Set: 2

The correct approach to implementing an OSGi service in AEM is to use the Declarative Services annotation @Component(service = Interface.class). This ensures that the OSGi container properly registers the service against its interface, making it available for injection into other services, Sling Models, or servlets. In this case, the service is required to fetch store locations from an external API. Using an HTTP client within the OSGi service is the appropriate method to manage these requests. Option A is invalid because @OSGIService is not a valid annotation for service declaration. Option C is incorrect because @Service is not an OSGi Declarative Services annotation in this context. Adobe emphasizes encapsulating external API logic in OSGi services so that components and Sling Models can consume the data in a decoupled manner. This promotes separation of concerns and reusability.

In multi-module AEM Maven projects, the all module is responsible for packaging and deploying all submodules. To ensure a new module is included during installation, it must be listed in the embeddeds section of the filevault-package-maven-plugin configuration inside the all module. This ensures the module is packaged into the final deployable ZIP and installed into AEM. Option A and B are incorrect because the maven-bundle-plugin manages OSGi bundle metadata, not multi-module embedding. Adobe’s official archetype documentation specifies that developers must add new modules to the embeddeds configuration for them to be recognized in the final deployment.

Cloud Manager’s Content Copy feature allows administrators to copy content from Production to non-production environments such as Stage or Development. This is intended to provide accurate and representative content for testing, QA, or UAT purposes. Content cannot be copied from Development or Integration to Stage, as Adobe enforces strict controls to prevent non-production content from contaminating Production or Stage environments. Option C is correct because Production is the only valid source environment for copying content to Stage. Adobe emphasizes that copying content from Production ensures consistency and valid test data while maintaining governance and security in AEMaaCS.

Run mode-specific configurations in AEM follow a strict naming convention under the osgiconfig folder. The folder structure defines both the run mode (author or publish) and the environment (e.g., dev, stage, uat, prod). For UAT author environments, the correct structure is config.author.uat. Option C follows this convention correctly. Option A and B use incorrect naming patterns, which would prevent AEM from loading the configuration under the desired run mode. Adobe emphasizes the importance of placing OSGi configs in the correct folder paths within the ui.apps project or ui.config project depending on deployment structure.

Modern AEM projects often include front-end build processes for handling CSS, JavaScript, and component-specific assets. Webpack is the recommended tool for managing dependencies, bundling code, minification, transpilation (e.g., ES6+ to ES5), and optimizing assets. It integrates with the AEM Maven build process and supports workflows like Single Page Applications (SPA) and client libraries. Option B, Apache Sling, is the underlying web framework for AEM, not a front-end tool. Option C, Maven, manages project builds and back-end dependencies but not front-end asset pipelines. Option D, the AEM Sites Console, is for authoring and managing pages, not development builds. Adobe documentation for SPA Editor and modern AEM projects consistently demonstrates Webpack as the standard tool for front-end optimization.