According to the web search results1, the timecard_admin role is the minimum role that is required to assign a time sheet policy to a user. A time sheet policy is a rule that controls the creation and operation of time sheets for resources who log time against work items. The timecard_admin role can create and modify time sheet policies, time sheet groups, and time sheet periods, as well as approve time sheets or submit time cards on behalf of team members. The other options are incorrect because:

A. ppm_admin: The ppm_admin role is a higher-level role that can access all Project and Portfolio Management modules and features, but it is not the minimum role required for assigning a time sheet policy to a user2.

C. it_project_manager: The it_project_manager role can create and manage projects, but not assign time sheet policies to users3.

D. It is not possible to assign a time sheet policy to a user: This is false, as it is possible to assign a time sheet policy to a user by using the Time Sheet Policy field on the User form4.

1: 3 2: https://docs.servicenow.com/bundle/vancouver-it-business-management/page/product/project-management/reference/r_Roles.html 3: https://docs.servicenow.com/bundle/vancouver-it-business-management/page/product/project-management/concept/c_ProjectManagement.html 4: https://docs.servicenow.com/bundle/vancouver-it-business-management/page/product/time-card-management/reference/r_TimeCardManagementRoles.html

According to the ServiceNow documentation1, the Idea [im_idea_core] table is a base table that is not extended from any other table. It stores information about ideas and their categories. The other options are incorrect because:

Task: The Task table is a base table that is extended by many other tables, such as Project, Demand, Incident, etc2.

Idea Modules: The Idea Modules table is a child table of the Idea [im_idea_core] table that defines the idea modules displayed on the Idea Portal3.

Project: The Project table is a child table of the Task table that stores information about projects.

1: https://docs.servicenow.com/bundle/vancouver-it-business-management/page/product/demand-management/reference/r_IdeaTable.html 2: https://docs.servicenow.com/bundle/vancouver-platform-administration/page/administer/table-administration/concept/c_TableHierarchy.html 3: https://docs.servicenow.com/bundle/vancouver-it-business-management/page/product/demand-management/reference/r_IdeaModulesTable.html : https://docs.servicenow.com/bundle/vancouver-it-business-management/page/product/project-management/reference/r_ProjectTable.html

According to the ServiceNow documentation1, the it_pps_admin role is the minimum role that has access to the Project Administration > Settings > Preferences-Project module. This role can configure the project preferences, such as the default project template, the default project currency, and the default project status. The other options are incorrect because:

A. it_program_manager: The it_program_manager role can create and manage programs, but not project preferences2.

B. sys_admin: The sys_admin role can access all modules and features on the platform, but it is not the minimum role required for the Project Administration > Settings > Preferences-Project module3.

C. it_project_manager: The it_project_manager role can create and manage projects, but not project preferences4.

1: https://docs.servicenow.com/bundle/vancouver-it-business-management/page/product/project-management/reference/r_Roles.html 2: https://docs.servicenow.com/bundle/vancouver-it-business-management/page/product/project-portfolio-management/concept/c_ProgramManagement.html 3: https://docs.servicenow.com/bundle/vancouver-platform-administration/page/administer/users-and-groups/concept/c_Roles.html 4: https://docs.servicenow.com/bundle/vancouver-it-business-management/page/product/project-management/concept/c_ProjectManagement.html

The Transition stage of the Now Create methodology includes the activities of Transition, Mobilize, Prepare and Conduct. This stage is focused on transitioning the solution from development to production, mobilizing the stakeholders for the go-live, preparing the environment and data for the launch, and conducting the final testing and validation. You can find more information about the Transition stage in the Now Create ebook or the Project Methodology website for ServiceNow.

According to the ServiceNow documentation1, the cost_plan_breakdown table stores the cost information for a specific fiscal period. This table contains the fields such as cost plan, fiscal period, amount, and currency. The other options are incorrect because:

B. pm_project: The pm_project table stores the information about projects, such as name, description, state, and status2.

C. cost_plan: The cost_plan table stores the information about cost plans, such as name, type, and project3.

D. expense_line: The expense_line table stores the information about expense lines, such as expense type, amount, and date4.

1: https://docs.servicenow.com/bundle/vancouver-it-business-management/page/product/project-management/reference/r_CostPlanBreakdownTable.html 2: https://docs.servicenow.com/bundle/vancouver-it-business-management/page/product/project-management/reference/r_ProjectTable.html 3: https://docs.servicenow.com/bundle/vancouver-it-business-management/page/product/project-management/reference/r_CostPlanTable.html 4: https://docs.servicenow.com/bundle/vancouver-it-business-management/page/product/project-management/reference/r_ExpenseLineTable.html

