Sign in
Home/ServiceNow/Project Portfolio Management (CIS-PPM)/Free questions

ServiceNow Certified Implementation Specialist - Project Portfolio Management (CIS-PPM) — Free Practice Questions

10 free sample questions from a bank of 245, with the correct answers and explanations. No signup required — start practising right now.

1Which of the following checks to see if the assessable record exists for the demand and creates an assessable record if none exists?
  • Validate Assessment Metrics for Demand
  • Auto Business Rule for Assessments
  • Update Demand State
  • Create OnDemand Assessment
Answer: B

The short version

B — Auto Business Rule for Assessments checks and creates assessable records. Demands need an assessable wrapper before surveys run. That rule guarantees one exists automatically.

Key concepts in this question

  • Assessable record: linkage object that allows assessment instances to attach to a demand.
  • Auto Business Rule for Assessments: background logic that verifies existence and creates the wrapper if missing.
  • Validate Assessment Metrics: check on metric definitions rather than record creation.
  • Update Demand State: stage transition action, not an assessable provisioning step.
  • Create OnDemand Assessment: manual trigger for a specific survey, assuming the wrapper already exists.

Why B is correct

The named auto rule exists precisely to see if an assessable record exists for the demand and to create one when none is found. That behavior matches the stem verbatim and carries very strong community support. Other options either validate content or move state but do not provision the linkage. B is therefore the settled key.

Why the others are wrong

  • A. Validate Assessment Metrics confirms metric setup, it does not create assessable records.
  • C. Update Demand State advances workflow stage, it has no assessable creation duty.
  • D. Create OnDemand Assessment launches a survey instance instead of ensuring the parent wrapper.

CIS-PPM exam tip

Tie the phrase exists and creates if none exists to the Auto Business Rule, and keep manual assessment creation separate.

2Plugins may be added to the base platform in one of the following ways: (Choose three.)
  • Activated by an admin (not by default).
  • Activated by an it_portfolio_manager.
  • Requested from ServiceNow.
  • Activated by default in the base ServiceNow system.
  • Activated by an it_pps_admin.
Answer: A, C, D

The short version

ACD — Plugins come via admin activation, ServiceNow request, or default activation. The platform ships some plugins on, leaves others for admin opt-in, and gates some behind entitlement requests. Those three paths cover the model.

Key concepts in this question

  • ServiceNow plugins: modular capabilities that extend tables, roles and logic beyond the base build.
  • Admin activation: optional plugin turned on by an administrator from the plugins list.
  • Requested from ServiceNow: entitlement path where the customer asks ServiceNow to enable a licensed plugin.
  • Activated by default: bundled functionality present without extra steps in a fresh instance.
  • Role-specific activation: portfolio or PPS admin grants are not listed as plugin sourcing channels.

Why ACD is correct

Platform plugins concept documentation enumerates exactly these three avenues, and the settled key ACD mirrors them. Admin opt-in, ServiceNow request and default-on together exhaust how base-platform plugins arrive. Portfolio manager or PPS admin activation are invented distractors with no documented plugin-channel role. Unanimous agreement confirms the trio.

Why the others are wrong

  • B. it_portfolio_manager governs portfolios, it is not a documented plugin activation channel.
  • E. it_pps_admin administers PPM suite use, not general plugin provisioning paths.

CIS-PPM exam tip

Memorize plugin paths as admin plus request plus default, and reject any answer naming a business role as the activation channel.

3Which demand category would a demand manager select, if they need to create an enhancement?
  • Change
  • Strategic
  • Defect
  • Operational
Answer: B

The short version

B — Strategic is the demand category for an enhancement. Enhancement work maps to strategic demand because it extends capability for business value, not to defect, operational, or change buckets used for other purposes.

Key concepts in this question

  • Demand categories: classification that drives routing, assessment, and conversion of a demand into project, enhancement, change, or defect artifacts.
  • Strategic demand: request tied to business strategy and improvement, including enhancements that add features or extend existing services.
  • Enhancement artifact: follow-on work that improves a live service without being a break-fix or day-to-day operational task.
  • Other categories: defect for faults, operational for run work, and change for controlled alterations each have distinct handling.

