A project manager is updating a project in Workfront that is behind schedule.
Which action could be taken so that all tasks are completed by the requested completion date?
Answer : B
In Adobe Workfront, task Duration represents the time frame available for a task to be completed. Adobe documentation states that task duration is the difference between the task's Planned Start Date and Planned Completion Date, and that planned task dates affect the overall project timeline. When a project is behind schedule and must still meet a requested completion date, reducing task durations is a valid scheduling action because shorter durations can move planned completion dates earlier and compress the project timeline. Applying a Must Start On constraint to all tasks is not the best approach because that constraint forces each task to start on a specified date and can reduce Workfront's ability to calculate the schedule dynamically. Adjusting all Planned Start Dates to the same day is also inappropriate because it ignores task sequence, predecessors, dependencies, and realistic resource planning. Workfront recommends using durations and predecessor relationships to establish project timelines rather than relying on manually forced constraints. Therefore, the correct action is B. Reduce the durations of the tasks.
=========
A project manager checks an Incomplete Tasks report and notices that several tasks are listed even though the items are marked as 100% complete. What column can the project manager add to the view to understand why those tasks are included in the report?
Answer : C
Even though tasks may be marked as 100% complete, their Status may still be listed as incomplete in reports if the task's status has not been updated to 'Completed.' The Status column provides insight into the current state of the task, which helps identify if the task is still listed as 'In Progress' or another incomplete status despite being marked as fully complete. Adding this column clarifies why the task appears in the Incomplete Tasks Report.
What item, when shared with a user, can never give that user inherited permission to a project?
Answer : C
Adobe Workfront, permissions can be inherited through various objects like projects, portfolios, or tasks when shared with users. However, when sharing a report, the permissions do not cascade to related items like projects or tasks within that report. This is because reports are generated views and do not directly control object-level permissions. A report can be shared to allow a user to see data within the report, but it will not grant them inherited permissions to the underlying projects or tasks displayed in that report.
The vice president of operations asks one of their project managers to create a Workfront report that automatically sums columns so that it is similar to a Microsoft Excel file. The project manager decides to use a matrix grouping to show the data, but one of the columns isn't showing in the report.
What did the project manager forget to do?
Answer : A
In Adobe Workfront, a matrix report displays report data in a table format based on matrix groupings. When a report uses a matrix grouping, the values that appear in the matrix depend on whether the relevant columns are configured to be summarized. Adobe's documentation for creating a matrix report states that, in the Columns (View) tab, the user must select the column and use the Summarize this column by setting to choose an available summary option. Adobe specifically notes that if this option is not selected, the information from that column is not displayed correctly in the matrix report. This directly matches the scenario where one of the columns is not showing after the project manager created a matrix grouping. Text mode is not required just to make a standard matrix column appear, and conditional formatting only changes how values are visually styled. Therefore, the project manager forgot to summarize the columns, making the correct answer A.
=========
In the approval path shown below, which Project Status will the Project be if rejected?
Answer : A
In Adobe Workfront, an approval process can define what happens when an object is approved or rejected. The screenshot shows that the approval process starts when the project status is set to Requested, and the approval path includes an If rejected setting. In that setting, the displayed rejection status is Rejected. Adobe Workfront documentation explains that when an approval path has a rejection status configured, the rejected object moves to the selected rejection status. Adobe's approval-process documentation also notes that if the rejection status itself is associated with another approval process, the object can move into that status as pending approval; however, in this case, the visible selected rejection status is simply Rejected. The Requested status is the status that triggers the approval process, not the status after rejection. Current is a normal active project status and is not shown as the configured rejection result. Therefore, based on the approval path shown, the project status will be Rejected if the approval is rejected.
=========
A company has decided that all projects for the year need to be created from templates and staffed in the following quarter. The projects will need to remain in a backlog until the team has capacity to work on them. There has been confusion previously because the team used Planning status for all work not started.
What should the project manager do to help the team see the difference between work in the backlog versus work that is now being planned?
Answer : C
In Workfront, creating a custom status specifically for 'Backlog' allows the team to differentiate between work that is pending capacity and work that is actively being planned. This prevents confusion and allows for better project tracking, ensuring that tasks move smoothly from backlog to the planning phase when appropriate.
A portfolio manager has inadvertently given too much access to all the projects in their portfolio to Program Manager A.
How does the portfolio manager rectify the situation to ensure that Program Manager A has Manage access only on their own program?
Answer : C
In Workfront, when adjusting user access, it's important to ensure that Program Manager A only has the necessary level of access to their own program. To rectify the over-access issue, the portfolio manager must share the relevant program with Program Manager A with the correct Manage access and remove their broader Manage access to the portfolio. This restricts their control to only their specific program.