Free CIS-SPM Practice Test

In the ServiceNow Demand Management lifecycle, assessments are sent to stakeholders during the Screening state. After a demand is submitted, it enters the Screening state, where a demand manager performs an initial review. To gather essential information regarding the demand's value, risk, size, and strategic alignment, the manager triggers assessments (metric-based surveys) to be sent to relevant stakeholders. The responses from these assessments are then used to score the demand and determine if it should be qualified for further evaluation and potential approval.

A. Creation: Assessments are not sent during the Creation (or Draft) state, as the demand has not yet been formally submitted for review.
B. Assessment: While the activity is "assessment," it is not a formal state in the standard Demand Management lifecycle. The state in which this activity is initiated is "Screening."
C. Planning: Planning is not a state within the Demand Management lifecycle. It is a phase that occurs after a demand has been approved and converted into a project or another work item.

1. ServiceNow Product Documentation - Demand states: The official documentation outlines the base system states for a demand. It lists "Screening" as the state following "Submitted," where the initial evaluation occurs. The states are: Draft, Submitted, Screening, Qualified, Approved, Completed, and Deferred.

Source: ServiceNow Product Documentation, "Demand states," Utah Release.

2. ServiceNow Product Documentation - Screen a demand: This document explicitly states the role of assessments in the Screening state. "During the Screening state, the demand manager and stakeholders collaborate to add details to the demand. The demand manager can request stakeholders to complete their assessments."

Source: ServiceNow Product Documentation, "Screen a demand," Utah Release.

3. ServiceNow Product Documentation - Demand Management: The overview of the Demand Management process confirms this workflow. "When a demand is in the Screening state, you can create assessments to send to stakeholders to gather information for demand qualification."

Source: ServiceNow Product Documentation, "Demand Management," Utah Release.

In the ServiceNow Strategic Portfolio Management (SPM) data model, a clear hierarchy exists. A portfolio is a high-level container used to group related programs, projects, and demands to align with and achieve strategic business objectives. A program, in turn, is a container for a group of related projects and demands. Programs can have their own associated records such as program tasks, issues, risks, and cost plans to manage program-level work and governance. Therefore, a program is contained within a portfolio, not the other way around.

A. Program tasks: A program can contain its own tasks to manage work that is specific to the program level and not part of any single underlying project.
B. Issues: Issues can be logged and managed directly against a program to track obstacles or problems that affect the entire program's delivery.
C. Cost plans: Programs have their own budgets and financial tracking. Cost plans are used at the program level to manage and monitor planned versus actual costs.

1. ServiceNow Product Documentation: Program Management. On the Program form, the related lists explicitly include Program Tasks, Issues, Risks, Cost Plans, and Benefit Plans, demonstrating these are components of a program. The documentation states, "A program is a group of related projects and demands..."

2. ServiceNow Product Documentation: Portfolio Management. This documentation defines a portfolio as "a collection of demands and projects managed as a group to achieve strategic and operational objectives." It further clarifies that you can "group related programs in a portfolio," establishing that portfolios contain programs.

3. ServiceNow Product Documentation: Program form in Strategic Portfolio Management. This page details the fields and related lists on the standard program form. The "Financials" tab contains Cost Plans, and other related lists include Issues and Program Tasks, confirming they are child records of a program.

The costplanbreakdown table stores the time-phased distribution of a cost plan. When a cost plan is created for a project or demand, the system automatically generates records in this table, breaking down the total planned cost into specific fiscal periods (e.g., months, quarters). Each record in the costplanbreakdown table represents the planned cost for one fiscal period, enabling detailed financial planning, tracking, and reporting over the duration of the project.

B. pmproject: This table contains the primary project record and its summary fields, not the detailed, period-specific cost breakdowns.
C. costplan: This table stores the overall cost plan header information, such as the total cost and duration, but not the breakdown by individual fiscal periods.
D. expenseline: This table is used to record actual costs (expenses) as they are incurred, not the planned cost information for a fiscal period.

1. ServiceNow Product Documentation - Project cost plan breakdowns: "Cost plan breakdowns are created when you create a cost plan. A cost plan breakdown is a record in the Cost Plan Breakdown [costplanbreakdown] table. The cost plan breakdown stores the planned cost for a specific fiscal period."

2. ServiceNow Product Documentation - Cost management tables: This document outlines the key tables for cost management. It defines the costplanbreakdown table as storing "the breakdown of the cost plan by fiscal period." It also defines costplan as the table for the overall plan and expenseline for actual expenses.

When creating a resource plan to request resources for a project or demand, the form includes a field to specify how the effort is measured. This field, labeled "Request type" on the Resource Plan form, dictates the unit for the requested and allocated time. The out-of-the-box options available for this field are Person days, Hours, and FTE (Full-Time Equivalent). These selections determine the unit of measurement used for planning, requesting, and allocating resource capacity throughout the resource management lifecycle.

