Adobe AD0-E123 Adobe Experience Manager Sites Developer Professional Exam Practice Test

Answer : A

When accessing the Automated Maintenance Tasks in AEM via the specified URL, the default timing card available is the 'Daily Maintenance Window'. AEM provides a set of pre-configured maintenance tasks that can be run on a daily, weekly, or monthly basis, but the daily window is the standard default card that is presented in the maintenance console for configuring these tasks.

Monthly Maintenance Window (Option B) and Quarterly Maintenance Window (Option C) are not the default options that are presented in the AEM maintenance console.

Answer : A

The CQ_JVM_OPTS parameter in an AEM start script is used to set options for the Java Virtual Machine (JVM). The setting '-agentlib:jdwp=transport=dt_socket,address=8000,server=y,suspend=n' enables the Java Debug Wire Protocol (JDWP) agent for the JVM, allowing a debugger to attach to it. The suspend=n flag means the JVM will not suspend at the start but will wait for a debugger to connect on port 8000. This effectively runs the AEM instance in debug mode, which is useful for development and troubleshooting.

Option B is incorrect because the suspend=n setting means the JVM does not suspend on start-up.

Option C is incorrect because this parameter is for debug mode, not for specifying the run mode of the AEM instance.

Answer : C

In the context of AEM as a Cloud Service, a 'Golden Master' typically refers to the production-ready, main branch within the Cloud Manager Git Repository. This repository is used to manage and deploy code to AEM Cloud Service environments. It is considered the source of truth for the codebase that is used to build, test, and deploy AEM applications in the cloud.

Answer : C

In Maven for AEM, application is the packageType that is typically used for immutable code packages. These are packages that contain code that is not expected to change between deployments, such as OSGi bundles and certain content packages that do not contain user-editable content. This type of package is intended to be deployed to an AEM instance as part of the application's codebase, and the application packageType signifies this use case.

container is not a standard package type in AEM Maven project structures.

content is typically used for packages that contain mutable content, such as pages and configurations that can be edited by authors.

Answer : B

In AEM, the Sightly/HTL scripting language is used to develop robust and secure components. To render content conditionally based on the WCM (Web Content Management) mode, the wcmmode object is used. The correct property to check if the current mode is edit is wcmmode.edit. The HTL syntax for testing a condition is data-sly-test followed by the condition in ${}. The option B correctly uses this syntax to test if the WCM mode is edit, and if so, renders 'Hello World'.

Option A uses wcm.edit which is not the correct object property.

Option C uses wcmmode editor which is not the correct property and the syntax has a typo (should be data-sly-test).

Answer : C

The correct logger to be created for debugging SAML (Security Assertion Markup Language) within AEM (Adobe Experience Manager) is the one pertaining to the Granite platform, which is part of AEM's internal framework dealing with authentication. The Granite framework provides services that include user, group, and permission management, and is integral to AEM's SAML authentication process. Thus, the logger com.adobe.granite.auth.saml is the appropriate logger that should be created and configured to capture and display debug logs related to SAML authentication processes.

Answer : C

Given the dispatcher configuration snippet provided in the image, we can understand the URL patterns that will be ignored (not cached) by the dispatcher. The configuration under /ignoreUrlParams shows patterns to match query parameters in the URLs:

/0001 { /glob '*' /type 'deny' } means that by default, all query parameters are ignored (not cached).

/0002 { /glob 'search' /type 'allow' } specifically allows caching for URLs with the 'search' parameter.

/0003 { /glob 'order' /type 'allow' } specifically allows caching for URLs with the 'order' parameter.

Based on this, let's evaluate the options:

A) /myproduct/myrecipe.html?search=searchparam --- This URL will not be cached because the 'search' parameter is allowed, but the actual value 'searchparam' does not match any allow pattern. B) /myproduct/myrecipe.html?search=s&order=asc&brand=ad --- This URL will not be cached because although 'search' and 'order' parameters are allowed, the 'brand' parameter is not allowed according to the configuration. C. /myproduct/myrecipe.html?brand=mybrand --- This URL will be cached because there are no allowed parameters, so the default deny does not apply, and the page can be cached without considering the 'brand' parameter.

Therefore, the page that will be cached on the dispatcher is the one in option C, as it does not contain any of the explicitly allowed query parameters ('search' or 'order'), and all other parameters are ignored by default.