AD0-E128 Exam Dumps - Adobe Experience Manager Questions and Answers

Comprehensive Explanation

Adobe Experience Manager supports exposing structured component data through the Sling Model Exporter, which serializes Sling Model properties into JSON representations.

In an AEM Single Page Application (SPA) implementation, the frontend application consumes exported component data to render the user interface.

The .model.json selector provides access to the JSON representation generated by the Sling Model Exporter.

For example, a homepage located at /content/mysite/en/home.html can expose its exported model through:

/content/mysite/en/home.model.json

The developer can inspect this response to determine whether the custom component and its expected property are included in the exported model.

Option A correctly uses the .model.json selector.

Option B is incorrect because /sling.json is not the documented endpoint for the page's Sling Model Exporter representation.

Option C is incorrect because /sling-model.json does not follow the required selector structure.

If the property is absent, the developer should inspect the Sling Model's exported getters, annotations, implementation, component resource type, and the frontend component mapping.

The developer must also confirm that the relevant component is present in the page model and that the exported property is not explicitly excluded from JSON serialization.

This diagnostic method allows the frontend and backend implementations to be evaluated independently.

Official Adobe Reference: Sling Model Exporter — JSON Serialization; AEM SPA Editor and Model Exporter.

Comprehensive Explanation

In AEM 6.5, configuration changes made through the Apache Felix Web Console can be persisted in the JCR repository as .config resources beneath the /apps hierarchy.

The /apps directory stores application-specific components, services, scripts, and configuration definitions. A common location for configurations created through the Web Console is /apps/system/config . Project-specific configurations can also be maintained under directories such as /apps/myproject/config .

A configuration is typically identified by its OSGi Persistent Identity (PID). Administrators can locate persisted configurations through CRXDE Lite or by querying repository nodes associated with the relevant PID.

Option A is incorrect in this context because /conf primarily stores context-aware configurations and editable-template definitions. Option C refers to the content hierarchy, where website pages and other managed content are stored. Option D is not a valid configuration location.

For AEM as a Cloud Service, the development model differs: configuration files are maintained in source-controlled project modules, commonly ui.config , and deployed using Cloud Manager. The standard configuration format is .cfg.json .

Therefore, /apps is the correct answer under the repository-persistence model specified in the question.

Official Adobe Reference: Configuring OSGi — Configuration Persistence and Configuration Files.

Verification note: The template-level property allowedPaths is not present among the options.

Comprehensive Explanation

The cq:allowedTemplates property controls which page templates are permitted within a particular section of the AEM content hierarchy.

When configured on the jcr:content node of a site root or another page, this property contains expressions identifying the templates available for pages created within that content branch. For example, an administrator can restrict a site to templates stored under /conf/myproject/settings/wcm/templates/ .

Adobe also documents a separate property named allowedPaths , which can be defined directly on a template to restrict the content locations where that template may be used.

This distinction matters because allowedPaths does not have the cq: prefix in Adobe's documented template-availability configuration. Consequently, option A, cq:allowedPaths , does not represent the documented property name.

Options B and C are incorrect because the sling: namespace does not identify the relevant template-availability properties.

Among the supplied choices, D is the valid configuration property for restricting template availability to a designated content branch. However, if the requirement specifically means configuring the restriction on the template itself, the technically correct property is allowedPaths , which is absent from the choices.

Official Adobe Reference: Templates — Template Availability; Editable Templates — Template Availability.

Comprehensive Explanation

Adobe Experience Manager supports Dispatcher cache invalidation through replication-agent configurations located on the Author instance or the Publish instance.

In a traditional Author-based configuration, a Dispatcher Flush Agent sends an invalidation request to Dispatcher when content is published. This corresponds to option D.

In a Publish-based configuration, a Dispatcher Flush Agent sends the invalidation request after receiving the newly published content. This corresponds to option B.

Adobe documents both architectural approaches. Publish-side flushing can reduce synchronization problems caused by invalidating cached content before the updated resource has reached the Publish instance.

Dispatcher flushing is performed through an HTTP request containing special headers, including CQ-Action , CQ-Handle , and CQ-Path . Adobe's documented flush-agent implementation uses HTTP GET requests with these headers.

Options A and C mention custom servlets. Custom implementations can technically issue valid HTTP invalidation requests, but simply sending an ordinary GET request does not invalidate the cache. The necessary Dispatcher-specific headers and configuration must also be provided.

Consequently, B and D are the two standard, explicitly documented flush-agent mechanisms.

Verification note: The question would be more precise if it asked specifically for the two supported Dispatcher Flush Agent configurations. Custom invalidation mechanisms are possible, making the original wording broader than the intended answer.

Official Adobe Reference: Invalidate Cached Pages from AEM — Invalidate from Author and Publish; AEM Dispatcher Flushing.

Comprehensive Explanation

