PEGACPSA23V1 Exam Dumps - Certified Pega System Architect 23

To create a view with editable fields in an application built on the Constellation architecture:

B. In a step of the case life cycle, configure a view. Configuring a view directly within a case step allows the inclusion of fields that can be edited as part of that step in the case processing.

D. On the UX tab of a data object, create a Form view. The UX tab in a data object allows you to define how the data is displayed and interacted with, including creating forms with fields that users can edit.

For routing customer warranty service requests, particularly when different routing rules apply based on product status:

D. Route the assignment to the vice president of service when the request is for the beta release. Otherwise, route the assignment to the warranty resolution group. This routing strategy is efficient for handling cases where special attention is required by higher management (e.g., the vice president of service) for beta and release products, ensuring that such cases are escalated appropriately while other standard warranty requests continue to be processed by the usual resolution group. This setup optimizes the handling process by directing cases based on their specificity and importance.

To configure a service-level agreement (SLA) with a passed deadline interval that repeats:

D. Dev Studio. Dev Studio provides advanced configuration options, including the ability to set up complex SLAs. This environment allows you to define detailed parameters for SLAs, such as a passed deadline interval and the repetition of those intervals.

For an online shopping application, ensuring accurate item pricing and total cost calculations in the shopping cart is crucial for functionality and user trust. Unit testing focused on verifying these aspects is essential during development.

• A. Verify the data page has the correct item prices: This test ensures that the prices pulled from the external inventory management system into the application via the data page are accurate. Correct item pricing is foundational to calculating the total cost for items in the shopping cart.
• D. Verify the order total cost property is accurately calculated: This test checks whether the application correctly calculates the total cost of all items in the shopping cart, considering both the individual item prices and their quantities. Accurate total cost calculation is crucial for the final order summary and checkout process.

Verifying the data transform copies the correct value (B) is important for data integrity but is a more granular detail compared to the overarching need to ensure accurate pricing and total calculations. Verifying the price fields are displayed in the correct format (C) is also significant but focuses more on UI presentation than on the underlying functional correctness of pricing and total cost calculations.

To configure an application that allows users to download a mobile app by selecting a platform and then directing them to the appropriate app store:

A. Add a button for each platform and configure an action set for each button. In each action set, specify a click event and add an action that opens the vendor's URL in a window. This method allows distinct actions to be set for each platform button, providing direct and relevant responses to the user's choice. Each button’s action set specifically targets the corresponding platform's store URL, ensuring users are directed correctly based on their selection.

For the requirement that the tax identification number must contain 10 digits, configuring the field to enforce this specific format is crucial.

• B. Use an edit validate rule: This rule type is designed to enforce specific patterns or formats in data input. By configuring an edit validate rule for the tax identification number field, the system can ensure that only values matching the 10-digit pattern are accepted, directly meeting the requirement.

Setting the minimum and maximum values in a text field (A) might control the length of input but does not enforce numeric or pattern-specific constraints. Using a decimal property type (C) ensures numeric input but does not restrict the field to exactly 10 digits or to being treated as a non-numeric pattern. Configuring a validate rule (D) could enforce certain conditions but is generally broader and less specific than an edit validate rule for pattern enforcement.

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.

For a list report that includes columns for purchase requests and regional cost centers, and with a requirement to show the total number of purchase requests for each regional cost center, the correct approach is to summarize the relevant data in a way that aligns with the manager's needs.

• C. Summarize the purchase requests column by count: This configuration aggregates the purchase requests data, providing a count of purchase requests per cost center. It effectively meets the manager's requirement by offering a clear and concise summary of the total number of purchase requests for each regional cost center, facilitating easy analysis and decision-making.

Using the purchase requests column to group the cost centers (A) might organize the data differently than required, focusing on purchase requests rather than summarizing them by count for each cost center. Filtering the results to include only cost center and purchase requests (B) simplifies the report but does not aggregate the data as

