MENU
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
Suggested Answer: B, D, E
Get Premium ARC-101 Questions
as Interactive Web-Based Practice Test or PDF
Real Exam Format
Detailed Explanations
Instant Access
Get Your Practice Test
32 comments · newest first
DE
Destiny
11 months ago
Not sure about B, automatic retries could lead to more chaos.
LE
Leota
11 months ago
Middleware coordinating sounds smart, so A is a good pick!
DE
Devora
12 months ago
Wait, how can the Payment System ensure it only processes once? Seems tricky.
EL
Elmira
12 months ago
Totally agree, option D makes sense too for retries.
DE
Derrick
1 year ago
I think option C is a must, can't have duplicate processing!
RI
Ricki
1 year ago
I’m leaning towards option D because having both the Payment System and Middleware retry requests could help with those intermittent errors we talked about in class.
FR
Francesco
1 year ago
I think we practiced a similar question where coordinating request delivery was emphasized. So, option A might be a good choice too.
WI
Willard
1 year ago
I'm a bit unsure about the best approach here. I feel like retrying requests could help, but I'm not sure if it should be done at the Data Entry Point or Middleware.
LY
Lynda
1 year ago
I remember we discussed the importance of ensuring that the Payment System processes each request only once to avoid duplicates. So, I think option C makes sense.
PE
Pearlene
1 year ago
I agree, the Middleware should play a central role in managing the flow and handling any retries or conflicts. That seems like the best way to meet the SLA.
ST
Stephaine
1 year ago
Coordinating the request delivery and payment processing through the Middleware could also be a good approach to prevent those update issues.
VI
Viva
1 year ago
I'm leaning towards recommending automatic retries at the Data Entry Point and Middleware to improve the SLA. That should help reduce the update conflicts.
JA
Jacquelyne
1 year ago
Okay, let's think this through step-by-step. The key seems to be handling the update conflicts in the Payment System.
DE
Deeanna
1 year ago
This question seems straightforward, but I want to make sure I understand the flow correctly before answering.
KR
Krissy
1 year ago
Okay, I've got this. The key advantage is that an automated system reduces errors, which is option B. Manually tracking attendance is prone to mistakes, so an automated system solves that problem.
NE
Nelida
1 year ago
Okay, let's see. The key things I'm looking for are the relationships between the Shipments object and other objects like Accounts and Contacts. I'll need to check if there are any required lookups or master-detail relationships.
EL
Elouise
1 year ago
I think the key here is to focus on the Journalizing tab, since that's where the order of data stores is managed. Option A looks like the most straightforward approach.
FE
Felicidad
2 years 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.
YO
Youlanda
1 year ago
That sounds like a solid plan to avoid update conflicts and ensure smooth processing.
CA
Caitlin
1 year ago
C) Payment System should process a payment request only once.
MA
Margurite
1 year ago
A) Middleware should coordinate request delivery and payment processing.
TO
Tomoko
1 year 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.
DE
Derick
2 years ago
B) Data Entry Point and Middleware should automatically retry requests.
CH
Charisse
2 years ago
A) Middleware should coordinate request delivery and payment processing.
CL
Clay
2 years 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.
TY
Tyisha
2 years ago
Definitely agree that the Payment System should only process a payment request once. Avoiding duplicate payments is crucial for their SLA.
MA
Marg
2 years 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.
NO
Noah
1 year ago
B: Data Entry Point and Middleware should automatically retry requests.
RE
Rene
2 years ago
A: Middleware should coordinate request delivery and payment processing.
DA
Darrel
2 years ago
I think both options A and C are important to improve the SLA and handle update conflicts effectively.
IS
Isadora
2 years 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.
MA
Margurite
2 years ago
I think option A) Middleware should coordinate request delivery and payment processing is a good recommendation.