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

OutSystems Exam Architecture-Specialist-11 Topic 1 Question 5 Discussion

Actual exam question for OutSystems's Architecture-Specialist-11 exam
Question #: 5
Topic #: 1
[All Architecture-Specialist-11 Questions]

Which is not a reason you should use Architecture Canvas?

Show Suggested Answer Hide Answer
Suggested Answer: A

Contribute your Thoughts:

Viola
8 days ago
Haha, Hubert, you're killing me! But I actually think option D, minimizing the impact of changes, is the correct answer here. I mean, if you're trying to minimize the impact of changes, why would you use a tool that's all about promoting abstraction and loose coupling? Seems kind of counterintuitive to me.
upvoted 0 times
...
Hubert
8 days ago
You guys are getting too serious! I think the real reason you shouldn't use the Architecture Canvas is option C - it promotes abstraction of reusable services. Because who needs reusable services when you can just copy-paste code everywhere, am I right? *wink wink*
upvoted 0 times
...
Aleta
9 days ago
I'm not so sure about that, Angelyn. I think option B, optimizing lifecycle independence, is actually the reason you shouldn't use the Architecture Canvas. Isn't the whole point of the Canvas to promote reusability and minimize the impact of changes?
upvoted 0 times
...
Angelyn
10 days ago
Hmm, this is a tricky one. I'm not entirely sure about the correct answer, but I think option A might be a good one. Promoting segregation and loose coupling of services seems like a pretty important reason to use the Architecture Canvas, doesn't it?
upvoted 0 times
...

Save Cancel