For selecting one severity option from a predefined set, radio buttons are the best choice. This control allows users to see all available options and select exactly one, ensuring clear and error-free selection. Unlike checkboxes, which are suitable for selecting multiple options, radio buttons inherently prevent multiple selections, which is ideal for severity levels where only one should be applicable at any given time.

DevOps practices in Pega are designed to improve deployment efficiency and software quality:

B. Acceptance criteria helps to focus customer-centric deployment. Establishing clear acceptance criteria is a cornerstone of DevOps, ensuring that the deployments meet the specific needs and expectations of the customer.

C. Pega can integrate third-party DevOps tools to promote flexibility. Integration with various third-party DevOps tools allows for a more versatile and adaptable development environment, catering to diverse operational needs.

E. Tests are run before publishing changes to ensure compatibility. Running tests before deploying changes is fundamental in DevOps to maintain stability and compatibility within the application environment.

The minimum components of a UI action set in Pega systems are:

B. One action and one event. An action set in Pega requires at least one action (e.g., Set Value, Refresh Section) that defines what happens, and one event (e.g., Click, Change) that triggers the action. This combination is the fundamental requirement to create interactive elements within Pega's UI, allowing developers to define how the application responds to user inputs.

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.

Configuring correspondence in Pega is required when automated communication with parties involved in a case is needed:

A. Fax a new insurance claim to the auto repair shop. This requirement necessitates the configuration of correspondence to automatically handle the sending of insurance claim details via fax, streamlining communication and ensuring timely sharing of necessary documents.

B. Text the customer with status changes in an insurance claim. Sending automated texts to customers about status updates in their insurance claim process is another example where correspondence configuration is essential, enhancing customer service through timely updates.

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.

To design a report definition that sorts cases so that the case with the most recent create date appears at the top of the list and descends in order, the sorting of the Create Date column must be configured appropriately.

• C. Select Highest to Lowest sort type for Create Date: This sorting option ensures that the report organizes the cases starting with the most recent (highest) create date first, descending to the earliest (lowest) create date. This configuration aligns directly with the manager's requirement to have the most recently created cases at the top of the report, facilitating quick access to the latest cases.

Selecting Lowest to Highest sort type for Create Date (A) would result in the opposite of the requested order, placing the oldest cases at the top. Adding a filter condition where Create Date is greater than the current date (B) wouldn't be practical, as create dates cannot be in the future. Making the Create Date the first column in the report (D) might aid in readability but on its own does not ensure the correct sorting order.

The appropriate scope for a data page that lists products purchased by a customer viewed in an online portal is "Requestor". This scope ensures that the data page is unique to each user session and is accessible across multiple requests within that session. The "Requestor" scope is suitable because it persists for the duration of the user's interaction with the application, across multiple threads or cases, making it ideal for situations where a user might be working on multiple support requests during a single login session.

Branched rulesets are particularly useful in scenarios where parallel development efforts are ongoing, such as when one team is working on a patch (minor updates or fixes) while another team is developing a major version of the application. This configuration allows both teams to work independently on different versions of the application without interfering with each other's changes, thus maintaining the integrity and continuity of the application development lifecycle.

In the context of configuring dynamic layouts in Pega, the options that are typically configurable include:

B. Label Positioning. This option allows the developer to define where the labels of fields will appear relative to the fields themselves (e.g., left, right, top) within the layout, aiding in creating a user-friendly and accessible form structure.

C. Number of columns in each row. This setting controls how many columns can be included in each row of the layout, which is crucial for structuring complex forms and ensuring that they are presented in an organized and visually coherent manner.

To create a custom status named Open-Review in Pega, applicable to assignments in a specific application:

C. Create a field value record named Open-Review for .pyStatusWork with the Apply To class set to the class group. This solution involves creating a field value for the custom status within the context of the specific application's class group. This approach ensures that the custom status is recognized and used correctly within the application, maintaining consistency and clarity in status handling across the application.

