Haha, I bet the person who wrote this question has had to deal with some pretty nasty legacy systems in their time. A) Inflexible and slow-moving legacy systems is definitely the way to go here.
A) Inflexible and slow-moving legacy systems : adapting legacy systems to business changes may be difficult. Changes in complex and inflexible systems can take a long time
I'm going with D) Poor service abstraction. If the business concepts are not properly isolated, it can lead to a lot of duplicate code and make the system harder to maintain and update.
I think the correct answer is B) Tech Debt. A lack of architecture concerns can definitely lead to the accumulation of technical debt, which can slow down future development and make the system less flexible.
I think A) Inflexible and slow-moving legacy systems is the answer. Lack of architecture concerns can lead to systems that are difficult to adapt to changes.
upvoted 0 times
...
Log in to Pass4Success
Sign in:
Report Comment
Is the comment made by USERNAME spam or abusive?
Commenting
In order to participate in the comments you need to be logged-in.
You can sign-up or
login
Cristina
1 months agoTheron
9 days agoSelma
12 days agoHershel
13 days agoEmily
2 months agoLili
2 months agoLachelle
3 days agoVilma
5 days agoLinette
9 days agoJin
1 months agoPaola
2 months agoLourdes
2 months agoHildegarde
2 months ago