ITIL 4 Strategist: Direct, Plan and Improve (DPI) (DPI) DPI Questions 301–313 | Page 5/5

301

MCQmedium

An organization is using the ITIL continual improvement model to support its directional strategy. At which stage of the direction-setting and planning cycle should the 'Where do we want to be?' question be addressed?

A.Only when executing tactical changes without any prior planning.

B.During the definition of the vision, mission, and measurable objectives (target state).

C.When determining how to keep momentum going at the very end of an initiative.

D.Exclusively during the measurement of baseline metrics after project completion.

AnswerB

The 'Where do we want to be?' question defines the target state, so it belongs to vision, mission and measurable objectives. This stage translates directional strategy into specific, quantifiable goals, giving the improvement cycle its destination before gaps are analysed or plans executed.

Why this answer

The 'Where do we want to be?' question in the ITIL continual improvement model is addressed during the definition of the vision, mission, and measurable objectives, which sets the target state. This stage establishes the desired outcomes and goals before planning how to achieve them. It is a foundational step in the improvement cycle.

Exam trap

The trap is confusing the sequence of the continual improvement model; candidates may associate 'Where do we want to be?' with later stages like measurement or momentum.

How to eliminate wrong answers

Option A is wrong because executing tactical changes without planning skips the direction-setting stage entirely. Option C is wrong because keeping momentum going is about sustaining progress, not defining the target state. Option D is wrong because measuring baseline metrics occurs after the target state is defined, to assess current performance against goals.

Full explanation →

302

MCQeasy

What is the primary focus of value stream mapping during the planning phase?

A.Writing marketing copy for product brochures.

B.Visualizing the end-to-end flow of activities to identify waste, delays, and improvement areas.

C.Designing server network topologies and firewall rules.

D.Calculating annual employee salary bonuses.

AnswerB

Value stream mapping renders the entire sequence of activities, handoffs and information flows visible, exposing non-value-adding steps, queues and delays across the end-to-end path. That visibility is what enables planning-phase decisions about where to remove waste before committing to changes.

Why this answer

Value stream mapping (VSM) is a lean technique that creates a visual representation of all steps — both value-adding and non-value-adding — required to deliver a product or service from customer request to delivery. During the planning phase, its primary purpose is to expose waste (muda), bottlenecks, handoff delays, and rework loops so the organization can prioritize improvement efforts. By making the end-to-end flow visible, teams can quantify lead time, process time, and percent complete/accurate metrics to target systemic constraints rather than local optimizations.

Exam trap

The trap here is confusing value stream mapping with generic project planning or technical architecture design, causing candidates to select an option that sounds like 'planning' but has nothing to do with visualizing flow and eliminating waste.

How to eliminate wrong answers

Option A is wrong because writing marketing copy is a communications/marketing activity unrelated to process flow analysis and produces no visibility into value delivery. Option C is wrong because designing server network topologies and firewall rules is a technical infrastructure design task, not a lean process-mapping exercise that traces value from demand to delivery. Option D is wrong because calculating annual employee salary bonuses is a compensation/HR finance activity and has no relationship to identifying waste or delays in a value stream.

Full explanation →

303

MCQmedium

A technology company is reviewing its KPI framework. Leadership notices that teams are hitting 100% of their individual KPIs, yet the overall company strategic goals are failing. According to ITIL 4, what flaw exists in the metric design?

A.The metrics lack alignment and cascade from overarching organizational objectives to operational activities.

B.The reporting frequency is too slow, causing strategic drift.

C.The teams are not using agile frameworks like Scrum.

D.The organization is using ServiceNow instead of Salesforce for KPI tracking.

AnswerA

Individual KPIs hitting target while strategic goals fail shows metrics are not derived from and linked to organisational objectives. ITIL 4 requires a cascade from strategic intent down to operational measures, so each team's activity demonstrably contributes to the overarching outcomes leadership is pursuing.

Why this answer

Cascading and alignment failures occur when local metrics do not contribute to broader organizational outcomes and value chains.

Full explanation →

304

Multi-Selecthard

An OCM practitioner is assessing cultural readiness for a DevOps transformation. Which THREE assessment techniques provide valid qualitative and quantitative data regarding organizational readiness?

Select 3 answers

A.Administering standardized cultural and behavioral readiness surveys.

B.Analyzing historical adoption patterns and agile metric trends from pilot squads.

