What is the hierarchical relationship between a Queue Topic and Topic Group?
A
Explanation:
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.
Reference
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.
A project manager needs to share a Custom Form that was created to support their portfolio. What
should the project manager understand about this requirement?
B
Explanation:
In Adobe Workfront, Custom Forms can be shared by their authors with specific permissions. The
author of a Custom Form has the ability to control who can view, share, and edit the form. These
permissions can be set for individuals, roles, groups, teams, and even across the entire company.
This functionality is critical for maintaining control over who can access and modify the forms,
ensuring that only authorized users have the appropriate level of access.
Reference
This information is consistent with the permissions settings outlined in the Workfront documentation
and in various training resources provided by Adobe.
A Workfront developer is tasked with building a new custom form to collect project requests. The
form will display different sets of options based on different selections, which requires the use of
display logic and skip logic in the form.
What are two considerations the developer should take into account when building the conditional
logic in the form? (Choose two.)
A, D
Explanation:
When building a custom form in Adobe Workfront that uses display logic and skip logic, developers
need to consider the following:
When copying an old form: If you copy an existing custom form that includes display logic or skip
logic, these logic settings will not be transferred to the new form. The logic needs to be manually
recreated in the new form to ensure it functions as intended.
Skip logic limitations: Skip logic does not operate effectively with certain elements like widgets or
section breaks within the form. This limitation means that skip logic cannot be applied to control the
visibility or behavior of these elements, potentially impacting how the form is structured and
functions.
Reference
These considerations are detailed in advanced reporting and form customization documentation and
have been highlighted in various Workfront admin training sessions.
In which scenario would an administrator use a request queue to resolve a business need?
C
Explanation:
Request queues in Adobe Workfront are particularly useful for managing the intake of work requests
into a department. By setting up a request queue, a team can standardize the process for receiving,
evaluating, and assigning incoming requests. This helps in ensuring that all requests are handled
consistently and efficiently, prioritizing and delegating work based on the team’s capacity and
current workload.
Reference
The usage of request queues for managing work intake is a common practice outlined in Workfront
training materials and is emphasized in several case studies and user guides provided by Adobe.
An organization wants to ensure that everyone can fill out the general project custom form
associated with the general project template. What is the correct sharing setting for the custom
form?
B
Explanation:
Objective: Ensure that everyone in the organization can fill out the general project custom form
associated with the general project template.
Form Sharing Settings:
Correct Setting: Update the form sharing to "Make this visible system-wide so that everyone in
Workfront can see it".
Explanation: This setting ensures that the form is accessible to all users within the system, allowing
anyone to fill out the form as required.
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?
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.
Explanation: 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.)
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.
Explanation: 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?
B
Explanation:
Objective: Understand how requests are routed when the default assignee in a routing rule is
deactivated.
Routing Behavior:
Explanation: 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?
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.
Explanation: 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?
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.
A portfolio manager has deleted a portfolio that is no longer relevant to the business strategy. Which
is a result of this action in Workfront?
B
Explanation:
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.
A project manager is using information in the Portfolio Optimizer to analyze which projects to
prioritize. Where is this information coming from?
A
Explanation:
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.
What are the constraints among Programs, Portfolios. Tasks, and Projects?
B
Explanation:
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.
A project manager wants to use Portfolios and Programs to organize projects. What two
considerations would apply when using these objects? (Choose two.)
C, E
Explanation:
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.
A customer has a set of users who need to review and approve proof assets associated with projects.
The approvals always need to route to the users' team for feedback before being sent to their
manager.
What needs to be set up in the system to support this consistent review and approval process?
A
Explanation:
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.
Explanation: This ensures a structured and consistent approval process, routing the assets first to the
team for feedback and then to the manager for final approval.
Reference: Detailed information on setting up workflows can be found in the Workfront
documentation on automated workflows.