A manager needs to create a Request queue that tracks requests for Creative assets and Website changes, and assigns the requests to different teams…

To meet the manager's requirement, distinct pathways for "Creative assets" and "Website changes" are needed. This is achieved by creating two Queue Topics, one for each request type. To automatically assign these requests to different teams, two Routing Rules must be configured. Each Routing Rule is then linked to its corresponding Queue Topic. This ensures that when a user selects a specific topic on the request form, the associated rule is triggered, directing the request to the correct team's project or queue for fulfillment.

A. Routing Rules are assigned to Queue Topics to define the request's destination, not to Topic Groups, which are for organizational display.

C. This option lacks Routing Rules, which are the essential mechanism for automatically assigning the submitted requests to different teams.

1. Adobe Workfront Documentation, "Create Queue Topics": This document states, "Queue topics allow you to define the types of requests that users can submit to a request queue... After you create a queue topic, you can associate it with a routing rule to define where the issue is routed after it is submitted." This confirms the direct relationship between Queue Topics and Routing Rules. (See section: "Create a Queue Topic").

2. Adobe Workfront Documentation, "Create Routing Rules": This source explains, "Routing rules define the destination of a request that is submitted to a request queue. For example, you can route requests to a specific project, or assign them to a specific user or team depending on what Queue Topic is selected." (See section: "Create a Routing Rule").

3. Adobe Workfront Documentation, "Create Topic Groups": This document clarifies the function of Topic Groups: "Topic groups allow you to group similar queue topics together... This makes it easier for users to find the correct queue topic when they are making a request." This confirms their role is organizational, not functional for routing. (See section: "Create a Topic Group").