Deal of The Day! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25

- Free Preparation Discussions

OutSystems Architecture-Specialist-11 Exam - 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?

APromotes segregation and loose coupling of services

BOptimizes lifecycle independence

CPromotes abstraction of reusable services

DMinimizes impact of changes

Show Suggested Answer

Suggested Answer: A

by Janine at Nov 27, 2023, 01:42 AM

Limited Time Offer

25%

Off

Get Premium Architecture-Specialist-11 Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

Submit Cancel

Lizette

7 months ago

B is also a good point, but not the main one.

upvoted 0 times

...

Britt

7 months ago

A and C are definitely reasons to use it!

upvoted 0 times

...

Pedro

7 months ago

Wait, are we sure about that?

upvoted 0 times

...

Erasmo

7 months ago

Totally agree, D doesn't fit.

upvoted 0 times

...

Deandrea

7 months ago

I think D is the right answer.

upvoted 0 times

...

Paulina

7 months ago

I feel like minimizing the impact of changes is definitely a goal of Architecture Canvas, so D could be the answer. But I need to think more about it.

upvoted 0 times

...

Isadora

8 months ago

I’m a bit confused about C and D. I thought both were benefits of using Architecture Canvas, but now I’m second-guessing myself.

upvoted 0 times

...

Yvonne

8 months ago

I remember practicing a question about lifecycle independence, and I feel like B might be a reason to use it, not the opposite.

upvoted 0 times

...

Beata

8 months ago

I think Architecture Canvas is supposed to help with loose coupling, so maybe A is the right answer? But I'm not entirely sure.

upvoted 0 times

...

Roosevelt

8 months ago

I've got this! The Architecture Canvas is designed to minimize the impact of changes and promote abstraction of reusable services. So the answer that goes against those principles would be A - Promotes segregation and loose coupling. Easy peasy!

upvoted 0 times

...

Loise

8 months ago

Okay, let's see. The Architecture Canvas is all about creating a cohesive, well-integrated architecture, right? So I'm pretty sure the answer can't be anything related to segregation or loose coupling. I'm leaning towards C or D as the correct answer.

upvoted 0 times

...

Jodi

8 months ago

Hmm, I'm a bit unsure about this one. I know the Architecture Canvas is supposed to help with things like optimizing lifecycle independence and promoting reusable services, but I'm not totally clear on how it relates to segregation and coupling. I'll have to think this through carefully.

upvoted 0 times

...

Laticia

8 months ago

This question seems straightforward. I think the answer is A - Promotes segregation and loose coupling of services, since that's the opposite of what the Architecture Canvas is supposed to do.

upvoted 0 times

...

Benedict

8 months ago

I think option B is the most likely answer here. "The ability of one ESM Server to take over for another" sounds like it could be related to "Service Protection" in the context of the Traps product. But I'm not 100% sure, so I'll double-check the other options before making a final decision.

upvoted 0 times

...

Alex

8 months ago

Wait, I'm confused. The question talks about Synchronized Data Sources, but none of the API options seem directly related to that. I'm not sure if the REST API is the right choice here. Maybe I should review the Salesforce and Marketing Cloud documentation to better understand the integration options.

upvoted 0 times

...

Viola

2 years 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

2 years 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

Alfreda

2 years ago

Exactly! It's all about efficiency and scalability in the end

upvoted 0 times

...

Dominic

2 years ago

True, copy-pasting code can lead to a lot of issues later on. Better to use reusable services

upvoted 0 times

...

Brandee

2 years ago

Yeah, I get what you mean. Reusable services can save a lot of time and effort in the long run

upvoted 0 times

...

Marylin

2 years ago

Haha, I see where you're coming from with that! But I think option C still has its benefits

upvoted 0 times

...

Linwood

2 years ago

D) Minimizes impact of changes

upvoted 0 times

...

Charlene

2 years ago

B) Optimizes lifecycle independence

upvoted 0 times

...

Mohammad

2 years ago

A) Promotes segregation and loose coupling of services

upvoted 0 times

...

...

Aleta

2 years 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

2 years 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

...