New Year Sale 2026! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions
Mail Us support@pass4success.com
Location US
Mob_nav_barsMENU

Salesforce ARC-101 Exam - Topic 3 Question 62 Discussion

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

Northern Trail Outfitters wants to use Salesforce as a front end for creating accounts using the lead-to-opportunity process.

1. An order is created in Salesforce when the opportunity is closed and won, but the back-end ERP system is the data master for order,

2. Customer wants to be able to see within Salesforce all the stages of order processing like Order Created, Order Shipped, Order Paid that are within the retention window.

Which two message durability considerations should an Integration Architect make when designing a solution to meet these business requirements?

Choose 2 answers

Show Suggested Answer Hide Answer
Suggested Answer: A, D

https://developer.salesforce.com/docs/atlas.en-us.api_streaming.meta/api_streaming/using_streaming_api_durability.htm


by Cecilia at Jul 05, 2025, 06:26 AM

Limited Time Offer

25%

Off

Get Premium ARC-101 Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

0/2000 characters
Submit Cancel
Arlette
2 months ago
B seems off, I thought it was 72 hours.
upvoted 0 times
...
Margo
3 months ago
I thought high-volume messages were stored for longer than 24 hours?
upvoted 0 times
...
Bernardine
3 months ago
Totally agree, we need to track all events!
upvoted 0 times
...
Mari
3 months ago
D is definitely the way to go for message durability!
upvoted 0 times
...
Lashaunda
3 months ago
A is correct, ReplayID -2 is key for old events.
upvoted 0 times
...
Yuette
3 months ago
I’m pretty confident that when subscribing to the Event bus, -1 is for new events, but I need to double-check that against our notes.
upvoted 0 times
...
Toi
4 months ago
I feel like we practiced a question similar to this, and I recall that high-volume messages are definitely not stored for just one day.
upvoted 0 times
...
Reid
4 months ago
I think high-volume event messages are stored for 72 hours, but I might be mixing it up with something else we studied.
upvoted 0 times
...
Wei
4 months ago
I remember something about ReplayID values, but I'm not sure if -1 or -2 is the right one for seeing old events.
upvoted 0 times
...
Jacqueline
4 months ago
I feel pretty confident about this one. The question is asking for two specific considerations, so I'll make sure to select two relevant answers that address the requirements.
upvoted 0 times
...
Helga
4 months ago
Okay, I've got a strategy. I'll start by considering the business requirements around seeing all the order processing stages within the retention window. That should help me narrow down the right message durability options.
upvoted 0 times
...
Eleonora
5 months ago
Hmm, I'm a bit confused about the difference between the ReplayID values of -1 and -2. I'll need to review that part carefully.
upvoted 0 times
...
Lyla
5 months ago
This question seems straightforward. I think the key is to focus on the message durability considerations for the Salesforce Event bus.
upvoted 0 times
...
Bulah
6 months ago
A and D, for sure. Anything less than 72 hours for event storage is like trying to keep track of your order by reading tea leaves - it's just not going to cut it.
upvoted 0 times
...
Ines
7 months ago
I'm going to have to go with A and D on this one. Trying to design an integration without considering message durability is like trying to build a house without a foundation - it's just not going to work.
upvoted 0 times
Martina
5 months ago
A) When subscribing to Salesforce Event bus, ReplaylD is used with a value of -2 to be able to see old and new events.
upvoted 0 times
...
...
Hyman
7 months ago
Hmm, I'm going with A and D as well. Anything less than 72 hours for event storage would be like trying to catch a fish with a net made of string. Not very reliable, if you ask me.
upvoted 0 times
...
Lashunda
7 months ago
Definitely A and D. Who would want to see new events only? That's like trying to track a package after it's already been delivered. And 24 hours? Come on, that's just not enough time.
upvoted 0 times
Afton
7 months ago
Having high-volume event messages stored for 72 hours provides a sufficient retention window.
upvoted 0 times
...
Belen
7 months ago
Seeing old and new events is crucial for tracking order processing stages.
upvoted 0 times
...
Leah
7 months ago
I agree, A and D are the best options for message durability considerations.
upvoted 0 times
...
...
Levi
7 months ago
I think the answer is A and D. Replaying old events is important to meet the requirement of seeing all order processing stages, and high-volume events should be stored for at least 72 hours to cover the retention window.
upvoted 0 times
Talia
6 months ago
Replaying old events is important to meet the requirement of seeing all order processing stages, and high-volume events should be stored for at least 72 hours to cover the retention window.
upvoted 0 times
...
Hassie
7 months ago
I think the answer is A and D.
upvoted 0 times
...
...
Martina
7 months ago
I agree with Lashaunda, A seems like the right choice for message durability.
upvoted 0 times
...
Lashaunda
8 months ago
But A makes sense because we need to see old and new events.
upvoted 0 times
...
Gretchen
8 months ago
I disagree, I believe the answer is B.
upvoted 0 times
...
Lashaunda
8 months ago
I think the answer is A.
upvoted 0 times
...

Save Cancel