Skip to content

Tracks Drills Topics Technologies Tech stacks Skill areas

Tracks Drills Topics

Loading

Aporeon interview preparation

About Privacy Terms

.NET Concurrency & Parallelism

Synchronization

Shared state, atomic operations, locks, race conditions, deadlocks, and coordination between concurrent work.

12 drillsPractice one at a timeOrdered pathConcept questionComparison questionDebugging scenarioArchitecture scenario

Recommended start

SemaphoreSlim

Use SemaphoreSlim to bound concurrent asynchronous work without blocking threads unnecessarily.

Medium~7 minStep 1 of 12

Practice this drill Choose another

Search

12 of 12 shown

1SemaphoreSlimRecommended startUse SemaphoreSlim to bound concurrent asynchronous work without blocking threads unnecessarily.Concept questionMedium~7 min.NETASP.NET CoreC#Practice 2

Practice order

12 drillsOne at a time

1SemaphoreSlimUp next / Medium / ~7 min
2lock vs SemaphoreSlimMedium / ~7 min
3Race ConditionsMedium / ~10 min
4

lock vs SemaphoreSlimCompare lock and SemaphoreSlim for protecting shared state and coordinating async workflows.Comparison questionMedium~7 min.NETASP.NET CoreC#

Practice

3Race ConditionsInvestigate and fix a race condition caused by shared mutable state in a .NET service.Debugging scenarioMedium~10 min.NETASP.NET CoreC#Practice

4ConcurrentDictionaryChoose between ConcurrentDictionary and explicit locks when managing concurrent in-memory data.Comparison questionMedium~7 min.NETASP.NET CoreC#Practice

5Locking and AwaitingExplain why awaiting while holding synchronization resources can create deadlocks, contention, or stalled workflows.Debugging scenarioHard~12 min.NETASP.NET CoreC#Practice

6Interlocked vs lockChooses between atomic operations and a critical section based on whether one value or a multi-step invariant must change safely.Comparison questionMedium~7 min.NETC#Practice

7volatile and thread safetySeparates memory visibility and ordering from atomic multi-step updates, avoiding volatile as a substitute for real synchronization.Concept questionHard~9 min.NETC#Practice

8ReaderWriterLockSlim trade-offsEvaluates whether read-heavy access justifies a reader/writer lock instead of a simpler lock or immutable snapshot.Comparison questionHard~9 min.NETC#Practice

9Immutable snapshotsRedesigns read-heavy shared state so readers observe a complete version without coordinating every access through a lock.Architecture scenarioMedium~10 min.NETC#Practice

10Lock orderingFinds circular lock acquisition and replaces timing-dependent nested locking with a stable order or a simpler ownership boundary.Debugging scenarioHard~12 min.NETC#Practice

11Per-key coordinationSerializes work for the same resource while preserving concurrency across independent keys and managing keyed-lock lifetime safely.Architecture scenarioHard~12 min.NETASP.NET CoreC#Practice

12Lazy initializationUses runtime-supported initialization rather than timing-dependent manual checks and defines failure, retry, and disposal behavior explicitly.Concept questionMedium~7 min.NETC#Practice

ConcurrentDictionary

Medium / ~7 min

5Locking and AwaitingHard / ~12 min

6Interlocked vs lockMedium / ~7 min

7volatile and thread safetyHard / ~9 min

8ReaderWriterLockSlim trade-offsHard / ~9 min

+4 more drills in this section

Synchronization - .NET Concurrency & Parallelism | Aporeon