CIS-SPM Sample Questions Answers

According to the ServiceNow documentation1, a demand manager can view and edit the following artifacts from a demand:

Decision: A decision that affects the demand or its outcome2.

Risk: A risk that could impact the demand or its outcome3.

Requirement: A requirement that defines the scope or functionality of the demand4.

The other options are not artifacts of a demand, but rather related entities that can be created from a demand or linked to a demand.

1: https://docs.servicenow.com/bundle/vancouver-it-business-management/page/product/demand-management/concept/c_DemandManagement.html 2: https://docs.servicenow.com/bundle/vancouver-it-business-management/page/product/demand-management/task/t_CreateADecision.html 3: https://docs.servicenow.com/bundle/vancouver-it-business-management/page/product/demand-management/task/t_CreateARisk.html 4: https://docs.servicenow.com/bundle/vancouver-it-business-management/page/product/demand-management/task/t_CreateARequirement.html

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.

A resource event is a non-scheduled activity that affects the availability and capacity of a resource or a group of resources. Examples of resource events are vacations, holidays, training, or sick leave. Resource events can be created by resource managers or resources themselves, and they can be viewed in the resource calendar or the resource workbench. You can find more information about resource events in the Product Documentation for ServiceNow.

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 ServiceNow documentation1, the color band at the top of the project card in Project Workspace displays the project status. The project status is a calculated field that indicates the health of the project based on the schedule, cost, and scope variance. The color band can be green, yellow, or red, depending on the status value. The other options are incorrect because:

B. Risk: The risk is a potential problem that could affect the project or its outcome. The risk level is displayed as a circle icon on the project card, not as a color band2.

C. State: The state is the current phase of the project, such as Draft, Planning, Work in Progress, or Closed. The state is displayed as a text field on the project card, not as a color band3.

D. Issues: The issues are the actual problems that affect the project or its outcome. The number of issues is displayed as a badge icon on the project card, not as a color band4.

1: https://docs.servicenow.com/bundle/vancouver-it-business-management/page/product/project-management/concept/c_ProjectWorkspace.html 2: https://docs.servicenow.com/bundle/vancouver-it-business-management/page/product/project-management/task/t_CreateARisk.html 3: https://docs.servicenow.com/bundle/vancouver-it-business-management/page/product/project-management/reference/r_ProjectTable.html 4: https://docs.servicenow.com/bundle/vancouver-it-business-management/page/product/project-management/task/t_CreateAnIssue.html

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.

According to the Completing Demand Assessments document, demand assessments are triggered as soon as the demand enters the Submitted state. The other options are not correct, as demand assessments are not triggered when the demand is Approved, Screening, or Qualified.

According to the RIDAC (Risk, Issue, Decision, Action, and Request Changes) record entries for a project document, the RIDAC workflow can be modified by using the Workflow Editor, which is a graphical tool that allows you to create and edit workflows. The other options are not correct, as they are not recommended features for modifying the RIDAC workflow. The Project Form is used to create and update project records. The Flow Designer is used to automate processes without coding. The Service Catalog is used to order items and services.

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 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 Assigning Resource Roles document, you define ‘Roles’ requested via resource plans under resource roles in the Resource Management application. Resource roles are the roles that users can request or allocate for resource plans. The other options are not correct, as they are not the places where you define ‘Roles’ requested via resource plans. The system roles are the roles that grant access to various applications and modules in the system. The roles under system security are the roles that control the security settings and permissions for the system. The skill management modules are the modules that manage the skills and skill levels of users and groups.

According to the Product Documentation for ServiceNow, the business stakeholder role (rm_business_stakeholder) can read and retrieve data from any table of the Release Management application to generate reports. This role can also view the release dashboard, release calendar, and release roadmap. The other roles have different levels of access and permissions for the Release Management application. You can find more information about the roles and responsibilities for Release Management in the Product Documentation for ServiceNow.

According to the ServiceNow documentation1, the pm_home_page_config table is used to configure the parameters displayed on a project card on the My Projects Space page of the Project Workspace. The other tables are used for different purposes:

pm_project: Stores information about projects2.

pm_toplevel_project: Stores information about top-level projects3.

project_template_config: Stores information about project templates.