Concurrency basics · interview question
In a multithreaded e-commerce application, why is it dangerous to use a standard HashMap for tracking session data?
Multiple choiceEasychapter-15-curatedpremiumconcurrencyconcurrent-collections
Answer and explanation
Correct answer
B. It can become corrupted or enter an infinite loop.
Why
A standard HashMap is not thread-safe. Under concurrent modifications, it can become corrupted or even enter an infinite loop, especially during resizing.
Test yourself on Concurrency basics
A free test with instant, explained results. No account needed.
More Concurrency basics questions
- How can you ensure that a CompletableFuture runs on a specific Executor?
- Which situation benefits most from using AtomicInteger over synchronized blocks?
- Which CompletableFuture method should be used to execute a task asynchronously in a non-blocking manner?
- In which scenario would you use.thenCompose() over.thenApply() in CompletableFuture?
- Which CompletableFuture method should be used to handle both results and exceptions in a unified way?
- How does AtomicInteger's getAndIncrement method differ from incrementAndGet?