Why B is correct

Option B Strategic is correct because ServiceNow demand guidance treats enhancements as strategic investment items that grow capability and require business-case review. Creating an enhancement from a demand follows the strategic path through screening, assessment, and approval before conversion. The settled key names B, and vendor prose plus unanimous community alignment confirm that enhancement equals strategic in CIS-PPM scope.

Why the others are wrong

  • A. Change governs controlled alterations with risk and approval controls, not capability growth through enhancement.
  • C. Defect tracks faults and failures needing correction, not new or improved functionality requested as an enhancement.
  • D. Operational covers day-to-day run and support load, not strategic improvement that expands value and justifies investment review.

CIS-PPM exam tip

Link enhancement to strategic every time. Picture demand category equals artifact type, then remember strategic plus enhancement, defect plus fix, operational plus run, change plus control. Any enhancement question points to strategic.

4On the demand form, what does the Discount Rate impact?
  • Internal Rate of Return %.
  • ROI.
  • Financial Benefit.
  • Net Present Value (NPV).
Answer: D

The short version

D — Discount Rate impacts Net Present Value on the demand. The rate discounts future benefits and costs to present worth. NPV moves whenever the rate moves.

Key concepts in this question

  • Discount Rate: percentage input on the demand form controlling time-value math.
  • Net Present Value: present worth of future cash flows after discounting, used for screening.
  • Internal Rate of Return: rate where NPV hits zero, an output rather than the impacted field.
  • ROI: return ratio summarizing profitability, derived after NPV math.
  • Financial Benefit: nominal gain stream before discounting is applied.

Why D is correct

Demand financial logic uses Discount Rate to compute NPV, so changing the rate directly changes NPV. Community and vendor notes affirm d is correct with full agreement. IRR, ROI and benefit describe related but distinct outcomes that do not name the directly impacted present-value field. D is the settled key.

Why the others are wrong

  • A. Internal Rate of Return is solved from cash flows, it is not the field impacted by the rate input.
  • B. ROI summarizes return as a ratio, it is downstream of the NPV calculation.
  • C. Financial Benefit is the undiscounted inflow, not the discounted present value itself.

CIS-PPM exam tip

On the demand form always connect Discount Rate to NPV first, and treat IRR and ROI as secondary derived metrics.

5As a demand manager, you can view an artifact from a demand. What artifacts are part of a demand?
  • Incidents, Problems, Change.
  • Decision, Risk, Requirements.
  • Project, Defect, Requests.
  • Stories, Vulnerability Tasks, Enhancements.
Answer: C

The short version

C — Project, Defect, and Requests are viewable demand artifacts. Demands generate downstream work records for tracking delivery, and this trio reflects the core artifact set a demand manager inspects from the demand.

Key concepts in this question

  • Demand artifacts: records created or linked from an approved demand to carry out the work, including projects, defects, enhancements, changes, and agile entities.
  • Project artifact: execution vehicle with tasks, resources, and schedules created when a demand is approved for delivery.
  • Defect and request linkage: quality and fulfillment records tied to demand scope so scope plus issues stay traceable.
  • Other groupings: incidents plus problems plus change belong to operations, while stories plus tasks belong to agile breakdown, not the demand artifact view.

Why C is correct

Option C Project, Defect, Requests is correct because demand guidance lists project, defect, change, enhancement, and scrum entities as available types, and the settled key narrows the choice to this trio. Vendor prose plus community support confirms C.

Why the others are wrong

  • A. Incidents, Problems, Change describes ITSM operation records, not the demand-to-delivery artifact chain centered on projects and defects.
  • B. Decision, Risk, Requirements are demand details and logs used during qualification, not separate executable artifacts created from a demand.
  • D. Stories, Vulnerability Tasks, Enhancements mixes agile plus security items without the project anchor, so it misses the primary execution record.

CIS-PPM exam tip

Link demand artifacts to project plus defect plus change plus enhancement plus agile entities. On artifact-view questions, look for the option containing Project first, then eliminate any choice built only from logs like decisions or risks.

