MENU
What does NOT happen due to a lack of architecture concerns?
Suggested Answer: B
Get Premium Architecture-Specialist-11 Questions
as Interactive Web-Based Practice Test or PDF
Real Exam Format
Detailed Explanations
Instant Access
Get Your Practice Test
24 comments · newest first
LA
Lacey
11 months ago
Not sure about C, seems like it could be managed better.
LE
Leanora
11 months ago
Wait, are we really saying poor abstraction isn't a big deal?
EV
Eva
11 months ago
Can't believe people underestimate tech debt!
RO
Rodolfo
12 months ago
I think D is the real issue here.
MA
Major
12 months ago
A is definitely a problem with legacy systems.
ME
Melynda
12 months ago
Poor service abstraction sounds like a direct result of not having clear architecture guidelines, so D seems like it could be a consequence as well.
OL
Oliva
1 year ago
I practiced a question similar to this, and I think unmanageable dependencies definitely arise from poor architecture, which makes me lean towards C as a possible answer.
GL
Glory
1 year ago
I'm not entirely sure, but I think tech debt is something that accumulates when architecture isn't prioritized, so B could be a valid option too.
LE
Leah
1 year ago
I remember discussing how inflexible legacy systems can really slow down business changes, so I think A might be a consequence of not addressing architecture concerns.
LA
Lanie
1 year ago
I'm feeling pretty confident about this one. A lack of architecture concerns would not lead to AI Mentor raising technical debt, since that's more of an architectural consideration. The other options all seem like valid consequences of not thinking about architecture, so I'm going to select B.
MA
Martina
1 year ago
Okay, I think I've got it. The question is asking what does NOT happen due to a lack of architecture concerns, so the answer must be the one that is not a consequence of poor architecture. I'm going to go with B, since the other options seem like clear issues that can arise from not considering architecture.
CA
Cathrine
1 year ago
This question seems straightforward - I think the answer is B, since a lack of architecture concerns would not lead to AI Mentor raising technical debt.
EL
Elza
1 year ago
Hmm, I'm a bit confused by this one. I'm not sure if the correct answer is B, since a lack of architecture concerns could also lead to the other issues mentioned, like inflexible legacy systems or unmanageable dependencies. I'll need to think this through carefully.
SH
Sherell
1 year ago
Hmm, I'm a bit unsure about this one. The options seem similar, but I'm not totally clear on the nuances between them. I'll need to re-read the question and think it through carefully.
RE
Remedios
1 year ago
I believe Proposal B is the right answer since its PI suggests a positive value. I feel like I saw a similar question on this in practice tests.
VI
Vincenza
1 year ago
I'm not totally sure about this one. I know the different contract types have specific characteristics, but I'm having trouble keeping them straight. I'll have to review my notes and try to reason through the options.
NG
Nguyet
3 years ago
Ooh, that's a good point, Melvin. I was actually leaning towards option A, 'Inflexible and slow-moving legacy systems,' as the one that doesn't necessarily happen. I mean, you can have inflexible legacy systems even with a solid architecture, right? It's just a pain to maintain those things, architecture or not.
ME
Melvin
3 years ago
Hmm, I'm not so sure about that, Adela. I was thinking that 'Poor service abstraction' (option D) might be the one that doesn't necessarily happen from a lack of architecture concerns. I mean, you could still have crummy service abstraction even if you have a decent architecture in place.
AD
Adela
3 years ago
Hah, tell me about it, Audra. This is why we need a 'none of the above' option sometimes. Or maybe a 'all of the above' option, just to keep us on our toes. *chuckles*
HA
Halina
3 years ago
D) Poor service abstraction : Business concepts not correctly isolated, business rules tend to be spread over different systems and little to no code reuse
LU
Lucina
3 years ago
C) Unmanageable dependencies : System not isolated from each other. Updating or replacing a system has a cascade/snowball effect on other systems
CH
Chau
3 years ago
B) Tech Debt : AI Mentor will raise architectural tech debt such as cyclic dependency and side to side dependency
FR
Freeman
3 years ago
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
AU
Audra
3 years ago
Ugh, you guys are making my head spin. This is why I hate multiple-choice questions - there are always so many viable options! *sighs* I guess I'll just have to go with my gut on this one and hope for the best.