MENU
Which is not a reason you should use Architecture Canvas?
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
26 comments · newest first
LI
Lizette
11 months ago
B is also a good point, but not the main one.
BR
Britt
11 months ago
A and C are definitely reasons to use it!
PE
Pedro
11 months ago
Wait, are we sure about that?
ER
Erasmo
12 months ago
Totally agree, D doesn't fit.
DE
Deandrea
12 months ago
I think D is the right answer.
PA
Paulina
12 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.
IS
Isadora
1 year 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.
YV
Yvonne
1 year ago
I remember practicing a question about lifecycle independence, and I feel like B might be a reason to use it, not the opposite.
BE
Beata
1 year 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.
RO
Roosevelt
1 year 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!
LO
Loise
1 year 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.
JO
Jodi
1 year 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.
LA
Laticia
1 year 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.
BE
Benedict
1 year 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.
AL
Alex
1 year 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.
VI
Viola
3 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.
HU
Hubert
3 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*
AL
Alfreda
3 years ago
Exactly! It's all about efficiency and scalability in the end
DO
Dominic
3 years ago
True, copy-pasting code can lead to a lot of issues later on. Better to use reusable services
BR
Brandee
3 years ago
Yeah, I get what you mean. Reusable services can save a lot of time and effort in the long run
MA
Marylin
3 years ago
Haha, I see where you're coming from with that! But I think option C still has its benefits
LI
Linwood
3 years ago
D) Minimizes impact of changes
CH
Charlene
3 years ago
B) Optimizes lifecycle independence
MO
Mohammad
3 years ago
A) Promotes segregation and loose coupling of services
AL
Aleta
3 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?
AN
Angelyn
3 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?