AD0-E137 Exam Dumps - Adobe Experience Manager Sites Developer Expert

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

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

Explanation (Adobe Docs Reference):

When querying with QueryBuilder API:

type=cq:Page ensures only AEM pages are selected.

property=jcr:content/cq:template filters by the template path.

property.value=/conf/geometrixx/templates/homepage ensures only pages created with the homepage template are returned.

p.hits=selective restricts returned properties.

p.properties=jcr:title ensures only the jcr:title is returned.

Options B, C, and D are invalid due to wrong property paths (jcr:title/cq:template, cq:template, or jcr:content/template) or typos (jrc:title).

Adobe Documentation:

“The property parameter can be used to restrict results based on template usage. Use jcr:content/cq:template to filter by template and p.properties with p.hits=selective to return specific fields.”

— AEM QueryBuilder API Guide

When unit testing a service that depends on JCR queries, the best practice is to use mocking frameworks (such as Mockito) to mock the Query and QueryResult objects. The purpose of a unit test is to isolate the service under test and not rely on a real JCR repository or SlingContext persistence layer, which moves testing into integration testing territory. By mocking the Query object and using the when(...).thenReturn(...) pattern, developers can control query results and validate how the service behaves under different scenarios. This ensures that the test runs quickly, without dependency on repository setup or external data. Option B is incorrect because currentResource() is used in Sling Model tests rather than for query-driven services. Option C with SlingContext and JCR_OAK would be used in integration or functional tests, not in lightweight unit tests. Adobe documentation highlights that JCR queries should be mocked in unit tests to ensure isolation and speed.

The Oak query engine, which underpins AEM’s repository search and indexing capabilities, supports multiple query syntaxes. However, Adobe recommends using XPath or JCR-SQL2, with XPath being the most widely used. JCR-SQL (option A) is deprecated and should not be used in modern AEM implementations. Plain SQL (option B) is not supported as queries must operate within the JCR structure. Option C, XPath, integrates tightly with Oak’s indexing system and provides efficient query execution. Adobe documentation states explicitly that developers should use XPath or JCR-SQL2 for queries, as both are optimized for Oak’s indexing and repository structure. Since the question provides XPath as an option but not JCR-SQL2, XPath is the correct answer.

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 Retry Delay setting in a replication agent specifies the interval (in milliseconds) to wait before retrying a failed replication request. This ensures that temporary network or system issues don’t permanently block replication, as the agent will automatically attempt to resend content at the configured delay interval.

From Adobe Documentation:

“Retry Delay: The time (in milliseconds) to wait before attempting to retry a failed replication. This helps ensure that replication requests are retried at regular intervals if initial delivery fails.”

— Adobe AEM 6.5 & AEMaaCS – Replication Agent Configuration