What best describes when a data page should use a keyed structure in Pega?

A keyed structure in the context of data pages is most appropriately used when specific instances of data are required for display or processing. This approach allows you to efficiently retrieve and manage individual records based on their unique identifiers, such as primary keys. When you have a scenario where you need to work with distinct data instances—like fetching a particular customer record or detailing a specific order—leveraging a keyed structure is essential.

Keyed data pages can provide performance benefits and resource optimization since they avoid unnecessary loading of complete sets of data. Instead, they focus on fetching only the relevant instances you need, which is particularly beneficial in applications where responding to user actions quickly is crucial. This targeted access also supports scenarios where data integrity and specific configurations are maintained, ensuring that the right instance of data is retrieved based on the context of the process.

In contrast, using a keyed structure may not be the ideal choice for instances where data changes dynamically on a frequent basis without unique identifiers, or when dealing with purely static data that doesn't require instance-specific retrieval.