AD0-E128 Adobe Experience Manager Sites Developer Professional Questions and Answers

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

In Adobe Experience Manager 6.5, sling:OsgiConfig is the correct JCR node type for defining an OSGi configuration directly within the repository. It belongs to the Apache Sling configuration mechanism and enables developers to maintain service configuration declaratively.

OSGi configurations control the runtime behavior of AEM services, including logging, authentication, workflow processing, and custom application components. Each configuration is associated with a Persistent Identity (PID), typically corresponding to the fully qualified name of the service implementation.

When defining an OSGi configuration through CRXDE Lite, developers can create a node of type sling:OsgiConfig under an appropriate configuration folder, such as /apps/myproject/config . Configuration properties are added to this node and interpreted by the OSGi framework.

Option B is incorrect because cq:OsgiConfig is not the proper node type. Option C is also incorrect because cq:Configuration does not represent the standard Sling OSGi configuration node.

A significant version distinction applies: AEM as a Cloud Service uses .cfg.json configuration files deployed through the application project rather than relying on legacy XML sling:OsgiConfig definitions.

Official Adobe Reference: Configuring OSGi — OSGi Configuration with Repository Nodes; Configuring OSGi for Adobe Experience Manager as a Cloud Service.

Comprehensive Explanation

Adobe Experience Manager provides an Operations Dashboard for monitoring repository health and managing routine maintenance tasks.

The Automated Maintenance Tasks interface is available through the specified URL:

/libs/granite/operations/content/maintenance.html

This interface includes predefined maintenance scheduling cards, including the Daily Maintenance Window and the Weekly Maintenance Window.

The Daily Maintenance Window is used for operations that should execute regularly to maintain repository performance and stability.

Adobe documents the default Daily Maintenance Window as running from 2:00 A.M. to 5:00 A.M. Tasks associated with this window include Revision Cleanup and Lucene Binaries Cleanup, depending on the AEM version and repository configuration.

The Weekly Maintenance Window normally operates during a separately configured interval and supports tasks such as workflow purging, audit-log maintenance, and data-store garbage collection.

Option A is not the best answer because monthly scheduling is an available configuration capability in certain AEM versions, but it is not the primary default timing card referenced in the question.

Option B is incorrect because Quarterly Maintenance Window is not one of the documented default cards.

The Daily Maintenance Window enables administrators to schedule repository maintenance during periods of reduced system activity, minimizing the impact of maintenance operations on production workloads.

Official Adobe Reference: Operations Dashboard — Automated Maintenance Tasks; Revision Cleanup — How to Run Online Revision Cleanup.

Comprehensive Explanation

Adobe has deprecated the JavaScript Use API for AEM as a Cloud Service and explicitly identifies the Java Use API as its recommended replacement.

The JavaScript Use API historically allowed developers to implement server-side component logic using JavaScript files referenced through HTL's data-sly-use mechanism.

The Java Use API provides an alternative architecture that separates presentation markup from application logic through Java classes and Sling Models.

Java-based implementations can provide stronger compile-time type checking, dependency injection, reusable service integrations, and more structured unit-testing capabilities.

The HTL layer remains responsible for rendering presentation markup, while Java classes handle data processing and application-specific functionality.

Option A, the JCR API, provides repository access and content-manipulation capabilities. It does not replace the component-level HTL Use API.

Option C, the Jackrabbit Oak API, relates to the underlying content repository implementation and is not the recommended replacement.

Option D, the Assets HTTP API, provides asset-related operations and is unrelated to the JavaScript Use API's primary purpose.

Adobe's AEM as a Cloud Service documentation explicitly lists JavaScript Use API under deprecated Sites functionality and identifies Java Use API as its replacement.

For new development, developers should implement business logic using Java-backed components and appropriate Sling Models rather than creating new dependencies on deprecated server-side JavaScript implementations.

Official Adobe Reference: Deprecated and Removed Features — Sites, JavaScript Use API; Getting Started with HTL — Java Use API.

Comprehensive Explanation

The exhibit contains a JCR-SQL2 query that selects repository nodes of type nt:base where the status property equals STARTED .

To support this query efficiently through a Lucene index, the index definition must include an applicable node-type rule and a property definition capable of evaluating the equality restriction.

Option D provides the required nt:base index rule. Because the query operates against nt:base , the index must support the relevant node types rather than restricting its definition to an incompatible resource type.

Option C enables property indexing for status by setting propertyIndex=true . This tells the Lucene index to maintain property values suitable for query constraints such as equality comparisons.

Option A is incorrect because propertyIndex=false does not enable the required property-based lookup.

