Free PEGACPSA23V1 Exam Braindumps
Certified Pega System Architect 23 Questions 65–72 (page: 10)

Updated On: 1-Apr-2026

Apartment tenants submit maintenance requests that specify their name, address, request type, and description of the request. Tenants may submit multiple maintenance requests for different request types. The company wants to identify duplicate maintenance requests from the same address.
Which two configurations, when used together on the Search duplicate cases step, achieve this goal? (Choose Two)

  1. Configure the request type as a weighted condition.
  2. Configure the tenant name as a basic condition.
  3. Configure the apartment address as a basic condition.
  4. Configure the apartment address as a weighted condition.

Answer(s): B,C

Explanation:

In the context of identifying duplicate maintenance requests from the same address in an apartment management application, focusing on key identifiers such as tenant name and apartment address is essential.
B . Configure the tenant name as a basic condition: Including the tenant name as a basic condition in the duplicate search criteria helps to identify requests coming from the same tenant,



As part of the case design, after someone completes a purchase, the application should send a confirmation email. How do you design the case life cycle to send the email?

  1. As part of the stage configuration
  2. As an alternate stage
  3. As part of the case configuration
  4. As a separate process step

Answer(s): D

Explanation:

To ensure that a confirmation email is sent after a purchase is completed within a case, incorporating this functionality directly into the case life cycle is crucial. The most straightforward and effective way to achieve this is by designing it as a distinct step in the process. D . As a separate process step: Adding the action of sending a confirmation email as a separate process step immediately following the completion of a purchase allows for clear, logical sequencing in the case design. This approach ensures that the email is sent as an integral part of the case progression, directly linked to the purchase completion event. Configuring it as part of the stage configuration (A) or as an alternate stage (B) might not provide the direct, immediate linkage to the purchase completion action that is necessary for timely email dispatch. Considering it as part of the general case configuration (C) is too broad and does not specify where in the case life cycle the email should be sent.


Reference:

Pega's case management and process design documentation detail the implementation of automatic actions, such as sending emails, as process steps within a case life cycle, ensuring they are executed at the appropriate points in the case progression.



