Question Q-8647 A project manager is tracking a construction project with dependencies:…
2 comments · last active May 18, 2026
By Marcus Chen · Updated May 25, 2026
| Questions | 25 |
| Passing Score | 75% |
| Format | 100% Multiple Choice |
| Sessions Logged | 776 |
| Your progress | Log in / Register to track times taken, best score, questions mastered, and coverage on this quiz. |
| Rating |
Uncategorized25 questions
Log in to post a comment, reply, or expand a question.
Investment bubble chart: risk vs strategic value, bubble size = budget, color = run/transform/innovate. Sorted list (opt A) can't show balance.
Steering committee uses this to see if you're all gray "run" bubbles and no innovation.
Phase Gates with executive approval — not separate projects per phase (opt C). WBS lives inside each phase on one project record.
Change Management phases (opt D) is a classic trap if you come from ITSM only.
Resource Workbench = capacity vs committed across ALL projects. Manual surveys (opt A) are never the exam answer.
Red highlighting on over-allocation is the giveaway — aggregate view is the whole point.
100 demands / 30 capacity → Demand Management scoring (strategic alignment, ROI, risk). Gut-feel IT Director (opt A) is bait.
Ranked demand list then pick top N within capacity — transparent portfolio selection.
EVM: CPI = EV/AC, SPI = EV/PV. Enable earned value on work packages + time charged — not Excel (opt A).
CPI < 0.8 flags on PMO dashboard tie to Q13 health scoring too.
OKRs in SPM: link Key Results to project milestones — progress updates when milestone closes, not monthly spreadsheet (opt C).
Strategy-to-execution alignment is the SPM pitch; disconnected OKRs (opt A) defeats the module.
EAC > budget by 10% → auto alert to portfolio manager + sponsor. Waiting until over budget (opt C) kills corrective action.
Estimate at Completion from actuals + ETC — PM enters ETC on status, system projects overrun.
Portfolio Scenario Planning — sandbox copy, add Project X, see capacity/budget impact WITHOUT touching live portfolio.
Promote scenario after approval. Adding to live portfolio first (opt A) is how you break real resource plans.
ERP = Program parent with 5 child Projects — rollup budget, cross-project deps, program risks. One 500-task mega-project (opt C) is wrong.
Data Migration blocking Financials go-live is a program-level dependency example they use.
Portfolio health thresholds CPI/SPI < 0.8 → Red on PMO dashboard + alerts. Reviewing 200 projects weekly (opt A) doesn't scale.
Exception reporting is the PMO superpower here — traffic-light grid beats slide decks.
Catalog listing of the 5 preview questions for this quiz.
A project manager is tracking a construction project with dependencies: Task B cannot start until Task A is complete, and Task C cannot start until both Task A and Task B are complete. If Task A is delayed by 3 days, how should ServiceNow PPM automatically handle this?
ServiceNow PPM schedule dependency management: (1) Dependency Types: Finish-to-Start (B cannot start until A finishes), Start-to-Start, Finish-to-Finish, Start-to-Finish; (2) Automatic Rescheduling: when a task's duration or completion date changes, all dependent tasks are automatically rescheduled; (3) Task A delayed 3 days → Task B start date shifts 3 days → Task C start date shifts to max(A finish + lag, B finish + lag); (4) Critical Path Method: ServiceNow PPM identifies the critical path — the longest sequence of dependent tasks determining the project end date; (5) Float: non-critical tasks show float (slack) — how many days they can slip without affecting the end date; (6) End Date Impact: overall project end date updates to reflect cascading delays; (7) Project Health: if delayed end date exceeds planned end date, health indicator changes to Yellow/Red. Manual date management (option A) in a project with many dependencies is error-prone and time-consuming.
A company's SPM governance board wants to implement a formal stage-gate review process for all major IT investments, inspired by Phase-Gate Management (Cooper's Stage-Gate model). Projects must pass through Gates: Gate 1 (Idea Screen), Gate 2 (Second Screen), Gate 3 (Decision to Develop), Gate 4 (Post-Development Review), Gate 5 (Launch/Implement). How does ServiceNow SPM/PPM configure this?
ServiceNow SPM Phase-Gate Management: (1) Gate Configuration: create Gate records for each review point with: Gate Name, Gate Number, required Deliverables (checklist that must be complete), Evaluation Criteria (scored 1-5 on strategic fit, financial attractiveness, competitive advantage, risk), and designated Gate Keepers (specific individuals or roles); (2) Deliverable Enforcement: project cannot advance to the next gate until all required deliverables are attached and marked complete; (3) Gate Review: Gate Keepers formally evaluate the investment, apply scoring, and record their decision (Go, Kill, Hold, Recycle); (4) Gate Record: all gate decisions, scores, comments, and deliverables preserved for portfolio audit trail; (5) Kill Criteria: if investment scores below the minimum threshold at any gate, it is automatically placed in "Hold" pending review; (6) Portfolio Intelligence: portfolio analytics show how many investments are at each gate stage and average time per gate. Option D is incorrect — gates without blocking authority are meaningless governance theater.
A project manager needs to track that a critical project milestone — "System Integration Testing Complete" — has been achieved before the project can move to User Acceptance Testing. If the milestone is missed, the project plan should be flagged and the sponsor notified. How is this configured in ServiceNow PPM?
Milestone tracking in ServiceNow PPM: (1) Milestone Task: create a project task with "Is Milestone" checked — milestones have no duration, representing a specific point in time; (2) Dependencies: tasks after the milestone have "Finish-to-Start" dependency — UAT tasks cannot start until SIT Complete milestone is checked; (3) Milestone Monitoring: a business rule or scheduled flow checks: if milestone planned date < today AND milestone state != Closed, project health = Orange; if milestone date + 5 days AND state != Closed, project health = Red; (4) Automatic Notification: project sponsor and stakeholders notified of milestone breach; (5) Timeline Impact: automatic recalculation of downstream task dates based on milestone delay; (6) Project Health Dashboard: shows all projects with breached milestones. Work notes (option A) don't enforce dependencies or trigger automated notifications.
A company wants to implement IT Financial Management alongside PPM — specifically, they want to track the total cost of each project (labor + tools + licenses) and show the actual cost vs. budget on project dashboards. How should this be configured in ServiceNow?
ServiceNow IT Financial Management + PPM integration: (1) Resource Rates: configure cost rates per role/resource (Senior Developer = $120/hour, Project Manager = $95/hour); (2) Time Tracking: resources log actual hours against project tasks; system calculates labor cost = hours × rate; (3) Direct Costs: project managers log non-labor costs (software licenses, external vendor invoices, training) as expense records on the project; (4) Budget tracking: project budget fields (planned cost) vs. actual cost (calculated from time + direct costs); (5) Budget Variance Report: dashboard shows each project's budget consumed, remaining, and variance; (6) Cost Rollup: program and portfolio levels show total spend across all component projects; (7) Forecasting: project managers can enter ETC (Estimate to Complete) for remaining work to project final cost. Siloed ERP tracking (option A) prevents project managers from seeing real-time cost performance.
A company's PMO wants to identify projects that are consistently over budget, behind schedule, or at risk of cancellation across a portfolio of 200 active projects. Instead of reviewing each project individually, they want automated identification of troubled projects. What SPM/PPM capability enables this?
Portfolio-wide exception management: (1) Health Score Thresholds: configure color-coded thresholds: Green (CPI 0.9-1.1, SPI 0.9-1.1), Yellow (CPI 0.8-0.9), Red (CPI < 0.8 or SPI < 0.8 or health manually set); (2) Real-time Dashboard: PMO Dashboard shows all 200 projects as a traffic light grid — Red and Yellow projects visible immediately without reviewing each one; (3) Automated Alerts: when a project's health changes from Green to Yellow/Red, automatic notification to: Project Manager, Project Sponsor, PMO Director; (4) Health Drill-down: clicking a Red project shows EVM metrics, overdue milestones, and top risks; (5) Trend Analysis: performance Analytics shows which projects have been consistently Red for multiple periods (candidates for corrective action or cancellation). Reviewing all 200 projects weekly (option A) requires 10-20 minutes per project × 200 = days of meeting time.
Finish-to-Start delay cascades — Task A +3 days pushes B then C; critical path recalculates. Dependencies aren't decorative.
Manual date updates (opt A) at scale = errors. PPM does the math when predecessor slips.