AD0-E128 Leak Questions

Comprehensive Explanation

In the traditional Adobe Experience Manager Author-Publish topology, replication agents manage the publication of content from the Author environment to one or more Publish environments.

A replication agent is configured on the Author instance with the appropriate transport URI, authentication credentials, and replication settings.

When an author activates content, AEM sends a publication request to the configured replication agent. The agent packages the relevant repository content, places the request in its replication queue, and transmits the content to the designated Publish instance.

A receiving servlet on the Publish instance processes the incoming request and installs the replicated content.

Option A is incorrect because workflows may initiate publication operations but are not themselves the underlying transport mechanism responsible for replication.

Option B is incorrect because although OSGi services participate in replication functionality, creating an arbitrary custom OSGi configuration is not the standard procedure for establishing Author-to-Publish replication.

Option D is incorrect because Dispatcher provides caching, request filtering, and load-balancing functionality rather than acting as the primary content-replication mechanism.

Version distinction: AEM as a Cloud Service uses a managed content-distribution architecture. Traditional replication-agent configuration remains relevant for AEM 6.5 and Adobe Managed Services environments.

Official Adobe Reference: Replication — Replicating from Author to Publish; Replication Agents — Configuration Parameters.

Comprehensive Explanation

Adobe Experience Manager as a Cloud Service separates application code from mutable repository content through a defined content-package architecture.

Immutable code packages must declare their package type as application . This designation identifies packages containing application definitions, components, configuration resources, and other code-related repository structures.

The property is configured within the FileVault Package Maven Plugin configuration:

< packageType > application < /packageType >

In a typical AEM Project Archetype implementation, the ui.apps module contains immutable application resources under /apps , while the ui.content module contains mutable content resources.

Option B is incorrect because content identifies packages containing mutable repository content, commonly associated with paths such as /content and /conf .

Option C is incorrect because container packages organize and distribute other packages. The corresponding container package generally acts as an aggregation mechanism rather than representing an individual immutable application package.

This separation is particularly important in AEM as a Cloud Service because application code is deployed through Cloud Manager pipelines using an immutable infrastructure model.

Adobe explicitly requires code packages to use the application package type, while mutable content packages use content .

Official Adobe Reference: AEM Project Structure — Package Types and Immutable Code Packages.

Comprehensive Explanation

Adobe Experience Manager Dispatcher documentation identifies two principal mechanisms for updating cached content: Content Updates and Auto-Invalidation.

Content Updates remove specific cached documents and related resources when content changes. This enables Dispatcher to retrieve fresh representations from the rendering instance when subsequent requests arrive.

Auto-Invalidation uses timestamp-based validation through statfiles. When an appropriate invalidation event occurs, Dispatcher updates the relevant statfile. Cached documents subject to automatic invalidation are subsequently checked against the statfile timestamp to determine whether they are stale.

Option A therefore identifies one documented cache-update mechanism, while option D identifies the other.

Options B and C are incorrect because restarting an AEM Author or Publish instance does not inherently remove or invalidate files held in the Dispatcher web server's cache directory.

Operational qualification: The absence of a Dispatcher Flush Agent matters. Content Updates and Auto-Invalidation are mechanisms, not independent triggers that necessarily detect AEM publications without configuration. In a traditional topology, the Dispatcher must still receive a suitable invalidation request or use another correctly configured mechanism, such as time-based expiration.

Therefore, A and D match Adobe's documented cache-update methods, but the question should not imply that both automatically respond to content changes when no cache-invalidation mechanism is configured.

Official Adobe Reference: Dispatcher Overview — Methods for Caching, Content Updates and Auto-Invalidation; Configure AEM Dispatcher — Automatically Invalidating Cached Files.