Adobe Experience Manager AD0-E128 Exam Questions and Answers PDF

Comprehensive Explanation

Adobe Experience Manager's HTML Template Language supports URI manipulation through expression options, including selectors , addSelectors , and removeSelectors .

The selectors option can replace the selector portion of a URI. When invoked without an assigned value, or with an explicitly empty string, it removes all selectors while preserving the resource path and extension.

For the original value path/page.woo.foo.html , the two valid HTL expressions are:

${linkValue @ selectors}

${linkValue @ selectors=''}

Both produce:

path/page.html

Option C is valid as written and removes all selectors.

Option B is clearly intended to represent the empty-string approach, but the uploaded document contains malformed syntax. It requires correction before it can be executed.

Option A removes the foo selector but leaves woo , producing path/page.woo.html .

Option D uses a comma-separated string rather than the documented selector string format, which uses periods, or an array of selector values. It therefore cannot be relied upon to remove the individual selectors.

Verification finding: B and C are the intended examination answers. Strictly evaluated without correcting the original source, only C is demonstrably valid. This question requires a source correction before inclusion in a technically accurate practice test.

Official Adobe Reference: HTML Template Language Specification — URI Manipulation, selectors and removeSelectors.

Comprehensive Explanation

Adobe Experience Manager maintains an HTTP request log that records incoming requests and their corresponding responses, including response times.

The request.log file is particularly useful for identifying slow page requests, diagnosing performance problems, and evaluating application responsiveness.

Each request receives an identifier that associates the incoming HTTP request with its corresponding response. The response record includes the HTTP status code, content type, and processing time.

For example:

09:43:41 [66] - > GET /content/site/en.html HTTP/1.1

09:43:41 [66] < - 200 text/html 797ms

In this example, AEM required 797 milliseconds to process the request.

Option A is incorrect because audit.log primarily records auditing information, such as content-related administrative and moderation activities.

Option B is incorrect because stdout.log captures standard-output messages, including startup-related information, rather than providing the dedicated request timing records.

Option C is correct because request.log provides a direct mechanism for analyzing HTTP response times.

Adobe recommends using request-log analysis to identify slow pages, evaluate request concurrency, and diagnose application performance bottlenecks.

For extensive performance investigations, developers can aggregate response times by URL and correlate slow requests with thread dumps, repository query performance, and application logs.

Official Adobe Reference: Monitoring and Maintaining Your AEM Instance — Interpreting the request.log; Examples of request.log Analysis.

Comprehensive Explanation

Adobe Experience Manager Dispatcher controls external HTTP request access through the /filter section of its farm configuration. This section can permit or reject requests according to their HTTP method, URL, selectors, extensions, and query strings.

When Dispatcher rejects a request containing query parameters, the developer should inspect its access-filter rules to determine whether an appropriate /query condition has been configured.

For example:

/filter {

/0001 {

/type "allow"

/method "GET"

/url "/content/site/*"

/query "q=*"

}

}

This rule permits matching GET requests containing the designated query parameter.

Option A controls the AEM rendering instances and does not determine whether query strings are permitted. Option B generally refers to cache rules, which govern cache eligibility. Option C controls caching behavior, including /ignoreUrlParams , rather than request authorization.

Technical qualification: The actual Dispatcher configuration directive is /filter , not /filters . Therefore, option D contains a naming error.

Additionally, if the problem concerns pages with query parameters bypassing the cache rather than being rejected, option C would be relevant because /cache/ignoreUrlParams controls query-parameter caching behavior.

For requests being denied, D identifies the intended configuration area.

Official Adobe Reference: Configure Dispatcher — Restrict Query Strings and Ignore URL Parameters.

Comprehensive Explanation

The exhibit contains a JCR-SQL2 query that selects repository nodes of type nt:base where the status property equals STARTED .

To support this query efficiently through a Lucene index, the index definition must include an applicable node-type rule and a property definition capable of evaluating the equality restriction.

Option D provides the required nt:base index rule. Because the query operates against nt:base , the index must support the relevant node types rather than restricting its definition to an incompatible resource type.

Option C enables property indexing for status by setting propertyIndex=true . This tells the Lucene index to maintain property values suitable for query constraints such as equality comparisons.

Option A is incorrect because propertyIndex=false does not enable the required property-based lookup.

Option B is incorrect because aggregation is used principally to incorporate child-node content into a parent node's index representation, especially for full-text scenarios. It is not required for this direct property comparison.

An appropriately defined Lucene index can therefore support the query using the nt:base index rule and the indexed status property.

Implementation note: These are the necessary additions among the supplied choices, assuming a suitable Lucene index already exists. The complete index also needs appropriate index-definition properties, and production indexing should avoid unnecessarily broad repository scans.

Official Adobe Reference: Content Search and Indexing — Lucene Index Definitions; Oak Queries and Indexing — Lucene Property Index.