ServiceNow CIS-SPM Practice Test - Questions Answers, Page 6

According to the ServiceNow documentation1, a demand manager can view and edit the following artifacts from a demand:

Decision: A decision that affects the demand or its outcome2.

Risk: A risk that could impact the demand or its outcome3.

Requirement: A requirement that defines the scope or functionality of the demand4.

The other options are not artifacts of a demand, but rather related entities that can be created from a demand or linked to a demand.

1: https://docs.servicenow.com/bundle/vancouver-it-business-management/page/product/demand-management/concept/c_DemandManagement.html2: https://docs.servicenow.com/bundle/vancouver-it-business-management/page/product/demand-management/task/t_CreateADecision.html3: https://docs.servicenow.com/bundle/vancouver-it-business-management/page/product/demand-management/task/t_CreateARisk.html4: https://docs.servicenow.com/bundle/vancouver-it-business-management/page/product/demand-management/task/t_CreateARequirement.html

According to the ServiceNow documentation1, a user's availability is calculated as the ratio of allocated hours to total capacity, expressed as a percentage. Allocated hours are the hours that a user is assigned to work on a project or demand. Total capacity is the maximum number of hours that a user can work in a given period, based on their schedule and availability profile. A user's availability indicates how much of their time is already allocated and how much is still available for new assignments.

1: https://docs.servicenow.com/bundle/vancouver-it-business-management/page/product/resource-management/concept/c_ResourceManagement.html

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

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

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.html2: https://docs.servicenow.com/bundle/vancouver-it-business-management/page/product/project-portfolio-management/concept/c_PortfolioWorkbench.html3: 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

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: https://docs.servicenow.com/bundle/vancouver-it-business-management/page/product/resource-management/concept/c_RateCards.html2: https://docs.servicenow.com/bundle/vancouver-it-business-management/page/product/demand-management/concept/c_DemandRate.html3: https://docs.servicenow.com/bundle/vancouver-it-business-management/page/product/resource-management/concept/c_DefaultRate.html

According to the ServiceNow documentation1, a program is a container for the following:

Program tasks: Tasks that define the scope and deliverables of the program2.

Issues: Problems that affect the program or its outcome3.

Cost plans: Plans that estimate the cost of the program and its components4.

A portfolio is not a part of a program, but rather a collection of programs and projects that are aligned with a strategic goal or objective.

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-portfolio-management/task/t_CreateAProgramTask.html3: https://docs.servicenow.com/bundle/vancouver-it-business-management/page/product/project-portfolio-management/task/t_CreateAnIssue.html4: https://docs.servicenow.com/bundle/vancouver-it-business-management/page/product/project-portfolio-management/task/t_CreateACostPlan.html : https://docs.servicenow.com/bundle/vancouver-it-business-management/page/product/project-portfolio-management/concept/c_PortfolioManagement.html

In order to map custom fields from Microsoft Project to ServiceNow when importing a project, you must first create custom fields in your ServiceNow instance that match the names and data types of the custom fields in Microsoft Project. This will allow you to map the custom fields using a transform map when importing the project. You can find more information about this process in theProduct Documentationfor ServiceNow.