Free ServiceNow CIS-SPM Practice Exam with Questions & Answers | Set: 2

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.

the default project template configuration records available in the Template Config module are Project task, Project, and Project template. These records define the fields and values that are copied from the template to the project when a project is created from a template. The other options are incorrect because:

B. Project subtask: Project subtask is not a valid record in the Template Config module, as it is a child of the Project task record2.

D. Task: Task is not a valid record in the Template Config module, as it is a parent of the Project task record3.

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

According to the Using rate types and labor rate cards document, a user can choose from multiple rate types for their work, while logging a time card, only if the capability is enabled in the Time Sheet Policies. This capability allows users to select different rate types for different tasks, such as standard, overtime, or travel. The other options are not correct, as they are not the places where the capability can be enabled. The Project Record is used to create and update project details, such as name, description, and state. The Project Preferences are used to set the default values for project fields, such as number, type, and priority. The option C is not correct, as more than one rate type can apply if the capability is enabled.

According to the ServiceNow documentation1, the it_program_manager role is needed to group related projects and demands. This role can create and manage programs, which are containers for projects and demands that share a common goal or objective. The other options are incorrect because:

B. it_project_manager: The it_project_manager role can create and manage projects, but not group them into programs2.

C. it_demand_manager: The it_demand_manager role can create and manage demands, but not group them into programs3.

D. it_project_user: The it_project_user role can view and edit project tasks, but not create or manage projects, demands, or programs4.

1: https://docs.servicenow.com/bundle/vancouver-it-business-management/page/product/project-portfolio-management/concept/c_ProgramManagement.html 2: https://docs.servicenow.com/bundle/vancouver-it-business-management/page/product/project-management/concept/c_ProjectManagement.html 3: https://docs.servicenow.com/bundle/vancouver-it-business-management/page/product/demand-management/concept/c_DemandManagement.html 4: https://docs.servicenow.com/bundle/vancouver-it-business-management/page/product/project-management/reference/r_Roles.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, 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

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.

According to the Assigning Resource Roles document, to set up a group for selection in a resource plan, the group record needs to include the pps_resource role. This role grants access to the Resource Management application and allows the group members to view and update their resource allocations. The other options are not correct, as they are not required for a group to be selected in a resource plan. The it_project_user role grants access to the Project Portfolio Management application and allows the user to create and update projects. The itil role grants access to the ITIL application and allows the user to manage incidents, problems, and changes. The resource_manager role grants access to the Resource Management application and allows the user to manage resource plans and allocations.