PEGACPLSA23V1 practice question 12 of 15
[Application Design] 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)
Full set: 60 questionsThe Pega design pattern for handling limited availability and concurrency, such as booking a flight with few seats, relies on a case locking strategy. The fundamental principle is first-come-first-serve (D), where the first user to successfully acquire a lock and commit the transaction secures the resource. In a common implementation using optimistic locking, both users can initiate the booking process. However, when the first user confirms their booking, the system updates the flight's seat count. When the second user attempts to commit, the system detects the data has changed (no seats left) and notifies them that the booking cannot be completed, as described in (C).
A: This describes a waitlisting pattern, which is a different business process. The core concurrency pattern focuses on immediate success or failure, not deferring the outcome. B: Rejecting both bookings is inefficient and not how Pega's locking mechanisms are designed. The system's goal is to successfully process one transaction, not fail all concurrent attempts.
1. Pega Academy
Lead System Architect (LSA) 8.7 Mission
Module: Case Locking. This module details the two primary locking strategies in Pega: pessimistic and optimistic.
Pessimistic Locking: The default mechanism where the first user to open a case obtains a lock
preventing others from making changes. This directly enforces the first-come-first-serve principle (Option D).
Optimistic Locking: Allows multiple users to open a case. When a user submits an update
the system verifies if the case was modified by another user. If so
the update fails
and the user is notified. This mechanism results in the scenario described in Option C.
2. Pega Documentation
"Managing case locking". This official document explains
"With optimistic locking
the system does not lock a case when a user opens it. The system acquires a lock only when the user submits the changes... If the case has been updated in the meantime
the user's changes are rejected." This directly supports the process described in Option C as a valid outcome of the design pattern.
Keep practicing
Take the free PEGACPLSA23V1 practice test
Ten exam-style questions with answers and explanations, plus the exam facts and study guides.
More questions
Other PEGACPLSA23V1 practice questions
- Question 1[Security Design] An application has a web page where users can upload and view images. T…
- Question 2[Reporting Design] In a retail inventory management application, the system captures and …
- Question 3[Data Modeling] As an LSA developing a Pega application for an online grocery store, you …
- Question 4[Data Modeling] In a hospital's patient management Pega application, patient details are …
- Question 5[Deployment and Testing] You are a Pega developer working on a large project. You must im…
- Question 6[Work Delegation and Asynchronous Processing] Hospital XYZ wants to analyze patient data …
