AD0-E127 Sample Questions & Answers

The AEM Forms Signature Service is specifically designed for applying digital signatures to PDF documents. It can be configured to use certificates from various sources, including trust stores and HSMs, to certify or sign documents as part of an automated process like a workflow. The Reader Extensions service enables features in Adobe Reader, and the Encryption service is for password-protecting documents.

The Form Data Model (FDM) provides a mechanism to handle data transformations directly within its service configuration. When configuring the 'GET' service for a data source, you can define a custom script (often using JavaScript) to process the raw response from the API and map it to the FDM's target structure. This is the intended and most maintainable location for such logic.

A DDX (Document Description XML) file is used to provide instructions to the Assembler service. This file specifies the source documents, how they should be combined or manipulated (e.g., adding headers, footers, watermarks, page numbers), and the structure of the resulting output document.

By default, the AEM Dispatcher blocks most POST requests for security reasons. Form submissions are sent as POST requests. A 404 error in this scenario often indicates that the Dispatcher's filter rules are blocking the request before it can reach the AEM publish instance. An explicit 'allow' rule for the submission URL (e.g., /content/forms/af/my-form/jcr:content/guideContainer.af.submit.jsp) is required in the dispatcher.any file's '/filter' section.

When a form is submitted to an OSGi service (typically a Sling Servlet), the submitted data is encapsulated in the SlingHttpServletRequest object. This object provides methods like getRequestParameter() to get field values and getRequestParameterMap() to get all parameters. For file attachments, getRequestPart() or getRequestParts() are used to access the uploaded files as RequestPart objects.

This is the out-of-the-box solution provided by AEM Forms for this exact use case. The Forms Portal components ('Drafts & Submissions') are designed to work with authenticated users to manage their in-progress forms (drafts) and completed submissions. By enabling the 'Save' action, the form data and attachments are securely stored on the publish instance, associated with the user's profile. When the user re-opens the form from the portal, the data is automatically prefilled. This approach meets all requirements with minimal custom code.

When a field's value is changed programmatically via the GuideBridge API (e.g., using myField.value = 'newValue'), it does not automatically fire the 'change' event that the rule editor and other scripts listen for. To ensure the form's logic reacts to the programmatic change, the developer must manually trigger the event on the field object using .trigger('change'). This signals to the form model that the value has changed, causing it to re-evaluate all dependent expressions and rules.

In an AEM Forms on JEE environment, database connectivity is managed through the underlying Java EE application server. After the JDBC driver is available, the administrator must configure a JNDI Data Source within the application server's console (like WebSphere, JBoss, or WebLogic). This data source contains the connection details (URL, user, password). AEM Forms services then look up this data source via its JNDI name. This step must be completed before configuring connectors in the AEM Forms Administration Console.

The 'Set Value' process step is designed for this purpose. It can read data from the workflow payload (the submitted XML data) using XPath expressions and write the extracted values to the workflow's metadata map. This allows for declarative, code-free logic for routing and decisions within the workflow based on submitted form data.

Adaptive Form Fragments are specifically designed to create reusable segments of a form. A developer can create a fragment containing fields (like street, city, state, zip), associated rules, and scripts. This fragment can then be embedded into multiple adaptive forms, promoting consistency and dramatically reducing development time. Any updates to the fragment are automatically reflected in all forms that use it.