PEGACPSA23V1 Pegasystems Certified Pega System Architect Free Practice Exam Questions (2025 Updated)

The scenario describes a series of actions related to managing a job application process. Proper naming of steps in a business process is crucial for clarity and effective communication. The step "Schedule Interview" directly reflects the action of setting up the date and location for the interview, while "Notify Candidate" describes the action of sending an email confirmation to the candidate. These names are clear, action-oriented, and specific to the tasks being performed, aligning with best practices in business process modeling.

Field Value rules in Pega are used primarily for localizing user interface elements:

A. Labels and drop-down values on a section rule. Localizing these elements ensures that applications can adapt to different languages and regional settings, enhancing user accessibility and usability across diverse geographical locations.

To dynamically update the total cost of a travel reservation as users update each child case component:

B. Configure the Create Case shape to propagate the total cost from each child case to the reservation. Create a declare expression to update the reservation total when the cost of each component changes. This approach leverages the use of a declare expression to automatically update the total cost in the parent case whenever any changes occur in the child cases' costs. It ensures that the reservation total remains accurate and reflective of the current costs associated with the flight, hotel, and vehicle rental bookings.

To display multiple options (like balance transfer offers) on a form where only one can be selected at a time, the suitable control types are:

B. Radio buttons. Radio buttons are ideal for allowing users to select one option from multiple choices. They are mutually exclusive, which means selecting one option deselects any other previously selected option.

D. Drop-down list. A drop-down list also allows users to select one option from multiple choices presented in a compact form. It ensures that only one selection can be made at any time, fitting the requirement to prevent multiple selections.

Responsive breakpoints in UI design:

A. Responsive breakpoints trigger selected behaviors to optimize data presentation. Breakpoints are specific widths at which a site’s layout will adjust to provide the best user experience. They help to ensure that no matter the size of the screen, from a mobile phone to a desktop monitor, the application presents data in an organized and readable manner.

To ensure medical claims are resolved within a 5-day timeframe, the appropriate configuration in a service level agreement involves setting a specific deadline:

C. Deadline. In Pega, the deadline parameter in a service level agreement specifies the maximum allowable time by which a case or task must be completed. Setting this to 5 days ensures that the medical claim processing adheres strictly to the required timeframe.

For a purchase request list report that includes columns for case ID and regional cost center, and with a requirement to show the total of purchase requests for each regional cost center, summarizing data correctly is essential.

B. Summarize the case ID column by count: This configuration tallies the number of purchase requests (case IDs) for each regional cost center, effectively meeting the manager's requirement. By summarizing the case ID column by count, the report will display the total number of

The Estimator tool is primarily used for project management and planning in Pega, particularly for determining the scope and scale of development efforts:

D. A stakeholder needs to know how much time and effort is needed to build MLP2. This use case describes the fundamental function of the Estimator tool, which is to provide stakeholders with detailed estimates of time, effort, and resources required to build a specified part of an application, such as MLP2.

In Pega, calculating values such as total working hours, sick hours, and vacation hours often involves using data transforms to manipulate and set property values based on logic defined within the application. A "Calculate field" in a data transform would allow for the dynamic calculation of these values based on inputs such as logged time entries, absence records, and other relevant data inputs. This method is efficient for real-time computation and updates of calculated fields within a table or data page.

To ensure a form supports accessibility, especially when enabling a user to specify a date, using an interface that is intuitive and easy to navigate is key. Among the provided options, a calendar control that displays an entire month is the most accessible and user-friendly method for date selection.

C. Use a calendar control that displays an entire month: This method provides a visual and interactive way for users to select a date, offering both keyboard navigation and screen reader support, making it accessible to users with a wide range of disabilities, including visual impairments. A month view gives users an overview of the dates, allowing for easy selection without requiring manual date entry, which can be prone to errors and less accessible for some users.

