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

Salesforce Exam ARC-101 Topic 3 Question 33 Discussion

Actual exam question for Salesforce's ARC-101 exam
Question #: 33
Topic #: 3
[All ARC-101 Questions]

A company accepts payment requests 24x7. Once they accept a payment request, their

service level agreement (SLA) requires them to make sure each payment request is processed

by their Payment System. They track payment requests using a globally unique identifier created at the Data Entry Point. Their simplified flow is as shown in the diagram.

They encounter intermittent update errors when two or more processes try to update the same Payment Request record at the same time.

Which two recommendations should an integration architect make to improve their SLA and update conflict handling?

Choose 2 answers

Show Suggested Answer Hide Answer
Suggested Answer: B, D, E

Contribute your Thoughts:

Felicidad
4 days ago
Seems like a good balance of options. Coordinating the request flow and ensuring reliable processing should help them meet their SLA without too much hassle.
upvoted 0 times
...
Clay
5 days ago
Ha! Imagine if the Payment System just said 'Nah, I'm not feeling like processing that request today.' Automatic retries are a must-have for this scenario.
upvoted 0 times
...
Tyisha
10 days ago
Definitely agree that the Payment System should only process a payment request once. Avoiding duplicate payments is crucial for their SLA.
upvoted 0 times
...
Marg
16 days ago
Middleware coordination and automatic retries seem like a solid approach to handle the update conflicts. I'm curious to see how they can implement that without introducing too much complexity.
upvoted 0 times
...
Darrel
18 days ago
I think both options A and C are important to improve the SLA and handle update conflicts effectively.
upvoted 0 times
...
Isadora
19 days ago
I agree with Margurite. Option C) Payment System should process a payment request only once also seems like a good solution to avoid update conflicts.
upvoted 0 times
...
Margurite
20 days ago
I think option A) Middleware should coordinate request delivery and payment processing is a good recommendation.
upvoted 0 times
...

Save Cancel
az-700  pass4success  az-104  200-301  200-201  cissp  350-401  350-201  350-501  350-601  350-801  350-901  az-720  az-305  pl-300  

Warning: Cannot modify header information - headers already sent by (output started at /pass.php:70) in /pass.php on line 77