Adobe Experience Manager Assets Developer Free Sample Questions

The combination of a unique document root for each tenant's site (e.g., /var/www/html/tenantA) and a /statfileslevel that corresponds to the depth of the site structure within that docroot ensures that auto-invalidation via .stat file creation is scoped only to that tenant's directory tree. When content is activated for tenantA, the .stat file is touched only within tenantA's hierarchy, leaving tenantB's cache untouched. Setting /statfileslevel to 0 disables auto-invalidation, which is incorrect. Using /virtualhosts helps with domain mapping but doesn't inherently solve cache invalidation isolation. Unique cache roots are a part of the solution but are ineffective without the correct /statfileslevel and unique docroots.

The AEM standard for managing environment-specific OSGi configurations is to use run mode-specific config folders. By creating config.author and config.publish folders within the project's /apps/my-project/ directory, AEM will automatically apply the correct org.acme.MyService.cfg.json file based on the active run mode of the instance. This approach avoids hardcoding, keeps configuration out of the code, and is the standard deployment practice for AEM projects.

For queries that filter by a specific property value, creating a custom Oak property index is the standard and most efficient solution. By defining an oak:index node (e.g., under /oak:index/acmeTags) with type='property', propertyNames=['acme:tags'], and reindex=true, the Oak repository will build an index that allows for rapid lookups based on that property, drastically improving query performance and avoiding costly repository traversals. Using a Lucene index is more suitable for full-text search. Modifying the query without an index won't solve the underlying traversal issue. Increasing heap size is a temporary fix for memory issues, not slow queries.

The LDAP (Lightweight Directory Access Protocol) Identity Provider is the specific AEM OSGi configuration designed to integrate with directory services like Active Directory. It allows AEM to delegate authentication to the external LDAP server, meaning AEM never stores the passwords. It also supports user and group synchronization, fulfilling the typical requirements for enterprise integration with Active Directory.

Sling Models are the recommended best practice for encapsulating business logic for AEM components. Using a Sling Model allows for clean separation of concerns, moving complex logic out of the presentation layer (HTL). By using annotations like @ChildResource and a @PostConstruct init method, the model can efficiently access JCR data, perform necessary computations, and expose the results through simple getter methods, which can then be easily accessed in HTL. This approach is highly testable, maintainable, and scalable.

The MapComponents helper function is the core mechanism provided by the AEM SPA Editor SDK for React. It takes a list of AEM resource types and maps them to their corresponding React components. This mapping allows the SPA Editor to dynamically instantiate the correct React component based on the JSON model received from AEM, which contains the :type property for each component. This is the essential bridge between the AEM content structure and the front-end SPA rendering.

AEM Workflows are designed for orchestrating multi-step, long-running, and potentially fallible processes. By creating a workflow model with a custom Java process step that calls the external email service, you gain reliability, retry capabilities, and administrative oversight. A workflow launcher can be configured to automatically start this workflow when a 'Press Release' page is modified or replicated. This is superior to an event listener, which is less robust for handling failures with external systems.

The AemContext object (from io.wcm.testing.mock.aem.junit5.AemContext) is the primary entry point for writing AEM unit tests with AEM Mocks. It provides methods like load().json() to build a mock resource tree from a JSON file and currentResource() to set the context resource. The model can then be adapted from this context resource, allowing for isolated testing of the model's logic without a running AEM instance.

This approach follows AEM best practices for security and configuration management. The OSGi Configuration Admin allows the API key to be stored as a secret, managed via run modes or Cloud Manager secret variables, and kept out of the codebase and content. Injecting this configuration into the service cleanly separates configuration from code. Using a robust HTTP client library like Apache HttpClient provided by AEM is the standard for making reliable external calls.