Configuring a text box for date entry (A) may not be as accessible because it relies on users correctly typing the date, which can be challenging for some people. Using a calendar control that displays an entire year (B) can be overwhelming and less practical for date selection. Providing separate controls for month, day, and year (D) could increase complexity and potentially decrease accessibility due to the need to navigate between multiple controls.

In these examples, each path notation accesses properties from presumably a single-record data structure (where each record corresponds to a single instance of an Address or similar object). "Single record data relationship" refers to accessing data from a single instance, rather than multiple records or a list. Each path is structured to directly access specific properties within a singular data context, which is characteristic of single record relationships.

In Pega Express, when creating a new child case, the "Create Case" shape in the case designer is used to configure the propagation of data from a parent case to a child case. This shape can be configured to copy specified properties to the new child case, ensuring that necessary data is automatically carried forward. This configuration is essential for maintaining data consistency and relevance across related cases, facilitating seamless case management and data integrity.

UI object that represents the combination of data and a template. - Template

Preassembled view with a preset template and data requirements. - View

Automatically generated view that represents a single case in Pega Platform. - Full case view

Generic rendering structure that presents data with visual style and interaction behavior. - Widget

Comprehensive Detailed Explanation with References:

The four descriptions provided relate to elements within the Pega Platform, specifically tailored for the Constellation UI architecture, which is focused on delivering a responsive and user-friendly interface for applications.

Template: In Pega, a template refers to a predefined format for presenting data. It specifies the layout and structure used to display information. A UI object that combines data and a template can be seen as the blueprint from which UI elements are generated, ensuring consistency and adherence to design standards.

View: A view in Pega is a configuration that determines how data is displayed in the UI. It's a preassembled component that combines a specific template with data requirements, thus simplifying the creation of user interfaces by allowing developers to reuse common patterns and layouts with different sets of data.

Full case view: This refers to a holistic view of a case in Pega, showing all relevant information and actions that can be taken. It is generated automatically by the platform to represent all the aspects of a case, providing a comprehensive interface for users to interact with case data and perform necessary tasks.

Widget: Widgets in Pega are generic, reusable UI components that display data and offer interactive behavior. These can range from simple data fields to complex graphical components. They are styled and have behaviors that allow users to interact with the data presented, such as drop-down menus, charts, or data grids.

References:

Pega Community articles and documentation provide insights into these concepts. Specifically, you can refer to Pega Community resources for understanding the Constellation UI architecture and the role each component plays within it.

Pega Platform Help files, which can be accessed directly through the Pega Platform, offer detailed explanations and guidelines for creating and using templates, views, full case views, and widgets.

As noted in Question No: 119, in Pega’s Case Designer, tagging automations and approval decisions for an MLP release is strategic for project sizing. This method is used to ensure that these components, which are critical to the operation and user experience of the application, are developed, tested, and refined early in the project lifecycle. This helps in aligning development priorities with business needs and in ensuring that the most impactful features are ready and optimized in the initial release of the product.

Major version: In Pega, a major version update is typically used when there are significant changes to the application, such as the introduction of new functionalities, case types, or major changes to existing functionalities. Adding a new "Order return" case type to the Shopping application constitutes a significant enhancement, thus it would usually require incrementing the major version of the ruleset.

Minor version: Minor version updates are used for less significant changes that don't alter the application's primary functionality but still add enhancements or optional components to the existing structures. Adding a stage-specific optional action to an "Order placement" case lifecycle would be a good candidate for a minor version update because it extends the functionality without fundamental changes.

Patch version: Patch versions are often used for bug fixes or minor improvements that do not add new functionalities but rather correct issues with existing ones. Fixing a bug that lists product options by product ID instead of by name is a classic example of a patch fix, as it corrects a specific issue without materially expanding or altering the functionality of the application.

References:

Pega official documentation would typically include a section on ruleset versioning that describes the scenarios for using major, minor, and patch versions.

Best practices as described in Pega Community articles and the Pega Academy training materials also discuss how to manage ruleset versions effectively in various development scenarios.