Pass the ServiceNow CIS-Strategic Portfolio Management CIS-SPM Questions and answers with CertsForce

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

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

If an it_project_manager does not want to equally distribute hours across the resource plan time frame, the allocation spread should be set to Any. This option allows the it_project_manager to manually enter the hours for each month or quarter in the resource plan. The other options (Even, Back Load, and Front Load) automatically distribute the hours evenly, from the end, or from the start of the time frame, respectively. You can find more information about the allocation spread in the Product Documentation for ServiceNow.

Resource capacity is the total number of hours that a resource or a group of resources is available for work in a given time period. According to the Product Documentation for ServiceNow, resource capacity is derived from the user or group schedule, which defines the working hours and days for each resource. The group capacity is rolled up from the schedules of all the members. Note: Capacity is not derived from FTE, but from schedules. Both FTE and schedules must be in synchronization with each other. FTE is a measure of how much work a resource can perform in a standard work week, and it is used to calculate the resource demand and allocation.

The demand workbench is a feature of ServiceNow Demand Management that allows you to view and assess business demands in a single place. You can use the demand workbench to compare demands with portfolios and see how they align with your strategic goals and objectives. You can also use the demand workbench to compare and prioritize demands against other demands based on their scores, risks, and benefits. You can find more information about the demand workbench in the Product Documentation for ServiceNow.

A checklist item record provides a name and a complete field. The name field is the label of the checklist item, and the complete field is a checkbox that indicates whether the checklist item is done or not. You can find more information about checklist items in the Product Documentation for ServiceNow.

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