[Solved] Which statement best explains why StringBuilder is not thread-safe while StringBuffer is? — Ans: StringBuffer methods are synchronized; StringBuilder methods are not. | Java

Java - Strings and String Handling

Which statement best explains why StringBuilder is not thread-safe while StringBuffer is?

A<code>StringBuilder</code> methods are synchronized; <code>StringBuffer</code> methods are not.

BBoth are thread-safe because they are mutable.

C<code>StringBuffer</code> methods are synchronized; <code>StringBuilder</code> methods are not.

DNeither is thread-safe because they both modify strings.

Step-by-Step Solution

Solution:

Step 1: Understand synchronization in StringBuffer
StringBuffer methods are synchronized, making it safe for use by multiple threads.
Step 2: Understand lack of synchronization in StringBuilder
StringBuilder methods are not synchronized, so it is faster but not thread-safe.
Final Answer:
StringBuffer methods are synchronized; StringBuilder methods are not. -> Option C
Quick Check:
Synchronization = StringBuffer; no sync = StringBuilder [OK]

Quick Trick: StringBuffer is synchronized; StringBuilder is faster but not thread-safe [OK]

Common Mistakes:

Master "Strings and String Handling" in Java

9 interactive learning modes - each teaches the same concept differently

More Java Quizzes

Which statement best explains why StringBuilder is not thread-safe while StringBuffer is?