Adobe AD0-E908 Practice Test - Questions Answers, Page 3

Objective: Understand how requests are routed when the default assignee in a routing rule is deactivated.

Routing Behavior:

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.

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.

In Adobe Workfront, if a portfolio manager deletes a portfolio, the immediate effect is that all programs associated with that portfolio are also deleted. However, the projects associated with those programs remain intact but will no longer be associated with any portfolio or program unless they are reassigned. This hierarchical deletion ensures that while the structural organization (programs) under the portfolio is removed, the actual project data remains unaffected and can be reassigned or restructured as needed.

The Portfolio Optimizer in Adobe Workfront is a tool used by project managers and portfolio managers to analyze and prioritize projects. The information used in the Portfolio Optimizer primarily comes from the project's Alignment Score. This score is a calculated metric that reflects how well a project aligns with the strategic goals and priorities of the organization. The Alignment Score helps in objectively comparing and prioritizing projects based on their strategic value.

In Adobe Workfront, there are specific constraints regarding the association of projects, programs, portfolios, and tasks. A project and its tasks can only belong to one portfolio and one program at a time. This means that a single project cannot be simultaneously associated with multiple portfolios or programs. This constraint ensures clear and unambiguous project management and reporting within the organizational structure.

When organizing projects using Portfolios and Programs in Adobe Workfront, two key considerations apply:

Portfolios are containers for Programs: This means that programs are organized within portfolios, and a portfolio can contain multiple programs. This hierarchical structure helps in managing and aligning various programs under broader strategic initiatives represented by portfolios.

Projects can be associated with only one Program or Portfolio: A project can be linked to a single program and, by extension, to the portfolio containing that program. This ensures clarity in project alignment and reporting within the organizational structure.

Reference

These considerations are discussed in the Workfront training materials and documentation, which explain the hierarchical relationships and constraints for using portfolios and programs to organize projects.

Objective: Set up a consistent review and approval process where the approvals are first routed to the users' team and then to their manager.

Workflow Setup:

Step 1: Create an automated workflow template within Workfront.

Step 2: Define two stages in the workflow template:

Stage 1: Approval by the team members.

Stage 2: Approval by the manager.

Step 3: Apply this workflow template to the uploaded proof assets.

Objective: Trigger the approval by the lead designer for a task to be completed.

Approval Trigger:

Action: Request a document approval from the lead designer.