6As an it_pps_admin, what can you use to detect corrupt data in a project, such as tasks with invalid parents or cyclic relations in a project?
  • Project Diagnostics.
  • System Diagnostics.
  • Edge Encryption Diagnostics.
  • Analytics Diagnostics.
Answer: A

The short version

A — Project Diagnostics finds corrupt project data. Invalid parents, cyclic relations, and structural faults are detected by the purpose-built project health check, not by platform-wide or unrelated diagnostic tools.

Key concepts in this question

  • Project Diagnostics: admin utility that scans project structure for corrupt data such as tasks with invalid parents or cyclic dependencies.
  • it_pps_admin scope: role that owns project administration, settings, and health checks across PPM data.
  • Corrupt data patterns: orphaned tasks, loops in predecessor logic, and hierarchy breaks that block scheduling and rollups.
  • Other diagnostics: system, edge encryption, and analytics diagnostics target platform health or data protection, not project structure.

Why A is correct

Option A Project Diagnostics is correct because ServiceNow project documentation describes this tool as the way to detect structural faults like invalid parents and cyclic relations. Running it as it_pps_admin surfaces issues before they corrupt schedules, resource rollups, and status calculations. The settled key names A with unanimous community backing and vendor prose citing the diagnostics overview, confirming fit for CIS-PPM scope.

Why the others are wrong

  • B. System Diagnostics checks instance health and performance, not project task hierarchy or predecessor loops.
  • C. Edge Encryption Diagnostics validates encryption configuration, which has no relation to task parents or scheduling logic.
  • D. Analytics Diagnostics troubleshoots reporting and scoring utilities, not corrupt project network structure.

CIS-PPM exam tip

Link corrupt plus cyclic plus invalid parent to Project Diagnostics. Picture admin opening project settings to run the health scan, then remember other diagnostics belong to platform, security, or analytics. Any structure-corruption stem points to A.

7In which scenario would using the Copy Project action NOT result in a new project record being created?
  • When copying an existing project
  • When copying a new project
  • When copying sub-projects
  • When copying partial projects
Answer: D

The short version

D — Copying partial projects does not create a new project record. Full, new, and sub-project copies instantiate fresh records, while a partial copy reuses scope without spawning a standalone project.

Key concepts in this question

  • Copy Project action: utility that duplicates project structure, tasks, and selected fields into a new or existing target.
  • Partial project copy: selective copy of project slices that updates a target without creating a separate project header record.
  • Full and sub-project copies: operations that generate new project records with their own numbers, states, and schedules.
  • Default copy behavior: numbers and state are reset while descriptive and planning fields carry over per copy rules.

Why D is correct

Option D When copying partial projects is correct because ServiceNow copy guidance distinguishes partial copies that fill an existing target from full copies that spawn new records. Copying an existing project, a new project shell, or sub-projects creates fresh project headers for independent tracking. The settled key names D with full community agreement and vendor prose citing the copy task page, confirming the exception in CIS-PPM scope.

Why the others are wrong

  • A. When copying an existing project creates a new record by duplicating structure into a fresh header for separate management.
  • B. When copying a new project still results in a created record once the shell is saved with copied content.
  • C. When copying sub-projects generates child project records linked to the parent, so creation does occur.

CIS-PPM exam tip

Link partial copy to no new record. Picture full copy equals new header, partial copy equals fill existing target. On NOT questions, scan for the partial or selective option and choose it while eliminating full-creation cases.

8When copying a source project to a target project, what fields are copied by default? (Choose three.)
  • Number.
  • Duration fields.
  • Short description.
  • Planned dates.
  • State.
Answer: B, C, D

The short version

BCD — Duration, Short description, and Planned dates copy by default. Copy carries planning content forward while identity and lifecycle fields reset, so this trio reflects the default field set.

Key concepts in this question

  • Copy Project defaults: field set duplicated automatically from source to target unless excluded by configuration.
  • Duration fields: effort and timeline inputs that preserve scheduling intent across the copy.
  • Short description and planned dates: descriptive plus time-bound data that gives the new project context and calendar placement.
  • Excluded fields: number and state reset so each project keeps unique identity and starts in the correct lifecycle point.

