Pegasystems PEGACPSA23V1 Online Practice Questions and Exam Preparation

Pegasystems PEGACPSA23V1 Online Questions & Answers

• Question 251:

  When a user selects a item in a list, the application displays data about that item. Data is copies to a page property using the Copy from a data page options. After the data has been copies to the property, when is the data copies to the property again?

  A. Never
  B. The next time the case is opened
  C. The next time the property is accessed
  D. When the item is changed
  C. The next time the property is accessed

  ---

  Explanation/Reference:

  In the context of copying data from a data page to a page property in Pega:

  C . The next time the property is accessed. The data is copied to the property again whenever the property is accessed, ensuring that the most current data from the data page is reflected. This behavior is part of Pega's strategy to maintain updated and relevant data within user interactions, particularly in dynamic environments where data can change frequently.

• Question 252:

  Identify Text, Multi record data relationship, Single record data relationship

  A. .Address( 1 ).pincode
  B. .ShippingAddress.City
  C. .BillingAddress.Telephone
  A. .Address( 1 ).pincode
  B. .ShippingAddress.City
  C. .BillingAddress.Telephone

  ---

  Explanation/Reference:

  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.

• Question 253:

  A requirement states When a customer applies for a credit card, a credit check must be completed in order for the credit card to be approved. Select the case type relationship that satisfies the requirement.

  A. Make both loan request and credit check top cases.
  B. Make credit check a spin-off case of credit card request.
  C. Make credit check a child case of credit card request.
  D. Make credit card request a child case of credit check.
  C. Make credit check a child case of credit card request.

  ---

  Explanation/Reference:

  For the requirement that a credit check must be completed for a credit card to be approved, incorporating the credit check as part of the credit card application process is necessary. The most straightforward way to model this is by using case type relationships.

  C . Make credit check a child case of credit card request: This configuration establishes the credit check as an integral step within the credit card request process, ensuring that the credit check is completed before the credit card can be

  approved. Making the credit check a child case means it is directly associated with and dependent on the parent credit card request case, aligning perfectly with the requirement. Making both the loan request and credit check top cases (A)

  does not establish the necessary dependency. Creating a spin-off case (B) suggests a parallel or subsequent process not inherently dependent on the completion of the credit check for the credit card request, which could misalign with the

  requirement. Making the credit card request a child case of credit check (D) inverts the intended relationship and does not accurately represent the process flow described in the requirement.

  Pega's case management documentation provides insights into designing case hierarchies and relationships, including the use of child cases to model dependent processes within an overarching case.

• Question 254:

  Which three use cases demonstrate the Pega dynamic Ul behavior? (Choose Three)

  A. Display a message upon form submission that a date field must be in the future.
  B. Unmask a password field when users click an icon.
  C. Automatically calculate order total when users change quantities.
  D. Display partner information fields when a screen loads for married applicants.
  E. Display a shipping address section when users select the Different than billing address check box.
  A. Display a message upon form submission that a date field must be in the future.
  C. Automatically calculate order total when users change quantities.
  E. Display a shipping address section when users select the Different than billing address check box.

  ---

  Explanation/Reference:

  Dynamic UI behavior in Pega is exemplified by interactions that adjust in real-time to user input or conditions:

  A . Display a message upon form submission that a date field must be in the future. This is a validation feature that dynamically checks the validity of date inputs against the condition set (future date) at the time of form submission. C . Automatically calculate order total when users change quantities. Dynamic UI behavior includes recalculating values in real-time as users adjust input parameters, like quantity in this case, enhancing the interactive experience. E. Display a shipping address section when users select the 'Different than billing address' checkbox. This functionality shows additional UI components based on user selections, which is a key feature of dynamic UIs, allowing for a responsive and adaptive user interface.

• Question 255:

  You are developing a Visa case type to process visa applications. As part of the process, applicants need to schedule an interview with the consulate. A child Interview case is created for the interview process and assessment. Following the

  interview, it typically takes 48 hours for the consulate to reach a decision. For the visa case to proceed to applicant notification, the Interview case needs to be resolved.

  How do you configure a case type to achieve the required behavior?

  A. Add a Create Case step that creates the Interview child case. Following this step, add a Wait step that pauses the parent case until the Interview case reaches a status of Resolved and after 48 hours have elapsed.
  B. Add a Create Case step that creates the Interview child case. Following this step, add a Wait step that pauses the parent case until 48 hours have elapsed.
  C. Add a Create Case step that creates the Interview child case. Following this step, add a Wait step that pauses the parent case until the Interview case reaches a status of Resolved.
  D. Add a Create Case step that creates the Interview child case. There is no need to add a Wait step.
  C. Add a Create Case step that creates the Interview child case. Following this step, add a Wait step that pauses the parent case until the Interview case reaches a status of Resolved.

  ---

  Explanation/Reference:

  To configure a case type that properly manages the progression of a visa application contingent upon the resolution of an Interview child case:

  C . Add a Create Case step that creates the Interview child case. Following this step, add a Wait step that pauses the parent case until the Interview case reaches a status of Resolved. This approach ensures that the main Visa case does not proceed to the next phase until the Interview child case is fully resolved, aligning the process flow with the actual completion of necessary steps. The 48-hour period for decision-making is likely internal to the consulate's process and does not affect the configuration of the wait condition in the case type.

• Question 256:

  Which two configurations do you use to validate the minimum age of a new potential customer in the Collect Account lnformation assignment step? (Choose Two)

  A. Create an Edit Validate rule to check the customer age.
  B. Reference the Edit Validate rule on the Collect Account lnformation flow action.
  C. Reference the Validate rule on the Collect Account lnformation flow action.
  D. Reference the Validate rule on the Collect Account lnformation assignment.
  E. Reference the Edit validate rule on the Collect Account lnformation assignment.
  F. Create a Validate rule to check the customer age.
  B. Reference the Edit Validate rule on the Collect Account lnformation flow action.
  F. Create a Validate rule to check the customer age.

  ---

  Explanation/Reference:

  To validate the minimum age of a potential customer in a specific assignment step within Pega:

  B . Reference the Edit Validate rule on the Collect Account Information flow action. Although typically, an Edit Validate rule would be used to check formats rather than conditions like age, referencing a validation rule within the flow action is the right approach to ensure data correctness before the user progresses past this step.

  F . Create a Validate rule to check the customer age. A Validate rule is suited for checking conditions such as age requirements, ensuring that only eligible individuals can proceed. It checks that the age meets a specified minimum before allowing the process to continue.