Your ASP.NET Core application has a scenario where a user tries to update a record that another user has already modified. How can you handle such scenarios using Entity Framework Core to ensure data integrity?

  • Optimistic Concurrency
  • Pessimistic Locking
  • No Locking
  • Dirty Read
Optimistic Concurrency is a technique used in Entity Framework Core to handle concurrent updates. When enabled, it checks if a record has been modified by another user since it was loaded, and if so, it prevents the update, ensuring data integrity and preventing data loss due to overwrites.
Add your answer
Loading...

Leave a comment

Your email address will not be published. Required fields are marked *