Pegasystems PEGACPSA23V1 - Certified Pega System Architect

To ensure the validation that the 'Date account opened' is indeed in the past for a loan application:

B. Use a validate rule to verify the Date account opened is in the past. Validate rules in Pega are used to enforce data integrity and accuracy, making them suitable for verifying that a date entered is before the current date. This method ensures that data meets the business requirement directly and effectively.

A data element in Pega is essentially defined by two key components:

B. The name of the data element. This is the identifier for the data element, which allows it to be referenced and manipulated within processes and data structures.

D. The value of the data element. This represents the actual data stored within the element, which can be any piece of information relevant to the application processes, such as a user input, system-generated data, or data retrieved from external sources.

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.

When diagnosing an issue with a calculated property value using the Tracer tool:

B. Breakpoints. This feature allows you to pause the execution at certain points, enabling you to inspect the processing of the rules and properties, which is helpful in identifying where and why a property is not calculating as expected.

C. The Watch function. By watching specific properties, you can monitor changes to their values in real time as the process executes, which helps in determining the point at which the unexpected result occurs, all with minimal overhead on application performance.

To minimize clutter on an order form where customers select one option out of four, using UI controls that efficiently manage screen real estate while ensuring user-friendliness is crucial.

A. Dropdown: A dropdown menu consolidates the four options into a single interactive element. When not in use, it takes up minimal space on the form, contributing to a cleaner, less cluttered appearance. It expands when interacted with, allowing the user to make a selection from the list.

C. Radio buttons: Radio buttons allow all options to be visible at once, ensuring immediate visibility of choices without additional interaction. Because selecting one option automatically deselects any other, radio buttons are ideal for single-choice scenarios. They can be designed to be compact, minimizing their impact on the form’s layout.

Checkboxes (B) are typically used for selections where multiple options can be chosen simultaneously, which does not align with the requirement for a single selection. Autocomplete (D) is useful for forms with a large number of options or for facilitating quick selection from a list through typing, which might not be necessary or as efficient for a small, fixed set of four options.

The requirement specifies that modifying physician details should be possible at any time without impacting primary case processing. An alternate stage in Pega allows for actions that do not directly interfere with the main process flow of the case life cycle. This configuration enables asynchronous processing of secondary tasks such as updating details that are important but not critical to the main case progression. This approach keeps the primary case stages focused on their core objectives while providing flexibility for side tasks.

For an international online car parts business aiming to facilitate vehicle-specific searches by customers based on make, model, and year, integrating with a comprehensive, up-to-date database is crucial.

B. Configure a connection to an external system of record: This approach leverages an existing, authoritative source of vehicle data, ensuring that customers have access to accurate and comprehensive information for their searches. By establishing a connection to an external system of record, the application can dynamically access the latest vehicle data without the need for manual updates or maintenance, enhancing the search functionality's reliability and coverage.

Configuring a data page (A) could support data access but would still require a data source, potentially from an external system. A static list (C) may quickly become outdated due to the vast and evolving variety of vehicles. Local data storage (D) offers control but might lack the breadth or current data found in specialized external systems.

The step name "Investigate Claim" most accurately describes the activity where the customer service agent reviews the details of a fraud complaint. This naming is clear and action-oriented, specifying what the agent is doing (investigating) and the subject of the investigation (the claim). It is preferred over options like "Claim Investigation" or "Investigate Fraud" because it follows the verb-noun format that is recommended for naming steps in Pega, where the verb denotes the action and the noun denotes the object of the action.

When configuring mobile app channels for ABC BankCorp's Transaction Dispute application to accommodate GloboBank and LocalBank, certain requirements directly influence the need for separate channels due to differing functionalities or branding.

B. Customers can create only dispute cases, while CSRs can also create fraud report cases: This requirement indicates a functional difference between the apps intended for customers and CSRs. The ability of CSRs to handle additional case types (fraud report cases) necessitates a tailored app configuration to support these distinct functionalities, likely leading to the need for separate app channels for customers and CSRs.

C. Mobile app color palette is customized for each subsidiary: The requirement for subsidiary-specific branding, including color palettes, directly impacts the app's UI design. To maintain distinct brand identities for GloboBank and LocalBank within the app, separate mobile app channels would be required to accommodate the different branding elements for each subsidiary.

Supporting both phones and tablets (A) and customizing currency units and date/time format according to the user's locale (D) are requirements that can typically be met within a single mobile app channel through responsive design and localization features, and thus do not inherently require multiple app channels.

For displaying book cover pictures in a grid or list format on an online bookstore form:

C. Repeating dynamic layout. This layout type is ideal for displaying collections of items such as book covers, as it can dynamically repeat content based on the data source. It allows for an organized, responsive, and visually appealing presentation of new arrivals, each represented by their respective cover image.