C.Conducting cross-functional focus groups and semi-structured interviews.

D.Reviewing personal employee credit score reports from external financial agencies.

E.Randomly guessing employee readiness levels based on executive intuition.

AnswersA, B, C

Standardised surveys yield quantitative scores on cultural and behavioural readiness, directly satisfying the stem's demand for valid quantitative data. Their validated psychometric structure enables benchmarking and trend comparison across squads, complementing qualitative techniques within the three-technique assessment set.

Why this answer

Option A is correct because standardized cultural and behavioral readiness surveys are a validated quantitative instrument that yields comparable, benchmarkable data on dimensions such as trust, psychological safety, collaboration, and change appetite across the organization. Option B is correct because analyzing historical adoption patterns and agile metric trends from pilot squads provides objective quantitative evidence—such as deployment frequency, lead time, and adoption curves—that reveals how readily teams absorb DevOps practices. Option C is correct because cross-functional focus groups and semi-structured interviews generate rich qualitative data that uncovers underlying attitudes, resistance drivers, and contextual barriers that surveys alone cannot capture.

Option D is not appropriate because personal employee credit score reports from external financial agencies are irrelevant to organizational change readiness and would raise serious privacy and compliance concerns. Option E is not appropriate because random guessing based on executive intuition is neither qualitative nor quantitative and produces unreliable, non-evidence-based assessments.

Exam trap

DPI often tests whether candidates can distinguish valid assessment methods from invalid ones — options involving personal financial data or pure intuition are distractors that violate data ethics and methodological rigor.

Full explanation →

305

MCQhard

An organization is establishing key performance indicators (KPIs) to measure the effectiveness of its Continual Improvement practice. Management wants to ensure the metrics evaluate both velocity and value realization. Which combination of metrics best satisfies this requirement?

A.Total budget allocated to software licensing and number of staff resignations.

B.Average cycle time of improvement initiatives and percentage of targeted business outcomes successfully achieved.

C.Total number of major incidents reported and average speed of hardware replacements.

D.Number of open improvement tickets and average time spent on training courses.

AnswerB

Cycle time measures velocity, showing how quickly improvement initiatives progress, while the percentage of targeted business outcomes achieved measures value realisation. Together they satisfy the stem's requirement to evaluate both dimensions, preventing speed metrics from masking absent benefits.

Why this answer

Velocity and value realization are two distinct dimensions of continual improvement effectiveness. Average cycle time of improvement initiatives measures velocity — how fast improvements move from idea to delivery. Percentage of targeted business outcomes successfully achieved measures value realization — whether the improvements actually delivered the intended business benefit.

Together they cover both speed and worth, which is exactly what management asked for.

Exam trap

The trap is selecting activity or volume metrics (tickets, training hours, incidents) that feel like improvement measures but do not actually evaluate velocity or value realization.

How to eliminate wrong answers

Option A is wrong because budget allocated to licensing and staff resignations are input/HR metrics, not measures of improvement velocity or value realization. Option C is wrong because major incident counts and hardware replacement speed measure operational stability and logistics, not the effectiveness of the continual improvement practice itself. Option D is wrong because open improvement tickets and training hours measure backlog volume and activity, not velocity of delivery or realization of business outcomes — activity metrics are classic 'vanity metrics' that don't prove value.

Full explanation →

306

MCQhard

An enterprise is undertaking a value stream planning initiative for a new cloud-native application delivery pipeline. The team discovers that manual CAB (Change Advisory Board) approvals take 5 days per release. According to ITIL 4 value stream planning, how should this be resolved?

A.Replace traditional manual CAB approvals with automated quality gates and risk-based peer reviews.

B.Restrict releases to once per year to accommodate CAB review schedules.

C.Expand the CAB committee size to include more senior managers for thorough reviews.

D.Eliminate all change authorization entirely without any safeguards.

AnswerA

Automated quality gates with risk-based peer reviews replace the five-day manual CAB bottleneck with continuous, proportionate control, directly resolving the stem's constraint. This aligns with ITIL 4 value stream planning by removing wait time while retaining appropriate risk assurance for cloud-native releases.

Why this answer

