New Year Sale 2026! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Pegasystems PEGAPCBA87V1 Exam - Topic 5 Question 20 Discussion

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

You need to fetch exchange rates that are updated on a daily basis from a web service and make them available in your application using a data page .

Which scope would you select for the data page?

Show Suggested Answer Hide Answer
Suggested Answer: D

it routes an assignment so that any available member of the Finance department can perform the task. A work queue is a shared list of assignments that can be accessed by multiple users who have the same role or skill. By routing the assignment to a work queue, you can ensure that any qualified user can pick up and complete the task. Reference: https://academy.pega.com/library/87/pega-certified-business-architect-pcba-87v1 (Module 8: Routing)


Contribute your Thoughts:

0/2000 characters
Long
3 months ago
I disagree, Thread scope could work if you need it per user session.
upvoted 0 times
...
Filiberto
3 months ago
I'm surprised there's no mention of Node scope! Isn't that relevant?
upvoted 0 times
...
Mitzie
3 months ago
Wait, why not Request scope? Seems like a valid option too.
upvoted 0 times
...
Lura
4 months ago
Totally agree, Application scope makes sense here!
upvoted 0 times
...
Ressie
4 months ago
I think the best choice is Application scope for this.
upvoted 0 times
...
Rory
4 months ago
I lean towards thread scope since it seems like it could handle updates well, but I’m not sure if it’s the best fit for this scenario.
upvoted 0 times
...
Miesha
4 months ago
I practiced a similar question, and I feel like node scope could be relevant, but I’m not confident about it in this context.
upvoted 0 times
...
Sean
4 months ago
I'm not entirely sure, but I remember something about request scope being temporary. Would that work for daily updates?
upvoted 0 times
...
Brigette
5 months ago
I think the application scope might be the right choice since the exchange rates need to be available across the entire application.
upvoted 0 times
...
Nikita
5 months ago
Hmm, I'm a bit torn between the application and request scopes here. I'll have to review the details of each scope to make sure I choose the right one for this scenario.
upvoted 0 times
...
Chandra
5 months ago
Okay, let me see. The exchange rates are updated daily, so they need to persist beyond a single request. And they should be available globally in the app, not just on a specific node or thread. I'm leaning towards the application scope.
upvoted 0 times
...
Gearldine
5 months ago
The application scope makes the most sense to me. The exchange rates need to be accessible throughout the app, not just for a single request or thread. I'm confident this is the right approach.
upvoted 0 times
...
Sylvie
5 months ago
I'm a bit unsure about this one. Is the request scope a possibility since the exchange rates might only be needed for a specific request? I'll have to think this through carefully.
upvoted 0 times
...
Thora
5 months ago
Hmm, this seems straightforward. I think the application scope would be the best choice here since the exchange rates need to be available across the entire application.
upvoted 0 times
...
Mariann
5 months ago
This seems like a straightforward question about stakeholder analysis. I'm pretty confident I know the answer - the axes of the stakeholder analysis grid depict power and interest.
upvoted 0 times
...
Geoffrey
5 months ago
Hmm, this is a tricky one. I'll need to think carefully about the key factors for performance testing.
upvoted 0 times
...
Annmarie
5 months ago
Okay, I've got a plan. I'll create a Calm blueprint that calls the Calm APIs to automate both the database and application deployments. That way, we can have a fully automated, end-to-end solution.
upvoted 0 times
...
Erasmo
5 months ago
I think levels of absenteeism could be important to understand the workforce dynamics, but I'm not entirely sure if that's a primary focus for internal analysis.
upvoted 0 times
...
Yuki
10 months ago
Thread scope? Haha, that's a good one! I'm picturing the exchange rates getting passed around like a hot potato between different threads. Definitely not the way to go here.
upvoted 0 times
Jess
8 months ago
C) Node
upvoted 0 times
...
Francisca
8 months ago
B) Request
upvoted 0 times
...
Elouise
9 months ago
A) Application
upvoted 0 times
...
...
Craig
10 months ago
Node scope? What is this, a JavaScript question? I'm pretty sure that's not the right answer for a data page in a .NET application.
upvoted 0 times
Shannan
9 months ago
D) Thread
upvoted 0 times
...
Shelton
9 months ago
Node scope is not the right choice for a data page in a .NET application.
upvoted 0 times
...
Lemuel
9 months ago
C) Node
upvoted 0 times
...
Leslie
9 months ago
B) Request
upvoted 0 times
...
Ardella
9 months ago
A) Application
upvoted 0 times
...
...
Bettina
10 months ago
Request scope? That's not going to work. The exchange rates need to persist beyond a single request. I'm going with Application scope on this one.
upvoted 0 times
...
Annmarie
10 months ago
Application scope seems like the right choice here. The exchange rates need to be accessible throughout the entire application, not just for a single request.
upvoted 0 times
...
Cordelia
10 months ago
That's a good point, Flo. It depends on whether you want the exchange rates to be updated with every request or just once for the whole application.
upvoted 0 times
...
Flo
11 months ago
I would go with scope B) Request, as it would fetch fresh exchange rates every time a new request is made.
upvoted 0 times
...
Heike
11 months ago
I agree with Cordelia, selecting Application scope would make the exchange rates available throughout the application.
upvoted 0 times
...
Cordelia
11 months ago
I think I would select scope A) Application for the data page.
upvoted 0 times
...

Save Cancel