Free Pegasystems PEGACPSA23V1 Practice Exam with Questions & Answers | Set: 2

Calculated fields in Pega are used to compute values based on other data elements within the application, suitable for:

A. A sales representative wants to quote the cost of an insurance policy based on selected coverage options. Calculated fields can dynamically compute the total cost of an insurance policy as different coverage options are selected, providing real-time pricing information.

C. A project manager wants to estimate the cost of painting a banquet hall based on labor and materials required. Similarly, calculated fields can be used to aggregate costs of materials and labor to provide an overall estimate for a project, facilitating budget management.

Statements true about Configuration sets:

B. Used to organize Configuration settings with a common element. Configuration sets in Pega are used to group related settings, which can be managed collectively and applied consistently across the application.

D. Enables the business to control application behavior. Configuration sets allow business users to change certain aspects of the application behavior without modifying the underlying code directly, providing greater agility and control over the application.

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.

To inspect and verify the contents of a data page during form testing:

A. The Clipboard tool. This tool is integral for developers to view and manage the current state of data pages in memory, providing a detailed snapshot of all data pages loaded during a session, including their contents and structure. It is invaluable for verifying data integrity and troubleshooting data-related issues in forms.

To improve the performance of a report listing customer order cases where the Order Total value is a critical criterion:

A. Order Total. Optimizing the Order Total property allows for faster sorting and filtering operations specifically on this field, which is crucial for performance, especially when dealing with large datasets where queries are based on financial thresholds.

Adding an external data source to a data object in Pega requires specific details to ensure proper integration and functionality:

A. The authenticating information, if required by the corresponding service. Secure access to external data services often requires authentication details, such as API keys or login credentials, to ensure that interactions are authorized.

D. The uniform resource identifier that identifies the web service. The URI is crucial as it specifies the exact location and endpoint of the web service from which data is to be fetched, acting as a link between the Pega application and the external data source.

The appropriate scope for a data page that lists products purchased by a customer viewed in an online portal is "Requestor". This scope ensures that the data page is unique to each user session and is accessible across multiple requests within that session. The "Requestor" scope is suitable because it persists for the duration of the user's interaction with the application, across multiple threads or cases, making it ideal for situations where a user might be working on multiple support requests during a single login session.

In Agile Workbench, when a stakeholder identifies an issue like a missing option in a dropdown list during a playback session, the appropriate work item to create is a "Bug." This is because the issue represents a deviation from the expected functionality or requirements that need to be addressed by the development team. Bugs in Agile Workbench are used to track errors or problems that need resolution to meet the outlined specifications or user expectations.

To meet the requirement that loan applicants must enter their annual salary and that the application process diverges based on whether the salary is above or below a qualifying threshold, the configuration options chosen must efficiently manage the conditional logic and user interaction.

• A. Design a user view with an annual salary field and a data relationship for cosigner information: This approach efficiently handles the collection of applicant salary information and conditional display of cosigner information fields. A visibility condition based on the annual salary ensures that additional cosigner information is requested only when necessary, streamlining the application process for those above the threshold.
• B. Use a collect information step with an annual salary field. Use a decision shape to determine whether to advance to a step to enter cosigner information or complete the process: This configuration leverages the process modeling capabilities in Pega, where a decision shape dynamically directs the flow of the application based on the salary entered. It succinctly captures the requirement's logic, ensuring applicants are either promptly approved or directed to provide cosigner details, as appropriate.

Option C proposes an optional action for collecting cosigner information, which might not strictly enforce the requirement for applicants below the salary threshold. Option D, involving manual review by a loan officer, introduces potential bottlenecks and departs from the requirement for automatic approval based on salary.

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.