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
Mail Us support@pass4success.com
Location PL
Mob_nav_barsMENU

Pegasystems Exam PEGAPCSSA87V1 Topic 5 Question 29 Discussion

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

In which two scenarios is it a Pega best practice to use Pega Web Mashup over a Pega API integration? (Choose two.)

Show Suggested Answer Hide Answer
Suggested Answer: B, C

by Stevie at Apr 11, 2024, 12:23 AM

Limited Time Offer

25%

Off

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

Contribute your Thoughts:

Submit Cancel
Vannessa
6 months ago
That makes sense, Limited access to App Studio does point towards using Pega Web Mashup.
upvoted 0 times
...
Naomi
7 months ago
I believe option B is also a good scenario for using Pega Web Mashup. Developers with only App Studio access would find it easier to configure.
upvoted 0 times
...
Paris
7 months ago
I agree with Users creating cases and managing data privacy would benefit from Pega Web Mashup.
upvoted 0 times
...
Vannessa
7 months ago
I think option C is one scenario where Pega Web Mashup is best to use.
upvoted 0 times
...
Ettie
8 months ago
Haha, yeah, I was just thinking the same thing. If the question is asking for two scenarios, I'd go with A and D. Minimal resources for updates and using UI Kit on 8.2 seem like the most plausible cases where a Pega Web Mashup could be preferable.
upvoted 0 times
...
Laquanda
8 months ago
You know, Option D is an interesting one. If the application is built on Pega 8.2 using UI Kit, that might be a scenario where a Pega Web Mashup could be a good fit, especially if the integration is with a third-party system that isn't natively supported by the Pega Platform.
upvoted 0 times
...
Moira
8 months ago
Hmm, I'm not sure about Option C. Creating cases, opening assignments, and managing data privacy seem more like core Pega functionality that you'd want to handle through a Pega API rather than a Web Mashup. I could be wrong, but that one doesn't seem quite right to me.
upvoted 0 times
Quinn
6 months ago
I agree with Dallas. A and B make the most sense to me.
upvoted 0 times
...
Doretha
6 months ago
I'm not so sure about that. I believe it's B and D.
upvoted 0 times
...
Dallas
7 months ago
I think the correct options are A and B.
upvoted 0 times
...
...
Latonia
8 months ago
Okay, let's break this down. Option A talks about minimal resources for Pega Platform updates, which could make a Pega Web Mashup a better choice since it wouldn't require as much maintenance on the Pega side. Option B mentions developers only having access to App Studio, which might limit their ability to configure a full-blown API integration.
upvoted 0 times
...
Renea
8 months ago
I agree, this seems like a tricky one. From what I know, Pega Web Mashup is generally used when you want to integrate external content or applications into a Pega application. So the scenarios where that would be preferred over a Pega API integration are likely where there are some unique requirements or constraints.
upvoted 0 times
...
Alita
8 months ago
Hmm, this is an interesting question. I think the key here is to understand the scenarios where Pega Web Mashup would be a better choice over a Pega API integration. Let's take a closer look at the options.
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