To secure a Pega application in production, which of the following is the best practice for password management?
Correct Answer: B
Question 12
Assume that two customers are simultaneously attempting to book tickets for the same flight, which has limited seat availability. How does the design pattern for limited availability and concurrency handle this scenario? (Choose Two)
Correct Answer: C,D
Comprehensive and Detailed Explanation From Exact Extract: Pega's limited availability and concurrency design pattern, as taught in Pega Academy'sApplication Design Missionand thePega Certified Lead System Architect Study Guide, relies on locking mechanisms to manage resource contention, such as booking limited flight seats. It ensures fair and consistent handling of concurrent requests. * Option A (Incorrect): Recording attempts and placing customers on a waiting list is a business process, not a core feature of the concurrency design pattern.The pattern focuses on locking and allocation, not waitlist management, per theConcurrency Designmodule. * Option B (Incorrect): Rejecting both bookings and entering an ambiguity mode is not a standard Pega approach. The platform uses locking to resolve concurrency, not ambiguous retries, as noted in the Locking Mechanismsguidelines. * Option C (Correct): The design pattern allows both customers to attempt booking, but Pega's locking (e.g., pessimistic locking) ensures only one secures the seat. The other receives a notification of no available seats after the system checks availability, aligning with Pega's concurrency handling, as documented in theLimited Availability Patternsection of Pega Community. * Option D (Correct): The pattern often prioritizes bookings on a first-come-first-serve basis, with the first request to lock the resource (e.g., seat) succeeding. This is managed by Pega's locking mechanism, per theConcurrency Designmodule. : Pega Academy:Application Design Mission(covers concurrency and limited availability). Pega Community:Locking MechanismsandLimited Availability Pattern(details on booking scenarios). Pega Certified Lead System Architect Study Guide (v23): Section onApplication Design(emphasizes locking for concurrency).
Question 13
Which of the following types of testing are typically included in a comprehensive testing strategy? (Select all that apply)
Correct Answer: A,B,C,D,E
Question 14
The test coverage report in Pega Platform helps to determine the number of rules covered during a test cycle. It is viewable at the application and user level. Which of the following statements describes the difference between these two levels?
Correct Answer: B
Comprehensive and Detailed Explanation From Exact Extract: Pega's test coverage reports, as described in Pega Academy'sTesting Missionand thePega Certified Lead System Architect Study Guide, provide insights into rule execution during testing, available at both application and user levels. The distinction lies in the scope of the testing session. * Option A (Incorrect): The test coverage report does not differentiate based on ruleset types (application vs. branch rulesets). It tracks rule execution regardless of where rules reside, per theTest Coveragemodule. * Option B (Correct): The application-level report aggregates test coverage for all users in a session, providing a comprehensive view of rule execution across the application. The user-level report is specific to the individual user who initiated the testing session, focusing on their actions. This is explicitly stated in theTest Coverage Reportssection of Pega Community. * Option C (Incorrect): Test coverage reports do not distinguish between API-based and user-based testing. They track rule execution regardless of the testing method, as clarified in theTesting Framework module. * Option D (Incorrect): The report does not differentiate based on enterprise vs. implementation layers. Coverage is based on rule execution within the application context, not class hierarchy, per theTest Coverageguidelines. : Pega Academy:Testing Mission(covers test coverage reports). Pega Community:Test Coverage Reports(details on application vs. user levels). Pega Certified Lead System Architect Study Guide (v23): Section onDeployment and Testing(emphasizes testing metrics).
Question 15
Which two benefits does the Search and Reporting Service offer over embedded Elasticsearch? (Choose Two)
Correct Answer: A,C
Comprehensive and Detailed Explanation From Exact Extract: Pega's Search and Reporting Service (SRS), as described in Pega Academy'sLead System Architect Mission and thePega Certified Lead System Architect Study Guide, is a managed cloud service that replaces embedded Elasticsearch for full-text search, offering improved reliability and flexibility. * Option A (Correct): SRS eliminates issues with data index loss when Util nodes crash, as it is a managed service with built-in redundancy and fault tolerance, unlike embedded Elasticsearch, which relies on local nodes. This is documented in theSearch and Reporting Servicesection of Pega Community. * Option B (Incorrect): Row-level security is managed by Pega's access control mechanisms, not by SRS or embedded Elasticsearch. SRS focuses on search functionality, per theSecurity Designmodule. * Option C (Correct): SRS operates on independent release cycles from the Pega Platform, allowing updates without impacting core application functionality. This contrasts with embedded Elasticsearch, which is tightly coupled, as noted in theSRS Architectureguidelines. * Option D (Incorrect): SRS is a specific Pega-managed service, not a generic connector for any full- text search engine. It replaces embedded Elasticsearch but does not support arbitrary engines, per the Search Configurationmodule. : Pega Academy:Lead System Architect Mission(covers Search and Reporting Service). Pega Community:Search and Reporting Service(details on benefits over Elasticsearch). Pega Certified Lead System Architect Study Guide (v23): Section onPega Platform Architecture(emphasizes SRS advantages).
