Adobe AD0-E137 Adobe Experience Manager Sites Developer Expert Exam Practice Test

Explanation (Adobe Docs Reference):

The correct OSGi Declarative Services (DS) implementation in AEM:

Must use implements (not extends).

Must register the service interface (SimpleService.class).

Should return an implementation for getMessage().

Option D is the correct implementation.

Options A, B, C are wrong because:

A incorrectly uses extends.

B and C register the wrong service type (MySimpleService).

Adobe Documentation:

“An OSGi service implementation must implement its interface and be annotated with @Component(service=Interface.class) to register the service.”

— OSGi Services in AEM

Two important weekly maintenance tasks for repository health are:

Datastore Garbage Collection (A): Cleans up unreferenced binaries in the datastore, preventing unnecessary growth in storage size.

Online Revision Cleanup (D): Reclaims space in the segment store by compacting revisions and removing obsolete data.

Option B, Clientlib Dumps, does not affect repository size. Option C, Version Purge, should be scheduled daily rather than weekly for continuous health. Adobe’s official guidelines recommend combining datastore GC with revision cleanup to prevent segment store bloat and performance degradation, ensuring repositories remain lean and optimized.

The error clearly indicates that the bundle is exporting a package without specifying a version. In OSGi, best practices dictate that every exported package must declare a version in the Export-Package manifest header. Furthermore, consumers of these packages must use Import-Package with version ranges to ensure compatibility and avoid conflicts during runtime. The absence of a version means other bundles cannot reliably resolve the correct package version, leading to potential deployment issues. Option A and D are general dependency resolution checks but do not address the specific missing version. Option B relates to conflicts with AEM-provided bundles, which is not the cause here. The correct fix is to add a version to the Export-Package declaration and ensure imports define version ranges. Adobe explicitly highlights this as part of OSGi bundle troubleshooting.

In AEM, fine-grained access control is managed using JCR Access Control Entries (ACEs). To grant access only to a specific node but exclude all child nodes, the correct approach is to set the rep:glob = "" property. This ensures that permissions apply strictly to the node itself and not recursively. Option B, rep:globs = "**", would apply access recursively to all descendants. Option C, rep:glob = "child", is invalid and does not represent a valid configuration. Adobe recommends precise use of rep:glob patterns to restrict user access according to security requirements, ensuring least-privilege principles.

AEM package files follow a standard naming convention in CRX Package Manager:

--.zip

Thus, with the package name aem-package, group aem_group, and version 1.0, the correct package name is aem-package-aem_group-1.0.zip. Option B is invalid because group names and content paths are not combined in filenames. Option C omits the group name, making it incomplete. Adobe documentation emphasizes this naming convention for easier package identification and dependency management across environments.

In AEM, multi-site management allows centralized content updates to be pushed across different localized or departmental sites. The “Partial” option on the rollout configuration ensures that only specific components or regions designated for shared updates are synchronized, while leaving local content intact. This fits the described requirement where a portion of each school’s homepage must receive university updates without affecting school-specific content. Option A, Experience Fragments, could be used but are better suited for shared fragments of design/content, not controlled rollout scenarios. Option C requires manual inheritance restoration per page, which is inefficient. Option D, implementing custom rollout logic, is not needed when the built-in “Partial Rollout” option fulfills the requirement. Adobe emphasizes using partial rollout in multi-site configurations to balance central control with localized autonomy.

When workflows require complex conditional logic or integration with external systems, Adobe recommends writing custom workflow process steps in Java. By implementing the WorkflowProcess interface, developers can evaluate metadata dynamically and invoke APIs or services as needed. Option A is too limited because out-of-the-box workflow steps support simple operations but cannot manage advanced branching or integrations. Option C is not suitable because content fragments are intended for structured content authoring, not for managing asset workflows. Adobe’s documentation states that workflows should remain modular, with custom steps encapsulating business-specific logic, while the Workflow Model defines the process flow. This ensures extensibility, testability, and clean separation between workflow orchestration and implementation logic.

Explanation (Adobe Docs Reference):

