Free Pegasystems PEGACPSA23V1 Practice Exam with Questions & Answers | Set: 7

Service Level Agreements (SLAs) with specific configurations like passed deadlines are typically set up in a more technical environment within Pega:

C. Dev Studio. Dev Studio provides advanced configuration capabilities needed for setting up complex SLAs, including those involving deadlines. It offers the tools required to define and manage the intricate aspects of SLAs that impact the processing timelines of cases.

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.

To achieve reuse and consistency between the Payment view and the Order Summary view in an application that sells office supplies, converting the layout that groups the order items into a reusable section is an effective solution. This reusable section can then be embedded in both the Payment and Order Summary views. This approach ensures that any updates to the order items are automatically reflected in both views, maintaining a single source of truth and reducing maintenance overhead.

In the Case Designer within Pega, components such as automations and approval decisions can be tagged with a Minimum Lovable Product (MLP) release for project sizing. This helps in prioritizing development tasks: C. Automations are significant because they often represent complex backend processes that can greatly enhance the application’s efficiency and are crucial for an MLP where automated features can define product usability and appeal. D. Approval decisions are key business processes that often require careful consideration and testing to ensure they meet business requirements effectively, making them important to highlight in early releases for user acceptance and feedback.

When development teams are working on separate enhancements with uncertain release dates, it is practical to: A. Create a new ruleset version for each team, allowing them to manage their versions independently, ensuring that their changes are isolated and do not impact other teams. B. Set up a branch ruleset for each team, which is ideal for supporting parallel development efforts. Branch rulesets enable teams to work in isolation, merging their work back into the main application ruleset once their individual enhancements are complete and ready for integration.

To configure a pie chart that displays the number of cases each manager has created using a list report:

B. Group the manager name column. Grouping the report by the manager name column aggregates the data such that each manager's entry shows the count of cases they have created. This configuration provides the necessary data structure for a pie chart visualization, where each slice represents a manager and their corresponding case count.

For routing loan requests to specific loan officers based on the type of loan, the configuration needs to precisely match the type of loan to the designated officer.

• D. Route the case to a worklist using a When condition: This approach utilizes Pega's conditional logic capabilities to evaluate the type of loan and route the case accordingly. A "When" condition can be configured for each loan type to determine the appropriate loan officer's worklist (Adam Ross for mortgages, Julia Samuels for automobile loans, and Don Smith for equity lines). This ensures that each loan request advances directly to the correct officer's attention based on the specified criteria.

Routing the case to a worklist or work queue using a skilled router (A and C) could be used in scenarios where assignment is based on skill levels or capabilities rather than specific conditional logic. Routing the case to a work queue using a When condition (B) is close but less direct than using worklists for individual officers, as work queues are typically used for groups or teams rather than individuals.

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

Simulating integrations in Pega is particularly useful when: A. External services exhibit slow response times, affecting development and testing cycles. Simulation allows for testing without delays. B. The external service or API is not yet available, but development needs to proceed. Simulation provides a way to develop and test the integration points based on expected behaviors without the actual service being live.

In the context of creating a customer loyalty account where the customer's contact information is captured and displayed within the case, organizing and relating this data efficiently is key.

• B. An Embedded data field: This option allows the contact information (name, email, phone number, address) to be structured as part of the case data in a coherent and integrated manner. Embedding this information ensures it is directly associated with each loyalty account case, facilitating data management and access within the application's data model.

A Data reference field (A) links to data instances outside the case, which is not the primary requirement here. A Case reference field (C) is used for linking cases together, which does not apply to this scenario of capturing contact information. A Query field (D) is intended for retrieving data based on a query, which is not relevant for directly embedding and displaying entered contact information within a case.