AD0-E137 Sample Questions & Answers

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.

In the standard AEM Project Archetype structure, the autoInstallSinglePackage profile is configured in the root pom.xml. When this profile is activated (e.g., mvn clean install -PautoInstallSinglePackage), Maven builds all the individual modules (core, ui.apps, ui.content, etc.) and then uses the content-package-maven-plugin to embed them into a single 'all' package. This 'all' package is the final artifact that gets deployed to AEM, ensuring all parts of the project are installed together.

The Code Scanning gate in a Cloud Manager pipeline is a mandatory step that performs static code analysis on the project's source code. It uses a combination of SonarQube, Oak-Pal content package validation, and Dispatcher configuration validation to enforce quality standards. This gate is crucial for ensuring the stability, security, and performance of code deployed to AEM as a Cloud Service environments.

The filter.xml syntax for content packages in AEM is path-based and does not support filtering based on JCR property values or mixin types. The include/exclude rules operate solely on the node paths. To achieve such conditional packaging, a more advanced solution like a custom build hook (using the content-package-maven-plugin's hooks feature) or a script that programmatically builds the package definition would be required.

For administrator-driven content migration between environments (like staging to prod), using content packages is the standard and most reliable method. It allows for precise definition of content paths (filters), inclusion of ACLs, and versioning. The resulting package is a single ZIP file that can be downloaded, stored, and then uploaded to the target instance. Crucially, packages can be uninstalled, providing a straightforward rollback mechanism. Replication is for author-to-publish, and the Content Transfer Tool is for migrating to AEMaaCS.

This is false. While the syntax is valid, the underlying architecture of AEM as a Cloud Service is different. The service referenced might not be available or might have been replaced by a different API. Furthermore, the dynamic nature of the cloud environment means services can be restarted or redeployed more frequently. Code must be resilient. All code, regardless of its apparent compatibility, must be reviewed and tested against the Cloud Service SDK and analyzed with the Cloud Readiness Analyzer.