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

According to the Category Configuration document, the default table that stores the idea categories that a user can select from when submitting an idea is im_category. This table contains the predefined categories for ideas, such as Business Process, Customer Service, or IT Service. The other options are not correct, as they are not the tables that store the idea categories. The dmn_demand table stores the demand records that are created from the approved ideas. The im_module table stores the idea modules that are used to group ideas by different criteria. The im_idea_core table stores the core fields of the idea records.

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: 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-portfolio-management/concept/c_PortfolioWorkbench.html 3: https://docs.servicenow.com/bundle/vancouver-it-business-management/page/product/it-business-management/concept/c_Lens.html : https://docs.servicenow.com/bundle/vancouver-it-business-management/page/product/demand-management/concept/c_DemandWorkbench.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.

The project status report allows project managers to do the following:

Show historical trend of project KPI’s: The project status report displays the key performance indicators (KPIs) of the project, such as schedule variance, cost variance, and earned value. It also shows the historical trend of these KPIs over time, which helps project managers monitor the progress and performance of the project. You can find more information about the project status report KPIs in the Product Documentation for ServiceNow.

Print as a PDF attachment: The project status report can be printed as a PDF attachment and sent to the stakeholders or sponsors of the project. This helps project managers communicate the status and health of the project in a clear and concise format. You can find more information about the project status report PDF attachment in the Product Documentation for ServiceNow.

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 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 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 Portfolio Planning document, the first step in the process when configuring Portfolio Planning to work with ServiceNow® Project Portfolio Management is to generate default mapping configurations. This step creates the default mappings between the Portfolio Planning fields and the ServiceNow® Project Portfolio Management fields. The other options are not correct, as they are not the first step in the process. Creating an alignment integration is the second step, creating custom mapping configurations is the third step, and creating personalized portfolio plans is the fourth step.