Free Practice Questions for Adobe AD0-E137 Exam

Cloud Manager’s Content Copy feature allows administrators to copy content from Production to non-production environments such as Stage or Development. This is intended to provide accurate and representative content for testing, QA, or UAT purposes. Content cannot be copied from Development or Integration to Stage, as Adobe enforces strict controls to prevent non-production content from contaminating Production or Stage environments. Option C is correct because Production is the only valid source environment for copying content to Stage. Adobe emphasizes that copying content from Production ensures consistency and valid test data while maintaining governance and security in AEMaaCS.

The Dispatcher should be configured to cache static pages like .html, but when query parameters are present (used for personalization, targeting, or dynamic rendering), the dispatcher must invalidate or bypass cache to prevent stale or incorrect content delivery.

Option A is correct → balances performance (cache static .html) and personalization (invalidate with query strings).

Option B is incorrect → POST requests should never be cached, as they modify content.

Option C is incorrect → disabling cache for all .html removes performance benefits.

Adobe Documentation:

“The dispatcher can be configured to cache .html responses while invalidating the cache when query string parameters are present. This ensures efficient caching while supporting personalization and dynamic content.”

— AEM Dispatcher Caching Guidelines

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.

In AEM, fine-grained access control is managed using JCR Access Control Entries (ACEs). To grant access only to a specific node but exclude all child nodes, the correct approach is to set the rep:glob = "" property. This ensures that permissions apply strictly to the node itself and not recursively. Option B, rep:globs = "**", would apply access recursively to all descendants. Option C, rep:glob = "child", is invalid and does not represent a valid configuration. Adobe recommends precise use of rep:glob patterns to restrict user access according to security requirements, ensuring least-privilege principles.

The RepoInit feature is the correct solution. RepoInit scripts allow developers to define repository initialization instructions in a declarative manner. With RepoInit, engineers can register namespaces, create folders, define service users, configure access control lists (ACLs), and create groups — all in one script. Option A, Ensure Authorizable, is limited to ensuring users or groups exist but does not handle namespaces or folder creation. Option C, OnDeploy Scripts, is not recommended for these tasks, as RepoInit is the standard, supported, and maintainable approach for repository initialization in AEM. Adobe documentation highlights RepoInit as the best practice for managing repository initialization in both AEM 6.5 and AEM as a Cloud Service.

AEM package files follow a standard naming convention in CRX Package Manager:

--.zip

Thus, with the package name aem-package, group aem_group, and version 1.0, the correct package name is aem-package-aem_group-1.0.zip. Option B is invalid because group names and content paths are not combined in filenames. Option C omits the group name, making it incomplete. Adobe documentation emphasizes this naming convention for easier package identification and dependency management across environments.

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.

Explanation (Adobe Docs Reference):

The correct OSGi Declarative Services (DS) implementation in AEM:

Must use implements (not extends).

Must register the service interface (SimpleService.class).

Should return an implementation for getMessage().

Option D is the correct implementation.

Options A, B, C are wrong because:

A incorrectly uses extends.

B and C register the wrong service type (MySimpleService).

Adobe Documentation:

“An OSGi service implementation must implement its interface and be annotated with @Component(service=Interface.class) to register the service.”

— OSGi Services in AEM

In AEM’s Template Editor, there are multiple modes that allow template authors to configure different aspects of templates. The Structure mode defines static and editable areas in templates. The Page Policy allows defining rules such as which components are available for use. However, the Layout mode is specifically designed for defining grid settings for different devices. With Layout mode, template authors can configure responsive layouts and grid behavior across breakpoints such as desktop, tablet, and mobile. This ensures consistent responsive design and adaptability across devices. Adobe documentation specifies that “Layout mode allows authors to configure responsive grid layouts for different breakpoints, ensuring that pages render appropriately on devices of varying screen sizes.” This mode is essential for enabling adaptive and responsive designs in AEM projects. Options B and C do not allow for device-specific grid settings and thus are not correct.