In the context of service levels in Pega, the "passed deadline" interval starts immediately after the "end of the goal interval". This setup helps in distinguishing between the targeted resolution time (goal) and the ultimate deadline by which the task must be completed, allowing for escalated actions or notifications to be triggered if the deadline is approached or passed, ensuring timely completion of assignments.

In a hiring application that includes tasks performed by different teams—HR creating and sending the offer letter, IT assigning the workstation, and Facilities assigning the work desk—the personas to be created correspond to each team handling specific responsibilities. Each persona represents a user or team involved in the process with distinct roles and access requirements. Therefore, the personas for HR, IT, and Facilities should be created to accurately reflect the workflow and ensure that system permissions and interfaces are appropriately configured for each group's tasks.

To adapt the display of property photos to different screen sizes within an apartment hunting application, the best approach is:

A. Use a dynamic layout with a responsive breakpoint at 800 pixels to change from inline-grid triple to inline-grid double format. This option uses responsive design principles to adjust the number of columns based on screen size. When the screen width is below 800 pixels, the layout automatically changes from three columns (triple) to two columns (double), ensuring optimal display on smaller devices.

To ensure that valid data is used in a case:

A. The data fits the business logic. Valid data must align with the business rules and logic of the application, ensuring that the data used in case processing is appropriate for the business context.

C. The data is the correct field type. Having data that is of the correct field type is fundamental to ensuring that the application processes and stores information accurately. This includes ensuring that dates, numbers, text, and other data types are used in their respective fields appropriately.

To manage the progression of a Visa application case type, contingent upon the resolution of an Interview child case:

B. Following the Create Case step, add a Wait step that pauses the parent case until the Interview reaches the Resolved status. This approach is ideal for ensuring that the main Visa case does not proceed until the Interview child case is fully resolved, aligning the case progression with the actual completion of necessary procedural steps, thus maintaining process integrity and dependency.

When configuring mobile app channels for ABC BankCorp's Transaction Dispute application to accommodate GloboBank and LocalBank, certain requirements directly influence the need for separate channels due to differing functionalities or branding.

• B. Customers can create only dispute cases, while CSRs can also create fraud report cases: This requirement indicates a functional difference between the apps intended for customers and CSRs. The ability of CSRs to handle additional case types (fraud report cases) necessitates a tailored app configuration to support these distinct functionalities, likely leading to the need for separate app channels for customers and CSRs.
• C. Mobile app color palette is customized for each subsidiary: The requirement for subsidiary-specific branding, including color palettes, directly impacts the app's UI design. To maintain distinct brand identities for GloboBank and LocalBank within the app, separate mobile app channels would be required to accommodate the different branding elements for each subsidiary.

Supporting both phones and tablets (A) and customizing currency units and date/time format according to the user's locale (D) are requirements that can typically be met within a single mobile app channel through responsive design and localization features, and thus do not inherently require multiple app channels.

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.

Grouping a set of existing actions into a multistep form as per a stakeholder's request involves adding new functionality or modifying the existing functionality of an application. This type of change request is best captured as a User Story in Agile Workbench.

• D. User Story: User stories are a way to document specific requirements or changes in an agile development environment. They focus on the value or outcome of the change from the perspective of the end-user or stakeholder. In this case, creating a user story allows for the clear articulation of the stakeholder's preference for a multistep form, including the rationale and the expected benefit, facilitating prioritization and implementation during the development cycle.

Bugs (A) are used to report issues or errors in the existing application functionalities. Feedback (B) can capture general comments or suggestions but lacks the structured approach of a user story for implementing new features or changes. Status (C) is not a work item but an attribute used to track the progress of items like bugs, feedback, or user stories.

Given the updated business requirement allowing the parent Accident Claim case to continue independently of the status of the child cases:

