Deal of The Day! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

PeopleCert ITIL-4-Foundation Exam - Topic 2 Question 73 Discussion

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

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

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


Get Premium ITIL-4-Foundation Questions as Interactive Web-Based Practice Test or PDF Real Exam Format Detailed Explanations Instant Access Get Your Practice Test
28 comments · newest first
JE
Jenifer 11 months ago
A keeps things efficient and straightforward!
TO
Tonja 11 months ago
D is too limiting, we need flexibility.
RU
Rueben 11 months ago
Surprised that anyone would choose C, that's just overkill!
TE
Tegan 11 months ago
I disagree, B makes more sense to ensure value.
VI
Vicky 12 months ago
A is definitely the way to go!
AR
Art 12 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.
QU
Queen 12 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.
MA
Maryrose 1 year 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?
AD
Adell 1 year ago
I think option A makes the most sense since it emphasizes adding controls only when necessary. That aligns with keeping things simple.
LA
Laquanda 1 year 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.
HE
Herschel 1 year 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.
NI
Nikita 1 year ago
Personally, I'm a fan of the 'keep it simple, silly' approach. A all the way!
CO
Corinne 1 year ago
↳ replying to Nikita
Launa: It just makes everything easier to manage
LA
Launa 1 year ago
↳ replying to Nikita
User 2: Definitely, keeping it simple is key
JE
Jerry 1 year ago
↳ replying to Nikita
User 1: I agree, A) Only add controls and metrics when they are needed
MA
Ma 1 year ago
D sounds too restrictive. What about controls that aren't strictly for compliance but still provide value? I'd go with A.
LE
Leandro 1 year ago
↳ replying to Ma
I see your point, but D does have its merits in ensuring compliance. It's a tough choice.
KR
Kris 1 year ago
↳ replying to Ma
I think B could work too, designing first and then removing what's not necessary.
RO
Rossana 1 year ago
↳ replying to Ma
I agree, A seems like the best option. Only adding what is needed makes sense.
LI
Lina 1 year ago
Hah, C is like the kitchen sink approach. Adding controls one by one until the whole system is bloated? No thanks!
JE
Jerry 1 year ago
↳ replying to Lina
D) Only add controls and metrics that are required for compliance
LI
Lizbeth 1 year ago
↳ replying to Lina
B) Design controls and metrics first, then remove those not adding value
FA
Fairy 1 year ago
↳ replying to Lina
A) Only add controls and metrics when they are needed
HU
Huey 1 year 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.
NO
Novella 1 year ago
Option A definitely aligns with the 'keep it simple and practical' principle. Why add extra controls and metrics if they're not needed?
DA
Daniel 2 years 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.
UL
Ula 2 years ago
I disagree, I believe B) Design controls and metrics first, then remove those not adding value is the way to go.
AB
Abel 2 years ago
I think the correct approach is A) Only add controls and metrics when they are needed.
0/2000 characters

Save Cancel