Pegasystems PEGAPCSSA87V1 Exam - Topic 6 Question 30 Discussion

Actual exam question for Pegasystems's PEGAPCSSA87V1 exam

Question #: 30
Topic #: 6

You are updating a system of record using a SOAP connector. If the system of record is unavailable, you want to retry after an hour. If it is still unavailable after an hour, a notification should be sent to a system administrator.

How do you implement this requirement?

AImplement the logic in the data page's response data transform.

BImplement the logic in the connector's error handler flow.

CCustomize the standard pxErrorHandlingTemplate data transform.

DUse a transition condition in the activity step invoking the connector.

Show Suggested Answer

Suggested Answer: B, D, E

by Aja at Apr 24, 2024, 04:56 PM

Limited Time Offer

25%

Off

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

Contribute your Thoughts:

Submit Cancel

Cherrie

3 months ago

D sounds interesting, but I’d stick with B for clarity.

upvoted 0 times

...

Graham

3 months ago

I’m not sure about C, seems too complicated for this situation.

upvoted 0 times

...

Rusty

3 months ago

Wait, can we really just wait an hour? What if it’s down longer?

upvoted 0 times

...

Merri

4 months ago

Totally agree, B is the way to go!

upvoted 0 times

...

Jenelle

4 months ago

I think option B makes the most sense for error handling.

upvoted 0 times

...

Magnolia

4 months ago

Using a transition condition sounds like it could work, but I feel like it might not cover the retry aspect properly.

upvoted 0 times

...

Lilli

4 months ago

I'm a bit confused about the data transform options. Could customizing the pxErrorHandlingTemplate really handle notifications?

upvoted 0 times

...

Barrie

4 months ago

I remember a practice question where we had to handle errors in a similar way, and I think option B was the answer there too.

upvoted 0 times

...

Enola

5 months ago

I think the error handler flow might be the right place to implement the retry logic, but I'm not entirely sure.

upvoted 0 times

...

Devora

5 months ago

This is a good test of our understanding of error handling in the system. I'll carefully consider each option and choose the one that best fits the requirements.

upvoted 0 times

...

Leatha

5 months ago

I'm pretty confident I can solve this. The connector's error handler flow seems like the most straightforward way to implement the retry and notification requirements.

upvoted 0 times

...

Ressie

5 months ago

Okay, I think I've got a strategy here. I'll focus on the connector's error handler flow to handle the retry and notification logic.

upvoted 0 times

...

Glendora

5 months ago

Hmm, I'm a bit confused on where the retry logic should be implemented. I'll need to double-check the requirements.

upvoted 0 times

...

Amina

5 months ago

This looks like a tricky one. I'll need to carefully review the options and think through the best approach.

upvoted 0 times

...

Merissa

5 months ago

Okay, I think I've got this. Based on the options, it looks like I need to set a price rule in the Marketing section and also set pricing on the shared catalog. I'll make sure to double-check my work, but those seem like the two key actions to take.

upvoted 0 times

...

Carlee

5 months ago

Okay, this looks straightforward. I just need to plug the values into the SPI formula and calculate it.

upvoted 0 times

...

Lashanda

5 months ago

Hmm, I'm not entirely sure about the difference between some of these options. I'll need to think it through carefully.

upvoted 0 times

...

Kelvin

9 months ago

If the system of record is unavailable, just send the admin a notification saying 'System down, please flip the on/off switch.'

upvoted 0 times

...

Svetlana

9 months ago

B) all the way! Who wants to clutter up their data page with error handling code? Keep that stuff where it belongs - in the connector flow.

upvoted 0 times

Verlene

8 months ago

B) No way! Error handling should be kept separate from the data page logic for better maintainability.

upvoted 0 times

...

Pearly

8 months ago

A) But wouldn't it be easier to manage the retry logic in the data page's response data transform?

upvoted 0 times

...

Galen

9 months ago

B) Exactly! It's cleaner and more organized to handle errors directly in the connector flow.

upvoted 0 times

...

Zona

9 months ago

B) all the way! Who wants to clutter up their data page with error handling code? Keep that stuff where it belongs - in the connector flow.

upvoted 0 times

...

Emogene

10 months ago

I'd say B) is the way to go. Putting the retry and notification logic in the connector's error handler just seems like the cleanest and most logical approach.

upvoted 0 times

Felix

9 months ago

That's true, it keeps the logic centralized and makes it easier to manage.

upvoted 0 times

...

Andra

9 months ago

I agree, it makes sense to handle retries and notifications directly in the connector's error handler.

upvoted 0 times

...

Delmy

9 months ago

B) Implement the logic in the connector's error handler flow.

upvoted 0 times

...

Ranee

10 months ago

Definitely go with B. Having the error handling logic in the connector flow keeps things organized and makes it easier to maintain the code.

upvoted 0 times

Daren

8 months ago

C) Customize the standard pxErrorHandlingTemplate data transform.

upvoted 0 times

...

Antonio

8 months ago

B) Implement the logic in the connector's error handler flow.

upvoted 0 times

...

Rosendo

8 months ago

A) Implement the logic in the data page's response data transform.

upvoted 0 times

...

Jeannetta

9 months ago

B) Implement the logic in the connector's error handler flow.

upvoted 0 times

...

Isidra

10 months ago

B) Implement the logic in the connector's error handler flow seems like the most appropriate option. Handling the retry and notification in the connector's error handling makes sense to me.

upvoted 0 times

...