MENU
Often it is a requirement to wrap a legacy system with a service. This is typically accomplished by encapsulating calls to the legacy system's Application Programming Interface (API) within the core logic of the service. Care must be taken to not expose details of the underlying API through the service contract as it may unintentionally couple the service consumer to the legacy system. Which pair of service-orientation principles directly addresses this concern? Select the correct answer.
Suggested Answer: A
Get Premium S90.03 Questions
as Interactive Web-Based Practice Test or PDF
Real Exam Format
Detailed Explanations
Instant Access
Get Your Practice Test
20 comments · newest first
LI
Lili
2 months ago
A seems to address the encapsulation issue perfectly!
BA
Barney
2 months ago
I’m not sure about D. Standardized contracts are crucial, but A feels more relevant.
EM
Emilio
2 months ago
I feel like A covers the main concern well.
SH
Sheron
2 months ago
I’m leaning towards D. Autonomy is important too.
EM
Emerson
2 months ago
I agree, A makes sense. Loose coupling is key!
RO
Rosalia
2 months ago
This question is tricky! I think A is the right choice.
TE
Tenesha
3 months ago
Definitely A, can't let the legacy system leak into the service!
CO
Corazon
3 months ago
I thought it was about Service Autonomy and Standardized Service Contract?
JA
Jade
3 months ago
Wait, are we sure about that? Seems like a tricky area.
VI
Vinnie
3 months ago
Totally agree, keeping things decoupled is key.
JA
Jaime
3 months ago
A) Service Loose Coupling, Service Abstraction is the right choice!
NO
Noah
4 months ago
Definitely A, can't let the legacy system leak into the service!
BR
Brianne
4 months ago
I thought it was about Service Autonomy and Standardized Service Contract?
WY
Wynell
4 months ago
Wait, are we sure about that? Seems like a tricky area.
LI
Lili
5 months ago
Totally agree, keeping things decoupled is key.
KE
Kendra
6 months ago
A) Service Loose Coupling, Service Abstraction is the right choice!
JU
Julie
6 months ago
I recall that service autonomy is crucial for independent operation, but I’m not confident about how it pairs with the others. D sounds plausible too.
AR
Argelia
6 months ago
I practiced a similar question about service principles, and I think loose coupling is definitely involved. A seems likely, but I’m hesitant about the second part.
MI
Mica
6 months ago
I’m not entirely sure, but I feel like service abstraction is key to hiding the legacy API details. So, A could be correct, but I’m also considering D.
CO
Corrie
7 months ago
I remember studying about how important it is to keep services decoupled from their underlying systems. I think A might be the right choice.