To fetch daily updated exchange rates from a web service, what is the appropriate scope for the data page?

The appropriate scope for the data page that fetches daily updated exchange rates from a web service is Node.

When a data page is scoped to Node, it means that the data is cached at the level of the specific node in a Pega cluster. This is particularly beneficial for data that is relatively static or requires infrequent updates, such as daily exchange rates. By using Node scope, the data will be shared across all user sessions on that node, thus increasing efficiency by reducing repetitive calls to the web service every time a user needs the exchange rate.

Additionally, Node scope ensures that if there are multiple users accessing the same information from the same node, they can all benefit from the cached data without having to make separate requests to the external web service. This reduces latency and server load, optimizing performance.

The other options, such as Thread, Requestor, and Application, would not provide the same efficiency for this use case. Thread scope is limited to the individual requestor's interaction, meaning data would not be cached for subsequent uses. Requestor scope is similar, as it is specific to a single user session, and Application scope would typically cache data at an application-wide level, which might not be as efficient in a clustered environment compared to Node