To process a loan application, evaluate an applicant’s credit score: >700 to underwriting,

The question requires mapping a set of business rules to a Pega Decision shape. A Decision shape evaluates conditions sequentially to route a case. The logic is as follows:

1. If the credit score is greater than 700, the case proceeds to underwriting.

2. If not, it checks if the score is less than 500, in which case it sends a denial email.

3. If neither of the first two conditions is met (i.e., the score is between 500 and 700 inclusive), the case is routed for review.

Option A correctly models this logic by setting the first condition to >700, the second to <500, and using the else path for the remaining cases.

B: This option incorrectly routes scores >700 to review and scores <500 to underwriting, directly contradicting the specified business requirements.

C: This option incorrectly routes scores >700 to email and scores <500 to review, which misaligns with the required processing paths.

D: This option incorrectly routes scores >700 to review and uses the 'else' path for underwriting, failing to match the specified logic.

1. Pega Academy: Low-Code App Builder (24.1)

"Controlling the case workflow" module

"Conditional paths" lesson. This lesson explains that a Decision shape is used to model a decision point in a process. It evaluates conditions to determine which of the possible connectors to follow

including an "Otherwise" or "Else" path for when no other conditions are met.

2. Pega Documentation: Case management > Case life cycles > Conditional processing > Adding a conditional path to a case life cycle. This document states

"Create a conditional path in a case life cycle to ensure that your business process has a flexible flow. By defining conditions

you can determine which actions users can perform and when." It details configuring When conditions and the Otherwise path

which directly applies to the scenario.

3. Pega Documentation: Process and rules > Processes > Flows > Flow shapes > Decision shape. This section describes the function of the Decision shape: "Use a Decision shape to call a decision rule

such as a decision tree

or a map value

to determine which connector to follow out of the shape." The logic described in the question is a direct implementation of this shape's purpose.