Adobe AD0-E137 Exam With Confidence Using Practice Dumps

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.

To optimize queries against DAM assets with custom properties, developers must extend the existing damAssetLucene index. The correct method is to add the custom property under:

oak:index/damAssetLucene/indexRules/dam:Asset/properties. This ensures that the property is indexed for all assets and avoids traversal queries. Option B refers to a non-existent lucene index path, and Option C incorrectly suggests adding a property value (Hello) instead of the property name. Adobe’s indexing guidelines specify that extending existing Lucene indexes such as damAssetLucene is the standard approach for asset-related queries. This ensures queries remain efficient, scalable, and compatible across environments.

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