B. Group: This identifies a type of resource to be requested (i.e., a group of individuals with a specific skill), not a unit for measuring the amount of effort.
D. Weekly on weekdays: This describes a distribution schedule or pattern for how allocated effort is spread over time, not the fundamental unit of measurement for the effort itself.

1. ServiceNow Product Documentation - Create a resource plan: The official documentation details the fields on the Resource Plan form. It explicitly lists the options for the "Request type" field.

Reference: ServiceNow Product Documentation, "Resource plan form fields". In the table describing the form fields, the entry for "Request type" states, "Select the unit for requested or allocated hours. The options are Hours, FTE, or Person Days."

The Compare Baselines page within the new Project Workspace is the designated feature for analyzing financial performance over time. It allows a project manager to take a snapshot of the initial plan (the baseline) and compare it against the current planned costs, actuals, and forecasts. This comparison is presented in a time-phased grid, enabling a clear month-over-month analysis of variances between the original budget and the latest financial data, which is the exact requirement stated in the question.

A. Using the Cost plan breakdown form: This form displays the detailed fiscal period breakdown for a single cost plan, not a comparison between the current plan and a historical baseline.
B. Using the Financials Cost page: This page provides a summary of the project's current cost plans and actuals but does not offer the specific functionality to compare these against a saved baseline.
D. Using the project Details page: This page shows high-level project attributes, status, and metadata. It does not contain detailed financial comparison tools or time-phased cost data. ---

1. ServiceNow Product Documentation: Compare project baselines in Project Workspace. This document explicitly states, "Compare the current cost and benefit plan values of your project with a selected baseline to view the variance... The comparison is shown in a time-phased grid for the selected fiscal period." This directly supports the use of the Compare Baselines page for month-over-month comparison.

2. ServiceNow Product Documentation: Financial planning for projects and demands in Project Workspace. This guide details the financial management capabilities within the workspace, highlighting the "Compare Baselines" action as the method for tracking performance against the original plan.

3. ServiceNow Product Documentation: Create a project baseline in Project Workspace. This document defines a baseline as "a snapshot of the project's cost plan, benefit plan, and all the planned dates... at a specific point in time." This confirms that the "initial planned costs" are stored in a baseline, which is then used for comparison.

The Stakeholder Registry is a feature within ServiceNow Strategic Portfolio Management (SPM) used to identify and manage stakeholders for portfolios, programs, and demands. When adding a user to a specific portfolio as a stakeholder, the system enforces a uniqueness constraint. This means a single user can only be associated with a particular portfolio once within the registry. This prevents redundant entries and ensures clear, accurate tracking of stakeholder roles and responsibilities for each strategic entity.

A. Application Registry: This registry is part of Application Portfolio Management (APM) and tracks business applications, not the relationship between users and portfolios.
B. Event Registry: This is a core platform feature for defining and processing system events; it is not related to SPM portfolio or stakeholder management.
C. UX Page Registry: This is part of the Now Experience UI Framework and is used to register and define properties for user interface pages, not for managing user data.

1. ServiceNow Product Documentation: "Stakeholder Register". This document outlines the purpose of the stakeholder register, which is to "associate them [stakeholders] with a portfolio, program, or demand." The inherent function of this registry requires a unique association between a user and the entity (e.g., portfolio) they are a stakeholder for. See: Strategic Portfolio Management > Portfolio Planning > Stakeholder Register.

2. ServiceNow Product Documentation: "Add a stakeholder to the stakeholder register". The procedure for adding a stakeholder involves selecting a 'User' and a 'Portfolio' (or other parent entity). The underlying table, spmstakeholderregister, is designed with a unique index on the combination of the user and the parent record to maintain data integrity. See: Strategic Portfolio Management > Portfolio Planning > Stakeholder Register > Add a stakeholder to the stakeholder register.

The out-of-the-box (OOTB) processes for RIDAC items (Risks, Issues, Decisions, Actions, and Changes) within ServiceNow Strategic Portfolio Management are implemented as classic workflows. The standard and recommended tool for modifying these existing, state-based processes is the Workflow Editor. It provides a graphical canvas to configure the activities, transitions, and conditions that govern the lifecycle of RIDAC records. While Flow Designer is the modern tool for automation, the legacy RIDAC processes are maintained through the Workflow Editor.

B. Project Form: The form is a user interface for viewing and editing data on a specific record; it does not control the underlying process logic or state model.
C. Flow Designer: While a powerful automation tool, the standard OOTB RIDAC processes are not built with Flow Designer; they use the classic Workflow Editor for process management.
D. Service Catalog: The Service Catalog is an application for ordering products and services. It is unrelated to configuring the backend workflows for project management records.

1. ServiceNow Product Documentation - Workflow Editor: "The Workflow Editor is a graphical user interface for creating, editing, and managing workflows." This documentation establishes the Workflow Editor as the primary tool for managing classic workflows, which are used by the RIDAC processes. (ServiceNow Product Documentation, "Workflow Editor," Quebec release and later).

