A door manufacturer offers a finite list of colors on all its doors. As part of the order, customers can select the color of the door. Select the…

In Pega, when configuring data pages to source UI controls such as drop-down lists, it's crucial to

select the configuration that optimally uses memory and efficiently serves the data to the users. For

this scenario, the correct answer is Option F: List, ACME-Products-Data-Color, ReadOnly, Node.

List vs. Page: Choosing 'List' is appropriate because the requirement is to populate a drop-down list

with multiple entries (colors in this case). 'Page' would be used for single record data, which is not

the case here.

Object Type: 'ACME-Products-Data-Color' is chosen because the data represents a list of color

options provided by the manufacturer, which is typically static reference data, fitting the 'Data' class

layer rather than the 'Work' layer which is used for case management or the 'Work-ColorFeedback'

which would be used for storing feedback or interactions specific to colors.

Edit Mode: 'ReadOnly' is the correct mode since users are selecting a color from a pre-defined list

and are not expected to edit these values directly.

Scope: 'Node' is selected to minimize memory usage. By setting the scope to 'Node', the data page is

loaded once per node (server instance) and shared across all requestors (users) on that node, which

is memory efficient for data that doesn't change often and is applicable across all users, such as a list

of colors.

This configuration ensures that the data page is loaded efficiently in a read-only list format at the

node level, reducing the overall memory footprint while making the color selections available across

the application.

Reference: Pega Academy's Data Pages module, which covers data page types, scopes, and best

practices for optimizing application performance and memory usage.