ServiceNow CIS-SPM Practice Test - Questions Answers

According to the ServiceNow documentation1, the it_pps_admin role is the minimum role that has access to the Project Administration > Settings > Preferences-Project module. This role can configure the project preferences, such as the default project template, the default project currency, and the default project status. The other options are incorrect because:

A)it_program_manager: The it_program_manager role can create and manage programs, but not project preferences2.

B)sys_admin: The sys_admin role can access all modules and features on the platform, but it is not the minimum role required for the Project Administration > Settings > Preferences-Project module3.

C)it_project_manager: The it_project_manager role can create and manage projects, but not project preferences4.

1: https://docs.servicenow.com/bundle/vancouver-it-business-management/page/product/project-management/reference/r_Roles.html2: https://docs.servicenow.com/bundle/vancouver-it-business-management/page/product/project-portfolio-management/concept/c_ProgramManagement.html3: https://docs.servicenow.com/bundle/vancouver-platform-administration/page/administer/users-and-groups/concept/c_Roles.html4: https://docs.servicenow.com/bundle/vancouver-it-business-management/page/product/project-management/concept/c_ProjectManagement.html

According to the ServiceNow documentation1, the it_program_manager role is needed to group related projects and demands. This role can create and manage programs, which are containers for projects and demands that share a common goal or objective. The other options are incorrect because:

B)it_project_manager: The it_project_manager role can create and manage projects, but not group them into programs2.

C)it_demand_manager: The it_demand_manager role can create and manage demands, but not group them into programs3.

D)it_project_user: The it_project_user role can view and edit project tasks, but not create or manage projects, demands, or programs4.

1: https://docs.servicenow.com/bundle/vancouver-it-business-management/page/product/project-portfolio-management/concept/c_ProgramManagement.html2: https://docs.servicenow.com/bundle/vancouver-it-business-management/page/product/project-management/concept/c_ProjectManagement.html3: https://docs.servicenow.com/bundle/vancouver-it-business-management/page/product/demand-management/concept/c_DemandManagement.html4: https://docs.servicenow.com/bundle/vancouver-it-business-management/page/product/project-management/reference/r_Roles.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 theScenario Planning for PPMdocument, a portfolio manager can access the Portfolio Planning Workbench by navigating to either the Portfolio Planning related link on the portfolio form or the Portfolio Planning Workbench module under the Portfolio Planning application menu. The other options are not correct, as they do not lead to the Portfolio Planning Workbench. The Project module is under the Project Portfolio Management application menu and the Program Workbench is under the Program Management application menu.

According to theRIDAC (Risk, Issue, Decision, Action, and Request Changes) record entries for a projectdocument, 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 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.

According to theUsing the Demand Workbenchdocument, if a user creates a new demand from the demand workbench, the system saves the record in the qualified state and displays it on the bubble chart. The other options are not correct, as they are not the default state for a new demand created from the demand workbench. The approved state is the final state for a demand that has passed all the assessments. The open state is the initial state for a demand that is created from the Service Catalog. The draft state is the state for a demand that is created from the Demand form.

It is not possible to assign a time sheet policy to a user: This is false, as it is possible to assign a time sheet policy to a user by using the Time Sheet Policy field on the User form4. 1:32: https://docs.servicenow.com/bundle/vancouver-it-business-management/page/product/project-management/reference/r_Roles.html3: https://docs.servicenow.com/bundle/vancouver-it-business-management/page/product/project-management/concept/c_ProjectManagement.html4: https://docs.servicenow.com/bundle/vancouver-it-business-management/page/product/time-card-management/reference/r_TimeCardManagementRoles.html

According to the web search results1, the timecard_admin role is the minimum role that is required to assign a time sheet policy to a user. A time sheet policy is a rule that controls the creation and operation of time sheets for resources who log time against work items. The timecard_admin role can create and modify time sheet policies, time sheet groups, and time sheet periods, as well as approve time sheets or submit time cards on behalf of team members. The other options are incorrect because:

A)ppm_admin: The ppm_admin role is a higher-level role that can access all Project and Portfolio Management modules and features, but it is not the minimum role required for assigning a time sheet policy to a user2.

C)it_project_manager: The it_project_manager role can create and manage projects, but not assign time sheet policies to users3.