According to the ServiceNow documentation1, this property controls whether the start dates of the resource plan, cost plan, and benefit plan are automatically updated when the start date of the demand or project is changed. If this property is set to true, then the plans will be shifted by the same number of days as the demand or project start date change. If this property is set to false, then the plans will not be affected by the demand or project start date change.

1: https://docs.servicenow.com/bundle/vancouver-it-business-management/page/product/project-management/reference/r_Properties.html

According to the ServiceNow documentation1, a user’s availability is calculated as the ratio of allocated hours to total capacity, expressed as a percentage. Allocated hours are the hours that a user is assigned to work on a project or demand. Total capacity is the maximum number of hours that a user can work in a given period, based on their schedule and availability profile. A user’s availability indicates how much of their time is already allocated and how much is still available for new assignments.

1: https://docs.servicenow.com/bundle/vancouver-it-business-management/page/product/resource-management/concept/c_ResourceManagement.html

According to the ServiceNow support article1, the it_pps_admin role can configure the default columns in the project planning console by modifying the pm_project_planning_console list view. The admin role can also do this, as well as any other configuration on the platform2.

1: https://support.servicenow.com/kb?id=kb_article_view &sysparm_article=KB0714565 2: https://docs.servicenow.com/bundle/vancouver-platform-administration/page/administer/users-and-groups/concept/c_Roles.html

According to the Stakeholder Registry document, the combination of the user and the assigned portfolio must be unique when adding a user to the stakeholder registry. The stakeholder registry is a table that stores information about the stakeholders of a portfolio. The other options are not correct, as they are not registries that require a unique combination of user and portfolio. The application registry is a table that stores information about the applications in the system. The event registry is a table that stores information about the events that trigger notifications. The UX page registry is a table that stores information about the UX pages that are available for portfolios.

Cost Plans and Monetary Benefit Plans are the related lists that should primarily be used to capture financial data in a project. Cost Plans allow you to define the expected costs of a project over time, based on the planned and actual work, resources, and expenses. Monetary Benefit Plans allow you to define the expected financial benefits of a project over time, based on the estimated and realized value, revenue, and savings. You can find more information about these related lists in the Product Documentation for ServiceNow.

According to the ServiceNow documentation1, when requesting resources from a group and when resource role is specified, the planned cost is calculated from the hourly rate of the specified role. The system uses the rate card associated with the resource plan to determine the hourly rate for each role. The other options are incorrect because:

A. The distribution costs: The distribution costs are the costs that are distributed across the project tasks based on the resource plan allocation2.

B. The task rate cards: The task rate cards are the rate cards that are applied to the project tasks, not the resource plan3.

D. The CI rate cards: The CI rate cards are the rate cards that are applied to the configuration items, not the resource plan4.

1: https://docs.servicenow.com/bundle/vancouver-it-business-management/page/product/resource-management/concept/c_ResourcePlans.html 2: https://docs.servicenow.com/bundle/vancouver-it-business-management/page/product/resource-management/concept/c_DistributionCosts.html 3: https://docs.servicenow.com/bundle/vancouver-it-business-management/page/product/resource-management/concept/c_TaskRateCards.html 4: https://docs.servicenow.com/bundle/vancouver-it-business-management/page/product/resource-management/concept/c_CIRateCards.html

According to the ServiceNow Resource Management document, users with the pps_resource role can be considered for resource planning, as this role grants access to the Resource Management application and allows the users to view and update their resource allocations. The other options are not correct, as they are not roles that are related to resource planning. The it_project_user role grants access to the Project Portfolio Management application and allows the users to create and update projects. The it_user role grants access to the IT Service Management application and allows the users to manage incidents, problems, and changes. The it_pps_user role grants access to the Project Portfolio Suite application and allows the users to manage portfolios, programs, and projects.

According to the Planning Console document, if the ‘Move project for WIP projects’ property is enabled, project tasks associated with the project are also moved, except for tasks in the Work in Progress or Closed states. The other options are not correct, as tasks in the Pending or Open states are moved along with the project.

The Project Management application supports two types of external dependencies: hard dependency and soft dependency. A hard dependency is a dependency that must be met before a task can start or finish. A soft dependency is a dependency that is preferred but not mandatory for a task to start or finish. You can find more information about these dependency types in the Product Documentation for ServiceNow.