Free PeopleCert ITIL v4 Foundation Actual Exam Questions

C imo, practices are part of the service value chain steps, not a standalone SVS component. The rest (guiding principles, governance, four dimensions) fit better within the system framework.

A imo, the guiding principles are definitely a key part of the SVS, setting culture and behavior. The four dimensions are more like an overarching model, not a direct system component.

Maybe D doesn’t fit because it’s too positive and doesn’t capture any trickery or hidden problems. A seems off since sharing other customers’ data would be a privacy issue and unrelated to the watermelon concept. C sounds like it’s about shifting targets, but watermelon is about how things look good on the outside while hiding issues inside. So B still feels right since it talks about internal metrics painting a rosy picture even if customers aren’t happy. That mismatch is classic watermelon SLA territory.

Makes sense that it’s about hiding real issues inside nice-looking reports, so B fits well with the “watermelon” idea of green outside, red inside. Definitely not A or D. B it is.

It’s C for me, since service management isn’t just about capabilities but also the ongoing collaboration between provider and consumer to create value together. That joint activity focus feels key.

C imo, since service management involves the joint activities between provider and consumer.

It’s A too, since even the best tech won't protect data if people don’t follow security policies. So, the human factor is key for privacy and security.

Option B, since security measures are usually embedded in IT systems and data handling.

I’d rule out A and D since ‘value chain activities’ sound more like broad categories, not detailed steps. So between B and C, could the register be more about tracking rather than defining steps?

Probably C here. A ‘model’ usually means a structured process or set of steps, which fits better than just a list (register) or an activity name.

Probably B since assets cover all physical and digital supports, not just CIs.

Makes sense to stick with D here since configuration items are specifically what the practice tracks—not all assets or suppliers. D

It’s A for me. From what I understand, value streams map out the entire flow from demand to value realization, so they should cover all the main value chain activities. B seems too narrow since value streams are supposed to visualize the entire process, not just specific scenarios. C is definitely off because including all 34 ITIL practices in every value stream doesn’t seem realistic or necessary. D is tricky, but I don’t think suppliers or partners are mandatory in every single value stream—some might be completely internal.

I’m with option B here. Value streams are about specific outcomes, so it makes sense they’re designed for particular scenarios instead of a one-size-fits-all approach. The others seem off because not every value stream needs all 34 ITIL practices (C) or must involve partners (D), and definitely not all six value chain activities every time (A).

It’s A for me. Test definitely comes before operate since you want to catch issues before the software goes live. Plus, design has to happen before develop to know what you’re building. B and D both put things in a weird order that doesn’t flow logically—like retiring before you even start or testing right after ideation. The classic lifecycle always starts with ideation, moves through design and build, then testing, deployment, operation, and finally retirement. So A just fits best with how these phases usually work in practice.

Looks like the right order should start with Ideation and end with Retire. Testing usually happens right after development and before deployment, so A makes the most sense to me. Does anyone else think testing comes after deploy, like in D?

Never thought about it like this, but change management (A) does audit alterations that might trigger breaches, so it could help spot issues early, not just access control. A

I see why C might be the go-to since it’s all about permissions and access control. But I’m thinking A could also fit because change management tracks and audits changes that might cause security issues, potentially triggering incident detection. Still, access management (C) sounds more hands-on with catching breaches right when they happen. So I’d trust C for this one.

Probably C, since budgeting is about planning and managing money ahead.

Yeah, I’m with you on C. Budgeting is the only one that clearly involves both predicting future income/expenditure and controlling it. Governance is more about overall rules and policies, not the financial specifics, so B doesn’t fit as well. Charging and accounting are more about recording or allocating costs rather than planning ahead.

It’s D here because the question is about deciding which parts to keep based on their value contribution, which means simplifying and focusing on what’s really useful. While C looks at the big system, this is more about cutting down to essentials and avoiding unnecessary complexity, which matches “keep it simple and practical” better than the others. The focus isn’t just on seeing the whole but on making sure the retained parts are practical and actually add value without overcomplicating things.

A/D? I’m leaning towards A because "progress iteratively with feedback" often involves assessing current steps to see what works and what doesn’t, which ties into keeping valuable parts. D is about simplicity but might not focus on analyzing existing components specifically. So A seems to capture the idea of evaluating parts through feedback cycles better than D or even C.

Maybe D on this one. While the process owner sets up the framework, the continual service improvement manager is usually the one who defines and implements specific metrics to track how well changes are working over time. They focus on measuring effectiveness and driving improvements, which fits with setting up those success indicators. The change advisory board (B) and service owner (C) are more about approvals and operational aspects, so they’re less likely to define the actual metrics. So it makes sense if D handles the metrics part since it aligns with continual improvement responsibilitie

It’s A because the change management process owner sets the standards and framework for the process, which includes deciding how to measure success. The continual service improvement manager works with those metrics but doesn’t define them initially.

A imo, supplier management is the only one really focused on building stronger external partnerships. The others deal more with internal controls or processes, not fostering collaboration with outside parties.

I get why A feels right because managing suppliers is about partnerships. But what if D fits too? Service configuration management tracks relationships between components, which could mean closer ties within the service ecosystem itself. Not just external collaboration but internal too. Could that count as creating more collaborative relationships? Wondering if the question means collaboration inside the org or with external parties.

C vs B? I’m going with C because the register acts like a backlog for improvement ideas, keeping them all documented and organized. B sounds a bit too hands-on, like it’s managing the whole improvement process, which I think is separate from just registering ideas. The register’s more about collecting and tracking suggestions over time rather than providing a full structure for implementation.

C imo. It’s not about approving or managing resources, that’s more like change management. The register’s focus is to keep improvement ideas in one place over time.

A/C? Release management should have some control over authorizing changes before pushing them live, not just moving software. So it might cover both giving the green light and deployment steps.

It’s B. Release management isn’t just about the physical move (which is C), it’s also about ensuring the new features actually get rolled out and become usable for users. Moving software is part of it, but the main goal is making those features available in the environment where they can be accessed. So, B captures the broader purpose better than just moving software.