AD0-E906 Adobe Workfront for Experience Manager enhanced connector Expert Free Practice Exam Questions (2025 Updated)

When converting a request to a project in Adobe Workfront, it's important to ensure that custom fields and their values are correctly passed from the request form to the project form. To achieve this, you need to add the same custom field on the project form, but in this case, the calculation should be left blank because the calculated value from the request form will be passed over and does not need to be recalculated at the project level.

Same field: The field needs to be exactly the same (same internal name) so the data can flow between the request and the project during the conversion.

Blank calculation: By leaving the calculation blank, you ensure that the field will accept the value from the request without overriding it or attempting to recalculate it.

For more details on setting up custom forms in Workfront and handling calculated fields during request-to-project conversions, refer to theAdobe Workfront Form Customization Guide.

When configuring the Workfront Enhanced Connector in AEM, Workfront users who will use the connector areautomatically addedto a corresponding AEM user group via the connector. Thisautomatic process ensures that permissions and group assignments are correctly synced between Workfront and AEM without manual intervention.

Option A (using the Import People option in Workfront) refers to importing users into Workfront, not syncing users to AEM. Option C (from the Adobe Admin Console) is related to managing users in the Adobe platform but not specifically for the Enhanced Connector.

Refer toAEM and Workfront Enhanced Connector documentationfor more information on user synchronization and group management.

When creating a log file in AEM, the proper practice is to configure it under the/apps/myproject/configurationpath for the specific runmode folders (e.g., config.dev, config.stage, config.prod). This ensures that the log file configuration is applied based on the environment.

Runmode-specific configurationensures that logs are generated for the correct environment (development, staging, production), following best practices for AEM development.

Option A suggests using the /apps/systemconfiguration path, which is not the recommended location for project-specific configurations. Option B suggests asking for admin access, but developers typically create logs through code configuration rather than direct access to the console.

Refer toAEM’s logging configuration documentationfor details on setting up logs for specific environments.

For a workflow where a task assignee must upload a document, have it reviewed and marked up with annotations, and then have it approved by the director and customer, the best option is toupload the document with a proofing approval workflow attached. Proofing workflows allow for:

Annotations: Reviewers can mark up the document with comments and annotations.

Approvals: Once the document is reviewed, it can go through the necessary approval stages, including the director and customer.

Option A (using approvals under document details) does not allow for the same level of markup and annotation as a proofing workflow. Option C (uploading to a subtask) is not an ideal way to manage the review and approval process with annotations.

Refer toWorkfront’s proofing documentationfor more information on setting up proofing workflows with annotations and approvals.

In this scenario, the best approach is to create separategroupsfor Marketing and IT within the same Workfront instance. Each group will have its owngroup administrator, and each department’s resources (e.g., custom statuses, templates, reports) can be isolated and managed independently by the group admins.

This solution ensures that:

Theexisting IT setupis not disrupted.

The Marketing department can have its own customized Workfront environment without overlapping with IT's configurations.

This approach avoids creating unnecessary complexity (as in Option A with companies) or restricting functionality (as in Option B with teams).

Refer toWorkfront documentation on group managementto learn how to implement group-specific configurations in a single instance.

The issue of the custom field not displaying correctly on a component is likely because thenamespace 'myProject'is not registered in AEM. AEM requires that custom namespaces be registered before they can be used for storing metadata properties. Without registering the myProject namespace, the system cannot properly recognize the custom property, leading to issues displaying the value.

Namespace registration: Custom namespaces like myProject need to be defined in AEM before they can be used to store properties.

Option A is incorrect because the text field should accept special characters, and Option B is incorrect unless there is already a conflicting property name, which is not indicated in this scenario.

Refer toAEM documentation on namespace registrationfor steps on how to register a custom namespace in AEM.

In this scenario, the company wants only one department to use a custom metadata schema with a‘verifiedBy’ user picker fieldfor image assets. The best approach is to:

Create a new metadata schemafor the specific department.

Extend the Coral UI Componentto create a custom user picker field, which will allow the department to select users from the list of available users in the system.

Option A suggests modifying the default image metadata schema, which could impact all departments, and Option B involves manually adding users to a dropdown, which is not as efficient as using a user picker field.

Refer toAEM documentation on creating custom metadata schemasandextending Coral UI componentsfor more information.

To search for assets that are expiring within the next week, the most efficient way is to configure the search rail using theRelative Date Predicate. This predicate allows for dynamic filtering based on a relative date range, such as "next week."

TheRelative Date Predicateautomatically adjusts to search for assets within a specific upcoming time frame, such as the expiration date.

Option A and B are more rigid and require specific date or range configurations, which may not be as flexible or user-friendly as the relative date search.

Refer to AEM’sAssets Admin Search Rail configuration documentationfor more information on predicates and their use in filtering search results.

In Adobe Experience Manager (AEM) as a Cloud Service, deployments are handled through Cloud Manager, and all code, including third-party libraries, must be part of the versioned code repository. To deploy the third-party package provided by the vendor, it needs to be included as part of the AEM project’s codebase under theinstallfolder within the repository:

The package should be stored in the file;$(maven.multiModuleProjectDirectory)/install directory.

Once stored, the deployment will be handled through Cloud Manager’s deployment pipeline.

This ensures the third-party package is included in the standard deployment process and follows AEMaaCS's immutable infrastructure model, which ensures that changes to environments are made only through deployments using Cloud Manager.

Option B is incorrect because installing a package directly to production via CRX Package Manager is not allowed in AEM as a Cloud Service. Option C would work for self-hosted AEM instances but not for AEMaaCS, where dependencies must be part of the Maven build.

For more information, refer to AEMaaCS deployment best practices and theCloud Manager documentation.