ServiceNow CIS-SPM Certified Implementation Specialist - Strategic Portfolio Management Exam Practice Test

 According to the Create a customer project from a demand document, when creating a project from demand, the resource plan and the cost plan are moved and copied upon project creation. The resource plan defines the resources required for the project, and the cost plan defines the estimated and actual costs for the project. The other options are not correct, as they are not related records that are moved and copied upon project creation. The change requests, the idea, and the demand are not moved or copied to the project, but they are linked to the project as references. The assessment is not a record that is associated with the project, but with the demand.

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 Business Unit field on a Project or Demand form is a reference field that displays values from the cmn_department table. A reference field stores a link to a record on another table, rather than storing the data directly in the field2.

1:

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 baseline is a data copy of the current project’s task, schedule, or structure that can be used for comparison reporting later. A baseline captures the original plan of the project and allows you to track the changes and deviations from the plan over time. You can create multiple baselines for a project and compare them with the current state of the project. You can find more information about baselines in the Product Documentation for ServiceNow.

According to the ServiceNow documentation1, a rate card is a table that defines the hourly cost of labor for different roles or resources. A project rate is a fixed rate that is applied to all resources assigned to a project, regardless of their roles or individual rates. Both of these can be used to calculate the planned cost of a resource plan by multiplying the hours allocated to each resource by the corresponding rate. The other options are incorrect because:

A. Demand rate: A demand rate is a rate that is applied to a demand, not a resource plan. It is used to estimate the cost of fulfilling a demand before it is converted into a project2.

C. Default rate: A default rate is a rate that is applied to a resource when no other rate is specified. It is not a valid option for calculating the planned cost of a resource plan, as it is only used as a fallback option3.

1:

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:

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:

 According to the Demand Workbench document, the role that can configure the parameters of the demand workbench that is provided with the base system is it_pps_admin. This role grants access to the Project Portfolio Suite application and allows the user to configure the demand workbench settings, such as the axes, the quadrants, the bubble size, and the color. The other options are not correct, as they are not roles that can configure the parameters of the demand workbench. The all roles option is too broad and does not specify a particular role. The business_stakeholder role grants access to the Business Stakeholder Portal and allows the user to view and submit demands. The it_project_manager role grants access to the Project Portfolio Management application and allows the user to create and update projects.

According to the ServiceNow documentation1, the Project Workspace is a central location for creating and managing projects. It provides a graphical interface that allows users to view and edit project information, such as tasks, resources, risks, issues, and dependencies. The Project Workspace also enables users to collaborate with team members and stakeholders, track project progress, and generate reports.

The other options are incorrect because:

A. A central location to view of all projects in a portfolio to prioritize work: This describes the Portfolio Workbench, not the Project Workspace2.

C. A central location transform the navigation of lists and forms into an interactive graphical experience: This describes the Lens, not the Project Workspace3.

D. A central location for viewing and assessing business demands: This describes the Demand Workbench, not the Project Workspace.

1: :

According to the ServiceNow documentation1, the project property to update actual effort from time card is controlled at the project level. This property is called Update actual effort from time card and it determines if the Actual effort field on the Dates tab should be updated based on the hours entered from time cards for the project. If set to Yes, the Actual effort field is read-only on the Project and Project Task forms. If set to No, the Actual effort field is editable on the Project and Project Task forms.

1:

According to the ServiceNow documentation1, a lens is a hierarchical structure that consists of entities and relationships. An entity is a data object that represents a business concept, such as a project, a demand, or a resource. A relationship is a link between two entities that defines how they are connected. A lens can have up to four levels of entities, each with a parent reference to the entity above it, except for the top-level entity, which has no parent reference. The top-level entity is the root of the lens and defines its scope and type. For example, a project lens has a project as the top-level entity, and a demand lens has a demand as the top-level entity.

1:

According to the Planning Console document, an it_project_manager can convert a task to a milestone by right-clicking on the task in the Planning Console and selecting Convert to Milestone. The other options are not correct, as they are not the ways to convert a task to a milestone. A system admin or a PPS admin role is not required for this action. The task assignment is not relevant for this action.

According to the Innovation Management document, the plugin that activates the Ideas module to gather and evaluate ideas efficiently, and quickly identify ideas for implementation is Ideation with PPM. This plugin enables the Innovation Management application, which allows organizations and employees to collect, vote on, manage, and collaborate on ideas from a centralized location. The other options are not correct, as they are not plugins that activate the Ideas module. Test Management 2.0 is a plugin that enables the Test Management 2.0 application, which allows users to create, plan, and execute tests. Agile Development 2.0 is a plugin that enables the Agile Development 2.0 application, which allows users to manage scrum or development work throughout the lifecycle. Resource Management is a plugin that enables the Resource Management application, which allows users to manage resource plans and allocations.

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

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.