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.09 Exam - Topic 2 Question 5 Discussion

Service A is an entity service that provides a Get capability that returns a data value that is frequently changed. Service Consumer A invokes Service A in order to request this data value (1). For Service A to carry out this request, it must invoke Service B (2), a utility service that interacts (3.4) with the database in which the data value is stored. Regardless of whether the data value changed, Service B returns the latest value to Service A (5), and Service A returns the latest value to Service Consumer A (6). The data value is changed when the legacy client program updates the database (7) When this change happens is not predictable. Note also that Service A and Service B are not always available at the same time. Any time the data value changes. Service Consumer A needs to receive it as soon as possible. Therefore, Service Consumer A initiates the message exchange shown in the Figure several times a day. When it receives the same data value as before, the response from Service A is ignored. When Service A provides an updated data value, Service Consumer A can process it to carry out its task.The current service composition architecture is using up too many resources due to the repeated invocation of Service A by Service Consumer A and the resulting message exchanges that occur with each invocation. What steps can be taken to solve this problem?
D) None of the above.
A) The Event-Driven Messaging pattern can be applied by establishing a subscriber-publisher relationship between Service A and Service B . This way, every time the data value is updated, an event is triggered and Service B, acting as the publisher, can notify Service A, which acts as the subscriber. The Asynchronous Queuing pattern can be applied between Service A and Service B so that the event notification message sent out by Service B will be received by Service A, even when Service A is unavailable.
B) The Event-Driven Messaging pattern can be applied by establishing a subscriber-publisher relationship between Service Consumer A and Service A . This way, every time the data value is updated, an event is triggered and Service A, acting as the publisher, can notify Service Consumer A, which acts as the subscriber. The Asynchronous Queuing pattern can be applied between Service Consumer A and Service A so that the event notification message sent out by Service A will be received by Service Consumer A, even when Service Consumer A is unavailable.
C) The Asynchronous Queuing pattern can be applied so that messaging queues are established between Service A and Service B and between Service Consumer A and Service A . This way, messages are never lost due to the unavailability of Service A or Service B .

Arcitura Education S90.09 Exam - Topic 2 Question 5 Discussion

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

Service A is an entity service that provides a Get capability that returns a data value that is frequently changed. Service Consumer A invokes Service A in order to request this data value (1). For Service A to carry out this request, it must invoke Service B (2), a utility service that interacts (3.4) with the database in which the data value is stored. Regardless of whether the data value changed, Service B returns the latest value to Service A (5), and Service A returns the latest value to Service Consumer A (6). The data value is changed when the legacy client program updates the database (7) When this change happens is not predictable. Note also that Service A and Service B are not always available at the same time. Any time the data value changes. Service Consumer A needs to receive it as soon as possible. Therefore, Service Consumer A initiates the message exchange shown in the Figure several times a day. When it receives the same data value as before, the response from Service A is ignored. When Service A provides an updated data value, Service Consumer A can process it to carry out its task.

The current service composition architecture is using up too many resources due to the repeated invocation of Service A by Service Consumer A and the resulting message exchanges that occur with each invocation. What steps can be taken to solve this problem?

Show Suggested Answer Hide Answer
Suggested Answer: D

Contribute your Thoughts:

0/2000 characters
Mickie
7 months ago
Not sure about B, feels like it complicates things more than needed.
upvoted 0 times
...
Ocie
7 months ago
Option C is solid too, can't lose messages!
upvoted 0 times
...
Krissy
8 months ago
Wait, can Service A really handle that many events? Seems risky.
upvoted 0 times
...
Lizbeth
8 months ago
Totally agree, event-driven is the way to go!
upvoted 0 times
...
Antione
8 months ago
I think option A makes the most sense for real-time updates.
upvoted 0 times
...
Lucia
8 months ago
That sounds like a good strategy, Tom. I'm also thinking we could use a trigger based on the file name, since it doesn't have a consistent naming convention.
upvoted 0 times
...
Dominga
8 months ago
Manipulating the IGP metric feels like a less direct option, but I guess it could work for load balancing; still, I'm hesitant about this one.
upvoted 0 times
...
Iluminada
8 months ago
Hmm, I'm a little unsure about this one. Deleting cases as new ones are created seems risky, and I'm not sure about the quarterly review approach. I'll have to think this through carefully.
upvoted 0 times
...

Save Cancel