Adobe Updated AD0-E137 Exam Questions and Answers by nella

Workflow launchers in AEM are designed to monitor changes in specific repository paths such as /content, /content/dam, and /conf. However, changes under certain system-level paths, including /var, do not trigger workflows. This restriction is intentional, as /var is used for system-generated and internal data such as workflow instances, audit logs, and temporary nodes. Triggering workflows on changes under /var could result in recursive or unintended behavior. Option A is unrelated because Workflow Process Legacy Mode refers to backwards compatibility. Option B is incorrect, as AEM does allow system nodes under /var, but they are not workflow-launcher enabled. Adobe documentation makes clear that workflow launchers must be configured under supported content paths for them to execute correctly.

In AEM, multi-site management allows centralized content updates to be pushed across different localized or departmental sites. The “Partial” option on the rollout configuration ensures that only specific components or regions designated for shared updates are synchronized, while leaving local content intact. This fits the described requirement where a portion of each school’s homepage must receive university updates without affecting school-specific content. Option A, Experience Fragments, could be used but are better suited for shared fragments of design/content, not controlled rollout scenarios. Option C requires manual inheritance restoration per page, which is inefficient. Option D, implementing custom rollout logic, is not needed when the built-in “Partial Rollout” option fulfills the requirement. Adobe emphasizes using partial rollout in multi-site configurations to balance central control with localized autonomy.

The issue in this case is that the title field is declared but not annotated with @Inject. In Sling Models, all fields that should be populated from the resource or request must be annotated appropriately (@Inject, @ValueMapValue, or @Self). Without this annotation, the Sling Model cannot populate the field when adapting from the resource, resulting in the model not functioning as expected. Option A is incorrect because Resource.class is a valid adaptable for Sling Models. Option C does not apply because the problem is not with hard-coded paths but with injection. Option D is also incorrect because while @PostConstruct must be properly annotated, the root issue here is missing injection on the field. Adobe’s Sling Models documentation emphasizes correct use of injection annotations as a core requirement.

Explanation (Adobe Docs Reference):

Replication agents in AEM are responsible for transferring content and digital assets from the author instance to the publish instance (or to other targets like Dispatcher flush agents). This ensures that authored and approved content becomes available on the public site.

Options B and C are incorrect:

User permissions are not replicated by agents; they are managed by user synchronization.

Core Components are provided via Maven dependencies and not transferred via replication agents.

Adobe Documentation:

“Replication agents are central to AEM; they are used to publish (activate) content from an author to a publish environment, or to clear content from the dispatcher cache.”

— AEM Replication Agents