MENU
The application of the Legacy Wrapper pattern typically results in:
Suggested Answer: C
Get Premium S90.08 Questions
as Interactive Web-Based Practice Test or PDF
Real Exam Format
Detailed Explanations
Instant Access
Get Your Practice Test
34 comments · newest first
DI
Dion
11 months ago
A and B don’t really make sense in this context.
GR
Gregoria
11 months ago
Definitely C, it keeps things clean for the consumer.
FR
Francesco
11 months ago
Wait, isn't it surprising that we can completely decouple like that?
VI
Virgie
11 months ago
I disagree, I think A is the right answer.
BI
Billi
12 months ago
C is spot on! No coupling to the legacy system.
AN
Annalee
12 months ago
I thought the point of the wrapper was to keep the service consumer from needing to know about the legacy system, so I’m leaning towards option C as well.
PA
Page
1 year ago
I feel like I saw something about service contracts in the context of wrappers, but I can't recall if it was about coupling or not.
KI
Kiera
1 year ago
I remember practicing a question about how wrappers help isolate legacy systems from consumers. Maybe it's option C?
AL
Aleta
1 year ago
I think the Legacy Wrapper pattern is supposed to minimize coupling, but I'm not sure which option it specifically addresses.
ST
Stefania
1 year ago
I'm not entirely sure about this one. The question is asking about the typical result of applying the Legacy Wrapper pattern, but I'm not confident which type of coupling it's meant to address. I'll have to make an educated guess and go with option B.
AU
Augustine
1 year ago
Okay, I remember learning about the Legacy Wrapper pattern in class. I believe the key benefit is that it allows the wrapper service logic to be independent of the legacy system, so I'll select option A.
LA
Laquita
1 year ago
Hmm, I'm a bit confused by this question. The Legacy Wrapper pattern is supposed to reduce coupling, but I'm not sure if it's the service consumer or the wrapper service logic that should be decoupled from the legacy system. I'll have to think this through carefully.
LO
Loreta
1 year ago
This question seems straightforward, I think the Legacy Wrapper pattern is meant to decouple the wrapper service logic from the legacy system, so I'll go with option C.
GR
Gregoria
1 year ago
This seems like a straightforward question about integrating data from different sources. I'll need to think through the pros and cons of each option to determine the best approach.
AN
Anissa
1 year ago
This seems like a straightforward privacy question. I'd start by reviewing the options and thinking through the logical order of steps.
UN
Una
1 year ago
I remember discussing how to enable encryption for the RDS PostgreSQL, but I'm not clear if it can be done without downtime.
YO
Yolando
1 year ago
I'm not entirely sure about this one. The question is a bit ambiguous, and I'll need to consider the potential outcomes more closely.
CO
Colene
1 year ago
Hmm, I'm a little unsure about this one. I know there are a few different authentication methods used in HTTP, but I can't quite remember the details of each one. I'll have to think this through carefully.
AL
Alesia
2 years ago
D is the correct answer. The wrapper service should have no direct coupling to the service contract, allowing it to be more easily replaced or updated.
EM
Emerson
2 years ago
Haha, I bet the answer is none of the above! The Legacy Wrapper pattern is just a fancy way of saying 'duct tape and bubble gum'.
SA
Salley
2 years ago
A and C seem like the right options to me. The wrapper should decouple the service logic from the legacy system and the consumer from the legacy system.
SH
Shannan
2 years ago
I think A and C are the best choices. It ensures a clean separation of concerns.
RO
Ronnie
2 years ago
Definitely, A and C are the way to go. It helps maintain flexibility and ease of future changes.
WI
Willodean
2 years ago
I agree, A and C make sense. Decoupling is key in the Legacy Wrapper pattern.
VI
Viola
2 years ago
It's important to ensure that the service logic and consumer are not tightly coupled to the legacy system.
TA
Taryn
2 years ago
Definitely, that's the key benefit of using the Legacy Wrapper pattern.
BE
Bernardine
2 years ago
I agree, A and C make sense. It's all about decoupling.
LO
Louvenia
2 years ago
I think the correct answer is C. The Legacy Wrapper pattern is designed to encapsulate the legacy system and hide its complexity from the service consumer.
TH
Thurman
2 years ago
C) no coupling of the service consumer to the legacy system encapsulated by the wrapper service
KE
Kenneth
2 years ago
A) no coupling of the wrapper service logic to the legacy system
SH
Shonda
2 years ago
I think option A is also correct, as it talks about no coupling of the wrapper service logic to the legacy system.
GI
Gianna
2 years ago
I believe the answer is C, as it mentions no coupling of the service consumer to the legacy system.
VI
Vivienne
2 years ago
I agree, it helps in reducing coupling between systems.
NA
Naomi
2 years ago
I think the Legacy Wrapper pattern is really useful.