ITIL 4 value stream planning focuses on identifying and removing waste — non-value-adding steps — from the flow of work. A 5-day manual CAB approval is a classic bottleneck that adds lead time without adding value, so the correct remedy is to replace it with automated quality gates and risk-based peer reviews that preserve control while restoring flow. This aligns with ITIL 4's guiding principles of 'optimize and automate' and 'progress iteratively with feedback.'

Exam trap

The trap is a false dichotomy between 'no governance' and 'heavy governance' — candidates who equate removing a bottleneck with removing all controls pick the elimination option, while those who equate control with more approvers pick the expand-the-CAB option.

How to eliminate wrong answers

Option B is wrong because restricting releases to once per year worsens the bottleneck by batching changes, increasing risk per release and destroying the value stream's ability to deliver value — the opposite of flow optimization. Option C is wrong because expanding the CAB adds more approvers, which lengthens the approval queue and increases handoffs, directly contradicting value stream planning's goal of reducing wait time. Option D is wrong because eliminating all change authorization removes necessary risk controls; ITIL 4 advocates replacing manual gates with automated, risk-appropriate controls, not abolishing governance entirely.

Full explanation →

307

MCQmedium

A healthcare provider is configuring access controls in Epic EHR to comply with HIPAA regulations. Clinicians complain that multi-factor authentication (MFA) prompts every 15 minutes disrupt patient care. How should the governance board apply ITIL 4 principles to balance security compliance with clinical value?

A.Remove MFA entirely for all clinical staff to maximize speed of care.

B.Transfer patient care tasks to administrative staff to handle logins.

C.Apply 'Keep it simple and practical' and 'Focus on value' to adjust session timeout rules and implement context-aware authentication (e.g., badge-tap proximity access).

D.Increase MFA frequency to every 5 minutes to ensure maximum compliance rigor.

AnswerC

These two ITIL 4 principles directly resolve the conflict: context-aware authentication via badge-tap proximity preserves HIPAA-compliant MFA while removing disruptive 15-minute prompts, focusing on clinical value and keeping the control simple and practical for clinicians.

Why this answer

