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 Specialist Create Deliver and Support Exam - Topic 8 Question 11 Discussion

Actual exam question for PeopleCert's ITIL 4 Specialist Create Deliver and Support exam
Question #: 11
Topic #: 8
[All ITIL 4 Specialist Create Deliver and Support Questions]

In which circumstances should an organization buy, rather than build, software?

Show Suggested Answer Hide Answer
Suggested Answer: A

Contribute your Thoughts:

0/2000 characters
Magdalene
4 months ago
Really? I’m surprised anyone would choose D, seems risky!
upvoted 0 times
...
Lajuana
4 months ago
I disagree, B makes sense too for regulated industries.
upvoted 0 times
...
Kindra
4 months ago
A is the way to go, no need to reinvent the wheel.
upvoted 0 times
...
Catherin
4 months ago
C is a good point, changing requirements can be tough!
upvoted 0 times
...
Flo
5 months ago
Definitely A, if it's widely available, just buy it!
upvoted 0 times
...
Beula
5 months ago
D seems tricky; if users need a lot of customization, wouldn't that lean more towards building rather than buying?
upvoted 0 times
...
Pamella
5 months ago
I practiced a question similar to this, and I feel like C could be a reason to build software instead of buying it, especially if requirements are changing a lot.
upvoted 0 times
...
Mona
5 months ago
I'm not entirely sure, but I remember something about regulated industries needing custom solutions, so maybe B isn't the best choice for buying.
upvoted 0 times
...
Emogene
5 months ago
I think option A makes sense since buying software that's standardized can save time and resources.
upvoted 0 times
...
Britt
6 months ago
Ah, this is a good one. I think the key is to consider the organization's specific needs and constraints. The options give a nice set of scenarios to evaluate.
upvoted 0 times
...
Annice
6 months ago
Okay, I've got a strategy here. I'll start by identifying the key factors that would drive a buy vs. build decision, then match those up to the options provided.
upvoted 0 times
...
Noah
6 months ago
Hmm, I'm a bit unsure about this one. I'll need to think through the tradeoffs between standardized features, regulatory requirements, changing needs, and customization requirements.
upvoted 0 times
...
Kanisha
6 months ago
This seems like a straightforward question about when to buy vs. build software. I'll need to carefully consider the factors mentioned in the options.
upvoted 0 times
...
Stefan
7 months ago
Regulated industries need to be extra cautious, so option B is probably the safest bet.
upvoted 0 times
...
Franchesca
7 months ago
In that case, it might be better to build the software to ensure it can adapt to the changing needs of the organization.
upvoted 0 times
...
Reita
8 months ago
But what if the organization is rapidly expanding and the requirements are constantly changing?
upvoted 0 times
...
Rosio
8 months ago
I agree with Jules. It can save time and resources to purchase rather than build in that case.
upvoted 0 times
...
Loise
8 months ago
Option A seems like the most logical choice. Why reinvent the wheel when a standardized solution is available?
upvoted 0 times
Alex
7 months ago
A) The software is widely available and its features are standardized across most organizations
upvoted 0 times
...
Virgina
7 months ago
A) The software is widely available and its features are standardized across most organizations
upvoted 0 times
...
...
Jules
8 months ago
I think in circumstances where the software is widely available and standardized, it makes sense to buy.
upvoted 0 times
...

Save Cancel