Pegasystems PEGACPLSA88V1 Exam - Topic 5 Question 23 Discussion

Actual exam question for Pegasystems's PEGACPLSA88V1 exam

Question #: 23
Topic #: 5

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?

AA REST service that runs Queue-For-Agent method, and then returns a unique ID.

BA REST service that runs asynchronously by using a service request processor.

CA REST service that runs a connector in parallel to call a Pega server.

DA REST service that runs a spin-off flow to run the service asynchronously.

Show Suggested 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.

by Brandon at Sep 13, 2024, 09:02 AM

Limited Time Offer

25%

Off

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

Contribute your Thoughts:

Submit Cancel

Quentin

4 months ago

Not sure about B, though. What if the service fails after the ID is returned?

upvoted 0 times

...

Hana

4 months ago

I’m surprised this is even a question. Isn’t it obvious?

upvoted 0 times

...

Taryn

4 months ago

Wait, could it be D? Spin-off flows are also asynchronous.

upvoted 0 times

...

Tamie

4 months ago

Definitely agree with B! It fits the description perfectly.

upvoted 0 times

...

Lawana

5 months ago

I think option B is the right choice. Asynchronous processing is key here.

upvoted 0 times

...

Cletus

5 months ago

I recall that C involves connectors, but I don't think that's the right approach for this scenario. It seems more synchronous to me.

upvoted 0 times

...

Vallie

5 months ago

I feel like D could be a possibility too, since it talks about running a spin-off flow, but I'm not confident about the terminology.

upvoted 0 times

...

Luke

5 months ago

I'm not entirely sure, but I remember something about using Queue-For-Agent in a similar practice question. Could that be A?

upvoted 0 times

...

Micaela

5 months ago

I think the answer might be B, since it mentions running asynchronously, which seems to fit the requirement of not making the application wait.

upvoted 0 times

...

Andree

5 months ago

Based on the details provided, I believe Option B is the correct answer. The question specifically mentions the Pega REST service running asynchronously, which aligns with the description of a service request processor in Option B.

upvoted 0 times

...

Lyndia

5 months ago

I'm a bit confused by the wording of this question. It seems like there are a few different aspects to consider, and I'm not entirely sure which configuration would be the best fit. I'll need to re-read the question carefully and think through the requirements before making a decision.

upvoted 0 times

...

Dino

5 months ago

Okay, let me break this down. The question is asking about the configuration that implements the functionality of an external application calling a Pega REST service that takes a significant amount of time to respond, but Pega Platform returns a unique identifier instantly and runs the service without the application waiting. I'm leaning towards Option B, but I'll double-check the other options just to be sure.

upvoted 0 times

...

Buddy

5 months ago

Hmm, I think the key here is the requirement for the Pega REST service to return a unique identifier instantly while running the service asynchronously. Option B seems to fit that description best.

upvoted 0 times

...

Louisa

5 months ago

This looks like a tricky one. I'll need to carefully consider the details of the question to determine the best approach.

upvoted 0 times

...

Brandee

6 months ago

I remember practicing a question like this, and I feel like anything involving fraud would definitely not have materiality limits applied.

upvoted 0 times

...

Francesco

1 year 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

1 year 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 year ago

I'm glad we're on the same page. B it is for sure.

upvoted 0 times

...

Laura

1 year ago

Definitely, B is the way to go. Pega's asynchronous processing is key.

upvoted 0 times

...

Olive

1 year ago

I agree, B is the best option. Pega will handle the rest.

upvoted 0 times

...

Tawanna

1 year ago

I'm not sure, but I think option D could also work because it mentions running the service asynchronously.

upvoted 0 times

...

Bette

1 year 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

1 year 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 year ago

I think we can all appreciate the magic of asynchronous processing.

upvoted 0 times

...

Serita

1 year ago

Definitely, async is the way to go for faster response times.

upvoted 0 times

...

Erick

1 year ago

I agree, option B is the way to go for sure.

upvoted 0 times

...

Celeste

1 year ago

Definitely B. Waiting for a significant amount of time is a huge no-no in REST services.

upvoted 0 times

Tracey

1 year ago

I think using a service request processor is the best way to handle this situation.

upvoted 0 times

...

Kati

1 year ago

Agreed, it's important to optimize response times in REST services.

upvoted 0 times

...

Olen

1 year ago

That makes sense, we definitely don't want to keep the external application waiting.

upvoted 0 times

...

Paulina

1 year ago

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

upvoted 0 times

...

Naomi

2 years ago

Hmm, option B seems like the way to go. Asynchronous processing is the key here.

upvoted 0 times

Patrick

1 year ago

Yeah, using a service request processor will allow the application to continue without waiting for the response.

upvoted 0 times

...

Phil

1 year ago

Agreed, asynchronous processing will definitely help with the response time.

upvoted 0 times

...

Jimmie

1 year ago

I think option B is the best choice for this scenario.

upvoted 0 times

...

Kristeen

1 year ago

Yes, using a service request processor will allow the application to continue without delay.

upvoted 0 times

...

Brice

1 year ago

It's important to have the service run in the background without waiting.

upvoted 0 times

...

Tora

1 year ago

Asynchronous processing will definitely help improve performance.

upvoted 0 times

...

Louis

1 year ago

I agree, option B is the best choice for this scenario.

upvoted 0 times

...

Yuki

2 years ago

I think the answer is B) A REST service that runs asynchronously by using a service request processor.

upvoted 0 times

...