AD0-E123 Questions and Answers

Within the SAML (Security Assertion Markup Language) Authentication Handler configuration in AEM, the property that must be configured with the URL of a system entity that manages identity information is the Identity Provider URL. The Identity Provider (IdP) is a core component of the SAML specification that is responsible for issuing authentication assertions and managing user identity information. Configuring the Identity Provider URL in the SAML Authentication Handler ensures that the authentication requests are directed correctly to the IdP.

The service used in AEM to control how AEM instances interact with a topology while running on instances is the Apache Sling Resource-Based service. This service helps in managing the resources and how they're resolved and accessed within the AEM topology. It's part of the Apache Sling framework, which is an integral part of AEM's architecture.

• Option A, "Web Console Service," is more for administration and management of OSGi components, not specifically for topology interaction.
• Option C, "Offloading Service," is generally related to processing tasks outside of the AEM instances and does not directly control instance interactions within a topology.

The recommended approach to use AEM Core Components is by creating proxy components. Proxy components are essentially wrapper components within your own project that reference the core components. This practice allows developers to inherit functionality from the core components while being able to override and extend it as necessary. By using proxy components, developers can ensure that any custom styles and configurations are preserved even when the core components are updated in the future.

When an AEM instance starts with specified run modes, it selects configurations from the repository that match those run modes. Run modes allow for flexible management of settings and configurations across different environments. For the instance started with 'author', 'dev', and 'emea' run modes, it would apply configurations from paths that match these run modes.

Option B,/config/author.dev.emea.noldap, is correct. This path matches all three run modes specified and would, therefore, be included.

Option D,/apps/mysite/config.author.emea.dev, is also correct. This path matches the run modes and would be applied to the instance as well.

Options A and C do not match all three run modes and therefore would not be applied.

In HTL (HTML Template Language), the syntax to manipulate the URI path does not provide direct methods for removing selectors. However, within Sling and HTL, the Link Handler can be extended to support such operations. For out-of-the-box HTL, the proper approach to manipulate the link would be done in the Java layer (e.g., a Sling Model or a Use-Class in HTL), and then passed to the template for rendering. Nevertheless, if such a functionality were to be implemented within HTL, it would require custom code and not use the indicated syntax options. It is important to note that options A and B with 'removeSelectors' are not standard HTL syntax.

In HTL, theformatoption in the data-sly-use or data-sly-test attribute can be used to format values according to a pattern. The pattern'-#.##%'indicates that the number should be formatted as a percentage with up to two decimal places. ThepiValuevariable would be the number to format, and in this example, it would convert -3.14 to -314%. The@symbol is used to denote the use of an option with the variable in HTL.

• Options B and C are incorrect because they do not use the correct syntax for the format option in HTL. The use of@is to specify options and not part of the variable or pattern itself.

The request log in AEM records details about requests processed by the AEM instance, including transaction response times. This log is useful for developers when they need to analyze the performance of page requests, including how long each page takes to load. The request log can typically be found in thelogsdirectory of the AEM installation and may be namedrequest.log.

• stdout.logtypically contains the standard output of the AEM process and is not specific to request transactions.
• audit.logis used to log user actions for auditing purposes and does not include transaction response times.

AEM as a Cloud Service includes the latest AEM features out-of-the-box, including AEM Core Components, which are production-ready without the need for additional downloads or installations of sample content. This version of AEM has a continuousdelivery model, ensuring that the most up-to-date features and components are readily available.

• Option A, Version 6.3, is incorrect because this version would require the manual download and installation of core components.
• Option B, Adobe Managed Services, is not a version of AEM, but rather a hosting option that could include various versions of AEM.

When working with custom workflow steps in AEM, metadata associated with the workflow session can be programmatically accessed and manipulated. TheMetaDataMapobject serves as a container for this data. The correct way to access and modify this metadata in Java would be:

Option C,MetaDataMap wfd = WorkItem.getWorkflow().getWorkflowData().getMetaDataMap(); wfd.put("mykey", "My Step Value");This snippet correctly retrieves theMetaDataMapfrom theWorkflowDataof the currentWorkflowsession. It then uses theputmethod to store a new key-value pair, where "mykey" is the key and "My Step Value" is the value to be saved.

Options A and B do not properly chain the method calls to access theMetaDataMapassociated with the current workflow session and are therefore incorrect.

In AEM, when you need to extend a dialog from a core component but want to hide or exclude one tab or part of the dialog, you can use thesling:hideResourceproperty. This property allows you to selectively hide resources (like a tab in a dialog) inherited from a super type (the core component) in your overlay or custom component.