Service A has become increasingly difficult to maintain. Its core service logic has become bloated and convoluted because it has been updated numerous times during which additional functionality was added to interact with the database and the legacy system and to support interaction with Service Consumers A and B (via the two service contracts) as well as interaction directly with Service Consumer C .
What steps can be taken to solve these problems and to prevent them from happening again in the future?
Suggested Answer: B
Get Premium S90.09 Questions
as Interactive Web-Based Practice Test or PDF
Real Exam Format
Detailed Explanations
Instant Access
Get Your Practice Test
8 comments · newest first
BE
Beckie
12 months ago
C looks like a good balance between simplicity and functionality.
BA
Barabara
12 months ago
B seems a bit overkill with all those patterns.
CH
Cherry
1 year ago
Wait, can a facade really fix all that bloated logic?
CL
Claudio
1 year ago
Totally agree, it simplifies the interactions.
DU
Dustin
1 year ago
I think the Service Facade pattern is a solid choice!
MA
Maia
1 year ago
Hmm, I'm a little unsure about this one. I know digital signatures are used to verify the identity of the sender, but I'm not totally clear on the specifics of how they work. I'll have to think this through carefully.
JE
Jestine
1 year ago
I remember something about why the erase function works with multiset, but I can't recall if it will actually change the output or not. It might be option B, but I'm not completely confident.
CO
Colby
1 year ago
I've got a good strategy for this one. I'll carefully read through the answer choices and try to match them up with what I know about how Oracle Web Services Manager handles policy assertions. I think I can narrow it down to the two correct statements.