Pass the Adobe Experience Manager AD0-E137 Questions and answers with ExamsMirror

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.

developer documents: Vanity URLs in Adobe Experience Manager (AEM) allow authors to define custom, shorter, or more user-friendly URLs for pages directly in the page properties, which are then published and handled by the Dispatcher for caching and security. To enable Dispatcher to dynamically fetch and allow these vanity URLs without manually updating filters for each one, a specific configuration section must be defined in the Dispatcher configuration file (typically dispatcher.any). This section instructs Dispatcher on how to retrieve the list of vanity URLs from the AEM publish instance, store them locally, and automatically permit requests matching those URLs to bypass certain deny rules.

The correct property for defining this configuration is /vanity_urls, which is a child block under the /farms section in the Dispatcher configuration. This block contains sub-properties such as:

/url: The endpoint on the AEM publish instance to fetch the vanity URL list (e.g., "https://publish.example.com/libs/granite/dispatcher/content/vanityUrls.html ").

/file: The local file path where Dispatcher caches the fetched vanity URL list (e.g., "/tmp/vanity_urls"). Dispatcher requires write access to this file.

/delay: The interval (in seconds) between periodic fetches of the vanity URL list from AEM (default is 60 seconds).

/loadOnStartup: A boolean (0 or 1) to load the vanity URLs immediately when Dispatcher starts (default is 1).

For the vanity URL feature to function:

Install the VanityURLS-Components package on the AEM publish instance(s) from Adobe's Software Distribution to enable the /libs/granite/dispatcher/content/vanityUrls.html servlet.

Ensure Dispatcher filters deny vanity URL paths by default (e.g., via a rule like { /type "allow" /method "GET" /url "/libs/granite/dispatcher/content/vanityUrls.*" /extension "html" } to allow the fetch, but deny the vanity paths themselves).

Add the /vanity_urls block under /farms/{farmname}.

Restart the Apache web server after configuration changes.

If not configured correctly, errors like "Vanity URL file (/tmp/vanity_urls) not found, fetching..." may appear in Dispatcher logs, followed by failures if the AEM endpoint is unreachable.

Exact Extracts from Adobe Experience Manager (AEM) Sites Developer Documents:

From "Configure AEM Dispatcher": "Add the /vanity_urls section below /farms. Restart Apache web server. ... The value of this property must be '/libs/granite/dispatcher/content/vanityUrls.html'. /file: The path to the local file where Dispatcher stores the list of vanity URLs. Make sure that the Dispatcher has write-access to this file. /delay: (Seconds) The time between calls to the vanity URL service. ... If your render is an instance of AEM, you must install the VanityURLS-Components package from Software Distribution to enable the vanity URL service."

From "AEM Dispatcher vanity URLs feature": "For this reason, the Dispatcher module has a feature to auto-allow anything listed as a vanity in the content tree. ... Simple Dispatcher has an auto-filter allow mechanism and you have to install an AEM package and then configure the Dispatcher to point to that package page."

From "AEM Dispatcher Common Logs": "Thu Sep 27 17:40:29 2018 D pid 21844 Checking vanity URLs Thu Sep 27 17:40:29 2018 D pid 21844 Vanity URL file (/tmp/vanity_urls) not found, fetching... Thu Sep 27 17:40:29 2018 D pid 21844 Loaded 18 vanity URLs from file /tmp/vanity_urls"

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

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.

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.