The recommended way to bind servlets in AEM (OSGi DS) is via the @SlingServletResourceTypes annotation.

The methods value must be uppercase "GET".

doGet() method must use SlingHttpServletRequest and SlingHttpServletResponse instead of standard Servlet API request/response.

SlingAllMethodsServlet is safe for handling multiple HTTP verbs, but you can extend SlingSafeMethodsServlet too. However, in Adobe docs examples, the uppercase "GET" with doGet(SlingHttpServletRequest, SlingHttpServletResponse) is correct.

Text pre-extraction is recommended during reindexing of existing Lucene indexes that have binary extraction enabled. Binary extraction is the process where text content is extracted from binary files (such as PDFs or Word documents) for indexing. During reindexing, extracting text repeatedly from large binaries can cause performance degradation. Pre-extraction allows text to be extracted once and reused during indexing, significantly reducing reindexing time and system load. Option B is incorrect because small repositories don’t require pre-extraction optimization. Option C is also incorrect, as images generally don’t involve binary text extraction unless paired with OCR. Adobe highlights pre-extraction as a performance optimization technique for reindexing scenarios involving binary text content.

In Adobe Experience Manager Dispatcher configuration, cache-related settings are defined inside the dispatcher.any configuration files located under /etc/httpd/conf.dispatcher.d/cache/. By default, the dispatcher module loads its cache rules from the file named _cache.any. This file specifies which resources should be cached, ignored, or invalidated.

From Adobe Documentation:

“Cache configuration is defined in the dispatcher.any configuration file, typically found in /etc/httpd/conf.dispatcher.d/cache/_cache.any.”

— Adobe AEM Dispatcher Documentation – Cache Configuration (AEMaaCS & AEM 6.5+)

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.

Explanation (Adobe Docs Reference):

The SAML Authentication Handler in AEM requires the following key properties:

path: Defines the content path where this handler applies (here /content/siteB).

idpUrl: The Identity Provider’s SAML endpoint (here https://www.idpB.com).

Other properties like serviceProviderEntityId and assertionConsumerServiceURL are also required in a real-world setup but the correct basic mapping in this scenario is option B.

Adobe Documentation:

“The SAML authentication handler is configured by setting path to the protected resource root and idpUrl to the Identity Provider endpoint.”

— Adobe AEM 6.5 – SAML Authentication Handler

In Dispatcher configuration, request filtering is handled through the filters.any file. To deny access to specific content types or formats (like .json and .xml) for certain paths, the configuration must explicitly match both the extension and the path using correct syntax. The valid approach uses:

/0001 { /type "deny" /extension "(xml|json)" /path "(/path2|/path3)/*" }

Options A and B contain syntax errors. Option A incorrectly uses JSON/* instead of paths, and Option B mixes array-style brackets instead of regex or path expressions. Option C follows the correct pattern of specifying deny rules with /extension and /path. Adobe recommends always explicitly denying unwanted selectors or extensions to prevent exposure of sensitive content through JSON or XML requests.

Workflow launchers in AEM are designed to monitor changes in specific repository paths such as /content, /content/dam, and /conf. However, changes under certain system-level paths, including /var, do not trigger workflows. This restriction is intentional, as /var is used for system-generated and internal data such as workflow instances, audit logs, and temporary nodes. Triggering workflows on changes under /var could result in recursive or unintended behavior. Option A is unrelated because Workflow Process Legacy Mode refers to backwards compatibility. Option B is incorrect, as AEM does allow system nodes under /var, but they are not workflow-launcher enabled. Adobe documentation makes clear that workflow launchers must be configured under supported content paths for them to execute correctly.

In AEM as a Cloud Service, multi-tenant projects can be managed via independent repositories linked to a primary project repository using git submodules. When a new tenant is added, the tenant’s repository must be registered as a submodule of the main project so that it is included in the CI/CD build and deployment pipelines.

From Adobe Documentation:

“When using independent repositories for tenant modules, these repositories must be referenced as git submodules in the main project repository. This ensures they are included in the Cloud Manager build and deployment process.”

— Adobe AEM as a Cloud Service – Multi-tenant Setup & Git Submodules