ISC2 Certified Secure Software Lifecycle Professional (CSSLP) Practice Question

While designing the order-processing module of an e-commerce platform, you find that the persistence layer uses optimistic locking by keeping a version column in each order row. Under heavy load, frequent update conflicts cause users to repeat transactions. To reduce the risk of lost updates in this high-contention situation, which change would be most effective?

  • Adopt pessimistic concurrency by locking each row for update as soon as it is read, blocking other writers until the transaction commits.

  • Remove the version column and let the database accept the last update that arrives (last-write-wins).

  • Lower the transaction isolation level to READ UNCOMMITTED so concurrent updates proceed without blocking.

  • Replace row-level versioning with a single version counter for the entire table to apply optimistic locking at table scope.

ISC2 Certified Secure Software Lifecycle Professional (CSSLP)
Secure Software Implementation
Your Score:
Settings & Objectives
Random Mixed
Questions are selected randomly from all chosen topics, with a preference for those you haven’t seen before. You may see several questions from the same objective or domain in a row.
Rotate by Objective
Questions cycle through each objective or domain in turn, helping you avoid long streaks of questions from the same area. You may see some repeat questions, but the distribution will be more balanced across topics.

Check or uncheck an objective to set which questions you will receive.

Bash, the Crucial Exams Chat Bot
AI Bot