An implementation consultant needs to configure metadata mapping between Adobe Workfront custom form fields and Adobe Experience Manager metadata properties. Which Iwo types of custom forms can the implementation consultant use to define these mappings? (Choose two)
Answer : A, B
When configuring metadata mapping between Adobe Workfront custom form fields and Adobe Experience Manager metadata properties, you can use Issue and Document custom forms to define these mappings. These types of forms are commonly used for tracking and managing work items and documents, both of which need to have their metadata synchronized between the two systems.
Issue custom forms: Used for tracking work requests, such as issues or tasks.
Document custom forms: Specifically used for managing metadata related to documents, which can be mapped directly to AEM assets.
Options C (Portfolio) and D (Program) are not typically used for metadata mapping related to assets or documents.
Refer to Workfront Enhanced Connector documentation for more information on mapping custom forms to AEM metadata properties.
Given the following workflow launcher configuration:
What change should be made to the configuration to trigger the workflow?
Answer : A
In this scenario, the workflow launcher is configured to trigger a workflow for assets in the path /content/dam/projects/en/designs. However, to ensure that the workflow only triggers for image assets, the condition must be updated to filter the relevant asset types. The condition should be modified to dc:format==image/*, which ensures that only assets with an image format trigger the workflow.
Condition 'dc
==image/*': This filters assets based on their format (MIME type), ensuring that the workflow is only triggered for images, which matches the use case of working with assets such as JPGs or PNGs.
Option B suggests modifying the path, but the existing path (/content/dam/projects/en/designs) is correct for the project structure. Option C suggests changing the node type to nt:file, which is incorrect since the node type for assets in AEM is typically dam:Asset.
For more information, refer to AEM documentation on workflow launchers and DAM metadata properties.
A user applies a custom metadata schema to a folder in AEM Assets However, the user receives an error message. "Unable to edit properties", when trying to save changes to one of the metadata properties for all assets within that folder.
What are two reasons for receiving this message? (Choose two.)
Answer : A, D
There are two possible reasons for receiving the 'Unable to edit properties' error when trying to save metadata properties in AEM:
Insufficient Modify Permission: The user needs to have Modify permissions for the folder or assets within the folder to be able to edit the metadata. Without this permission, changes to metadata cannot be saved.
Invalid Metadata Path: If a metadata property in the schema is mapped to an invalid JCR path, AEM will not be able to save the changes. The system requires valid paths in the JCR to store metadata properties correctly, and any invalid path will result in an error.
Option B, involving asset locking, would prevent editing altogether rather than giving an error during property saving. Option C, mapping two properties to the same path, would result in overwriting issues rather than an error about saving properties.
For more details, refer to AEM's Metadata Schema documentation and permissions management.
As part of the configuration of the workfront for Experience Manager enhanced connector, the solutions consultant needs to limit the access of the legal team Specifically, the legal team should only have read access to all of the content in Experience Manager. This group of users will solely be working in Workfront. but will have access to Experience Manager via the enhanced connector. The consultant has created a new user group in Experience Manager that includes the members of the legal team that exist in wf-workfront-users.
How should the solution consultant manage their access?
Answer : B
In this case, the solutions consultant needs to limit the legal team's access to read-only for all content in AEM. Since the legal team will be working in Workfront and accessing AEM via the enhanced connector, the best way to manage their access is to apply Access Control Entries (ACEs) to the wf-workfront-users user group.
ACEs allow you to specify detailed permissions for a group or user in AEM, such as granting read-only access to specific resources or folders within the DAM.
Options A and C would either grant too much access (as in the case of the Everyone user group) or allow contributions, which is beyond the requirement of just reading access.
Refer to AEM Access Control Management documentation to learn more about setting up ACEs and managing permissions.
An AEM Author wants to search and filter through all assets in the DAM to find assets expiring within the next week.
What is the most efficient way of doing this?
Answer : C
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.
A developer needs to deploy com myCompany.ui.content package to only AEM Cloud Service author environment Which option should the developer choose to meet the requirement?
A)
B)
C)
D)
Answer : A
The requirement is to deploy the com.myCompany.ui.content package specifically to the AEM Cloud Service author environment. 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:
<target>/apps/my-company-packages/content/install.author</target>
The use of install.author ensures that the package will only be installed on the author environment of 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 the AEM Cloud Service documentation on deployment and package management for more details on targeting specific environments such as author during content deployment.
A marketing campaign is being managed in Adobe Workfront As part of this, a user wants to utilize an asset that was created for a previous campaign. This asset exists within Experience Manager Assets. The Workfront for Experience Manager Enhanced Connector has been configured and installed.
How should the user accomplish this?
Answer : B
In this scenario, the user is managing a marketing campaign in Workfront and wants to use an existing asset from AEM Assets. Since the enhanced connector is already installed and configured, the user can go to the Documents area within the Workfront project, click Add new, and then select the Experience Manager integration.
This integration allows the user to browse assets stored in AEM and select the required asset, which will be linked to the Workfront project without the need to download and re-upload the file.
This seamless integration between Workfront and AEM Assets enhances workflow efficiency by enabling users to directly access and use assets from AEM within their Workfront environment.
For more information, refer to the documentation on Workfront and AEM Asset Integration, which covers the process of selecting and using AEM-stored assets within Workfront.