D. Configure the step so that users can continue with the parent case process regardless of child case status. The Wait step previously used to pause the parent case should be removed or configured to not halt the parent case processing, thereby permitting the parent case to proceed without dependency on the child cases' progress or resolution. This change reflects the new requirement for the parent case to operate independently from the Vehicle Damage (VD-001) and Body Injury (BI-001) child cases.

To fulfill the requirement that all managers must be able to view the Employee vacation requests report in their Manager portal dashboards, the report must be made readily accessible in a manner that integrates seamlessly with the existing portal structure.

• D. Add the report to a public category, and then add the out-of-the-box Reports landing page to the portal: This approach ensures broad accessibility by placing the report within a public category, making it available to all managers. Integrating the Reports landing page into the portal provides a centralized location for managers to access this and potentially other relevant reports directly from their dashboard, enhancing the usability and efficiency of the portal.

Creating a new landing page (A) specifically for the new report may not be necessary if the existing Reports landing page structure can accommodate the report, and it may introduce unnecessary complexity. Adding a report widget and publishing it to the default (B) or without specifying the target audience (C) might not ensure the report's visibility to all managers as required.

Routing tasks to specific groups within an organization is a common requirement in case management systems. For the scenario involving voice over requests with distinct tasks for editors and actors, creating separate work queues for each group is the most straightforward and effective approach.

• A. Create two new work queues, one for editors and one for actors: This option allows for the segregation of tasks based

Similar to the previous validation question, using a single Validate rule that encompasses both conditions—minimum monthly income of GBP 2000 and a maximum credit card debt of GBP 20000—is the most straightforward and efficient approach. This ensures that all financial criteria are assessed together, maintaining consistency and simplicity in the validation process, and preventing the application from moving forward if either financial criterion is not met.

The step name "Investigate Claim" most accurately describes the activity where the customer service agent reviews the details of a fraud complaint. This naming is clear and action-oriented, specifying what the agent is doing (investigating) and the subject of the investigation (the claim). It is preferred over options like "Claim Investigation" or "Investigate Fraud" because it follows the verb-noun format that is recommended for naming steps in Pega, where the verb denotes the action and the noun denotes the object of the action.

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.

When configuring a data page that needs to retrieve details of a single record, the appropriate source to use is:

D. Lookup. Lookup is specifically used in Pega to retrieve a single record based on a key or a set of keys from a data type. This makes it suitable for data pages that are intended to provide detailed information about a particular entity, ensuring efficient and accurate data retrieval based on specific criteria.

Insights in Pega are designed to help users analyze and visualize data:

A. You can search for and select the fields that you want to include in an insight. This feature allows users to customize insights by choosing which data fields to analyze, enabling focused and relevant analyses.

B. You can transform data queries into shareable visualizations. Insights provide the capability to turn complex data queries into visual representations, such as charts or graphs, which can be easily understood and shared, enhancing the decision-making process.

To minimize clutter on an order form where customers select one option out of four, using UI controls that efficiently manage screen real estate while ensuring user-friendliness is crucial.

• A. Dropdown: A dropdown menu consolidates the four options into a single interactive element. When not in use, it takes up minimal space on the form, contributing to a cleaner, less cluttered appearance. It expands when interacted with, allowing the user to make a selection from the list.
• C. Radio buttons: Radio buttons allow all options to be visible at once, ensuring immediate visibility of choices without additional interaction. Because selecting one option automatically deselects any other, radio buttons are ideal for single-choice scenarios. They can be designed to be compact, minimizing their impact on the form’s layout.

Checkboxes (B) are typically used for selections where multiple options can be chosen simultaneously, which does not align with the requirement for a single selection. Autocomplete (D) is useful for forms with a large number of options or for facilitating quick selection from a list through typing, which might not be necessary or as efficient for a small, fixed set of four options.

To improve the performance of a report listing customer order cases where the Order Total value is a critical criterion:

