# Free SISSP practice questions

> 10 free SISSP practice questions with the correct answer and an explanation.

Page: https://devopscodelab.com/exams/servicenow-cis-spm/free-practice-questions/
Practice exams: https://devopscodelab.com/exams/servicenow-cis-spm/

### Question 1 of 10

A company runs projects in Germany and the United States, and executives want all project costs reported in USD while German project managers plan in EUR. Which approach supports this requirement?

- A. Require German planners to convert figures to USD first
- B. Enable multi-currency so local-currency plans convert to the reporting currency
- C. Create two copies of every cost plan, one in EUR and one in USD, and keep them aligned manually
- D. Set the system currency to EUR for German users and run a monthly report that multiplies by a fixed rate

**Answer:** B

**Explanation:** SPM supports multi-currency planning where cost plans are entered in a local currency and converted to the functional or reporting currency using maintained exchange rates. Duplicate plans create reconciliation errors. Forcing manual conversion burdens planners and loses the original amounts. A fixed-rate report outside the application is error prone and does not reflect current rates.

### Question 2 of 10

What is the typical sequence of states for a resource plan that is fulfilled successfully?

- A. New, Assessed, Authorized, Scheduled, Implemented
- B. Pending, Open, Work in progress, Closed complete
- C. Planning, Requested, Confirmed, Allocated
- D. Draft, Submitted, Screening, Approved

**Answer:** C

**Explanation:** Resource plans move from Planning to Requested when submitted, then to Confirmed (soft booking) and Allocated (hard booking) by the resource manager. Draft, Submitted, Screening and Approved describe demand states. Pending, Open and Work in progress describe project and task states. New, Assessed, Authorized and Scheduled belong to the change request lifecycle.

### Question 3 of 10

A resource plan requested a role rather than a named user. What does the resource manager typically do during fulfillment?

- A. Return the plan to Planning until the requester names the users
- B. Assign users who hold the role and have availability
- C. Approve the plan as-is for any user with the role
- D. Change the plan to a group request so the whole group is booked

**Answer:** B

**Explanation:** Role-based requests let the requester describe the need, and the resource manager selects suitable users who have the role and capacity when confirming or allocating. Booking a whole group over-commits people. Approving as-is leaves no named allocation for task assignment or timesheets. Returning the plan pushes fulfillment back to the requester unnecessarily.

### Question 4 of 10

When a demand of type Project is approved, which action creates the delivery record from it?

- A. Using Create Project on the approved demand
- B. Converting the demand into an idea for voting
- C. Assessing the demand again to trigger a project
- D. Closing the demand

**Answer:** A

**Explanation:** An approved demand of type Project is turned into a project using the Create Project action, which carries over relevant details such as dates, resource plans and cost plans. Ideas come before demands, not after. Closing the demand does not create a project on its own. Re-running an assessment only recalculates scores.

### Question 5 of 10

Business users without SPM roles need an easy way to submit new requests for investment. What is a common intake method?

- A. Emailing requests to the PMO, which then creates a project for each request received
- B. Asking users to log incidents with a category of New Project Request
- C. Granting each user it_demand_manager so they can open the demand list
- D. A record producer in the service catalog or portal that creates demands

**Answer:** D

**Explanation:** A catalog or portal record producer lets any user submit a demand in a guided form without SPM roles. Giving everyone the demand manager role over-privileges users. Emailing the PMO bypasses structured intake and skips demand evaluation. Incidents are for service disruptions and pollute ITSM data.

### Question 6 of 10

An organization runs several related projects that together deliver a new customer platform, and leadership wants a single record to track their combined schedule, cost and status. Which record type best fits this need?

- A. A program that the related projects are associated with
- B. A demand of type Project referencing them
- C. A portfolio containing only the projects for the customer platform
- D. A parent project task with each project linked as a sub-task

**Answer:** A

**Explanation:** Programs group related projects that deliver a shared outcome and roll up their schedule, cost and status. Portfolios are broader investment groupings typically aligned to a business area and used for prioritization and funding rather than coordinating a specific delivery. Nesting projects as tasks is not supported as a way to manage independent projects. A demand is a request for investment, not a container for running projects.

### Question 7 of 10

A project manager wants to visualize project tasks, their dependencies, and the critical path on an interactive Gantt chart where tasks can be dragged to new dates. Which interface provides this capability for a project?

- A. The Planning Console (timeline/Gantt view) of the project
- B. The Resource Grid for the project's resources
- C. The project's Status Report form with the schedule health field
- D. The Project Portfolio dashboard in Platform Analytics with a bar widget

**Answer:** A

**Explanation:** The Planning Console (the Gantt/timeline planning view, also surfaced in Project Workspace) lets project managers create tasks, draw dependencies, highlight the critical path and drag tasks to reschedule. A status report only captures health indicators and comments. The Resource Grid shows allocations per resource, not task schedules. Analytics dashboards report on data but do not allow schedule editing.

### Question 8 of 10

A PMO wants a project's planned start and end dates to roll up automatically from its child tasks, but for one fixed-date regulatory project the dates must be entered manually and not recalculated. Which project setting addresses this?

- A. Change the default project schedule to a 24x7 calendar for that project
- B. Mark the regulatory project's tasks as milestones so their dates cannot move
- C. Remove all dependencies from the regulatory project and lock each task
- D. Set the project's calculation to manual for the regulatory project only

**Answer:** D

**Explanation:** Projects have a calculation option: automatic calculation rolls dates and effort up from child tasks, whereas manual calculation lets the project manager control the values directly. Removing dependencies still leaves automatic roll-up of dates. A 24x7 schedule only changes working time used in duration calculations. Milestones have zero duration and do not stop the parent from recalculating.

### Question 9 of 10

By default, who approves a submitted time card that records hours against a project task?

- A. The resource manager of the user's resource group
- B. The demand manager who approved the original demand
- C. The timecard administrator
- D. The project manager of the related project

**Answer:** D

**Explanation:** Time cards for project tasks route to the project manager of that project for approval, while time cards that are not tied to a project typically go to the user's manager. Resource managers approve resource plans rather than time. Timecard administrators configure the application. Demand managers are not involved after the project is created.

### Question 10 of 10

A portfolio manager wants to include both approved projects and pending demands in next year's plan so they can be ranked together. How are these added to a portfolio plan?

- A. As child tasks of a portfolio project
- B. As planning items in the plan
- C. As resource plans for the portfolio
- D. As cost plan breakdowns for each period

**Answer:** B

**Explanation:** Portfolio plans contain planning items, which reference work such as demands and projects so they can be ranked and analyzed together. Resource plans request people. Cost plan breakdowns are period-level financial values. Portfolios are not projects and do not hold child tasks.

Ready for a timed run? Take the free 15-question SISSP mini exam: https://devopscodelab.com/app/exams/servicenow-cis-spm/mini/

DevOpsCode Lab is not affiliated with ServiceNow. SISSP and related names are trademarks of their owners. We write every question ourselves; these are not real exam questions.
