AD0-E906 Sample Questions Answers

When configuring allowed HTTP request methods for /bin/workfront-tools on the AEM dispatcher, the safest and most appropriate methods to allow areGET, POST, and PUT. These methods cover the basic operations for retrieving data (GET), submitting data (POST), and updating data (PUT), which are typically required for the Enhanced Connector functionality.

GET: Used to retrieve data from the server.

POST: Used to send data to the server.

PUT: Used to update resources on the server.

Options A (DELETE) and B (HEAD, DELETE) are riskier and less commonly needed for this use case, and DELETE should be restricted unless absolutely necessary to prevent unintended deletions.

Refer toAdobe documentation on Dispatcher securityfor best practices regarding allowed HTTP methods.

When handling high-volume content ingestion in AEM,transient workflowsare a key factor for optimizing performance. Transient workflows do not persist workflow data in the JCR repository, which greatly reduces the load on the repository and improves overall performance. Since content ingestion typically involves processing a large number of assets, using transient workflows prevents unnecessary data accumulation in the repository.

Transient workflowsare ideal for operations where you don’t need to keep historical data about each workflow instance, such as ingestion processes, thereby making the system faster and more efficient.

Option A (using schedulers) is not related to workflow performance, and Option B (allocating more RAM) is a generic solution but not directly tied to optimizing workflow efficiency.

For further guidance, refer to AEM's documentation onworkflow optimizationandtransient workflows.

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 onEvent Subscriptionsin the enhanced connector configuration.

Event Subscriptionsare 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 toAEM Enhanced Connector documentationon Event Subscriptions and their use in automating processes.

If themulti-value text fieldis being populated unexpectedly, the most likely cause is thatanother field in the metadata schema is mapped to the same property. When multiple fields are mapped to the same property in AEM, any updates to either field will overwrite or modify the property, leading to the unexpected population of values.

This can happen due to schema misconfiguration, where fields unintentionally share the same JCR property path.

Option B is incorrect because the value being required would not cause it to be populated automatically. Option C suggests simultaneous updates by different users, which is unlikely to cause the issue described.

Check themetadata schema configurationto ensure fields are mapped to distinct properties.

In Workfront, the best way to ensure that all documents within a project are shared with a designated team is toshare the entire project. By sharing the project, all documents and related assets within that project are automatically made available to the designated team members according to the project's access permissions.

Option C is incorrect because sharing one document does not automatically inherit the same access levels for the other documents. Option A suggests linking documents from AEM, but the question pertains to sharing documents within Workfront itself.

Refer to Workfront’sdocumentation on document sharingfor detailed instructions on how to share all project-related assets with teams.

Workfront includes adocument checkoutfeature 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 benotified 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 theDocument Collaboration and Managementsection in the Adobe Workfront documentation, which outlines how the check-in/check-out system works.

To configure the Enhanced Connector in AEM, including features like automatic project-linked folder creation, comment syncing, and automatic publishing of assets, you should navigate to:

Tools > Workfront Tools > Workfront Tools Configuration: This is where you can access and configure the connector settings within AEM. From there, selecting the configuration and choosingPropertiesin the action bar allows you to adjust the required settings.

Options B and C reference incorrect paths (Cloud Services and Assets), which are not used for the Enhanced Connector configuration.

Refer toAEM’s Enhanced Connector documentationfor step-by-step instructions on accessing and configuring the connector.

To include themountain assetsin the search results for "hiking" and ensure they show up at the top of the search, the best approach is to assign the‘hiking’ tagto these assets. By using tags, you can enhance the discoverability of the assets without modifying their titles or descriptions. Tags are indexed and have a strong influence on search results in AEM.

Tagging assetsis an efficient way to associate them with relevant topics or keywords, such as "hiking," which would improve their ranking in search results.

Option A suggests using "search boosting," which does not exist in AEM's metadata editor. Option C involves adding "hiking" to the content and status fields, which isn't the best way to influence search ranking and could clutter the metadata.

Refer toAEM documentation on metadata tagging and search optimizationfor more details.

In AEM, for a custom workflow process to be available for selection in the dropdown menu of a process step, theprocess.nameproperty 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 theAEM documentation on creating custom workflows and annotating components.

The requirement is to deploy the com.myCompany.ui.content package specifically to theAEM Cloud Service authorenvironment. The key here is ensuring that the package is targeted correctly to the author instance, without affecting other environments.

Option A uses the following target:

/apps/my-company-packages/content/install.author

The use of install.author ensures that the package will only be installed on theauthor environmentof AEM as a Cloud Service, meeting the developer's requirement. This is a common approach in AEM Cloud Service projects, where you differentiate between environments using the appropriate subfolder (in this case, author).

Option B (author.install) and Option D are similar but incorrect because they are not standard for specifying the exact environment, while Option C (install/) is too generic and could apply to both author and publish environments.

Refer to theAEM Cloud Service documentationon deployment and package management for more details on targeting specific environments such asauthorduring content deployment.

In Adobe Experience Manager (AEM), when mapping metadata fields from Workfront, custom form fields are referenced using theCUSTOM FORMSprefix followed by the internal name of the field. In this case:

TheLabelis "Creative Manager"

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

To reference this field in AEM metadata, you need to use theCUSTOM FORMS:prefix followed by the field's name, making the correct referenceCUSTOM 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.

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.

TheAuthorpermission role is necessary for the design team members who need toedit the proofsbefore they are sent for review by legal and financial teams. This role allows them to make changes directly to the proof and upload new versions, which is essential for their work in this multi-stage automated workflow.

Author role: Grants permission to edit and manage the proof, which includes uploading new versions and making changes to the existing proof content.

Options B (Reviewer) and C (Approver) are more restrictive roles that do not allow for editing proofs.

Refer toWorkfront Proofing roles and permissions documentationfor more information on the different proof roles.