New Year Sale 2026! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions
Mail Us support@pass4success.com
Location US
Mob_nav_barsMENU

PeopleCert ITIL 4 Foundation Exam - Topic 2 Question 73 Discussion

Actual exam question for PeopleCert's ITIL 4 Foundation exam
Question #: 73
Topic #: 2
[All ITIL 4 Foundation Questions]

Which approach is CORRECT when applying the guiding principle 'keep it simple and practical'?

Show Suggested Answer Hide Answer
Suggested Answer: D

Don't start from scratch and build something new without considering what you already have. It's almost always better to improve what you currently have than to throw it all away and start again, although you must also be able to recognise when a complete replacement is, in fact, needed.

Not only is this approach less wasteful than starting from scratch -- because it preserves value that you already have -- but it also helps you to keep your people on board. They're much more likely to support the changes you need if their previous contributions have been appropriately valued.

Don't rely on metrics and reports to tell you what the current situation is. When you carry out an assessment you should observe what is happening for yourself, and just use the metrics to support your observations.

https://www.sysaid.com/blog/itil/the-7-guiding-principles-of-itil-4-practical-advice-to-help-you-make-decisions


by Annelle at Aug 05, 2023, 05:48 AM

Limited Time Offer

25%

Off

Get Premium ITIL 4 Foundation Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

0/2000 characters
Submit Cancel
Jenifer
3 months ago
A keeps things efficient and straightforward!
upvoted 0 times
...
Tonja
3 months ago
D is too limiting, we need flexibility.
upvoted 0 times
...
Rueben
4 months ago
Surprised that anyone would choose C, that's just overkill!
upvoted 0 times
...
Tegan
4 months ago
I disagree, B makes more sense to ensure value.
upvoted 0 times
...
Vicky
4 months ago
A is definitely the way to go!
upvoted 0 times
...
Art
4 months ago
I vaguely recall something about adding controls one by one, which sounds like option C. But that seems like it could complicate things too much.
upvoted 0 times
...
Queen
4 months ago
I feel like D could be a trap. Just because something is required for compliance doesn't mean it's practical or simple.
upvoted 0 times
...
Maryrose
5 months ago
I'm not sure about A though; I remember a practice question where they suggested designing first and then trimming down. Maybe that's option B?
upvoted 0 times
...
Adell
5 months ago
I think option A makes the most sense since it emphasizes adding controls only when necessary. That aligns with keeping things simple.
upvoted 0 times
...
Laquanda
5 months ago
This question is testing my understanding of access management principles. I'll carefully read through each option and think about how they relate to authorization specifically.
upvoted 0 times
...
Herschel
5 months ago
Hmm, I'm a bit confused on this one. Do we need to create a separate app for the internal staff or can we just give them access to the main org? I'll have to think through the requirements for each persona carefully.
upvoted 0 times
...
Nikita
10 months ago
Personally, I'm a fan of the 'keep it simple, silly' approach. A all the way!
upvoted 0 times
Corinne
9 months ago
Launa: It just makes everything easier to manage
upvoted 0 times
...
Launa
9 months ago
User 2: Definitely, keeping it simple is key
upvoted 0 times
...
Jerry
9 months ago
User 1: I agree, A) Only add controls and metrics when they are needed
upvoted 0 times
...
...
Ma
10 months ago
D sounds too restrictive. What about controls that aren't strictly for compliance but still provide value? I'd go with A.
upvoted 0 times
Leandro
9 months ago
I see your point, but D does have its merits in ensuring compliance. It's a tough choice.
upvoted 0 times
...
Kris
9 months ago
I think B could work too, designing first and then removing what's not necessary.
upvoted 0 times
...
Rossana
10 months ago
I agree, A seems like the best option. Only adding what is needed makes sense.
upvoted 0 times
...
...
Lina
10 months ago
Hah, C is like the kitchen sink approach. Adding controls one by one until the whole system is bloated? No thanks!
upvoted 0 times
Jerry
9 months ago
D) Only add controls and metrics that are required for compliance
upvoted 0 times
...
Lizbeth
9 months ago
B) Design controls and metrics first, then remove those not adding value
upvoted 0 times
...
Fairy
9 months ago
A) Only add controls and metrics when they are needed
upvoted 0 times
...
...
Huey
10 months ago
I disagree, I think B is the way to go. Design everything first, then trim the fat. That ensures you have a solid foundation to work from.
upvoted 0 times
...
Novella
10 months ago
Option A definitely aligns with the 'keep it simple and practical' principle. Why add extra controls and metrics if they're not needed?
upvoted 0 times
...
Daniel
11 months ago
I see both points, but I think D) Only add controls and metrics that are required for compliance makes the most sense in this situation.
upvoted 0 times
...
Ula
11 months ago
I disagree, I believe B) Design controls and metrics first, then remove those not adding value is the way to go.
upvoted 0 times
...
Abel
11 months ago
I think the correct approach is A) Only add controls and metrics when they are needed.
upvoted 0 times
...

Save Cancel