Java: Which practice avoids a common mistake with NIO Files and Path?

Difficulty:

Medium

Questions:

1

Time Limit:

2 minutes

Passing Score:

100%

Question

Which practice avoids a common mistake with NIO Files and Path?

  1. Ignore the NIO Files and Path issue and rely on team discipline instead of APIs or contracts.
  2. Do not treat filesystem operations as simple string manipulation or assume they are instantly successful on every platform.
  3. Silence the NIO Files and Path problem by using raw types, broad catches, or shared mutable state.
  4. Prefer the version of NIO Files and Path that makes behavior less predictable as long as the code compiles.

Hint

Look for the option that protects correctness instead of hiding the problem.

Answer and rationale

Correct answer: B. Do not treat filesystem operations as simple string manipulation or assume they are instantly successful on every platform.

Do not treat filesystem operations as simple string manipulation or assume they are instantly successful on every platform. This is a common failure mode in real Java code and a frequent interview follow-up.

Track: Java