Java Interview Questions · interview question

Which practice avoids a common mistake with Adjacency List vs Adjacency Matrix?

Multiple choiceMediumjava-interview-2026interviewjavapitfall

Do not call a matrix representation efficient by default when the graph is sparse and memory matters.Silence the Adjacency List vs Adjacency Matrix problem by using raw types, broad catches, or shared mutable state.Prefer the version of Adjacency List vs Adjacency Matrix that makes behavior less predictable as long as the code compiles.Ignore the Adjacency List vs Adjacency Matrix issue and rely on team discipline instead of APIs or contracts.

Answer and explanation

Correct answer

A. Do not call a matrix representation efficient by default when the graph is sparse and memory matters.

Why

Do not call a matrix representation efficient by default when the graph is sparse and memory matters. This is a common failure mode in real Java code and a frequent interview follow-up.

Test yourself on Java Interview Questions

A free test with instant, explained results. No account needed.

Start free test

All Java Interview Questions questions →

Which practice avoids a common mistake with Adjacency List vs Adjacency Matrix?

Correct answer

Why

More Java Interview Questions questions