MENU
Which of the following is NOT a benefit of having well-defined application architecture?
Suggested Answer: A
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
25 comments · newest first
TR
Trina
11 months ago
Supports planning is essential for any project!
FR
France
11 months ago
Wait, are we sure poor service abstraction is a "benefit"?
PE
Pearly
11 months ago
Totally agree, risk reduction is key!
JO
Johnson
12 months ago
I think reducing costs is a huge benefit.
LI
Lili
12 months ago
Poor service abstraction is definitely a downside!
GA
Gabriele
12 months ago
I’m a bit confused; I thought all of these were benefits, but I guess poor service abstraction could be seen as a negative.
ST
Stefany
1 year ago
I think we had a practice question about architecture benefits, and I’m leaning towards A as the one that doesn’t fit.
ER
Erinn
1 year ago
I’m not entirely sure, but I feel like reducing costs is definitely a benefit, so it can't be the right choice.
TH
Therese
1 year ago
I remember discussing how poor service abstraction can actually be a drawback, so I think that might be the answer.
TO
Tomoko
1 year ago
I think I've got it. The key is to identify the benefits, and then choose the one that doesn't fit. Supports planning sounds like a good benefit, so that's probably not the answer.
LI
Lina
1 year ago
Wait, I'm a bit confused. Aren't reduced costs and reduced risk supposed to be benefits? I'm not sure about this one.
CR
Craig
1 year ago
Okay, let's see. Poor service abstraction doesn't sound like a benefit, so that might be the answer. I'll mark that one for now.
TO
Tomoko
1 year ago
Hmm, this one's a bit tricky. I'll need to think through the benefits of a well-defined application architecture to figure out which one is not a benefit.
BE
Bette
1 year ago
Hmm, I'm a bit unsure about this one. I need to carefully read through the details and think about how the different organizational elements might be involved.
TE
Tenesha
1 year ago
Okay, I think the key here is that the firewall needs to maintain information about established communication sessions. That sounds like it's describing a stateful firewall.
CA
Carry
1 year ago
I've got this! Variables and Datastores are the two objects that can be dragged to a Mapping.
AL
Alyce
1 year ago
Hmm, I'm not sure about this one. The question mentions wanting to lower costs without any performance implications, so I'm not sure if preemptible VMs (option C) would be the right choice. I'll have to think this through carefully.
JU
Junita
3 years ago
Exactly, I was thinking the same thing. This question is trying to trick us, but I'm confident A is the right answer. Unless, of course, the architects were 'abstractly challenged' when designing the system.
WE
Wendell
3 years ago
Definitely, a good architecture helps reduce costs by improving efficiency and maintainability. And it also helps support planning and risk mitigation, so B and C seem like the benefits here.
TA
Tammara
3 years ago
I agree with you there. A well-designed architecture should provide a clear separation of concerns and promote modularity, which is the opposite of poor service abstraction.
LA
Laticia
3 years ago
Hmm, this is a tricky one. I'm pretty sure the correct answer is A) Poor service abstraction. A well-defined architecture should actually improve service abstraction, not make it poor.
DI
Dick
3 years ago
A) Poor service abstraction
BE
Bernadine
3 years ago
D) Supports planning
CR
Craig
3 years ago
C) Reduces risk
CA
Cammy
3 years ago
B) Reduces costs