AD0-E906 Practice Questions

The features requested by the customer, such as automatic folder creation, synchronization of

Workfront document custom form values to AEM asset metadata, and automatic publication of

assets to Brand Portal upon project completion, rely on Event Subscriptions in the enhanced

connector configuration.

Event Subscriptions are triggered when certain events occur, such as project completion or updates

to custom form values, ensuring that the correct actions (like folder creation or asset publication)

happen automatically.

Option A (Workflows) would be used for content approval processes but not for these specific

automatic actions. Option B (Webhooks) can handle external notifications but is not directly relevant

for these tasks within AEM and Workfront.

For more information, refer to AEM Enhanced Connector documentation on Event Subscriptions and

their use in automating processes.

In Adobe Experience Manager (AEM), when mapping metadata fields from Workfront, custom form

fields are referenced using the CUSTOM FORMS prefix followed by the internal name of the field. In

this case:

The Label is "Creative Manager"

The Name is "managerCreative," which is the internal field name in Workfront.

To reference this field in AEM metadata, you need to use the CUSTOM FORMS: prefix followed by the

field's name, making the correct reference CUSTOM FORMS: managerCreative. This ensures that

AEM can correctly pull the metadata value from Workfront when syncing or using the Workfront

enhanced connector for AEM.

Options A and B are incorrect because they either lack the proper formatting or are incomplete.

For more details on this configuration, you can refer to Adobe Workfront's enhanced connector

documentation for AEM, particularly around metadata mapping and field referencing practices.

Workfront includes a document checkout feature that allows users to lock a document when it is

being edited, preventing others from downloading or editing the file simultaneously. This feature

effectively stops duplication of effort and ensures that only one person can work on a document at a

time.

Document Checkout: By navigating to the document details page and clicking "Check out," the

document will be locked for editing by the person who checked it out. Other users will be notified

that the document is being edited, and they will not be able to download or make changes until it is

checked back in.

Option B is incorrect because changing the document status to "Unavailable" does not prevent

downloading or editing. Option C, while helpful for communication, does not enforce restrictions,

which could still lead to duplication of effort.

For more detailed information, refer to the Document Collaboration and Management section in the

Adobe Workfront documentation, which outlines how the check-in/check-out system works.

In AEM, to limit the number of concurrent workflows running at the same time, you need to adjust

the Maximum Parallel Jobs setting in the OSGI console. This setting controls how many workflow jobs

can be processed simultaneously, and reducing this number will lower the load on the server by

limiting the number of workflows that can run concurrently.

This setting can be found under the Day CQ Workflow - Workflow Engine configuration in the OSGI

Web Console.

Options B and C refer to specific workflows and threads, but they do not directly address the overall

system limit on concurrent workflow executions.

Refer to the AEM documentation on workflow scaling and performance for more information on how

to adjust these settings in the OSGI configuration.

In AEM, for a custom workflow process to be available for selection in the dropdown menu of a

process step, the process.name property must be set in the @Component annotation. This property

defines the unique name under which the custom workflow process will be registered and visible in

the workflow model editor.

Here is an example of how this should be added to the existing code:

@Component(service = WorkflowProcess.class,

property = {"process.label=Custom Workflow Process",

"process.name=customWorkflowProcess"})

process.label: This is the label that appears in the workflow model editor dropdown.

process.name: This is the internal identifier used by AEM to register the workflow process.

Options A and B would define other properties but will not resolve the issue of the custom workflow

not appearing in the dropdown. The key property needed here is process.name.

For more details, refer to the AEM documentation on creating custom workflows and annotating

components.

To search for assets that are expiring within the next week, the most efficient way is to configure the

search rail using the Relative Date Predicate. This predicate allows for dynamic filtering based on a

relative date range, such as "next week."

The Relative Date Predicate automatically 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’s Assets Admin Search Rail configuration documentation for more information on

predicates and their use in filtering search results.

When metadata mappings between Adobe Workfront and AEM are configured, the process of

sending a document along with its metadata from Workfront to Adobe Experience Manager (AEM)

Assets is streamlined. The user selects the document in Workfront, clicks "Send to," and chooses the

Experience Manager integration.

The metadata fields that have been mapped are automatically synchronized along with the

document. There is no need for manual selection of metadata at this stage, as the integration

ensures that all configured mappings are applied.

This functionality is part of the enhanced connector, which simplifies the workflow between

Workfront and AEM Assets by automating the synchronization of mapped metadata fields during the

document transfer.

For more details, refer to Adobe's documentation on Workfront for Experience Manager Enhanced

Connector, which outlines how automatic metadata synchronization works during document

transfers.

In AEM Cloud Service, the correct approach to making changes, even urgent ones, is to update the

codebase and deploy it through the Cloud Manager pipeline. This ensures that the change is part of

the version-controlled, immutable repository and follows best practices for deployment.

Immutable infrastructure: AEMaaCS does not allow direct modifications to production environments

(e.g., via CRXDE Lite). All changes must be deployed through Cloud Manager, ensuring consistency

and traceability.

Making changes directly on production via CRXDE or deploying one-off fixes using the Package

Manager (Options B and C) violates AEMaaCS's immutable infrastructure principle and is not

supported.

Refer to Adobe Cloud Manager’s documentation for best practices on deploying urgent fixes in AEM

as a Cloud Service.

To implement conditional automatic publishing of assets from Workfront to AEM based on the value

of the custom form field, you should:

Check the option "Automatically publish assets when sent from Workfront": This ensures that the

assets will be automatically published to AEM when they are sent from Workfront.

Use the custom form field ("auto_publish_assets"): The system needs to check the value of this

custom form field, and if it is set to "Yes", the assets will be automatically published.

Set the Custom Form Field Value to "Yes": In the configuration, you’ll specify that automatic

publishing only occurs when the field value is "Yes."

Option B incorrectly refers to "Workflow" instead of "Workfront," and Option C refers to publishing to

Brand Portal, which is irrelevant since the customer does not have Brand Portal.

Refer to Workfront for AEM Enhanced Connector documentation for step-by-step guidance on

configuring conditional automatic asset publishing.

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 the Adobe Workfront Form Customization Guide.