Pegasystems PEGACPSA23V1 Online Practice Questions and Exam Preparation

Pegasystems PEGACPSA23V1 Online Questions & Answers

• Question 111:

  What are two attributes of application level security? (Choose two.)

  A. Create password and authentication policies.
  B. Identify authorized users who need access to the application.
  C. Set up security roles for personas in each case type.
  D. Prevent users from viewing features that they should not access.
  A. Create password and authentication policies.
  D. Prevent users from viewing features that they should not access.

  ---

  Explanation/Reference:

  Attributes of application level security typically involve measures that protect the application's data and features according to defined security policies:

  A . Create password and authentication policies. Application security includes establishing robust password policies and authentication mechanisms to ensure that only authorized users gain access to the application. D . Prevent users from

  viewing features that they should not access. Application level security also involves configuring permissions and access control to ensure that users can only interact with features and data they are authorized to use, thereby protecting

  sensitive information and maintaining the integrity of the application.

  maintaining the integrity of the application.

• Question 112:

  A requirement states: Loan applicants must enter their annual salary. If the salary is above the qualifying threshold, the application is automatically approved. If the salary is below the threshold, the applicant must identify a cosigner. Select the two configuration options that follow best practices to meet the requirement. (Choose Two)

  A. Design a user view with an annual salary field and a data relationship for cosigner information. Use a visibility condition to display the cosigner information when the salary is below 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.
  C. Design a user view with an annual salary field. Create an optional action to collect information about the cosigner and assign the action to the appropriate stage.
  D. Create an assignment step for a loan officer to review the applicant's annual salary and determine if a cosigner is necessary.
  A. Design a user view with an annual salary field and a data relationship for cosigner information. Use a visibility condition to display the cosigner information when the salary is below 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.

  ---

  Explanation/Reference:

  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. Pega's best practices for application development emphasize the importance of designing user interfaces and workflows that efficiently manage data collection and conditional processing, aligning with requirements for dynamic and responsive application behavior.

• Question 113:

  While testing a business process to approve an expense report, you receive an error. Which tool allows you to review the rule execution to determine the source of the error?

  A. The Tracer
  B. The Clipboard tool
  C. The Application Profiler
  D. The Dependency Analyzer
  A. The Tracer

  ---

  Explanation/Reference:

  When encountering errors during business process testing and needing to diagnose rule execution issues:

  A . The Tracer. This tool is essential for debugging and testing in Pega, as it allows developers to step through the execution of rules to identify and resolve errors, offering a real-time trace of rule processing, which helps pinpoint the source of errors in process execution.

• Question 114:

  DRAG DROP

  Drag the term that is used in App Studio from the left to the rule that you use in Dev Studio on the right.

  Select and Place:

  

  

  ---

  Explanation/Reference:

  Field: In the context of Pega's App Studio, a field represents an individual data element that can be placed on a user interface. In Dev Studio, the corresponding rule type for a field is a Property rule, which defines the characteristics and behavior of a single piece of data that can be used in various parts of the application, such as forms, data objects, or calculations.

  Goal and deadline: This term in App Studio refers to the objectives and time frames associated with a task or a case. The counterpart in Dev Studio is a Service-level agreement (SLA) rule. An SLA rule in Pega defines the time goals for the assignment, stages, and processes in a case, including the deadlines and what actions should be taken if those are not met.

  User: In App Studio, the term user typically refers to the human end-user interacting with the application, often associated with a specific role or set of permissions. In Dev Studio, a Operator rule is used to define the characteristics of a user, including their credentials, roles, skills, preferences, and the access group(s) they belong to.

  Persona: A persona in App Studio is a semi-fictional character created to represent different user types that might use a service, product, site, or brand in a similar way. When translating this to Dev Studio, it aligns with an Access group rule.

  An access group in Pega is a rule that defines a set of application roles, permissions, and other settings that correspond to the needs and permissions of a particular type of user or persona.

  Pega Academy and official documentation provide information on how these terms in App Studio relate to rules in Dev Studio.

  Knowledge articles and developer help resources within the Pega platform can give further explanations on how to use these rules within the context of building applications.

