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

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):

When configuring SAML SSO with AEM, the dispatcher must allow POST requests to the saml_login endpoint. If blocked, AEM redirects endlessly back to the IDP. This is done by allowing the POST request in filters.any.

Adobe Documentation:

“For SAML authentication to work with AEM behind a Dispatcher, you must configure the dispatcher filter to allow POST requests to /saml_login. Otherwise, authentication attempts will loop infinitely.”

— AEM Dispatcher and SAML Authentication Configuration

Modern AEM projects often include front-end build processes for handling CSS, JavaScript, and component-specific assets. Webpack is the recommended tool for managing dependencies, bundling code, minification, transpilation (e.g., ES6+ to ES5), and optimizing assets. It integrates with the AEM Maven build process and supports workflows like Single Page Applications (SPA) and client libraries. Option B, Apache Sling, is the underlying web framework for AEM, not a front-end tool. Option C, Maven, manages project builds and back-end dependencies but not front-end asset pipelines. Option D, the AEM Sites Console, is for authoring and managing pages, not development builds. Adobe documentation for SPA Editor and modern AEM projects consistently demonstrates Webpack as the standard tool for front-end optimization.