A. Order Total. Optimizing the Order Total property allows for faster sorting and filtering operations specifically on this field, which is crucial for performance, especially when dealing with large datasets where queries are based on financial thresholds.

Calculated fields in Pega are used to compute values based on other data elements within the application, suitable for:

A. A sales representative wants to quote the cost of an insurance policy based on selected coverage options. Calculated fields can dynamically compute the total cost of an insurance policy as different coverage options are selected, providing real-time pricing information.

C. A project manager wants to estimate the cost of painting a banquet hall based on labor and materials required. Similarly, calculated fields can be used to aggregate costs of materials and labor to provide an overall estimate for a project, facilitating budget management.

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.

For a purchase request case type where requests should automatically go to a manager of an employee, the most straightforward configuration is to design a step within the case lifecycle that specifically routes the case to the manager. This routing logic ensures that once an employee submits a purchase request, it is automatically forwarded to their manager for approval, streamlining the workflow and enforcing organizational approval hierarchies.

To construct a decision table for recommending a moving vehicle based on the number of bedrooms in the customer's current living space and whether heavy furniture is being moved, the decision table needs to account for these input parameters and provide a corresponding recommendation.

• A. Create a column for the recommended moving vehicle: This column will hold the output of the decision table, which is the type of moving vehicle recommended based on the input criteria. This setup allows for a clear and direct presentation of the recommendation to the customer.
• D. Create two columns, one for the number of bedrooms and one for whether the customer is moving heavy furniture: These columns will serve as the input conditions for the decision table. By evaluating the values in these columns, the decision table can determine the appropriate moving vehicle recommendation for each unique set of circumstances.

Creating rows for the recommended moving vehicle (B) would not follow the conventional structure of a decision table, where rows typically represent different rule conditions or scenarios rather than outcomes. Creating two rows, one for each input condition (C), misunderstands the structure of decision tables, where conditions are represented as columns and individual scenarios or rule conditions are represented as rows.

Configuration options for a mobile app channel in Pega focus on enhancing user experience and security specific to mobile environments:

A. Define security behavior for a mobile app such as biometric identifiers. This option allows for the integration of advanced security features, like biometric authentication, enhancing user security and data protection in mobile applications.

C. Define the UI behavior for each view in a case type when the case is displayed on a mobile device. Customizing how user interfaces behave on different mobile devices ensures that the app is responsive and provides an optimal user experience, adapting dynamically to various screen sizes and orientations.

The Localization Wizard in Pega is designed to facilitate the localization of various rule types that involve user-facing text:

B. Paragraph. Paragraph rules, which contain blocks of text used in user interfaces, are often localized to cater to different languages, making them accessible and understandable to users in various regions.

C. Correspondence Fragment. Correspondence fragments are parts of larger correspondence templates and typically contain text that needs to be presented in the user's language, making them crucial candidates for localization using the wizard.

To ensure that a list of hotels refreshes dynamically based on changes to check-in or check-out dates in a hotel reservation application, configuring action sets on these date fields is the correct approach. Action sets can be set to trigger a specific response, such as refreshing a section of the form, whenever the date fields are modified by the user. This setup maintains accurate and up-to-date availability data for the user, enhancing the application's responsiveness and user experience.

To effectively test a new process for a case type and verify that the UI elements collect the expected results, utilizing scenario testing in Pega is highly recommended. This approach allows for recording a set of interactions and saving the test result, which is crucial for verifying process functionality.

• B. Create a scenario test for the case type: Scenario testing in Pega allows for the simulation of an end-to-end process, including interactions with UI elements. This tool enables the creation and execution of tests that mimic real-world user actions, ensuring that the entire process functions as intended. By creating a scenario test, you can capture and automate the testing of specific pathways through a case type, making it an essential tool for validation.
• C. Add explicit assertions on the UI elements: Assertions are conditions that you expect to be true at a certain point in your test. By adding explicit assertions to the UI elements during scenario testing, you can specify the expected outcomes or states of those elements. This ensures that not only does the process flow correctly, but the UI elements also behave and capture data as intended. Assertions provide a powerful way to validate the functionality and user interface of your application precisely.