• Question 115:

  Users must provide values to certain fields before submitting a job application form. Which configuration adds asterisks to indicate the mandatory fields on the form?

  A. Use an Edit Validate rule to verify if each of the mandatory properties has a value.
  B. Configure the mandatory fields as Always Required on the form at runtime.
  C. Use a Validate rule to verify the mandatory fields have a value.
  D. Configure a Disable when condition on the mandatory fields at runtime.
  B. Configure the mandatory fields as Always Required on the form at runtime.

  ---

  Explanation/Reference:

  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.

• Question 116:

  Which scenario requires you to make updates in Dev Studio?

  A. A task is reassigned when it reaches a service-level agreement goal.
  B. An email correspondence is added to the case type.
  C. A customer representative can approve or reject a claim.
  D. A new confirmation view displays a read-only text property
  D. A new confirmation view displays a read-only text property

  ---

  Explanation/Reference:

  Certain updates require the capabilities of Dev Studio because of their complexity and the need for custom configuration:

  D . A new confirmation view displays a read-only text property. Creating and configuring new UI components, particularly those that involve specific behavior such as displaying read-only properties, typically necessitates using Dev Studio. This environment provides the necessary tools and features to design and implement detailed user interface requirements.

• Question 117:

  Which device characteristics should be considered when designing a mobile app?

  A. Customize controls for each responsive breakpoint.
  B. Test applications in the mobile preview.
  C. Design for finger taps.
  D. Use fixed positioning.
  B. Test applications in the mobile preview.
  C. Design for finger taps.

  ---

  Explanation/Reference:

  When designing a mobile app, it's important to consider how users interact with the device and how the app will be presented across different devices:

  B . Test applications in the mobile preview. Using the mobile preview feature allows designers to test how the application will look and operate on mobile devices, ensuring usability and optimal user experience. C . Design for finger taps. Mobile interfaces should be designed for touch interaction, with controls that are sized and spaced to accommodate finger taps, which is the primary mode of interaction on mobile devices.

• Question 118:

  Sales managers must be able to approve sales quote proposals by email and from a mobile device. How do you implement this requirement?

  A. Add an Approve/Reject step and enable email and mobile approval.
  B. Add an Approve/Reject step and a Send Email step.
  C. Add an Approve/Reject step with mobile approval enabled and a Send Email step.
  D. Add an Approve/Reject step and enable email notifications on the case type.
  A. Add an Approve/Reject step and enable email and mobile approval.

  ---

  Explanation/Reference:

  To fulfill the requirement that sales managers must approve sales quote proposals both via email and on a mobile device, the best approach is to add an "Approve/Reject" step in the workflow and enable capabilities for both email and mobile approval. This configuration allows sales managers to respond to approval requests directly from their email or through a mobile app, ensuring that the approval process is flexible and accessible across platforms, thus improving the workflow's efficiency and responsiveness.

• Question 119:

  Which option follows best practices for naming a ruleset in Pega Platform?

  A. Pega-prod:01-04-01
  B. Grand-Corporation-Human-Resources-Department:01-01-03
  C. Credit Check:03-01-02
  D. Expense:01-02-05
  D. Expense:01-02-05

  ---

  Explanation/Reference:

  RuleSet names may be up to 64 characters long, but normally are less than twenty characters long. See System limits and maximums

• Question 120:

  Which requirement is best implemented by using a Wait step in a case?

  A. You must pause a case until a user uploads a signed document.
  B. You cannot proceed in an expense report until a manager approves the request.
  C. You cannot complete a purchase case on a website unless you complete a new account subcase.
  D. You need to send an email after a user completes a form.
  A. You must pause a case until a user uploads a signed document.

  ---

  Explanation/Reference:

  Using a Wait step in Pega is best suited for scenarios where a case must be paused until a specific condition is met:

  A . You must pause a case until a user uploads a signed document. The Wait step is ideal for this requirement as it allows the case processing to be paused until the specified document is uploaded by the user, ensuring that the case does not proceed without the necessary documentation being properly submitted.