QUESTION 41 In the design of Pega enterprise applications, the Lead System Architect must prioritize Microjourneys according to Pega Express best practices. Which two of the following statements accurately describe the concept of Microjourneys in Pega implementations? (Choose Two)
Comprehensive and Detailed Explanation From Exact Extract: Microjourneys are a core concept in Pega Express, as taught in Pega Academy’sApplication Design Mission and thePega Certified Lead System Architect Study Guide.They represent focused, outcome-driven segments of a customer journey, designed to deliver value quickly and align with business objectives. * Option A (Correct): Microjourneys are segments of the customer journey that accomplish specific business outcomes, such as completing a loan application or resolving a complaint. This aligns with Pega Express’s focus on breaking down complex journeys into manageable parts, as outlined in the Microjourney Designmodule. * Option B (Correct): Microjourneys represent case life cycles or units of work that deliver significant outcomes for customers and users, such as approving a claim or onboarding a client. This is a key principle of Pega’s case-centric design, per theApplication Designmodule. * Option C (Incorrect): Microjourneys are not about creating reusable assets for citizen developers. While reusable assets may support Microjourneys, their primary purpose is delivering business outcomes, not enabling improvisation, as clarified in thePega Expressguidelines. * Option D (Incorrect): Microjourneys are not data objects; they are process-driven case life cycles, not data manipulation constructs. Data objects support Microjourneys but are distinct, per theData Modeling module. : Pega Academy:Application Design Mission(covers Microjourneys and Pega Express). Pega Community:Microjourney Design(details on outcome-driven design). Pega Certified Lead System Architect Study Guide (v23): Section onApplication Design(emphasizes Microjourneys).
QUESTION 43 A claims adjuster is working through a backlog of cases using a newly updated Pega insurance application. The adjuster is tasked with entering detailed information into a digital claims form for each case. However, as they proceed from one input field to another, they encounter noticeable delays in data rendering, and occasionally, the application becomes unresponsive, significantly slowing down their workflow. Given this situation, which two of the following are likely causes for the poor user experience observed by the claims adjuster? (Choose Two)
Comprehensive and Detailed Explanation From Exact Extract: Pega’s performance optimization techniques, as taught in Pega Academy’sPerformance Optimization Mission and thePega Certified Lead System Architect Study Guide, focus on minimizing data retrieval and ensuring asynchronous processing to enhance user experience. Delays in form rendering often stem from inefficient data handling or synchronous operations. * Option A (Incorrect): The “Use single page” option for data pages (node-level scoping) does not directly cause rendering delays. It controls data page scope, not fetch efficiency, and is unlikely to impact form performance, per theData Page Configurationmodule. * Option B (Correct): Retrieving a larger dataset than necessary from the system of record (e.g., fetching all case data instead of relevant fields) can overload the application, causing delays in rendering the claims form. Optimizing data queries is a key Pega best practice, as documented in theData Retrieval Optimizationsection of Pega Community. * Option C (Incorrect): The “Reload once per interaction” option, when disabled, may cause unnecessary reloads, but it is not a primary cause of form rendering delays. Its impact is minimal compared to excessive data retrieval or synchronous integrations, per theData Page Performance module. * Option D (Correct): Synchronous data fetches through integrations (e.g., waiting for an external API response) can cause the application to pause, leading to unresponsiveness. Pega recommends asynchronous processing for integrations, as noted in theIntegration Performanceguidelines. : Pega Academy:Performance Optimization Mission(covers data retrieval and asynchronous processing). Pega Community:Data Retrieval OptimizationandIntegration Performance(details on performance issues). Pega Certified Lead System Architect Study Guide (v23): Section onPerformance Optimization(emphasizes efficient data handling).
QUESTION 45 BigCo is currently working on two separate development projects, each handled by a different team. One team is developing the Quoting application, while the other is working on the Policy Administration application. These applications are under development on separate servers. The Quoting application is built on top of the Policy Administration application. The Policy Administration application needs enhancements to support other business areas. When a new version of the Policy Administration application is released, the Quoting team receives a notification, and then imports a RAP that contains the new version. What are the two best practices to reduce potentialdevelopment conflicts and ensure that the most recent version of the Policy Administration application is in use? (Choose Two)
Comprehensive and Detailed Explanation From Exact Extract: Pega’s application development and deployment practices, as taught in Pega Academy’sDeployment Mission and thePega Certified Lead System Architect Study Guide, emphasize managing dependencies and conflicts in multi-team environments. For layered applications like Quoting and Policy Administration, synchronization and governance are critical. * Option A (Correct): Periodically syncing the Policy Administration application code ensures the Quoting team uses the latest version, reducing conflicts from outdated dependencies. This can be achieved through RAP imports or pipeline automation, as documented in theApplication Dependency Managementmodule. * Option B (Incorrect): Sharing rulesets between applications risks unintended changes and tight coupling, increasing conflicts. Pega recommends separate rulesets for modular applications, per the Ruleset Managementguidelines. * Option C (Correct): Performing branch reviews when merging branches ensures that changes to the Policy Administration application are validated before integration, preventing conflicts and maintaining quality. This is a standard practice in Pega’s DevOps framework, as noted in theBranch Mergingsection of Pega Community. * Option D (Incorrect): Switching between applications when modifying rules is impractical and error- prone, as it does not address version synchronization or conflict prevention. It also violates Pega’s separation of concerns, per theApplication Developmentmodule. : Pega Academy:Deployment Mission(covers application dependencies and branching). Pega Community:Branch MergingandApplication Dependency Management(details on conflict prevention). Pega Certified Lead System Architect Study Guide (v23): Section onDeployment and Testing(emphasizes synchronization and reviews).
QUESTION 50 A healthcare company wants to migrate its patient management system to a more secure and scalable environment. After evaluating different options, the company decides to host their application on a Pega- managed cloud environment, expecting it to meet its growing data security and compliance needs while ensuring uninterrupted access to patient records. In this context, which three of the following responsibilities does Pega assume in managing the healthcare company’s application in the Pega Cloud environment? (Choose Three)
Comprehensive and Detailed Explanation From Exact Extract: Pega Cloud, as described in Pega Academy’sLead System Architect Missionand thePega Certified Lead System Architect Study Guide, is a managed cloud environment where Pega assumes specific responsibilities for infrastructure, security, and compliance, while clients manage application-level configurations. This is particularly critical for healthcare applications with stringent regulatory requirements. * Option A (Correct): Pega Cloud monitors the network and ensures system-level access control to protect patient information and maintain system integrity. This includes firewalls, intrusion detection, and network security, as outlined in thePega Cloud Servicessection of Pega Community. * Option B (Incorrect): While Pega installs the Pega Platform, the responsibility for installing additional Pega applications (e.g., industry-specific solutions) typically falls to the client or requires coordination via subscriptions. This is not a default Pega Cloud responsibility, per thePega Cloud Architecture module. * Option C (Correct): Pega Cloud securely stores data in a cloud repository, ensuring encryption and compliance with regulations like HIPAA for healthcare data. This is a core responsibility of Pega Cloud, as noted in theData Security in Pega Cloudmodule. * Option D (Correct): Pega Cloud oversees compliance, conducts security monitoring, and responds to security events to prevent breaches. This includes SOC 2 compliance and incident response, as documented in thePega Cloud Securitysection. * Option E (Incorrect): Authentication and authorization mechanisms (e.g., SSO, RBAC) are configured by the client within the Pega application, not managed by Pega Cloud. Pega provides the tools, but the client defines access policies, per theSecurity Designmodule. : Pega Academy:Lead System Architect Mission(covers Pega Cloud responsibilities). Pega Community:Pega Cloud Services(details on security and compliance). Pega Certified Lead System Architect Study Guide (v23): Section onPega Platform Architecture(emphasizes Pega Cloud management).
No Responses