CPSA Data Modeling and Properties 3 — Questions and Answers
Question 1: A data page is configured with scope set to 'Requestor'. What does this mean for data page lifetime?
- The data page is recreated for every rule execution
- The data page persists for the duration of the user's login session (Correct answer)
- The data page is shared across all users on the same node
- The data page is destroyed when the current thread ends
Correct answer: The data page persists for the duration of the user's login session
A Requestor-scoped data page persists for the entire duration of the user's login session, shared across all threads for that user.
Question 2: Which data page object type should be used when the data page must return a list of results rather than a single record?
- Page
- Single page
- List of pages (Correct answer)
- Scalar value
Correct answer: List of pages
Setting the data page object type to 'List of pages' allows it to return multiple records as an indexed page list.
Question 3: A developer configures a data page with 'Reload once per interaction' refresh strategy. When is the data page refreshed?
- Every time a property on the data page is accessed
- Once at the start of each new user interaction or flow action (Correct answer)
- Only when explicitly invalidated by a data transform
- Every 60 seconds by default
Correct answer: Once at the start of each new user interaction or flow action
The 'Reload once per interaction' strategy refreshes the data page once at the beginning of each flow action or user interaction.
Question 4: What is the correct syntax to reference a property named 'Status' inside a data page named 'D_CustomerData'?
- D_CustomerData(Status)
- D_CustomerData.Status (Correct answer)
- datapage:D_CustomerData.Status
- @D_CustomerData[Status]
Correct answer: D_CustomerData.Status
Pega uses dot notation to reference properties within a data page, so D_CustomerData.Status is the correct reference syntax.
Question 5: A data page uses a Report Definition as its data source. Which parameter must match between the data page and the Report Definition for the lookup to work correctly?
- The data page's class must match the Report Definition's applies-to class (Correct answer)
- The data page scope must be set to Node
- The Report Definition must return exactly one column
- The data page must have no parameters defined
Correct answer: The data page's class must match the Report Definition's applies-to class
The class the data page applies to must match the Report Definition's applies-to class so Pega can map the returned data correctly.
Question 6: Which data page parameter usage allows the same data page rule to return different data sets based on input values?
- Scope
- Object type
- Parameters with unique values (Correct answer)
- Refresh strategy
Correct answer: Parameters with unique values
When a data page has parameters, each unique combination of parameter values results in a separate cached instance of the data page.
Question 7: A Thread-scoped data page is loaded in a flow. When does this data page get destroyed?
- When the user logs out
- When the application server restarts
- When the thread (flow execution) ends (Correct answer)
- After a configurable timeout period
Correct answer: When the thread (flow execution) ends
A Thread-scoped data page exists only for the lifetime of a single flow thread and is destroyed when that thread completes.
A data page is configured with scope set to 'Requestor'.
What does this mean for data page lifetime?