A consultant is working with a customer's Marketing department on an Adobe Workfront engagement. The customer has already had a successful deployment of Workfront in the IT department. This installation has been extremely simple, with a single system administrator, five custom statuses used by the IT department, and some templates and reports. The director of Marketing is adamant that the Marketing department will not be using anything created for IT. The engagement cannot disrupt the existing installation.
Which approach should the consultant take?
Answer : C
In this scenario, the best approach is to create separate groups for Marketing and IT within the same Workfront instance. Each group will have its own group 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:
The existing IT setup is 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 to Workfront documentation on group management to learn how to implement group-specific configurations in a single instance.
A developer created a custom metadata profile and assigned default values to some fields. The developer applied this custom profile to a folder in the DAM that already uses a different metadata profile. When viewing the metadata properties of the existing assets in a subfolder, the developer noticed that the custom metadata profile was not applied to these assets.
What is causing this issue?
Answer : A
When a new metadata profile is applied to a folder in AEM, it only affects new assets added to that folder after the profile is applied. Existing assets that were already in the folder or subfolders prior to the profile being assigned will retain the metadata profile that was previously applied.
To update the metadata of existing assets with the new profile, you would need to either manually update the assets or run a script to reapply the metadata profile to those assets.
Option B is incorrect because the profile applies to all assets in the folder, not just direct children. Option C is incorrect because if there were invalid field values, you would likely see an error or warning, rather than a silent failure.
For more details, refer to AEM's documentation on managing and applying metadata profiles.
A creative agency submits proofs for review to stakeholders from multiple companies on a regular basis prior to releasing final assets the creative agency only requires one decision from a company prior to releasing a final asset.
Before the proofs are sent to the stakeholders, the creative director must review the proof. Since this is a standard workflow used for the majority of the work, a proofing workflow template can be set up to expedite the proof approval.
In which two ways may this proofing workflow template be set up? (Choose two)
Answer : A, D
In this scenario, the proofing workflow needs two stages:
Stage 1: This stage routes the proof to the creative director upon proof creation. By selecting 'do not allow this stage to be deleted,' the workflow ensures that the creative director must always review the proof before it is sent to stakeholders. This ensures consistency in the review process and makes sure the creative director is always involved.
Stage 2: This stage activates when all decisions are made on the parent stage (i.e., the creative director's approval). Additionally, since the creative agency only requires one decision from each company, the 'only one decision required' setting is appropriate to speed up the process while ensuring the necessary approvals are gathered.
Option B is incorrect because setting the stage as private may hinder collaboration, and Option C suggests waiting until all decisions are approved, which is not necessary in this scenario.
Refer to Workfront documentation on proofing workflows for details on setting up multi-stage approval processes.
While reviewing the customer's configuration, the consultant lists the following paths as existing within the customer's Experience Manager repository:
/Apps/dam/gui/content/foldermetadatasschemaeditor
/Apps/dam/gui/content/folderscheduleconfiguration
/Apps/dam/gui/content/folderschemaconfigproperties
Which path must be deleted prior to the installation of the Enhanced Connector?
Answer : A
Before installing the Enhanced Connector, the path /Apps/dam/gui/content/foldermetadatasschemaeditor should be deleted to avoid conflicts with the new configuration. This path relates to the older folder metadata schema editor, which can interfere with the Enhanced Connector setup.
Paths related to folder scheduling (folderscheduleconfiguration) and configuration properties (folderschemaconfigproperties) are not related to the Enhanced Connector and do not need to be removed.
Refer to the Enhanced Connector installation guide for specific details on preparing the AEM repository for the connector.
An internal marketing department is building a new workflow where they need to have the task assignee upload a document. That document then needs to be reviewed and potentially marked up with annotations as part of the review process. Then the document needs to be approved by the director of creative marketing and the customer. Which document management process meets this requirement?
Answer : B
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 to upload 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 to Workfront's proofing documentation for more information on setting up proofing workflows with annotations and approvals.
An implementation consultant is configuring the enhanced connector Project Linked holders feature for a customer. The customer wants the linked folder structure to be defined using the workfront Portfolio name. Workfront Program name. Workfront Project name, and the project type. The project type is a project custom form field defined by the following:

What Linked Folder Structure defines this correctly?
Answer : B
In this case, the customer wants to define the linked folder structure based on the Workfront Portfolio name, Program name, Project name, and Project Type. The Project Type is a custom form field with specific choices like 'Campaign,' 'Product Launch,' etc.
The correct format to define the folder structure in AEM based on these elements would be:
Portfolio, Program, Name, projectType: This structure will create a hierarchical folder system in AEM where the folders are nested by Portfolio, Program, Project Name, and Project Type (which is pulled from the custom form field).
Option A includes an incorrect syntax with 'DE
,' which is not necessary, and Option C repeats the 'Program' and misorders the fields.
Refer to Workfront Enhanced Connector documentation for further guidance on defining folder structures using custom form fields.
A web designer creates interactive web content via a URL. which needs to be approved I he user doing the reviewing has a Manager proofing permission profile in Adobe workfront. which they are currently accessing through the latest version of the Chrome browser. As part of the feedback process, the reviewer is required to leave comments on one page of the arte being reviewed before leaving the approval status. The Designer must be tagged in any updates required
which tool should be used to accomplish this?
Answer : B
In this scenario, the reviewer needs to leave comments on an interactive web content URL and tag the designer. The Web Proofing viewer is the appropriate tool for reviewing interactive web content in Adobe Workfront. The Web Proofing viewer allows users to:
Review and comment on web-based content directly in the browser.
Tag users in comments and updates.
Approve or reject the content with the necessary feedback.
Option A (Desktop Proofing viewer) is typically used for offline or downloadable content, and Option C (Legacy Proofing viewer) refers to an outdated tool that lacks modern proofing functionalities.
Refer to Workfront's proofing documentation for more information on using the Web Proofing viewer for interactive content.