support@Free-Braindumps.com
Register Login
Cisco
CompTIA
ISC
EC-Council
EXIN
Fortinet
ITIL
Juniper
Microsoft
VMware
Avaya
SAP
Google
NVIDIA
Salesforce
Amazon
Palo Alto Networks
ISC2
CrowdStrike
Anthropic
All Vendors
  1. Home
  2. Exams
  3. Adobe
  4. AD0-E908

Adobe AD0-E908 Exam Prep
Adobe Workfront Core Developer Professional (Page 6 )

Updated On: 27-Sep-2026
Page 3 of 15
PDF with 70 Questions

A client wants to keep track of project metrics based on the request that was submitted, but they do not want the requestor to fill this information out. How would a system administrator configure this request?

  1. Create a section break to the request Custom Form containing the metric fields, and change the permissions so it is not visible to the requestor
  2. Restrict access to the metric fields by removing request queue access from the requester and change their access level to "view"
  3. Do not make the additional fields in the Custom Form available to the requester, but add them to the project details section

Answer(s): C

Explanation:

Objective: Track project metrics based on the submitted request without allowing the requester to fill in this information.
Configuration Steps:
Step 1: Create a Custom Form with the necessary metric fields. Step 2: Do not include these metric fields in the part of the form visible to the requester. Step 3: Add these metric fields to the project details section instead. This ensures that the requester does not input the metric information, but the information can still be tracked and recorded as part of the project details.


Reference:

Refer to advanced reporting and custom field management in Workfront documentation.



Which two actions are necessary for a request queue to be visible in the system? (Choose two.)

  1. Check the box to publish as a help request queue
  2. Add a routing rule to the queue details
  3. Indicate the default fields to be shown on all requests
  4. Ensure that the queue project is within a status that equates to Current

Answer(s): A,D

Explanation:

Objective: Make a request queue visible in the system.
Necessary Actions:
Action 1: Check the box to publish as a help request queue. This action makes the queue available for users to submit help requests.
Action 2: Ensure that the queue project is within a status that equates to Current. This ensures the project is active and visible to users.

Both actions are required to ensure the request queue is not only visible but also active and functional for users.


Reference:

This information can be confirmed in the Workfront queue and project status settings documentation.



When someone who is named as the Default Assignee in a routing rule has their account deactivated, how does Adobe Workfront route requests?

  1. Requests will be routed to the default assignee's manager.
  2. Requests will continue to be routed to the deactivated account.
  3. Requests will be routed to another user with the same role.

Answer(s): B

Explanation:

Objective: Understand how requests are routed when the default assignee in a routing rule is deactivated.
Routing Behavior:
Workfront does not automatically reassign requests when the default assignee is deactivated. Requests will continue to be routed to the deactivated account unless manually reconfigured.


Reference:

This can be verified in the routing rules and account management sections of the Workfront documentation.



A manager needs to create a Request queue that tracks requests for Creative assets and Website changes, and assigns the requests to different teams for follow-up.
Which steps must be completed to meet this need?

  1. Create two Routing Rules Create two Topic Groups Assign Routing Rules to respective Topic Groups
  2. Create two Routing Rules m Create two Queue Topics
    Assign Routing Rules to respective Queue Topics
  3. Create two Topic Groups Create two Queue Topics Assign Queue Topics to respective Topic Groups

Answer(s): B

Explanation:

Objective: Track requests for creative assets and website changes and assign them to different teams.
Steps:
Step 1: Create two separate routing rules, one for creative assets and one for website changes. Step 2: Create two queue topics corresponding to the types of requests. Step 3: Assign each routing rule to the respective queue topic. This structure ensures that each type of request is properly categorized and routed to the appropriate team for follow-up.


Reference:

These steps are detailed in the Workfront documentation on setting up routing rules and queue topics.



An organization captures project requests in a request queue. Once the request has been triaged, it is converted into a project and the information captured in the request custom form should be carried over to the project.
How would a developer achieve this?

  1. Create a multi-object custom form with both the project and issue object types selected
  2. Create a project template and attach an issue custom form
  3. Check the box in the queue details to transfer the issue custom form to a project

Answer(s): C

Explanation:

In Adobe Workfront, when an organization captures project requests in a request queue and wants the information from the request custom form to be transferred to the project upon conversion, the developer should use the feature in the queue setup. Specifically, there is an option within the queue details where a checkbox can be selected to ensure that the custom form associated with the issue is transferred to the project. This allows all the information captured in the request custom form to be carried over seamlessly to the new project.



  PDF
Viewing page 6 of 15
Viewing questions 26 - 30 out of 70 questions


Post your Comments and Discuss Adobe AD0-E908 exam prep with other Community members:

AI Tutor AI Tutor 👋 I’m here to help!