Option B is incorrect because aggregation is used principally to incorporate child-node content into a parent node's index representation, especially for full-text scenarios. It is not required for this direct property comparison.

An appropriately defined Lucene index can therefore support the query using the nt:base index rule and the indexed status property.

Implementation note: These are the necessary additions among the supplied choices, assuming a suitable Lucene index already exists. The complete index also needs appropriate index-definition properties, and production indexing should avoid unnecessarily broad repository scans.

Official Adobe Reference: Content Search and Indexing — Lucene Index Definitions; Oak Queries and Indexing — Lucene Property Index.

Comprehensive Explanation

Adobe Experience Manager uses Apache Jackrabbit Oak as its underlying content repository. Oak provides query indexes to optimize access to repository content without requiring expensive traversal operations.

A custom Oak index is defined through an index definition under the /oak:index repository hierarchy. The definition identifies the index type, indexed node types, relevant properties, and additional indexing behavior.

For Lucene indexes, the definition typically uses jcr:primaryType set to oak:QueryIndexDefinition , type set to lucene , and an appropriate asynchronous indexing configuration.

Option D correctly identifies the fundamental process of defining a custom Oak index.

Option A is incorrect because Sling servlets handle HTTP requests rather than establishing native Oak repository indexes.

Option B is incorrect because writing a Query Builder query does not automatically create the necessary custom index.

Option C is incorrect because Dispatcher manages HTTP request caching and filtering, not repository-level Oak indexing.

Cloud Service qualification: Adobe recommends maintaining custom index definitions in the application codebase and deploying them through Cloud Manager. Production developers should not manually create or modify index nodes through CRXDE Lite.

For AEM as a Cloud Service, index definitions are generally maintained under the project's _oak_index directory using versioned index names.

Official Adobe Reference: Oak Queries and Indexing; Indexing Best Practices in AEM.

Comprehensive Explanation

Adobe Experience Manager Dispatcher provides request-level security filtering through the /filter section of its configuration. This mechanism determines which incoming HTTP requests are permitted to reach an AEM rendering instance.

When an incoming request matches a rule explicitly configured with /type "deny" , Dispatcher rejects the request and returns an HTTP 404 Not Found response.

The response is intentionally different from the HTTP 403 Forbidden status commonly associated with authorization failures. Dispatcher filtering operates as an access-control layer that can prevent external clients from discovering restricted repository endpoints.

For example:

/filter {

/0001 { /type "deny" /url "*" }

/0002 { /type "allow" /url "/content/*" }

}

This configuration denies requests by default and permits requests matching the specified content path.

Option B is incorrect for the documented default response to a denied Dispatcher filter request. HTTP 403 can occur in other authorization or security contexts, but it is not the expected filter-denial response here.

Option C indicates a malformed client request and is unrelated to the normal Dispatcher filtering behavior.

Adobe explicitly documents the 404 response for requests rejected through Dispatcher filter rules.

Official Adobe Reference: Configure AEM Dispatcher — Configure Access to Content, Example Filter: Deny All.

Comprehensive Explanation

Adobe Experience Manager's HTML Template Language supports URI manipulation through expression options, including selectors , addSelectors , and removeSelectors .

The selectors option can replace the selector portion of a URI. When invoked without an assigned value, or with an explicitly empty string, it removes all selectors while preserving the resource path and extension.

For the original value path/page.woo.foo.html , the two valid HTL expressions are:

${linkValue @ selectors}

${linkValue @ selectors=''}

Both produce:

path/page.html

Option C is valid as written and removes all selectors.

Option B is clearly intended to represent the empty-string approach, but the uploaded document contains malformed syntax. It requires correction before it can be executed.

Option A removes the foo selector but leaves woo , producing path/page.woo.html .

Option D uses a comma-separated string rather than the documented selector string format, which uses periods, or an array of selector values. It therefore cannot be relied upon to remove the individual selectors.

Verification finding: B and C are the intended examination answers. Strictly evaluated without correcting the original source, only C is demonstrably valid. This question requires a source correction before inclusion in a technically accurate practice test.

Official Adobe Reference: HTML Template Language Specification — URI Manipulation, selectors and removeSelectors.

Comprehensive Explanation

The -agentlib:jdwp Java Virtual Machine parameter activates the Java Debug Wire Protocol (JDWP), enabling a debugger to connect to a running Java process.

In Adobe Experience Manager, this configuration is commonly used when debugging Java code through an IDE such as Eclipse or IntelliJ IDEA.

The parameter transport=dt_socket specifies socket-based communication between the JVM and debugging client.

