PEGACPSA23V1 Questions Bank

For an internet provider's quiz designed to recommend internet speeds based on varying customer usage profiles, including differentiating between residential and business needs, employing a decision mechanism that efficiently handles multiple input factors is key.

• A. Configure a decision table: Decision tables are ideal for scenarios where the output (recommended internet speed) depends on multiple conditions (quiz answers about internet use). They offer a clear, concise way to map various combinations of inputs to their corresponding outputs, making it easy to update and manage as new conditions or outcomes are introduced. This configuration supports dynamic and nuanced decision-making based on customer responses.

Configuring a view with quiz questions (B) is necessary for collecting inputs but does not determine the outcome. A decision tree (C) could also be used but might become complex with multiple branching conditions. A process with multiple decision shapes (D) could handle the logic but may be less efficient and harder to maintain than a decision table.

In Pega, the ruleset list for a logged-in operator typically includes rules that the operator has permissions to access or modify. The "Admin@MyCo" ruleset, along with other listed rulesets, contains rules that are delegated to the operator. This delegation enables the operator to manage or override certain rules within their scope of responsibility, supporting customizable and dynamic application behaviors based on business needs and operational requirements.

To indicate mandatory fields on a form with asterisks, the correct approach is:

B. Configure the mandatory fields as Always Required on the form at runtime. This setting directly influences how fields are displayed on UI forms, including the automatic addition of asterisks to visually indicate that these fields must be filled out before submission. This approach does not involve validation rules, which are for data integrity checks post-entry, but rather it ensures user awareness of required inputs from the onset.

Configuring a service level at the stage level in an insurance claim application is the most effective way to ensure that all claims processed in that stage meet the specified resolution time of 1 week. Service levels defined at the stage level apply to all processes and steps within that stage, providing a consistent and enforceable timeframe for action on claims, which is crucial for meeting regulatory or business timeframes.