CIS-SPM: Certified Implementation Specialist - Strategic Portfolio Management

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:12: https://docs.servicenow.com/bundle/vancouver-it-business-management/page/product/project-management/reference/r_ProjectTaskTable.html3: https://docs.servicenow.com/bundle/vancouver-platform-administration/page/administer/table-administration/concept/c_TableHierarchy.html

According to thePortfolio Planningdocument, 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.

According to theServiceNow Resource Managementdocument, users with the pps_resource role can be considered for resource planning, as this role grants access to the Resource Management application and allows the users to view and update their resource allocations. The other options are not correct, as they are not roles that are related to resource planning. The it_project_user role grants access to the Project Portfolio Management application and allows the users to create and update projects. The it_user role grants access to the IT Service Management application and allows the users to manage incidents, problems, and changes. The it_pps_user role grants access to the Project Portfolio Suite application and allows the users to manage portfolios, programs, and projects.

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.

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 theNow Create ebookor theProject Methodology websitefor ServiceNow.

According to theProject Expense Linesdocument, a project expense line is cost associated with a specific source, such as fixed assets, resource, or software. The program field on the project expense line form is not a source of cost, but a reference to the program that the project belongs to. Therefore, the correct answer is B. Program. The other options are not correct, as they are sources of cost for a project expense line.

According to theStakeholder Registrydocument, the combination of the user and the assigned portfolio must be unique when adding a user to the stakeholder registry. The stakeholder registry is a table that stores information about the stakeholders of a portfolio. The other options are not correct, as they are not registries that require a unique combination of user and portfolio. The application registry is a table that stores information about the applications in the system. The event registry is a table that stores information about the events that trigger notifications. The UX page registry is a table that stores information about the UX pages that are available for portfolios.