The address=8000 setting identifies the port used for debugger connections, while server=y instructs the JVM to listen for incoming debugger connections.

The suspend=n setting is particularly important because it allows the AEM instance to continue starting without waiting for a debugger to attach.

Option A is incorrect because suspending startup would require suspend=y . Even then, startup would wait for a debugger rather than necessarily fail.

Option C is incorrect because the debug-agent settings do not determine the AEM instance's Author or Publish run mode.

Option B correctly identifies that the instance starts with remote debugging enabled.

Technical distinction: Remote JVM debugging is different from setting the AEM application log level to DEBUG . The JDWP parameter enables debugger attachment, breakpoints, and Java execution inspection.

Adobe recommends avoiding unnecessary remote debugging in production because it can introduce performance and security risks.

Official Adobe Reference: How to Debug an AEM App Using Eclipse — Add the Remote Debugging JVM Parameter.

Comprehensive Explanation

Adobe Experience Manager Dispatcher controls external HTTP request access through the /filter section of its farm configuration. This section can permit or reject requests according to their HTTP method, URL, selectors, extensions, and query strings.

When Dispatcher rejects a request containing query parameters, the developer should inspect its access-filter rules to determine whether an appropriate /query condition has been configured.

For example:

/filter {

/0001 {

/type "allow"

/method "GET"

/url "/content/site/*"

/query "q=*"

}

}

This rule permits matching GET requests containing the designated query parameter.

Option A controls the AEM rendering instances and does not determine whether query strings are permitted. Option B generally refers to cache rules, which govern cache eligibility. Option C controls caching behavior, including /ignoreUrlParams , rather than request authorization.

Technical qualification: The actual Dispatcher configuration directive is /filter , not /filters . Therefore, option D contains a naming error.

Additionally, if the problem concerns pages with query parameters bypassing the cache rather than being rejected, option C would be relevant because /cache/ignoreUrlParams controls query-parameter caching behavior.

For requests being denied, D identifies the intended configuration area.

Official Adobe Reference: Configure Dispatcher — Restrict Query Strings and Ignore URL Parameters.

Comprehensive Explanation

Adobe Experience Manager Multi Site Manager (MSM) enables organizations to maintain a centrally managed content source while distributing localized variations across multiple regional websites.

For this scenario, the appropriate implementation is to establish a primary French-language site and create Live Copies for Chad, Ivory Coast, and Senegal.

The primary French site serves as the content source, while individual country sites inherit common information through MSM Live Copy relationships. Rollout configurations determine when and how changes are synchronized between the source and regional destinations.

Each country can maintain localized information, including currency, shipping conditions, payment methods, promotional offers, and country-specific regulatory disclosures. Inheritance can be suspended where localized content must differ from the central version.

Option A is less appropriate because MSM does not perform language translation itself. Adobe recommends using translated language masters as sources for regional sites that share the same language.

Option C incorrectly emphasizes copying templates rather than managing Live Copies of content pages. Option D creates unnecessary duplication and weakens centralized content governance.

Using a French language master therefore provides consistent content management while preserving the flexibility required for country-specific localization.

Official Adobe Reference: Multi Site Manager and Translation; Reusing Content: Multi Site Manager and Live Copy.

Comprehensive Explanation

Adobe Experience Manager provides SAML 2.0 authentication functionality through its Adobe Granite SAML Authentication Handler.

To investigate authentication failures, assertion validation errors, certificate problems, or identity-provider integration issues, developers can configure a dedicated Apache Sling logger targeting the SAML authentication package.

Adobe explicitly documents the logger name as:

com.adobe.granite.auth.saml

The recommended diagnostic configuration uses the Apache Sling Logging Logger Configuration with the logging level set to DEBUG .

A dedicated file, such as logs/saml.log , can be configured to isolate authentication-related messages.

Option A is correct because it matches the Java package associated with the Adobe Granite SAML Authentication Handler.

Option B is incorrect because com.adobe.granite.debug.auth.saml is not the documented logger category.

Option C is incorrect because the SAML authentication handler uses the Adobe Granite namespace rather than the proposed com.adobe.sling.auth.saml namespace.

Diagnostic messages can reveal problems involving invalid assertion signatures, incorrect certificates, unavailable private keys, and authentication configuration mismatches.

Operational consideration: DEBUG logging may expose sensitive authentication-related diagnostic information and generate additional log volume. It should be enabled only for the required troubleshooting period and disabled afterward.

Official Adobe Reference: SAML 2.0 Authentication Handler — Configure a Logger for SAML; Configuring OKTA with AEM — DEBUG Logging.