In which two ways can an AEM Publish Instance refresh the Dispatcher cache?
Choose two
Through an HTTP GET Request sent by an Author Instance’s Custom Servlet to the Dispatcher
Through an HTTP GET Request sent by the Publish Instance’s Dispatcher Flush Agent to the Dispatcher
Through an HTTP GET Request sent by a Publish Instance’s Custom Servlet to the Dispatcher
Through an HTTP GET Request sent by the Author Instance’s Dispatcher Flush Agent to the Dispatcher
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.
A developer needs a component to be visible to authors but not editable on every page created from the template.
What should be implemented?
Remove the component from the allowed components in the policy
Place the component in the initial content section of the editable template
Disable the component in the layout container settings
Lock the component in the structure section of the editable template
Comprehensive Explanation
Editable templates in Adobe Experience Manager separate template configuration into Structure, Initial Content, Content Policies, and Layout.
The Structure section defines components that must remain consistent across pages created from the template. Components placed in this section can be locked to prevent page authors from modifying, moving, or deleting them.
When a component is locked in the template structure, it remains visible on resulting pages but cannot be edited directly by ordinary page authors.
This capability is particularly useful for mandatory page elements such as standardized headers, regulatory notices, branding elements, and structural containers.
Option A is incorrect because removing a component from the allowed-components policy restricts its availability for insertion; it does not establish an existing, non-editable component.
Option B is incorrect because Initial Content provides starting content that authors can subsequently modify on individual pages.
Option C does not provide the required template-level editing restriction.
The appropriate implementation is therefore to place the component in the editable template's Structure section and maintain it in a locked state.
Adobe's editable-template documentation explicitly distinguishes locked structure components from editable initial content, establishing the correct behavior for this requirement.
Official Adobe Reference: Editable Templates — Structure and Initial Content; Templates to Create Pages That Are Editable with the Page Editor.
What is the out-of-the-box Dispatcher response when a request is made for a URL defined as deny in the Dispatcher /filter setting?
404
403
400
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.
A developer has enabled log-file rotation.
Why is this process important for managing log files?
Choose three
It deletes previous log files.
It limits the size of the log file.
It reduces disk space usage.
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
A developer must create a new AEM project archetype that uses Adobe Managed Services.
Which property must be set while generating the project?
package
version
sdkVersion
aemVersion
Comprehensive Explanation
The AEM Project Archetype uses the aemVersion property to determine the target Adobe Experience Manager runtime environment for the generated project.
When generating a project intended for Adobe Managed Services (AMS), developers must specify a compatible AEM 6.5 version rather than selecting the Cloud Service target.
For example:
-DaemVersion=6.5.8
Adobe explicitly documents 6.5.8 as an example value for Adobe Managed Services or on-premises environments. The actual value should correspond to the AEM version targeted by the implementation.
If aemVersion is not specified, current archetype versions default to cloud , which generates an AEM as a Cloud Service-oriented project.
Option A controls the generated Java source package and does not identify the target AEM runtime.
Option B specifies the Maven project version, commonly initialized with a snapshot value.
Option C specifies an AEM SDK version when targeting the Cloud Service environment. It does not determine whether the project is intended for Adobe Managed Services.
The aemVersion property influences generated dependencies and deployment-related configuration. It is therefore essential when targeting an AMS environment rather than AEM as a Cloud Service.
Official Adobe Reference: AEM Project Archetype — Usage and Available Properties.
A developer wants to view response times for page transactions.
Which log file should they use?
audit.log
stdout.log
request.log
Comprehensive Explanation
Adobe Experience Manager maintains an HTTP request log that records incoming requests and their corresponding responses, including response times.
The request.log file is particularly useful for identifying slow page requests, diagnosing performance problems, and evaluating application responsiveness.
Each request receives an identifier that associates the incoming HTTP request with its corresponding response. The response record includes the HTTP status code, content type, and processing time.
For example:
09:43:41 [66] - > GET /content/site/en.html HTTP/1.1
09:43:41 [66] < - 200 text/html 797ms
In this example, AEM required 797 milliseconds to process the request.
Option A is incorrect because audit.log primarily records auditing information, such as content-related administrative and moderation activities.
Option B is incorrect because stdout.log captures standard-output messages, including startup-related information, rather than providing the dedicated request timing records.
Option C is correct because request.log provides a direct mechanism for analyzing HTTP response times.
Adobe recommends using request-log analysis to identify slow pages, evaluate request concurrency, and diagnose application performance bottlenecks.
For extensive performance investigations, developers can aggregate response times by URL and correlate slow requests with thread dumps, repository query performance, and application logs.
Official Adobe Reference: Monitoring and Maintaining Your AEM Instance — Interpreting the request.log; Examples of request.log Analysis.
In which folder are configuration changes persisted as .config files in the repository?
/conf
/apps
/content
/et’
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.
An AEM Developer is responsible for creating a French version of an e-commerce site for several French-speaking African countries, including Chad, Ivory Coast, and Senegal.
What are the correct steps for implementing the sites with localized content?
Select AEM Multi-Site Manager and then use a Primary English version of pages to create French versions for Chad, Ivory Coast and Senegal
Select AEM Multi-Site Manager and then use a Primary French version of pages to create French versions for Chad, Ivory Coast and Senegal
Use Multi-Site Manager to create live copy of site templates then use separate French version for Chad, Ivory Coast and Senegal
Use local content authors to create the content for the local sites
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.
A marketing team must reuse a product description across several pages and channels, including a website, a mobile app, and an email campaign.
Which AEM feature should the team use to manage this content and keep it consistent?
Template Fragment
Asset Fragment
Content Fragment
Experience Fragment
Comprehensive Explanation
Adobe Experience Manager provides the Multi Resource Support configuration option for workflow models that must process several content resources within a single workflow instance.
By default, when a workflow model without Multi Resource Support is applied to multiple selected assets or pages, AEM starts an independent workflow instance for each resource.
Enabling Multi Resource Support changes this behavior. AEM creates one workflow instance and attaches the selected resources through a workflow package, allowing them to be processed together.
To configure this feature, the developer opens the Workflow Models console, edits the relevant model, and selects Workflow Model Properties. The Multi Resource Support option is then enabled.
After saving the configuration, the developer must select Sync to generate the updated runtime model. This operation ensures subsequent workflow instances use the modified configuration.
Option A is incorrect because Transient Workflow controls workflow-history persistence and execution overhead. It does not consolidate multiple resource payloads into a single instance.
Option B is incorrect because Multi Resource Enable is not the documented configuration-property name.
Multi Resource Support is particularly useful for batch approval, grouped asset-processing operations, and coordinated publishing workflows where multiple resources share the same approval or processing sequence.
Adobe explicitly documents that activating this option starts one workflow instance even when multiple resources are selected.
Official Adobe Reference: Developing and Extending Workflows — Multi Resource Support; Creating Workflow Models — Configuring a Workflow for Multi Resource Support.
A customer has a topology where the cache flush agent is not configured.
Which two methods would the developer use to update the cache?
Choose two
Content Updates
Restart on AEM Publish Instance
Restart on AEM Author Instance
Auto-invalidation on the Dispatcher
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.
TESTED 21 Nov 2026
Copyright © 2014-2026 DumpsTool. All Rights Reserved