PEGACPSA88V1-QUESTION practice question 3 of 15

A library application used by staff creates a book request case when a member wishes toborrow one or more books. As part of the case process, the application shows the staff a readonly list of outstanding past-due books to remind the member to return late books, select the Data page definition for this use case.

Full set: 82 questions
Answer options
A: List,Readonly, Thread
B: Page,Editable,Node
C: Page,Readonly,Requester
D: List,Readonly,Requestor Correct answer
E: Page,Editable,Requester
F: List,Readonly,Node
Correct Answer:
D. List,Readonly,Requestor
Explanation

The use case requires displaying a "list of outstanding past-due books." This dictates the data page's structure must be a List, as it needs to hold multiple records (books). The requirement specifies a "read-only list," so the mode must be Read-Only. The data is specific to the member being assisted by the staff member for the duration of their interaction (session). The Requestor scope is most appropriate as it caches the data for the user's entire session, making it available across different cases or screens without reloading, which is efficient and contextually correct for data related to the user's current task.

Why Incorrect

A. List, Readonly, Thread: Thread scope is too narrow. The data is cached only for the current case, requiring a reload if the staff member opens another case for the same member.
B. Page, Editable, Node: Page is for a single record, not a list. Editable is incorrect. Node scope is for data shared by all users, which is inappropriate for member-specific data.
C. Page, Readonly, Requester: Page structure is incorrect as the requirement is to display a list of multiple books, not a single record.
E. Page, Editable, Requester: Page structure is for a single record, not a list. Editable mode is incorrect as the data is for display only.
F. List, Readonly, Node: Node scope is incorrect. The list of past-due books is specific to an individual member, not data to be shared across all users on the server node.

References

1. Pega Academy - System Architect 8.8 Mission, "Data Pages" Module: This courseware explains the fundamental components of a data page.

Structure: "On the Definition tab of a data page, you select either Page or List from the Structure drop-down list. Select List for a data page that returns a list of objects." This supports using List.

Mode: "Data pages can have one of three modes: Read-Only, Editable, or Savable." The Read-Only mode is used for presenting data to the user. This supports the Read-Only choice.

Scope: "Select Requestor to make the data page available to a single user session... For example, the contents of a shopping cart can be stored on a requestor-scoped data page." This supports using Requestor for data tied to the user's session context.

2. Pega Documentation - "Defining the structure of a data page": "For a data page that you want to contain a list of items of a certain class, in the Structure field, select List." This directly validates the choice of List for a "list of... books."

3. Pega Documentation - "Defining the scope of a data page": "Requestor - The data page is available for a specific user. The page is created when a user first accesses it and is removed when the user logs off... Use this scope for data that is specific to the user, for example, the user's profile." This confirms Requestor scope is correct for data tied to the user's context. The document contrasts this with Node (shared by all users) and Thread (specific to a single case).

Scroll to Top