Together, these configurations enable a robust testing framework that can simulate user interactions, verify UI behaviors, and ensure the overall functionality of the process and its fields.

To ensure the validation that the 'Date account opened' is indeed in the past for a loan application:

B. Use a validate rule to verify the Date account opened is in the past. Validate rules in Pega are used to enforce data integrity and accuracy, making them suitable for verifying that a date entered is before the current date. This method ensures that data meets the business requirement directly and effectively.

In Pega applications, work parties represent entities associated with a case. When configuring status updates for patients who are not users of the application, it is essential to use a class that accurately represents external individuals.

• A. Data-Party-Person: This class is designed to represent individual people as parties in a case. Using this class to create a work party for a patient allows the application to store relevant personal information and contact details necessary for sending status updates about medical test processing. Since patients are the recipients of the information and not operators or organizational entities within the system, this class is the most appropriate choice.

The other options, such as Data-Party-Operator (used for application users), Data-Party-Org (used for organizations), and Data-Party-Com (used for commercial entities), do not fit the context of individual patients receiving updates.

The Estimator tool in Pega is used for planning and sizing development efforts, particularly for Minimum Lovable Products (MLP):

B. MLP sizing leads to precision in the sprint cycle and resource planning. Accurate MLP sizing helps in detailed planning of sprint cycles and resource allocation, ensuring that development efforts are aligned with project goals and timelines.

D. Initial estimations are high-level and can be refined during sizing. Early estimations in the project are often broad and generalized but become more refined and accurate as the project sizing process progresses, allowing for better project planning and management.

The scenario describes a series of actions related to managing a job application process. Proper naming of steps in a business process is crucial for clarity and effective communication. The step "Schedule Interview" directly reflects the action of setting up the date and location for the interview, while "Notify Candidate" describes the action of sending an email confirmation to the candidate. These names are clear, action-oriented, and specific to the tasks being performed, aligning with best practices in business process modeling.

To write a single page of data to a single database row in the configured system of record:

D. Database save. A database save operation is used to persist data from a Pega data page into a database. It matches the structure of the data page to the corresponding database table structure and writes the data to a new row, fulfilling the requirement to synchronize a page of data to the database.

For automating the advancement of university admission application cases based on standardized test scores, the correct configurations would be:

A. Configure a process with a decision shape that continues if the TestThreshold configuration setting is less than the applicant’s test score. This configuration directly supports the requirement by placing a decision shape in the process that compares the applicant's test score against a pre-configured threshold. If the score exceeds the threshold, the case advances, automating the workflow based on performance.

D. Configure a TestThreshold Configuration setting with the national average for the test score threshold. This option involves setting a dynamic threshold that adjusts based on the national average each year. It ensures that the decision shape in Option A has a relevant and up-to-date threshold to compare against.

Options B and C are incorrect because B involves calculating the average rather than setting a threshold, and C incorrectly states the comparison logic.

The combination of configuring the case type to create temporary cases and adding a Persist case step to the case life cycle is appropriate for this scenario. Temporary cases allow users to enter and process data without immediately committing it to the database, ideal for initial checks like membership status. If the user decides to make changes (hence modifying the membership), the Persist case step can be used to save these changes and assign a case ID, thus converting the temporary case into a permanent record in the system.

For the requirement where an auditor needs to receive an email notification if the refund is greater than twice the price of the item, it's important to select a participant role that accurately reflects the auditor's involvement in the case.

• B. Interested individual: This role is designed to represent parties who need to be informed about certain events or milestones within a case but are not directly responsible for actioning the case. In this scenario, the auditor's role is to be notified under specific conditions for oversight purposes, making "Interested individual" the appropriate choice. This setup allows the application to send targeted notifications to the auditor without assigning them case responsibilities that are not part of their role.