Based on security factors, which two options are considered strong passwords? (Choose Two)

  1. lLik3Chocolate&sawDustIcecre@m
  2. d8073&gxn*,.ki;vnhdf($h&m
  3. bluedoor
  4. Pe6@5yst3m$

Answer(s): A,B

Explanation:

Strong passwords are crucial for enhancing security. They are typically characterized by a combination of uppercase and lowercase letters, numbers, and special characters, making them difficult to guess or crack.
A . lLik3Chocolate&sawDustIcecre@m: This password incorporates uppercase and lowercase letters, numbers, and special characters, and is sufficiently complex and lengthy, making it a strong password.
B . d8073&gxn,.ki;vnhdf($h&m*: Similarly, this password includes a mix of characters, numbers, and special symbols, contributing to its strength due to its complexity and unpredictability. Option C, "bluedoor", lacks the mix of character types and is relatively simple, making it a weak password. Option D, "Pe6@5yst3m$", though incorporating a mix of character types, is closer to a common pattern related to the word "password", which might not be as strong as options A and B, which are more complex and less predictable.


Reference:

Cybersecurity best practices emphasize the importance of strong passwords that combine various character types and avoid common words or patterns, enhancing account security against unauthorized access or brute-force attacks.



Before development, your team creates a spreadsheet with work items to populate the backlog. All work items that describe business requirements are prioritized as Must have. You also create work items to address:
A future enhancement request to group a set of existing steps into a multistep form A drop-down list that is missing one of the required options -- This work item is in progress because the missing option prevents work from being done
How do you populate the backlog directly from the spreadsheet?

  1. Create bugs
  2. Create feedback
  3. Import stories
  4. Create stories

Answer(s): C

Explanation:

When transitioning from planning to development, populating the backlog with work items that clearly articulate business requirements and enhancement requests is key. User stories are well- suited for capturing these needs in an Agile development environment. C . Create stories: User stories are a fundamental element in Agile methodologies, used to describe features, functionalities, or enhancements from the perspective of the end user. They are concise yet comprehensive, detailing what needs to be done and why. For the scenarios mentioned -- grouping steps into a multistep form as a future enhancement, and addressing a missing option in a dropdown list -- creating user stories allows these requirements to be clearly defined and prioritized in the backlog.
Importing stories (A) might be a method to bulk add pre-defined stories from external sources but does not pertain to the action of creating new stories based on the spreadsheet contents. Creating bugs (B) is more appropriate for issues or errors that need to be fixed, not for new development work or enhancements. Creating feedback (D) could capture suggestions or comments but lacks the structured format of user stories for development purposes.


Reference:

Agile development practices and Pega's Agile Workbench documentation highlight the use of user stories to effectively organize and prioritize development work, ensuring that the team focuses on delivering value according to business needs and user expectations.



Before development, your team creates a spreadsheet with work items to populate the backlog. All work items that describe business requirements are prioritized as Must have. You also create work items to address:
A future enhancement request to group a set of existing steps into a multistep form A drop-down list that is missing one of the required options -- This work item is in progress because the missing option prevents work from being done
How do you populate the backlog directly from the spreadsheet?

  1. Import stories
  2. Create bugs
  3. Create stories
  4. Create feedback

Answer(s): C

Explanation:

When transitioning from planning to development, populating the backlog with work items that clearly articulate business requirements and enhancement requests is key. User stories are well- suited for capturing these needs in an Agile development environment. C . Create stories: User stories are a fundamental element in Agile methodologies, used to describe features, functionalities, or enhancements from the perspective of the end user. They are concise yet comprehensive, detailing what needs to be done and why. For the scenarios mentioned -- grouping steps into a multistep form as a future enhancement, and addressing a missing option in a dropdown list -- creating user stories allows these requirements to be clearly defined and prioritized in the backlog.
Importing stories (A) might be a method to bulk add pre-defined stories from external sources but does not pertain to the action of creating new stories based on the spreadsheet contents. Creating bugs (B) is more appropriate for issues or errors that need to be fixed, not for new development work or enhancements. Creating feedback (D) could capture suggestions or comments but lacks the structured format of user stories for development purposes.


Reference:

Agile development practices and Pega's Agile Workbench documentation highlight the use of user stories to effectively organize and prioritize development work, ensuring that the team focuses on delivering value according to business needs and user expectations.



Choose two scenarios that you configure using procedural processing. (Choose Two)

  1. A prescription order page with a list of available prescriptions sent from the customer's health care provider.
    When the user opts to fill one or more prescriptions, the cost summary updates.
  2. A restaurant reservation page in which the user chooses a reservation and the system returns the number of available tables.
  3. A purchase order request page with a summary of items. The order total price updates after the customer changes a quantity.
  4. A flight booking page where customers can adjust the location and date of the departure and return flights. The ticket prices recalculate after the customer chooses the "recalculate price" option.

Answer(s): C,D

Explanation:

Procedural processing in application development is used for tasks that follow a specific sequence of steps or require updates based on user actions. It is particularly useful for calculations or updates triggered by user interactions.
C . A purchase order request page with a summary of items: This scenario involves procedural processing because the application needs to recalculate the total price whenever the customer changes the quantity of an item. This is a direct, sequential update process



Color options are available to the customer, but the options are available on the screen, and do not appear with the popup.
Which option to configure the color option?

  1. Dropdown
  2. Radio button
  3. Check box
  4. Autocomplete/Textfield

Answer(s): A

Explanation:

In this scenario, the requirement is to present color options to a customer without a popup, directly on the screen. The most suitable UI control for this situation is a dropdown. A dropdown allows users to see all available options upon interaction, occupies minimal screen space when not in use, and effectively groups single-option selections in a compact form. This approach avoids the potential clutter of radio buttons or checkboxes for numerous options and is more user-friendly than an autocomplete/text field for a fixed set of choices like colors.



Consider the following requirement:
The patient must be able to modify physician details at any time without impacting primary case processing.
Which configuration satisfies this requirement?

  1. Add a case-wide optional action to the case life cycle.
  2. Add a primary stage with at least one process to the case life cycle.
  3. Add an alternate stage with at least one process to the case life cycle.
  4. Add an assignment to the case life cycle.

Answer(s): C

Explanation:

The requirement specifies that modifying physician details should be possible at any time without impacting primary case processing. An alternate stage in Pega allows for actions that do not directly interfere with the main process flow of the case life cycle. This configuration enables asynchronous processing of secondary tasks such as updating details that are important but not critical to the main case progression. This approach keeps the primary case stages focused on their core objectives while providing flexibility for side tasks.



Viewing page 10 of 33
Viewing questions 73 - 80 out of 256 questions


Post your Comments and Discuss Pegasystems PEGACPSA23V1 exam prep with other Community members:

AI Tutor AI Tutor 👋 I’m here to help!