The abstraction that makes you know anyway

• A

  A leaky abstraction: the hidden cost still dictates how callers must write code

• B

  A violation of encapsulation, given that the internal behaviour is now visible

• C

  A missing cache, which would make the repeated queries cheap

• D

  A naming problem, since the methods do not say that they query