Cyber Monday 2024! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Pegasystems Exam PEGACPLSA88V1 Topic 5 Question 23 Discussion

Actual exam question for Pegasystems's PEGACPLSA88V1 exam
Question #: 23
Topic #: 5
[All PEGACPLSA88V1 Questions]

An external application calls a Pega REST service, which takes a significant amount of time to respond. Pega Platform returns a unique identifier instantly and runs the service without the application waiting.

Which configuration implements this functionality?

Show Suggested Answer Hide Answer
Suggested Answer: B

Service Request Processor for Asynchronous Processing:

Configuring a REST service to run asynchronously using a service request processor ensures that the service runs without making the external application wait. The system returns a unique identifier instantly and processes the request in the background.

Reference:

Pega's best practices for REST services and asynchronous processing recommend using service request processors for handling long-running processes.

Therefore, the correct answer is:

B . A REST service that runs asynchronously by using a service request processor.


Contribute your Thoughts:

Francesco
2 months ago
Wait, do I get a snack if I get this right? Anyway, B is the answer. Async all the way!
upvoted 0 times
...
Hyman
2 months ago
I'm with you, John. B is the way to go. Pega's got our backs on this one.
upvoted 0 times
Larae
1 months ago
I'm glad we're on the same page. B it is for sure.
upvoted 0 times
...
Laura
1 months ago
Definitely, B is the way to go. Pega's asynchronous processing is key.
upvoted 0 times
...
Olive
1 months ago
I agree, B is the best option. Pega will handle the rest.
upvoted 0 times
...
...
Tawanna
2 months ago
I'm not sure, but I think option D could also work because it mentions running the service asynchronously.
upvoted 0 times
...
Bette
2 months ago
I agree with Yuki, option B makes sense because it allows the application to continue without waiting for the response.
upvoted 0 times
...
Salena
2 months ago
I'm feeling a bit hungry, but option B is clearly the correct answer. Gotta love that async magic!
upvoted 0 times
Jennie
1 months ago
I think we can all appreciate the magic of asynchronous processing.
upvoted 0 times
...
Serita
1 months ago
Definitely, async is the way to go for faster response times.
upvoted 0 times
...
Erick
2 months ago
I agree, option B is the way to go for sure.
upvoted 0 times
...
...
Celeste
2 months ago
Definitely B. Waiting for a significant amount of time is a huge no-no in REST services.
upvoted 0 times
Tracey
1 months ago
I think using a service request processor is the best way to handle this situation.
upvoted 0 times
...
Kati
1 months ago
Agreed, it's important to optimize response times in REST services.
upvoted 0 times
...
Olen
2 months ago
That makes sense, we definitely don't want to keep the external application waiting.
upvoted 0 times
...
Paulina
2 months ago
B) A REST service that runs asynchronously by using a service request processor.
upvoted 0 times
...
...
Naomi
3 months ago
Hmm, option B seems like the way to go. Asynchronous processing is the key here.
upvoted 0 times
Patrick
2 months ago
Yeah, using a service request processor will allow the application to continue without waiting for the response.
upvoted 0 times
...
Phil
2 months ago
Agreed, asynchronous processing will definitely help with the response time.
upvoted 0 times
...
Jimmie
2 months ago
I think option B is the best choice for this scenario.
upvoted 0 times
...
Kristeen
2 months ago
Yes, using a service request processor will allow the application to continue without delay.
upvoted 0 times
...
Brice
2 months ago
It's important to have the service run in the background without waiting.
upvoted 0 times
...
Tora
2 months ago
Asynchronous processing will definitely help improve performance.
upvoted 0 times
...
Louis
3 months ago
I agree, option B is the best choice for this scenario.
upvoted 0 times
...
...
Yuki
3 months ago
I think the answer is B) A REST service that runs asynchronously by using a service request processor.
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