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 24 Discussion

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

In a telecom customer service application, birthday wishes must be sent to customers every day at midnight by email, according to KYC records. The business requirement states that if email delivery failures occur, the system must record the failures.

There is an infrastructure limitation in using an external stream node; other available nodes are Webuser, Background processing, and BIX only. What two options can comprise an alternative approach as an interim solution? (Choose Two)

Show Suggested Answer Hide Answer
Suggested Answer: B, D

Job Scheduler with SendEmailNotification Utility:

Running a job scheduler to pull customer records matching the current date and using the SendEmailNotification utility ensures that emails are sent out at midnight. Recording failures in a data type captures the necessary error information.

Job Scheduler with CorrNew Utility:

Using the CorrNew utility to send emails and record any exceptions in a data type also satisfies the requirement for recording email delivery failures.

Reference:

Pega documentation on job schedulers and email utilities provides guidelines for implementing scheduled tasks and handling email delivery.

Therefore, the correct answers are:

B . Run a job scheduler, and pull the customers that match the current date. For each record, invoke the SendEmailNotification utility. If any exception is received in email delivery, mark the failure in a data type.

D . Run a job scheduler, and pull the customers that match the current date. For each record, invoke the CorrNew utility. If any exception is received in email delivery, mark the failure in a data type.


Contribute your Thoughts:

Harrison
2 months ago
Yes, both options A and B provide practical solutions for the infrastructure limitation. Let's hope the exam question is similar to this scenario.
upvoted 0 times
...
Lyndia
2 months ago
I agree with you, Harrison. Option B also seems feasible as it involves invoking a utility for sending emails and marking failures.
upvoted 0 times
...
Felix
2 months ago
As an aspiring telecom customer service superhero, I'm leaning towards Option B. It's like a birthday party for our customers, except the cake is virtual and the candles are just data points. Simple, yet effective!
upvoted 0 times
...
Lashaunda
2 months ago
Option D has a certain charm to it, but I'm not convinced the CorrNew utility is the best way to handle this. Feels a bit like a workaround within a workaround, you know?
upvoted 0 times
Dacia
1 months ago
Let's go with Option A and B for now, they seem like the most efficient choices.
upvoted 0 times
...
Gilma
1 months ago
I see your point about Option D, it does seem like a workaround within a workaround.
upvoted 0 times
...
Alison
1 months ago
I agree, Option B also sounds practical, running a job scheduler to pull customers matching the current date.
upvoted 0 times
...
Sophia
1 months ago
Option A seems like a solid choice, using a data set with partitioning keys and filter keys for email delivery.
upvoted 0 times
...
...
Stevie
2 months ago
Haha, I bet the developers who came up with Option C were trying to be a little too clever. Invoking a Flow-New method just to send an email? Seems a bit overkill if you ask me.
upvoted 0 times
...
Harrison
2 months ago
I think option A is a good choice because it uses data sets and data flows to send emails and record failures.
upvoted 0 times
...
German
3 months ago
I would go with Option A. The use of a data set with partitioning and filtering keys sounds like a more robust and scalable solution in the long run.
upvoted 0 times
Refugia
2 months ago
Option A does sound like a good approach. It's important to have a system in place to handle email delivery failures.
upvoted 0 times
...
Tennie
2 months ago
I agree, Option A sounds like a reliable solution. Recording failed emails in a data type is important for tracking.
upvoted 0 times
...
Bettyann
2 months ago
Option A seems like a solid choice. Using a data set with partitioning keys can help with scalability.
upvoted 0 times
...
...
Marge
3 months ago
Option B seems like the most straightforward approach. It's simple, reliable, and easy to implement. I like how it handles the email delivery failures as well.
upvoted 0 times
Karan
2 months ago
I agree, Option B is the best choice. It covers all the bases for handling email delivery failures.
upvoted 0 times
...
Vanna
2 months ago
Option B is definitely the way to go. It's efficient and effective.
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