Why BCD is correct

Options B, C, and D are correct because ServiceNow copy documentation lists duration fields, short description, and planned dates among fields copied by default. These values let the target inherit scope and timing without manual re-entry. The settled key names BCD with unanimous support and vendor prose citing the copy task page, confirming the trio for CIS-PPM scope.

Why the others are wrong

  • A. Number is a unique identifier generated fresh for each project, so copying it would break identity and audit rules.
  • E. State reflects lifecycle position and is reset for the new record rather than inherited, preventing accidental closure or activation.
  • Any set with A or E. Including identity or lifecycle fields contradicts default copy logic that preserves planning content while resetting control fields.

CIS-PPM exam tip

Link copy defaults to planning content, not identity. Memorize duration plus short description plus planned dates as carried over, number plus state as reset. If number or state appears in an option, eliminate it.

9The Project management application supports two types of external dependencies. What are they? (Choose two.)
  • Hard Dependency.
  • Milestone Dependency.
  • Soft Dependency.
  • Task Dependency.
  • Change Dependency.
Answer: A, C

The short version

AC — Hard and Soft are the two external dependency types. External dependencies link tasks across projects. Hard enforces strict order while soft signals preferred order.

Key concepts in this question

  • External dependency: cross-project task relationship tracked in Project Management.
  • Hard Dependency: strict predecessor rule where successor cannot proceed until predecessor completes.
  • Soft Dependency: advisory sequencing preference without hard blocking enforcement.
  • Milestone and Task Dependency: generic internal link labels, not the external pair.
  • Change Dependency: change-control concept, unrelated to the project scheduling pair.

Why AC is correct

Product documentation states the Project management application supports two types of external dependencies, hard and soft. Vendor prose quotes that line directly and agreement is unanimous. Other labels describe internal or unrelated dependency ideas. AC is therefore the settled pair.

Why the others are wrong

  • B. Milestone Dependency names an internal scheduling usage, not an external type.
  • D. Task Dependency is too generic and is not listed as one of the two external types.
  • E. Change Dependency belongs to change management, not cross-project scheduling.

CIS-PPM exam tip

Lock external dependencies as Hard plus Soft, and do not let milestone, task or change labels pull you away.

10In order to map custom fields from Microsoft Project to ServiceNow when importing a project, you must first:
  • Configure the Project form
  • Export the project to XML format
  • Import your project
  • Create custom fields in your ServiceNow instance
Answer: D

The short version

D — Create custom fields in ServiceNow before mapping from Microsoft Project. Import mapping needs matching targets on the platform side, so the ServiceNow fields must exist first.

Key concepts in this question

  • Microsoft Project import: migration path that brings tasks, dates, and custom attributes into ServiceNow project tables.
  • Field mapping: pairing of source custom columns to destination ServiceNow fields during import configuration.
  • Custom field prerequisite: destination fields must be created so the mapper has valid targets with correct types.
  • Form and file steps: project form layout and XML export support the move but cannot substitute for missing targets.

Why D is correct

Option D Create custom fields in your ServiceNow instance is correct because mapping requires a destination for every custom source column, including type-compatible fields for dates, text, and numbers. Without prebuilt targets, the import wizard has nothing to bind Microsoft Project attributes to. The settled key names D with full community agreement and vendor prose citing the custom-field mapping task, confirming the sequence for CIS-PPM scope.

Why the others are wrong

  • A. Configure the Project form adjusts layout and visibility but does not create the underlying fields needed for mapping.
  • B. Export the project to XML format prepares the source file yet leaves the destination schema incomplete.
  • C. Import your project before defining fields forces failures or data loss because custom values have no mapped home.

CIS-PPM exam tip

Link custom mapping to create targets first. Picture source columns on the left needing ServiceNow fields on the right, then remember build before bind. Any sequence starting with import or export before field creation is wrong.

Want the full bank of 245 questions for ServiceNow Certified Implementation Specialist - Project Portfolio Management (CIS-PPM)? See all practice exams.