AD0-E137 Adobe Experience Manager Sites Developer Expert Questions and Answers

The segment store in AEM grows as new content versions are created and retained. If not managed, this can result in significant performance degradation and increased storage size. To address this, the Version Purge maintenance task should be scheduled daily. This task removes old, unused versions of nodes and ensures that the repository remains healthy and compact. Option A, Audit Log Purge, cleans old audit entries but does not significantly affect segment store size. Option B, Lucene Binaries Cleanup, targets binary references but is not the main factor behind large segment store growth. Adobe recommends running Version Purge regularly as part of AEM maintenance to balance data retention needs and performance optimization.

By default, when saving dialog values, AEM stores them as String types in the JCR unless a type hint is provided. To ensure a checkbox is stored as a Boolean, developers must add a hidden TypeHint field to the dialog. This informs Sling Post Servlet about the correct JCR type when persisting values. Option A, using a JCR Event Listener, is inefficient and adds unnecessary complexity. Option C, using a Switch, would still result in a String unless the TypeHint is specified. Adobe documentation specifies that TypeHint fields should be added whenever developers need precise control over how values are stored, especially for Boolean, Long, or Date properties.

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 AEM as a Cloud Service, dedicated preview service endpoints are configured under publish run modes. The correct configuration folder for a UAT preview service is config.publish.uat within the ui.config project. Option A incorrectly places the configuration under author run mode, which is unrelated to preview endpoints. Option C misorders the naming convention, using config.uat.author instead of the proper config.publish.uat. Adobe’s guidance specifies that preview service configuration is a publish-tier responsibility, requiring config.publish. folders in the configuration project.

The RepoInit feature is the correct solution. RepoInit scripts allow developers to define repository initialization instructions in a declarative manner. With RepoInit, engineers can register namespaces, create folders, define service users, configure access control lists (ACLs), and create groups — all in one script. Option A, Ensure Authorizable, is limited to ensuring users or groups exist but does not handle namespaces or folder creation. Option C, OnDeploy Scripts, is not recommended for these tasks, as RepoInit is the standard, supported, and maintainable approach for repository initialization in AEM. Adobe documentation highlights RepoInit as the best practice for managing repository initialization in both AEM 6.5 and AEM as a Cloud Service.

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.

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.

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.

Explanation (Adobe Docs Reference):

Assets in AEM are stored as dam:Asset nodes, not nt:base or cq:image.

Metadata like cq:lastModified is stored under jcr:content/metadata.

Therefore, the correct query must use [dam:Asset] with the proper metadata path.

Options A and C are invalid because they use wrong node types or incorrect property paths.

Adobe Documentation:

“Assets are represented as dam:Asset nodes. Metadata such as lastModified is stored under jcr:content/metadata and can be queried using JCR-SQL2.”

— AEM Assets – Querying Assets

The recommended way to generate a new AEM project is by using the official Adobe AEM Maven Archetype. Developers must specify the correct groupId (com.adobe.aem) and artifactId (aem-project-archetype). The archetypeVersion should match the latest stable archetype version (e.g., 50 for AEM 6.5). The groupId of the project should be set to the organization’s package, in this case com.mysite. The appId defines the project name and should match the intended application (mysite). The version is defined as 2.0 to represent the project version, while aemVersion=6.5 ensures compatibility with AEM 6.5. Option A is invalid because the archetype groupId is incorrect and the values are mismatched. Option C contains placeholders and an invalid groupId. Adobe’s official documentation for generating projects specifies option B as the valid approach.

Explanation (Adobe Docs Reference):

Replication agents in AEM are responsible for transferring content and digital assets from the author instance to the publish instance (or to other targets like Dispatcher flush agents). This ensures that authored and approved content becomes available on the public site.

Options B and C are incorrect:

User permissions are not replicated by agents; they are managed by user synchronization.

Core Components are provided via Maven dependencies and not transferred via replication agents.

Adobe Documentation:

“Replication agents are central to AEM; they are used to publish (activate) content from an author to a publish environment, or to clear content from the dispatcher cache.”

— AEM Replication Agents

Custom components built on Core Components should use the sling:resourceSuperType property to inherit functionality. When upgrading from v1 to v2 Core Components, the developer updates the sling:resourceSuperType property of the custom component to reference the new v2 implementation. This allows the custom component to inherit all new features and bug fixes introduced in v2 while retaining its customizations. Option A is incorrect because sling:resourceType defines the resource type of the component itself, not inheritance. Option B is incorrect because there is no automatic upgrade mechanism in AEM; developers must explicitly update the inheritance path. Adobe documentation clearly states that upgrading Core Components is achieved by re-pointing sling:resourceSuperType to the new version.