Why might a programmer choose to declare a method inside an interface?

• A. To have a single implementation across classes
• B. To allow any class to inherit it without instantiation
• C. To have private methods shared
• D. To control access to the method

Answer: (B)

Declaring a method inside an interface allows any class that implements the interface to inherit the method's declaration without instantiation. This characteristic is fundamental to the concept of interfaces in Java. They provide a way to define a contract that multiple classes can follow, enabling polymorphism. When a class implements an interface, it is committing to providing specific functionality outlined by that interface, thereby promoting a consistent interaction model across different implementations.

In Java, interfaces can contain method declarations (abstract methods) that do not specify concrete behavior, which must be defined in the implementing classes. By using interfaces, programmers can create methods that can be shared among multiple classes without requiring an instantiation of the interface itself. This fosters loose coupling and enhances code reusability.

The other options don't accurately capture the purpose of interface methods. The notion of a single implementation across classes is more aligned with abstract classes rather than interfaces, as interfaces generally encourage multiple implementations. Private methods shared across multiple classes pertain to either private methods in classes or default methods in interfaces but do not speak directly to the fundamental reason for declaring methods in an interface. Controlling access to methods typically pertains to encapsulation and visibility modifiers in classes rather than the primary purpose of interfaces.

Thus, the choice regarding allowing any