SQL for Java Devs · interview question
In a high-concurrency environment, which isolation level would you choose to prevent dirty reads but allow non-repeatable reads?
Multiple choiceHardchapter-8-curatedpremiumsql-for-java-devstransactions
Answer and explanation
Correct answer
C. Read Committed
Why
Read Committed is an isolation level that prevents dirty reads by only allowing access to committed data. However, it permits non-repeatable reads because data can be modified by others between reads within the same transaction.
Test yourself on SQL for Java Devs
A free test with instant, explained results. No account needed.
More SQL for Java Devs questions
- How can JDBC transactions help maintain data integrity during an e-commerce checkout process?
- What would be the effect of not closing a PreparedStatement in a Java application?
- In JDBC, how do you ensure that SQL injection is prevented when executing a query that searches for a user by email?
- Why do teams use SQL JOINs to fetch relational data in a single query in production code?
- What should a repository method mainly encapsulate?
- How can you prevent the N+1 query problem when retrieving a list of orders with their customer details?