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 data page definition configuration settings to source a color
drop-down list to minimize memory usage.
Object Type » ACME-Products-Data-Color or ACME-Products-Work-Color or ACME-Products-Work-
ColorFeedback
Edit Mode » Readonly Or Editable Or Savable Scope » Thread Or Requestor Or Node
F
Explanation:
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.
A Declare expression evaluates a circumstanced decision tree. The decision tree evaluates a property
set by a data transform. What two steps do you perform to ensure that the decision tree is
configured properly? (Choose 2)
A, B
Explanation:
When configuring a Declare Expression that evaluates a circumstanced decision tree, ensuring
accuracy and expected behavior is crucial. The steps necessary involve:
A . Test the declare expression: This ensures that the Declare Expression, which automatically sets
the value of a property based on changes in other properties, works as expected. Testing confirms
the logic encapsulated in the decision tree is correctly evaluated and applied by the Declare
Expression.
B . Configure a test page with data to satisfy the circumstancing condition: This involves setting up a
scenario that meets the specific circumstances under which the decision tree's logic is evaluated.
Circumstancing allows different versions of a rule to be applied based on specific conditions. By
creating a test page that mimics these conditions, you ensure that the circumstanced version of the
decision tree is invoked, allowing for accurate testing.
Options C and D, while important in broader testing contexts, are less directly involved in the specific
task of ensuring the correct configuration of a circumstanced decision tree via a Declare Expression.
Reference: Pega Academy's modules on Declare Expressions and Decision Trees, which detail the
process for configuring, circumstancing, and testing rules to ensure they meet application logic
requirements.
A bookseller maintains a database of more than 10,000 book titles. You have been asked to configure
a form that a allow users to select a book by title.
How do you configure the form?
C
Explanation:
In scenarios involving a large dataset, such as a database of over 10,000 book titles, the most
efficient way to allow users to find and select an item is by using an autocomplete control. This
approach enhances user experience by filtering options based on user input, making it easier to
navigate through large lists of data.
Why not a drop-down? A drop-down control (Options A and B) would not be practical for such a large
number of items because it would require loading all items at once, which can lead to performance
issues and a poor user experience.
Why an autocomplete control? The autocomplete control (Option C) is designed for scenarios like
this. It allows the user to begin typing the name of a book, and the control suggests matching titles
based on the input, narrowing down the options dynamically. This approach is much more user-
friendly and efficient for large datasets.
Why sourced from a data page? Sourcing the autocomplete control from a data page (Option C) is the
best practice because it allows for the efficient loading and caching of data. Data pages can be
configured to refresh at appropriate intervals or under specific conditions, ensuring that the data is
up-to-date. Furthermore, using a data page abstracts the data source from the control, making the
application easier to maintain and update.
This setup ensures a smooth and efficient user experience, allowing for quick and easy selection from
a vast database of book titles
A business architect has developed a new process for a case type. To verify that the UI elements
collect the expected result, you want to test the process and the fields.
Which two configurations, when used together, allow you to record a set of interactions and save the
test result to verify process functionality? (Choose two.)
B, C
Explanation:
To effectively test a new process for a case type and verify that the UI elements collect the expected
results, utilizing scenario testing in Pega is highly recommended. This approach allows for recording a
set of interactions and saving the test result, which is crucial for verifying process functionality.
B . Create a scenario test for the case type: Scenario testing in Pega allows for the simulation of an
end-to-end process, including interactions with UI elements. This tool enables the creation and
execution of tests that mimic real-world user actions, ensuring that the entire process functions as
intended. By creating a scenario test, you can capture and automate the testing of specific pathways
through a case type, making it an essential tool for validation.
C . Add explicit assertions on the UI elements: Assertions are conditions that you expect to be true at
a certain point in your test. By adding explicit assertions to the UI elements during scenario testing,
you can specify the expected outcomes or states of those elements. This ensures that not only does
the process flow correctly, but the UI elements also behave and capture data as intended. Assertions
provide a powerful way to validate the functionality and user interface of your application precisely.
Together, these configurations enable a robust testing framework that can simulate user interactions,
verify UI behaviors, and ensure the overall functionality of the process and its fields.
Reference: Pega's official documentation on scenario testing and the use of assertions within these
tests provides guidance on how to effectively utilize these features for comprehensive testing and
verification.
A business architect has developed a new process for a case type. To verify that the UI elements
collect the expected results, you want to test the process and the fields. Which two configurations,
when used together, allow you to record a set of interactions and save the test results to verify
process functionality? (Choose Two)
A, D
Explanation:
For verifying the functionality of a new process and its associated UI elements, the combination of
creating scenario tests and adding explicit assertions is most effective.
A . Add explicit assertions on the UI elements: Assertions are used in testing to verify that a UI
element is in the expected state or contains the expected value after certain interactions have
occurred. They are crucial for ensuring that the UI behaves as intended, making them an integral part
of thorough testing strategies.
D . Create a scenario test for the case type: Scenario tests allow you to record a sequence of
interactions within your application to simulate real-world usage. Creating a scenario test for a case
type enables the recording and playback of interactions, including navigating through the process
and inputting data into fields, to verify that the entire case behaves as expected from start to finish.
Both options, when used together, provide a powerful approach to testing by allowing you to define
and verify the expected behavior of UI elements within the context of the complete process flow of a
case type.
Reference: Pega Academy materials on scenario testing, which include instructions for creating
scenario tests and adding assertions to ensure the accuracy of both the process flow and the UI
element interactions.
A car insurance quote requires a view for potential customers to enter information to process the
request. What are two primary decisions to make before you add fields to the view? (Choose Two)
A, D
Explanation:
Before adding fields to a view, especially in the context of designing a user interface for entering car
insurance quote information, it's crucial to consider several factors that impact usability and
functionality:
A . Is field entry required?: Determining whether a field is mandatory is crucial for guiding users
through the form completion process efficiently. Required fields ensure that all necessary
information is collected for processing the car insurance quote, influencing form design and
validation logic.
D . How do users enter values into the field?: This involves deciding on the input method or control
type for each field (e.g., text input, dropdown selection, date picker). The choice depends on the
nature of the information being collected and aims to enhance the user experience by making data
entry intuitive and error-free.
These decisions are fundamental because they directly affect the user interface's effectiveness in
gathering necessary information from potential customers. A well-designed form takes into
consideration the importance of each field and the most appropriate way for users to provide their
information, ensuring a smooth and user-friendly experience.
Reference: Pega's UI design principles and best practices, as covered in Pega Academy's courses on
UI and case management, emphasize the importance of these considerations in creating efficient
and user-centric interfaces.
A case type for voice over requests includes two tasks: Edit Script and Record Script. Your team has
been asked to route Edit Script tasks to editors and Record Script tasks to actors.
Which approach fulfills this requirement?
A
Explanation:
Routing tasks to specific groups within an organization is a common requirement in case
management systems. For the scenario involving voice over requests with distinct tasks for editors
and actors, creating separate work queues for each group is the most straightforward and effective
approach.
A . Create two new work queues, one for editors and one for actors: This option allows for the
segregation of tasks based
A company often receives multiple IT tickets for the same issue, such as ''the office Wi-Fi is down.You
configure Search duplicate cases step to identify duplicate IT tickets. What is the basic condition for
the Search duplicate cases step?
B
Explanation:
When configuring the "Search duplicate cases" step in a Pega application, especially for IT ticketing
systems, the primary aim is to identify multiple tickets raised for the same underlying issue. The
most straightforward and effective criterion for identifying duplicates in this context is the issue type,
such as "the office Wi-Fi is down."
B . Issue type is same: This option targets the core reason behind the creation of a ticket. Since
multiple individuals can report the same issue from various departments or locations, filtering by the
issue type ensures that all reports concerning a single problem (e.g., Wi-Fi outage) are identified as
duplicates. This approach helps in consolidating the efforts to address and resolve the issue
efficiently, avoiding redundant work.
Filtering by the name of the submitter, department, or office location (Options A, C, and D) might
miss duplicates reported by different users or from different areas, making "Issue type is same" the
most logical and effective criterion for identifying duplicates in IT ticketing scenarios.
Reference: Pega's official documentation on case management and the "Search duplicate cases" step
provides guidance on setting up duplicate search criteria based on the specific needs of the
application, emphasizing the importance of choosing criteria that accurately reflect the nature of the
duplicates being targeted.
A company requires that patients receive status updates during processing of medical tests.
Patients are not users of the application. You create the work party for the patient as an instance of
which class?
A
Explanation:
In Pega applications, work parties represent entities associated with a case. When configuring status
updates for patients who are not users of the application, it is essential to use a class that accurately
represents external individuals.
A . Data-Party-Person: This class is designed to represent individual people as parties in a case. Using
this class to create a work party for a patient allows the application to store relevant personal
information and contact details necessary for sending status updates about medical test processing.
Since patients are the recipients of the information and not operators or organizational entities
within the system, this class is the most appropriate choice.
The other options, such as Data-Party-Operator (used for application users), Data-Party-Org (used for
organizations), and Data-Party-Com (used for commercial entities), do not fit the context of
individual patients receiving updates.
Reference: Pega Academy's courses on case management detail the use of work parties in cases,
explaining the purpose of various Data-Party classes and how they are applied in real-world
scenarios to manage communications and interactions.
A customer calls to apply for a new bank account. The customer service representative (CSR) needs
to perform an assignment named Select Account Type. During the discussion, the customer can
request written information regarding different account types.
Select the case lifecycle design that satisfies this requirement.
C
Explanation:
In the scenario where a customer service representative (CSR) might need to provide written
information about different account types during a case, adding flexibility to the case lifecycle is key.
C . Add a case-wide optional action: This approach allows the CSR to initiate the action of sending or
requesting information at any point during the case, without being tied to a specific stage or
assignment. Case-wide optional actions are accessible from anywhere within the case, providing the
necessary flexibility to respond to the customer's request at the moment it occurs, regardless of the
current case stage or assignment.
The other options, such as adding a user view (Option A), adding an optional action to a specific
stage (Option B), or adding a router (Option D), either limit the action to a particular context or don't
directly address the need to provide information flexibly throughout the case lifecycle.
Reference: Pega's case management documentation highlights the use of case-wide optional actions
as a means to introduce flexibility into the case workflow, allowing users to perform actions that are
relevant at any point in the case process, thereby enhancing the ability to respond to dynamic
requirements and customer requests.
A customer refund case type requires that an auditor receives an email notification if the refund is
greater than twice the price of the item. Which participant role do you select to configure this
requirement?
B
Explanation:
For the requirement where an auditor needs to receive an email notification if the refund is greater
than twice the price of the item, it's important to select a participant role that accurately reflects the
auditor's involvement in the case.
B . Interested individual: This role is designed to represent parties who need to be informed about
certain events or milestones within a case but are not directly responsible for actioning the case. In
this scenario, the auditor's role is to be notified under specific conditions for oversight purposes,
making "Interested individual" the appropriate choice. This setup allows the application to send
targeted notifications to the auditor without assigning them case responsibilities that are not part of
their role.
The other options, such as Customer (Option A), Owner (Option C), and Work queue (Option D), do
not accurately represent the auditor's role in relation to the specific notification requirement.
Reference: Pega's case management features include the ability to define and manage the roles of
various participants in a case. Documentation and training materials on case design and notification
strategies explain
A customer views a product available in multiple color options. The customer must select only one
color for each product. Which Ul control allows a developer to present the user with all color choices
at once, without prompting or clicking, while ensuring that the user can only select one of the color
options?
A
Explanation:
For a scenario where a customer is viewing a product available in multiple color options and must
select only one color for each product, radio buttons are the ideal UI control. Radio buttons allow all
options to be presented to the user simultaneously, without the need for any additional action to
view the choices. Importantly, they enforce a single selection, ensuring the user can only choose one
of the available color options.
A . Radio buttons: This control type is specifically designed for cases where a single choice must be
made out of multiple options presented. It is user-friendly and visually communicates that only one
option can be selected, making it perfect for selecting a product color.
The other options, such as Text input (B), Drop-down (C), and Check box (D), do not fulfill the
requirements as effectively. Text input doesn't provide predefined choices, a drop-down requires an
additional click to view options, and check boxes allow multiple selections, which does not match the
requirement of selecting only one option.
Reference: Pega's official documentation on UI controls details the use cases for different control
types, including radio buttons, emphasizing their use for single selections from a group of options.
A customer wants to copy the contents of a previous order to their current order. What rule type do
you use to copy the order contents?
B
Explanation:
To copy the contents of a previous order to a current order, the most appropriate rule type to use is a
Data Transform. Data Transforms in Pega are designed to set or copy data from one context to
another, making them ideal for this requirement.
B . Data transform: This rule type allows for the manipulation and copying of data between pages,
including complex structures such as order contents. It provides a straightforward way to define how
data from a previous order should be mapped and copied to the current order, allowing for
customizations such as conditionally copying certain items or applying transformations to the data
during the copy process.
The other options, such as Data page (A), Declare expression (C), and Function (D), serve different
purposes. Data pages are used to load data, Declare expressions for calculating values based on
changes in other values, and Functions for executing specific operations, none of which directly
address the requirement of copying order contents.
Reference: Pega Academy's materials on Data Transforms explain their use for copying and
manipulating data, providing examples and best practices for efficiently managing data within
applications.
A data page holds product information and has the Reload if Older Than field set to 30 minutes. The
data page is created at 7:43. The user then performs the following actions: 8:10 the user refreshes
the product information 8:45 the user refreshes the product information At what time is the data
page reloaded?
C
Explanation:
Given a data page set to reload if older than 30 minutes, understanding the timing for when the data
page is reloaded is essential for ensuring that users have the most current information. The data
page is created at 7:43. Based on the Reload if Older Than setting, it will reload if accessed after 30
minutes from its creation or the last reload.
C . 8:40: The data page would be reloaded at 8:40 because this is the next access time that falls
outside the 30-minute validity period established from the data page's last known load time or
creation. Although the user refreshes the product information at 8:10 and 8:45, the key moment for
reload based on the given timeline and settings would be 8:40, which is 30 minutes after the 8:10
refresh, not 8:45 since that's the time of access, not reload.
The options 8:13 (A) and 8:10 (B) are too soon for a reload based on the initial creation time and do
not account for the 30-minute refresh policy correctly. Option D (8:45) represents a time of user
action, not the actual reload based on the described criteria.
Reference: Pega documentation on data pages details how the "Reload if Older Than" setting
determines the refresh strategy for data pages, ensuring that data remains current without
unnecessary reloads, optimizing performance while providing up-to-date information.
A data page holds product information. The data page's Reload if older Than field is set to 15
minutes. The data page is created at 06:12.At 06:20 the user requests product information. At 06:42
the user requests product information. When is the data page reloaded?
D
Explanation:
For a data page set with a "Reload if Older Than" threshold of 15 minutes, it is essential to
understand how this setting dictates the data page's reload timing in response to user requests for
product information.
D . 06:42: The data page is reloaded at 06:42 because this is the point at which the next user request
for product information occurs outside the 15-minute validity window from the data page's last load
at 06:12. The 06:20 request does not trigger a reload since it falls within the 15-minute window. By
06:42, the data page has surpassed the "Reload if Older Than" threshold relative to its initial load
time, necessitating a reload to ensure the currency and accuracy of the product