2. ServiceNow Product Documentation - Project Management: The documentation for managing project artifacts like issues and risks describes their state models (e.g., Open, Work in Progress, Closed). These state models are controlled by underlying business rules and workflows. The documentation implicitly points to the use of classic platform features like Workflow Editor for customization. (ServiceNow Product Documentation, "Manage project issues," Utah release and later).

The question asks for an allocation spread to use when hours should not be distributed equally. ServiceNow Resource Management provides specific allocation types for resource plans. The 'Even' spread distributes hours equally across the plan's duration. To achieve an unequal distribution, the project manager must choose either 'Front Load,' which allocates more hours at the beginning of the plan, or 'Back Load,' which allocates more hours toward the end. Both options fulfill the stated requirement of not distributing hours equally.

A. Even: This option directly contradicts the requirement, as it is designed specifically to distribute hours equally over the time frame.
B. Any: This is not a valid, configurable allocation spread type within the ServiceNow platform. While conceptually the project manager could use "any" of the non-even methods, it is not a selectable option.

1. ServiceNow Product Documentation - Create a resource plan: "The allocation type for the resource plan.

Even load: Distributes the allocated hours evenly across the duration of the resource plan.

Front load: Allocates more hours at the beginning of the resource plan.

Back load: Allocates more hours at the end of the resource plan."

This documentation explicitly lists 'Front Load' and 'Back Load' as the methods for non-even distribution.

2. ServiceNow Product Documentation - Resource allocation: "You can allocate resources to a project or a demand by creating a resource plan. You can also modify the resource plan to change the allocation of resources... The allocation type for the resource plan: Even load, Front load, or Back load."

This confirms the specific, limited set of allocation types available, from which 'Front Load' and 'Back Load' are the only non-even options.

The 'Cost type' field on the Cost Plan [costplan] record is the designated attribute used to classify planned expenses as either Capital Expenditure (Capex) or Operational Expenditure (Opex). This classification is crucial for financial planning, budgeting, and reporting on projects and demands. When a cost plan is created, the user explicitly selects 'Capex' or 'Opex' from this field to determine how the associated costs will be treated from an accounting perspective, directly influencing financial summaries and portfolio-level reporting.

A. Resource plan (resourceplan): A resource plan details labor requirements and associated costs, but the Capex/Opex classification is set on the cost plan itself, not the resource plan record.
B. Currency type (currency.type): This field defines the monetary unit for the cost (e.g., USD, EUR) and has no bearing on its financial classification as Capex or Opex.
C. Resource category (resourcecategory): This field is used to group resources by function or skill (e.g., Developer, Analyst) and is not related to the accounting treatment of costs.

1. ServiceNow Product Documentation - Create a cost plan in Project Workspace: In the table describing the fields on the Cost Plan form, the "Cost type" field is defined. The documentation states, "Select the cost type for the cost plan, either Capex or Opex." This directly confirms that the 'Cost type' field serves this specific purpose. (ServiceNow Product Documentation for Strategic Portfolio Management, "Project Financials in Project Workspace", Section: "Create a cost plan in Project Workspace").

2. ServiceNow Product Documentation - Cost Plan fields: The official documentation for the Cost Plan [costplan] table lists the "Cost type" (field name: costtype) with choices 'Capex' and 'Opex'. This confirms it is the standard field for this classification. (ServiceNow Product Documentation, "Tables and Columns", costplan table schema details).

ServiceNow Resource Management determines a user's schedule based on a specific order of precedence. When a schedule is not explicitly defined on the user record—neither in the 'Schedules' related list nor in the 'Schedule' field—the system falls back to a predefined system property. The com.snc.resourcemanagement.defaultschedule property specifies the name of the schedule to be used as the default for any resource without an assigned schedule. This ensures that all resources have a defined schedule for accurate capacity and availability calculations.

B. Effort type (FTE or Person Days) is used for calculating and planning effort, not for defining a resource's working days and hours.
C. While Project Management uses schedules, the specific fallback mechanism for a resource without a schedule is governed by a Resource Management property, not a generic "Project Management Schedule".
D. This property defines the number of hours in a standard workday for FTE calculations, but it does not define the entire schedule (e.g., which days are workdays, holidays).

1. ServiceNow Product Documentation: Resource Management properties. The documentation lists the property com.snc.resourcemanagement.defaultschedule and its description: "Name of the schedule to be used for a resource if the resource does not have any schedule associated."

2. ServiceNow Product Documentation: Resource schedules. This document outlines the order of precedence for deriving a resource's schedule: "The resource schedule is derived in the following order of precedence: 1. Schedules in the Schedules related list on the User form. 2. Schedule in the Schedule field on the User form. 3. Schedule specified in the resource management property: Default Schedule Name (com.snc.resourcemanagement.defaultschedule)."