Adobe Experience Manager Multi Site Manager applies a defined configuration-resolution hierarchy when determining the rollout configuration for a Live Copy.

When a Live Copy page does not explicitly define a rollout configuration, AEM checks whether its associated blueprint source page specifies one. If a configuration exists on the blueprint source, AEM applies that configuration to the Live Copy.

This behavior ensures that synchronization policies defined at the source can govern associated Live Copies without requiring every individual page to maintain a duplicate configuration.

Adobe documents the resolution order as follows: an explicit Live Copy configuration takes precedence; otherwise, the blueprint source configuration is considered. If neither specifies a configuration, AEM checks the Live Copy parent page. Finally, the system default applies when no configuration is available through the preceding levels.

Option A is incorrect because the system default is a fallback, not the immediate choice. Option C is incorrect because the absence of an explicit configuration does not automatically cause a publication error. Option D describes a later fallback condition.

Therefore, option B correctly identifies the configuration that takes precedence in the scenario.

Official Adobe Reference: Configuring Live Copy Synchronization — Specifying the Rollout Configurations to Use.

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

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 uses the Apache Sling logging framework to record application events, exceptions, warnings, and messages generated by Java classes.

By default, application logging is directed to error.log , unless a specific logging configuration routes messages to an alternative destination.

When no dedicated logger has been configured for a Java class such as MyClass , the developer should first examine the standard AEM error.log .

The log contains messages generated by Java services, OSGi components, Sling Models, servlets, and other backend application functionality, subject to their configured logging levels.

Option A is incorrect because request.log primarily records HTTP request and response information, including status codes and execution times. It is useful for diagnosing request performance but is not the principal Java application log.

Option B is incorrect because debug.log is not the standard default application log file used by AEM.

Option C is incorrect because sling.log is not the default log file for general application exceptions in the standard AEM configuration.

If additional diagnostic detail is required, the developer can configure an Apache Sling Logging Logger Configuration for the Java package containing MyClass , temporarily set the logging level to DEBUG , and review the resulting diagnostic messages.

Official Adobe Reference: Logging — Standard Loggers and Writers; Monitoring and Maintaining Your AEM Instance — Log Files.

Comprehensive Explanation

Adobe Experience Manager uses Apache Sling's logging infrastructure to manage application log files, including log rotation, logging levels, file destinations, and retention settings.

Log rotation prevents an active log file from growing indefinitely by periodically creating a new file based on a configured time interval or size threshold.

Adobe distinguishes between the Apache Sling Logging Logger Configuration and the Apache Sling Logging Writer Configuration.

The Logger Configuration determines which logging categories produce messages, their severity levels, and their associated log destinations. The Writer Configuration controls how individual log files are written and rotated.

For central logging, the Apache Sling Logging Configuration provides settings for the number of retained log versions and rotation thresholds.

Option B is the closest answer because it belongs to the Sling logging infrastructure. However, configuring a logger alone does not explicitly establish the required rotation policy. A corresponding writer or global logging configuration is necessary.

Options A, C, and D do not represent the appropriate logging rotation configuration.

Verification finding: The technically correct option should be Apache Sling Logging Writer Configuration, or Apache Sling Logging Configuration when configuring the root logger. Neither appears in the question.

Additionally, Adobe warns that AEM as a Cloud Service restricts modifications to the default logging configuration. These settings should not be changed indiscriminately in managed cloud environments.

Official Adobe Reference: Logging — Global Logging and Loggers and Writers for Individual Services; OSGi Configuration Settings.

Comprehensive Explanation

Log-file rotation is an operational mechanism used in Adobe Experience Manager to prevent continuously growing log files from consuming excessive filesystem capacity.

AEM uses the Apache Sling logging infrastructure, which supports configurable rotation policies based on maximum file size or elapsed time.

Option B represents a principal benefit of size-based rotation. When the active log file reaches its configured threshold, the logging system rotates it and creates a new active log file.

Option C describes the storage-management benefit when rotation is combined with a suitable retention policy. By limiting the number of historical log files retained, administrators can prevent uncontrolled accumulation of diagnostic data.

Option A requires qualification. Rotation does not necessarily delete all previous log files. Instead, older files may be retained as rotated versions, with files beyond the configured retention limit subsequently removed.

Adobe documents configurable settings for the number of log-file versions retained, rotation intervals, and maximum file sizes.

These controls are especially important when DEBUG-level logging is enabled, because verbose diagnostic output can rapidly consume storage.

For production environments, rotation thresholds and retention limits should be selected according to storage capacity, troubleshooting requirements, and applicable log-retention policies.

Verification finding: All three selections match the intended question, but option A is imprecise. Log deletion depends on retention settings, and size limitation depends on the configured rotation strategy.

Official Adobe Reference: Logging — Global Logging; Loggers and Writers for Individual Services.

Batch 5 • Questions 41–50