Adobe AD0-E123 Exam Questions

Updating the cache in AEM is critical to ensure that users receive the most current content without unnecessary delays. Two common methods used to update the cache include:

A) Content Updates - Content updates can trigger an invalidation or flush of the cache. When content is published or updated on the AEM author instance and replicated to the publish instance, the dispatcher cache can be set to automatically invalidate the affected pages. This ensures that the next request to these pages serves the latest content.

D) Auto-invalidation on the Dispatcher - The dispatcher can be configured to automatically invalidate cached content under certain conditions, such as when a TTL (Time To Live) expires or when specific actions occur, such as a page activation or deactivation. This is often preferred to manual cache clearing as it can be more efficient and targeted to the specific content that has changed.

Options B and C are incorrect because restarting the AEM Author or Publish instances does not directly relate to cache update methods. These actions are more associated with system maintenance or updates and would not be standard practice for updating cached content.

AEM service pack release notes typically include information that helps users understand the changes that the service pack will bring to their AEM instance. These release notes commonly include:

A) Deprecated features - This section informs users about the features that are being deprecated with the current release and guides them on migrating away from deprecated features to the recommended alternatives.

B) Known issues - This section provides information about any issues or bugs that are known at the time of the release, which might not yet be fixed. It often includes workarounds for these issues if they are available.

Option C, 'Next service pack release date,' is not typically included because release dates are subject to change and are usually communicated through official channels closer to the actual release.

Option D, 'Download link to AEM jar,' is not included in the release notes but is typically available through the Adobe Software Distribution site or Cloud Manager for AEM as a Cloud Service.

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 the sling:hideResource property. 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.

When working with custom workflow steps in AEM, metadata associated with the workflow session can be programmatically accessed and manipulated. The MetaDataMap object 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 the MetaDataMap from the WorkflowData of the current Workflow session. It then uses the put method 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 the MetaDataMap associated with the current workflow session and are therefore incorrect.

When the 'Display Mode' is set to 'Single Text Element' in the configuration of a Content Fragment Component in AEM, the properties that will determine the resulting action are related to how the text is displayed and managed in terms of paragraphs.

C) Paragraph Range --- This property would determine the range of paragraphs to display from the multiline text element.

D) Paragraph Scope --- This property would define the scope of the paragraph, such as whether all paragraphs are included or just a specific subset.

Options A (Paragraph Description) and B (Paragraph Heading) are not directly related to the action of displaying a single text element with paragraph control.