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

Arcitura Education Exam S90.08 Topic 5 Question 76 Discussion

Actual exam question for Arcitura Education's S90.08 exam
Question #: 76
Topic #: 5
[All S90.08 Questions]

Legacy systems often rely upon a combination of proprietary data models, proprietary data formats, and proprietary transport protocols. For this reason the Legacy Wrapper pattern is often used together with which of the following patterns?

Show Suggested Answer Hide Answer
Suggested Answer: A

Contribute your Thoughts:

King
24 days ago
The Legacy Wrapper pattern? More like the 'Duct Tape and Chewing Gum' pattern, am I right? Just try to make those old systems play nice with the new ones. At least the Service Broker can be the bouncer, keeping the legacy systems in line.
upvoted 0 times
Odette
3 days ago
A) Atomic Service Transaction
upvoted 0 times
...
...
Nieves
1 months ago
Service Broker, definitely. It's like using a translator to communicate with that weird uncle who still uses a rotary phone. The Legacy Wrapper is the interpreter, and the Service Broker is the cool middleman making it all work.
upvoted 0 times
Merissa
2 days ago
Service Messaging can also be helpful in ensuring smooth communication between different systems.
upvoted 0 times
...
Sabrina
9 days ago
I agree, Service Broker is essential for integrating legacy systems with modern ones.
upvoted 0 times
...
...
Shawnee
1 months ago
Hmm, I'm not sure about this one. Maybe the Atomic Service Transaction pattern could work, since it ensures data consistency even with legacy systems. But the Service Broker seems like the most likely choice here.
upvoted 0 times
Amber
4 days ago
I agree, the Service Broker pattern is commonly used with Legacy Wrapper.
upvoted 0 times
...
Kara
26 days ago
I think the Service Broker pattern is the best choice here.
upvoted 0 times
...
...
Letha
2 months ago
I think the correct answer is C) Service Broker. The Legacy Wrapper pattern is specifically designed to work with proprietary systems, and the Service Broker pattern is perfect for integrating those systems with modern architectures.
upvoted 0 times
Marguerita
23 days ago
I agree, the Legacy Wrapper pattern is great for working with proprietary systems.
upvoted 0 times
...
...
Shonda
2 months ago
The Legacy Wrapper pattern is often used with the Service Broker pattern to handle the proprietary nature of legacy systems. This makes sense, as the Service Broker can act as an intermediary between the legacy system and modern services.
upvoted 0 times
Fairy
21 days ago
B) Service Messaging
upvoted 0 times
...
Broderick
23 days ago
A) Atomic Service Transaction
upvoted 0 times
...
Eladia
26 days ago
B) Service Messaging
upvoted 0 times
...
Malcolm
1 months ago
A) Atomic Service Transaction
upvoted 0 times
...
...
Fletcher
2 months ago
I'm not sure, but I think D) Messaging Metadata could also be a possibility.
upvoted 0 times
...
Melodie
2 months ago
I agree with Alpha, Service Broker makes sense for legacy systems.
upvoted 0 times
...
Alpha
2 months ago
I think the answer is C) Service Broker.
upvoted 0 times
...

Save Cancel
az-700  pass4success  az-104  200-301  200-201  cissp  350-401  350-201  350-501  350-601  350-801  350-901  az-720  az-305  pl-300  

Warning: Cannot modify header information - headers already sent by (output started at /pass.php:70) in /pass.php on line 77