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 S90.03 Exam - Topic 5 Question 124 Discussion

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.
A) Service Loose Coupling, Service Abstraction
B) Service Statelessness, Service Autonomy
C) Service Loose Coupling, Service Statelessness
D) Service Autonomy, Standardized Service Contract

Arcitura Education S90.03 Exam - Topic 5 Question 124 Discussion

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

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.

Show Suggested Answer Hide Answer
Suggested Answer: A

Contribute your Thoughts:

0/2000 characters
Barney
1 day ago
I’m not sure about D. Standardized contracts are crucial, but A feels more relevant.
upvoted 0 times
...
Emilio
7 days ago
I feel like A covers the main concern well.
upvoted 0 times
...
Sheron
12 days ago
I’m leaning towards D. Autonomy is important too.
upvoted 0 times
...
Emerson
17 days ago
I agree, A makes sense. Loose coupling is key!
upvoted 0 times
...
Rosalia
22 days ago
This question is tricky! I think A is the right choice.
upvoted 0 times
...
Tenesha
27 days ago
Definitely A, can't let the legacy system leak into the service!
upvoted 0 times
...
Corazon
1 month ago
I thought it was about Service Autonomy and Standardized Service Contract?
upvoted 0 times
...
Jade
1 month ago
Wait, are we sure about that? Seems like a tricky area.
upvoted 0 times
...
Vinnie
1 month ago
Totally agree, keeping things decoupled is key.
upvoted 0 times
...
Jaime
2 months ago
A) Service Loose Coupling, Service Abstraction is the right choice!
upvoted 0 times
...
Noah
2 months ago
Definitely A, can't let the legacy system leak into the service!
upvoted 0 times
...
Brianne
2 months ago
I thought it was about Service Autonomy and Standardized Service Contract?
upvoted 0 times
...
Wynell
2 months ago
Wait, are we sure about that? Seems like a tricky area.
upvoted 0 times
...
Lili
4 months ago
Totally agree, keeping things decoupled is key.
upvoted 0 times
...
Kendra
4 months ago
A) Service Loose Coupling, Service Abstraction is the right choice!
upvoted 0 times
...
Julie
4 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.
upvoted 0 times
...
Argelia
5 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.
upvoted 0 times
...
Mica
5 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.
upvoted 0 times
...
Corrie
5 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.
upvoted 0 times
...

Save Cancel