Option C is correct because it applies two ITIL 4 principles simultaneously: 'keep it simple and practical' (don't over-engineer security controls in ways that create workarounds and clinical risk) and 'focus on value' (the value here is safe, timely patient care, not maximal authentication friction). Context-aware authentication like badge-tap proximity access maintains security while removing the repetitive MFA burden that disrupts care.

Exam trap

The trap is framing security and clinical value as a zero-sum trade-off — candidates who think 'more MFA equals more compliance' or 'remove MFA to go faster' miss the ITIL 4 principle that value and simplicity must be balanced through context-aware design.

How to eliminate wrong answers

Option A is wrong because removing MFA entirely for clinical staff eliminates a critical HIPAA-required access control and creates unacceptable risk of unauthorized PHI access — speed of care cannot come at the cost of patient data security. Option B is wrong because transferring patient care tasks to administrative staff to handle logins is clinically unsafe, creates accountability gaps, and violates the principle that access should be tied to the person performing the task. Option D is wrong because increasing MFA frequency to every 5 minutes doubles down on the friction that caused the complaint, worsening clinician experience and increasing the likelihood of workarounds that undermine security.

Full explanation →

308

MCQhard

An executive board is defining strategic direction for a global bank. They emphasize that compliance and agility must be balanced. How should the planning team incorporate this direction into value stream design?

A.By separating compliance into a completely disconnected annual audit cycle.

B.By automating compliance validation steps directly inside the deployment pipeline to maintain flow.

C.By bypassing compliance requirements whenever speed is prioritized.

D.By requiring all code releases to undergo a mandatory 3-week manual review board.

AnswerB

Embedding automated compliance validation directly within the deployment pipeline enforces regulatory controls without adding manual gates, preserving flow and agility. This satisfies the stem's constraint that compliance and agility be balanced rather than traded off in value stream design.

Why this answer

The correct answer is B because it embeds compliance validation directly into the deployment pipeline, making it an automated, continuous part of the value stream rather than a separate, disruptive phase. This preserves flow and agility while ensuring every change is checked against regulatory requirements, achieving the balance the board demands. Automating compliance reduces manual bottlenecks and provides fast feedback, which is essential for a global bank operating under strict oversight.

Exam trap

The trap here is assuming that compliance and agility are mutually exclusive, leading candidates to choose extreme options like annual audits or manual review boards instead of integrated automation.

How to eliminate wrong answers

Option A is wrong because separating compliance into a disconnected annual audit cycle creates a compliance silo, delays feedback, and increases risk since issues are found long after deployment. Option C is wrong because bypassing compliance for speed directly violates regulatory mandates and introduces severe legal and financial risks, which is unacceptable for a bank. Option D is wrong because a mandatory 3-week manual review board introduces a massive bottleneck, destroys flow, and contradicts the goal of balancing agility with compliance.

Full explanation →

309

MCQeasy

A retail company is new to ITIL 4 DPI and wants to understand the difference between 'direct' and 'plan' in the context of the Direct, Plan and Improve module. Which statement accurately describes the distinction?

A.Direct is about governance and leadership, while plan is about designing the approach to achieve objectives.

B.Direct is about creating policies, while plan is about enforcing compliance.

C.Direct is about managing day-to-day operations, while plan is about long-term strategy.

D.Direct is about setting strategy and objectives, while plan is about executing tasks.

AnswerA

Direct focuses on governance, leadership, and setting direction, ensuring alignment with strategy. Plan involves designing the methods, resources, and timelines to achieve those objectives. This distinction is fundamental in ITIL 4 DPI. Direct provides the 'why' and 'what', while plan provides the 'how'. This option accurately reflects the roles of these two concepts in the module.

Why this answer

In ITIL 4 DPI, direct encompasses governance and leadership, setting the direction and ensuring alignment. Plan involves designing the approach, including policies, resources, and timelines, to achieve objectives. This distinction is crucial for understanding how the module integrates strategy with execution.

The other options misrepresent direct as operational or plan as mere execution or enforcement.

Exam trap

The trap here is equating direct with operational management or plan with enforcement, when direct is strategic governance and plan is about designing the approach.

Full explanation →

310

Multi-Selectmedium

An IT strategist is using ServiceNow Continual Improvement Management to govern improvement initiatives across the enterprise. Which TWO of the following capabilities are standard features of ServiceNow CIM that support tracking and reporting? (Choose two)

Select 2 answers

A.Automated physical badge reader integration for facilities management.

B.Continual Improvement Initiative records with structured lifecycle phases and task tracking.

C.Automatic bare-metal operating system provisioning and server racking.

D.Direct cryptographic packet sniffing for network intrusion detection.

E.Out-of-the-box reporting and dashboards displaying ROI, cost savings, and phase distribution.

AnswersB, E

Continual Improvement Initiative records provide the structured lifecycle phases and associated task tracking that ServiceNow CIM uses to move an initiative from identification through execution, satisfying the stem's requirement for standard tracking capability across enterprise improvement governance.

Why this answer

Option B is correct because ServiceNow Continual Improvement Management (CIM) is built around Continual Improvement Initiative records that carry structured lifecycle phases (such as Identify, Evaluate, Approve, Implement, and Review) plus associated tasks, which is exactly what enables governance and progress tracking of improvement efforts. Option E is correct because CIM ships with out-of-the-box reports and dashboards that surface metrics like ROI, cost savings, and phase distribution, directly supporting the tracking and reporting requirement in the scenario. The unmarked options do not belong: A (badge reader integration) is a facilities/physical security concern, C (bare-metal OS provisioning and racking) is data center automation outside CIM's scope, and D (cryptographic packet sniffing for intrusion detection) is a network security monitoring function, none of which are standard CIM capabilities.

Exam trap

The trap is that ServiceNow is a broad platform, so candidates may pick options that describe real ServiceNow capabilities from other modules (facilities, ITOM, security) and mistake them for CIM features, when CIM is specifically scoped to improvement initiative lifecycle and benefit reporting.

Full explanation →

311

Multi-Selectmedium

When applying 'Keep it simple and practical' to enterprise compliance and risk frameworks, which THREE practices should an organization adopt? (Choose three.)

Select 3 answers

A.Eliminating redundant approval steps that do not add measurable risk mitigation or business value.

B.Requiring manual spreadsheet logging for every single low-risk server ping.

C.Focusing on the absolute vital few controls that manage the greatest threats rather than trying to control everything equally.

D.Designing clear, straightforward policies that frontline staff can easily understand and execute.

E.Drafting 1,000-page governance manuals for every minor IT service desk procedure.

AnswersA, C, D

Redundant approval steps consume effort without reducing risk or adding value, so removing them directly embodies Keep it simple and practical. This satisfies the compliance scenario because the framework retains genuine risk mitigation while eliminating bureaucratic layers that slow delivery and dilute focus.

Why this answer

Option A is correct because 'keep it simple and practical' means removing redundant approval steps that add no measurable risk mitigation or business value, thereby reducing bureaucracy while preserving effective controls. Option C is correct because focusing on the vital few controls that address the greatest threats reflects a risk-based, prioritized approach rather than trying to control everything equally, which is impractical and dilutes effort. Option D is correct because clear, straightforward policies that frontline staff can easily understand and execute make compliance practical and more likely to be followed consistently.

Option B does not belong because requiring manual spreadsheet logging for every low-risk server ping is excessive, labor-intensive, and disproportionate to the minimal risk involved. Option E does not belong because drafting 1,000-page governance manuals for every minor IT service desk procedure is overly complex and contradicts the principle of simplicity and practicality.

Full explanation →

312

Multi-Selecthard

An organization is implementing a comprehensive KPI framework across its IT value streams. During the DPI review, the strategist identifies that several metrics are causing dysfunctional behaviors. Which THREE warning signs indicate that a KPI is poorly designed and driving negative behavior?

Select 3 answers

A.Teams artificially inflate ticket counts or close trivial tasks rapidly to boost productivity numbers.

B.Employees hide service failures or delays to avoid negative impact on their departmental scorecard.

C.The metric is based on objective, automated data collected directly from ServiceNow.

D.The metric trend is reviewed monthly in collaboration with business stakeholders.

E.A department meets all its local KPIs while the overall enterprise strategic goals fail.

AnswersA, B, E

Inflating ticket counts or rapidly closing trivial tasks shows the KPI rewards volume rather than outcomes. This is a classic dysfunctional metric, where staff optimise the number instead of resolving genuine issues, distorting reporting and degrading real service quality across the value stream.

Why this answer

Option A is correct because gaming a metric—such as artificially inflating ticket counts or rapidly closing trivial tasks—is a classic dysfunctional behavior showing the KPI rewards volume over value, which distorts true productivity. Option B is correct because hiding service failures or delays to protect a departmental scorecard indicates the metric drives fear and opacity rather than transparency and continuous improvement. Option E is correct because local KPI success while enterprise strategic goals fail demonstrates suboptimization, where the metric is misaligned with the broader value stream and organizational objectives.

Option C does not belong because objective, automated data from ServiceNow is a desirable KPI design characteristic, not a warning sign of dysfunction. Option D does not belong because monthly trend review with business stakeholders is a healthy governance practice that supports alignment, not a negative behavioral indicator.

Full explanation →

313

MCQhard

A multinational organization is standardizing its IT operating model across culturally diverse regions. A centralized change plan fails in a specific subsidiary. What fundamental OCM error was likely made?

A.The project team failed to use agile software development methodologies for the hardware rollout.

B.The corporate intranet site used an outdated cascading style sheet design.

C.The IT service desk ticketing tool lacked automated incident routing rules.

D.The change plan ignored local cultural nuances, communication norms, and regional stakeholder feedback.

AnswerD

Centralised change plans fail when they ignore local cultural context. This option names the specific omission: regional communication norms and stakeholder feedback were bypassed, so the subsidiary's cultural nuances were never accommodated, directly explaining the localised failure the stem describes.

Why this answer

A centralized change plan that fails in a specific subsidiary most likely ignored local cultural nuances, communication norms, and regional stakeholder feedback — a fundamental OCM error. Effective change management must adapt to local context rather than applying a one-size-fits-all corporate template.

Exam trap

The trap is attributing change failure to technical or tooling causes (methodology, intranet design, ticketing rules) when the scenario explicitly points to cultural and stakeholder factors in a multinational context.

How to eliminate wrong answers

Option A is wrong because the failure concerns cultural and stakeholder factors, not the choice of agile versus waterfall for a hardware rollout. Option B is wrong because an outdated CSS design on the intranet is a trivial technical detail unrelated to change adoption failure. Option C is wrong because missing automated incident routing rules in the ticketing tool is an operational tooling gap, not the root cause of a subsidiary rejecting a change plan.

Full explanation →

ITIL 4 Strategist: Direct, Plan and Improve (DPI) (DPI) (DPI) — Questions 301–313