The other options, such as Customer (Option A), Owner (Option C), and Work queue (Option D), do not accurately represent the auditor's role in relation to the specific notification requirement.

For a job application case type requiring both a physical assessment and a criminal background check, where the sequence of these checks can vary:

B. Create a process for the physical assessment that is parallel to the background check process. Configuring these processes to run in parallel allows both assessments to occur independently and in any order, as required by the case. This setup effectively manages variability in process sequencing without imposing a fixed order, thereby accommodating the specified flexibility in the application process.

Understanding data objects in Pega helps clarify their roles and functions within the platform:

A. Data objects can reuse assets from an existing data object through inheritance. Inheritance allows data objects to extend the properties and behaviors of existing data objects, promoting reusability and consistency across the application.

C. A data object created in App Studio creates a data type in Dev Studio. This statement is true as creating a data object in App Studio automatically sets up a corresponding data type in Dev Studio, ensuring that the data structure is available across both development environments for further customization and integration.

For time-off requests requiring multiple levels of approval based on the duration of the request, combining a cascading approval process with an authority matrix and custom approvals configured in the reporting structure is effective. The authority matrix can define different approval rules based on the length of the time-off requested, while custom approvals allow for the inclusion of additional approvers, such as HR, when the request exceeds a specific threshold (e.g., three weeks). This ensures that all necessary approvals are obtained in a structured and hierarchical manner.

To ensure that hospital staff can efficiently provide patients with a summary of their visit, the system needs to generate a document (PDF) and then email it. Configuring a "Create PDF" automation that references the detailed Patient visit summary view allows for the automatic generation of a comprehensive document containing all relevant visit details. Following this, adding a "Send Email" step with the capability to include attachments enables the system to attach the newly created PDF to the email sent to the patient. This combination ensures a streamlined process for distributing important healthcare information securely and efficiently.

In scenarios where a dropdown list needs to dynamically reflect data that could change over time, such as a list of laptop models maintained in an external system, using a data page is the best approach. Data pages in Pega are designed to retrieve and cache data from various sources, including external systems. They are ideal for scenarios where data needs to be up-to-date and reflected in UI elements like dropdown lists. Data pages can be configured to refresh as needed, ensuring that the dropdown always displays the current set of available models.

To configure the requirement that allows a customer to update their address at any point during case processing, including submission, verification, and approval of the new address, an approach that provides flexibility and accessibility throughout the case lifecycle is needed.

• A. Add a case-wide optional action to the workflow for the address submission: This configuration enables the address update functionality to be accessible at any stage of the case processing. A case-wide optional action ensures that the customer can initiate the address change process whenever necessary, without being constrained by the current stage or step in the case. This approach aligns with the requirement

To test the decision-based flow in a case type when the user interface for entering standardized test scores is not yet configured:

D. Use the Clipboard tool to set a value for the standardized test score field. The Clipboard tool allows you to manually manipulate the values of properties directly within the case context, facilitating the testing of process flows based on decision points without needing a fully configured UI.

To ensure that a survey email sent to a customer includes the case ID for the survey, incorporating dynamic content into the email is necessary. The most direct and efficient way to achieve this is by utilizing Pega's built-in functionality for email composition.

• D. Use the Insert Property feature of a Send Email step: This approach allows for the dynamic insertion of the case ID directly into the email content at the time of composing the email. The Insert Property feature is designed to reference and pull in property values (such as the case ID) from the case context, ensuring that the email content is accurately personalized for each recipient. This method ensures that the email template remains flexible and reusable, while still providing specific information like the case ID.

Creating a required field for the case ID (A) unnecessarily complicates the process for users. Calling a data transform (B) can copy data between pages within the application but does not directly address the insertion of case ID into an email. Creating a process using the Send Email step (C) provides a mechanism for sending emails but, without utilizing the Insert Property feature, does not automatically include the case ID in the email content.

