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

Salesforce ANC-201 Exam - Topic 5 Question 65 Discussion

Actual exam question for Salesforce's ANC-201 exam
Question #: 65
Topic #: 5
[All ANC-201 Questions]

The CRM Analytics consultant at Universal Containers has set data syncs and recipe runs back to back. However, they notice that the data syncs and recipe run jobs fail repeatedly. Upon investigation,

they realize the data syncs and recipes are tightly coupled which leads to too many runs being queued and eventually being canceled.

How should the consultant resolve this issue?

Show Suggested Answer Hide Answer
Suggested Answer: C

Contribute your Thoughts:

0/2000 characters
Vashti
6 days ago
A) Increasing the concurrency limits sounds like the easiest fix, but it might just be a band-aid. Better to address the root cause.
upvoted 0 times
...
Marylou
11 days ago
B) Notifications are crucial here. Gotta stay on top of those failures before they snowball.
upvoted 0 times
...
Weldon
16 days ago
C) Definitely the way to go. Priority scheduling is the key to keeping those pesky data syncs and recipes in check.
upvoted 0 times
...
Isaac
21 days ago
I vaguely recall something about managing job queues. Maybe prioritizing smaller runs is the best approach to prevent cancellations?
upvoted 0 times
...
Bernardo
27 days ago
I feel like we had a practice question about failure notifications. While they’re useful, I don’t think they actually solve the root problem here.
upvoted 0 times
...
Melodie
1 month ago
I'm not entirely sure, but I think raising a case with Salesforce Support might be a bit extreme for this situation. There should be a way to resolve it internally first.
upvoted 0 times
...
Pete
1 month ago
I remember we discussed how tightly coupled processes can lead to issues like this in class. It seems like enabling priority scheduling could help manage the runs better.
upvoted 0 times
...
Nydia
1 month ago
I'm leaning towards option C. Enabling priority scheduling seems like the most straightforward solution to prevent the data syncs and recipes from getting too tightly coupled and causing problems.
upvoted 0 times
...
Dick
2 months ago
Priority scheduling sounds like the way to go. That'll help ensure the system is running as efficiently as possible and minimize the risk of jobs getting stuck or canceled.
upvoted 0 times
...
Sheridan
2 months ago
Definitely set up failure notifications so I can stay on top of this issue. That way, I can jump in and fix things as soon as the jobs start failing, instead of waiting for everything to grind to a halt.
upvoted 0 times
...
Valda
2 months ago
I'm a bit confused on this one. Should we be raising a case with Salesforce Support to increase the concurrency limits? Or is there a way to handle this within the org settings?
upvoted 0 times
...
Merilyn
2 months ago
I think the best approach here would be to enable priority scheduling to queue the shorter or smaller runs first. That way, the longer or larger runs don't get stuck in the queue and cause everything to fail.
upvoted 0 times
...

Save Cancel