In which situation is a method considered native?

• A. When it is declared final
• B. When it is implemented in a programming language other than Java
• C. When it is exclusively used for database interaction
• D. When it has no return type

Answer: (B)

A method is considered native when it is implemented in a programming language other than Java. This involves the use of the native keyword in the method declaration, indicating that the method's actual implementation resides in a native library written in languages such as C or C++. This allows Java to leverage low-level operations or access system resources that are not directly accessible through Java itself.

The native methods are typically used when Java needs to perform operations that require higher efficiency or interaction with hardware or operating system functionalities, which can be accomplished more effectively in a language that allows finer control over system resources. For instance, native methods can significantly improve performance or enable capabilities that are unavailable through Java's standard libraries.

In contrast, the other choices do not define the "native" status of a method in Java. Being declared final relates to inheritance and prevents method overriding, exclusive database interaction pertains to design patterns rather than method implementation, and having no return type merely indicates that the method doesn't return a value but doesn't influence whether it is native or not.