The Estimator tool is primarily used for project management and planning in Pega, particularly for determining the scope and scale of development efforts:

D. A stakeholder needs to know how much time and effort is needed to build MLP2. This use case describes the fundamental function of the Estimator tool, which is to provide stakeholders with detailed estimates of time, effort, and resources required to build a specified part of an application, such as MLP2.

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.

To set a fixed yearly fee of USD 75 in a Credit Card Payment case type, the most straightforward and appropriate method is to use a data initialization configuration where the Yearly fee field is set to 75. This approach involves configuring the data model or the default value setting within the case type or relevant data transform to initialize the Yearly fee field at case creation. This ensures that the field is consistently set to the correct amount across all cases without requiring calculations or validations that are meant for data integrity or conditional logic.

In Pega, calculating values such as total working hours, sick hours, and vacation hours often involves using data transforms to manipulate and set property values based on logic defined within the application. A "Calculate field" in a data transform would allow for the dynamic calculation of these values based on inputs such as logged time entries, absence records, and other relevant data inputs. This method is efficient for real-time computation and updates of calculated fields within a table or data page.

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.

Creating a scenario test for the Onboarding case type is the most effective way to test the process and verify that UI elements collect the expected results. Scenario testing allows you to simulate real-world user interactions within the HR application, ensuring that the process flows correctly and that all UI components function as intended. This type of test covers a broader range of application functionalities compared to unit tests, which are more granular, and it is more comprehensive than adding assertions or validations to individual UI elements.QUESTION NO: 100

In a banking application, which two options must be used together to present users with a set of balance transfer options only if they select to transfer a balance to their credit card? (Choose two)

A. Add an action set on the layout containing the balance transfer offers to trigger a refresh

B. Add a visible when condition on the check box for the balance transfer election

C. Add an action set on the check box for the balance transfer election to trigger a refresh

D. Add a visible when condition on the layout containing the balance transfer offers

Answer: C, D

In a banking application, to dynamically present balance transfer options based on user selection, combining an action set on the checkbox (that triggers a UI refresh when the box is checked) with a visible when condition on the layout containing the balance transfer offers is necessary. This ensures that the layout becomes visible only if the checkbox is selected. The action set triggers the UI to re-evaluate conditions when the checkbox is toggled, and the visible when condition ensures the offers are displayed only under the correct circumstances, creating a seamless user experience.

Routing an assignment to a work queue is the appropriate method to allow any available member of a department to perform the task. Work queues are designed to hold assignments that can be picked up by any qualified user who has access to that queue. This differs from a work list, which is typically specific to an individual user. Routing to a work queue ensures efficient task allocation and flexibility in task management within a team or department.

For a purchase request list report that includes columns for case ID and regional cost center, and with a requirement to show the total of purchase requests for each regional cost center, summarizing data correctly is essential.

• B. Summarize the case ID column by count: This configuration tallies the number of purchase requests (case IDs) for each regional cost center, effectively meeting the manager's requirement. By summarizing the case ID column by count, the report will display the total number of

The purpose of the Test Coverage tool in Pega is:

A. To determine how many rules are covered and not covered by Pega Platform tests. This tool helps in assessing the extent of rule coverage by automated tests, identifying areas where test coverage is lacking, which is crucial for maintaining high-quality application development and ensuring robustness.

Conditional processing within a case type in Pega is used to determine the flow of cases based on specific criteria:

A. A scholarship eligibility application requires students to enter standardized test scores, Students with qualifying test scores can schedule an interview. Students without qualifying test scores receive a rejection email. This scenario clearly requires conditional processing to route students based on their test scores, either towards scheduling an interview or receiving a rejection.

D. A shopping application requires a guest to fill out payment information. A user who enters a membership number skips the payment information step. This use case also demonstrates the need for conditional processing, where the presence of a membership number changes the steps a user must complete.

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.