Independence Day Deal! Unlock 25% OFF Today – Limited-Time Offer - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Salesforce Exam B2C Commerce Developer Topic 20 Question 52 Discussion

Actual exam question for Salesforce's B2C Commerce Developer exam
Question #: 52
Topic #: 20
[All B2C Commerce Developer Questions]

A job executes a pipeline that makes calls to an external system.

Which two actions prevent performance issues in this situation? (Choose two.)

Show Suggested Answer Hide Answer
Suggested Answer: A

Contribute your Thoughts:

Layla
1 months ago
Disabling multi-threading? What is this, a single-threaded world? I'll take my chances with option D and leave the Stone Age behind.
upvoted 0 times
...
Linwood
1 months ago
Synchronous jobs? Are we still living in the dark ages? I'm going with option D, it's the only way to fly these days.
upvoted 0 times
Rochell
11 days ago
Using asynchronous jobs is the best choice for this situation. It's the modern way to handle external system calls.
upvoted 0 times
...
Murray
14 days ago
I agree, asynchronous jobs are much more efficient. Plus, they prevent performance issues.
upvoted 0 times
...
Daren
19 days ago
Using asynchronous jobs will definitely help prevent performance issues.
upvoted 0 times
...
Christiane
23 days ago
Synchronous jobs are so outdated. Option D is definitely the way to go.
upvoted 0 times
...
Dahlia
29 days ago
I agree, asynchronous jobs are much more efficient.
upvoted 0 times
...
Ruby
1 months ago
Synchronous jobs are so outdated. Option D is definitely the way to go.
upvoted 0 times
...
...
Aretha
2 months ago
Timeouts are definitely important, but I think option B is a bit of a bandaid. Why not just use asynchronous jobs and avoid the issue in the first place?
upvoted 0 times
Armando
19 days ago
I think having a timeout for the script pipelet is still important to avoid potential issues.
upvoted 0 times
...
Cheryll
1 months ago
That's true, but using synchronous jobs could also be a good option depending on the situation.
upvoted 0 times
...
Reta
2 months ago
But wouldn't disabling multi-threading also help prevent performance issues?
upvoted 0 times
...
Carline
2 months ago
I agree, using asynchronous jobs would be a better long-term solution.
upvoted 0 times
...
...
Hoa
2 months ago
Haha, disabling multi-threading? That's like putting your computer in a time machine and going back to the 90s. I'll stick with option D, thanks.
upvoted 0 times
Rosita
2 months ago
User2: Yeah, I think option D is the way to go for better performance.
upvoted 0 times
...
Horace
2 months ago
User1: I agree, disabling multi-threading seems like a step backwards.
upvoted 0 times
...
...
Verlene
2 months ago
I'm not sure about disabling multi-threading. But using asynchronous import or export jobs sounds like a good idea too.
upvoted 0 times
...
Oliva
2 months ago
I agree with Lottie. Also, configuring a timeout for the script pipelet could be beneficial.
upvoted 0 times
...
Lottie
2 months ago
I think using synchronous import or export jobs could help prevent performance issues.
upvoted 0 times
...
Rhea
3 months ago
I'm pretty sure option D is the way to go here. Using asynchronous jobs will prevent performance issues by not blocking the main thread while waiting for the external system to respond.
upvoted 0 times
Herminia
1 months ago
Using synchronous import or export jobs could also be a good option to prevent performance issues.
upvoted 0 times
...
Sharika
1 months ago
I'm not sure about option D, but I think configuring a timeout for the script pipelet could also help.
upvoted 0 times
...
Colette
2 months ago
Agreed, using asynchronous jobs is a common practice to prevent performance issues.
upvoted 0 times
...
Nathan
2 months ago
I think option D is a good choice too. It will definitely help with performance.
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