Free Adobe AD0-E908 Practice Exam with Questions & Answers | Set: 2

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.

Explanation: This structure ensures that each type of request is properly categorized and routed to the appropriate team for follow-up.

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.

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

Objective: Share a financial report with internal users while preventing external vendors from viewing it.

Steps:

Step 1: Open the financial report settings in Workfront.

Step 2: Configure sharing settings to give view access only to users within the primary company.

Explanation: By restricting view access to only the internal users of the primary company, external vendors will not have visibility of the financial report.

The total number of available hours (AVL) for a user in Workfront can be affected by the following settings:

Time Off: If days are entered in the Time Off menu within a user's settings, these days will be excluded from the total available hours, reducing the AVL value.

FTE (Full Time Equivalent): If a user's FTE setting is less than 1, this indicates that the user is working part-time. This setting will proportionally reduce the number of available hours shown in the AVL column.

References

These settings are documented in Workfront’s user management and scheduling documentation, where the impact of time off and FTE adjustments on user availability is detailed​​​​.

Widgets in Canvas Dashboards:

Canvas Dashboards support the addition of widgets, which are not available in legacy dashboards. Widgets provide dynamic and interactive elements that enhance the visualization of data.

Create the report:

Ensure that the reports intended for use in dashboards are created beforehand and contain the necessary data.

In Adobe Workfront, the hierarchical relationship between Queue Topics and Topic Groups is that Topic Group is the parent, and Queue Topic is the child. This means that a Topic Group can contain multiple Queue Topics, but a Queue Topic is always part of a Topic Group. This structure helps organize and categorize different types of requests or issues within Workfront, making it easier to manage and track them.

References

The hierarchy between Queue Topics and Topic Groups is frequently highlighted in Workfront documentation and training materials, reinforcing that Topic Groups serve as the broader category under which specific Queue Topics fall​​​​.

The Adobe Workfront for Jira native integration allows users to automate and streamline workflows between Workfront and Jira. Specifically, the integration supports the following key feature:

Creation of Jira Issues:

When items are created in Workfront, corresponding issues can be automatically created in Jira. This ensures that tasks and projects managed in Workfront are reflected in Jira, enabling teams to collaborate more effectively across both platforms.

References:

Detailed information on the capabilities of the Workfront for Jira integration is found in the official Workfront documentation and integration guides provided during webinars and training sessions (2.28.23 - The Case for FT Sys Admins)​​.

Create a project report:

Navigate to the Reports area in Workfront and select the option to create a new project report.

Objective: Identify prerequisites for using the Resource Planner and Workload Balancer.

Prerequisites:

Prerequisite 1: Job Roles assigned to Tasks

Explanation: Assigning job roles helps in resource allocation and planning within the Resource Planner and Workload Balancer.

Prerequisite 2: Task Planned Hours greater than zero

Explanation: Tasks need to have planned hours to be considered in the resource planning and workload balancing.

Prerequisite 3: Task Durations greater than zero

Explanation: Tasks must have a duration set to be included in the workload calculations.