Type 4: Native-protocol/all-Java driver. The native-protocol/all-Java driver (JDBC driver type 4) converts JDBC calls into the vendor-specific database management system (DBMS) protocol so that client applications can communicate directly with the database server.
http://www.javaworld.com/article/2076117/java-web-development/jdbc-drivers-in-the-wild.html
(a) By invoking the method get(..., String type) on the ResultSet, where type is the database type. (b) By invoking the method get(..., Type type) on the ResultSet, where Type is an object which represents a database. type. (c) By invoking the method getValue(...), and cast the result to the desired Java type.
http://javabysri.blogspot.in/2012/06/jdbc-objective-questions.html
Type 3 driver-the Network-Protocol Driver The JDBC type 3 driver, also known as the network-protocol driver is a database driver implementation which makes use of a middle-tier between the calling program and the database.
http://www.roseindia.net/jdbc/jdbc-driver-and-its-types.shtml
Type 2 Driver-the Native-API Driver The JDBC type 2 driver, also known as the Native-API driver is a database driver implementation that uses the client-side libraries of the database. The driver converts JDBC method calls into native calls of the database API.
http://www.roseindia.net/jdbc/jdbc-driver-and-its-types.shtml
JDBC driver type 2 -- the native-API/partly Java driver -- converts JDBC calls into database-specific calls for databases such as SQL Server, Informix, Oracle, or Sybase. The type 2 driver communicates directly with the database server; therefore it requires that some binary code be present on the client machine.
http://www.javaworld.com/article/2076117/java-web-development/jdbc-drivers-in-the-wild.html
The type 1 driver, JDBC-ODBC Bridge, translates all JDBC calls into ODBC (Open DataBase Connectivity) calls and sends them to the ODBC driver. As such, the ODBC driver, as well as, in many cases, the client database code, must be present on the client machine. Figure 1 shows a typical JDBC-ODBC Bridge environment.
http://www.javaworld.com/article/2076117/java-web-development/jdbc-drivers-in-the-wild.html
Type 4 - the Native-Protocol Driver The JDBC type 4 driver, also known as the native-protocol driver is a database driver implementation that converts JDBC calls directly into the vendor-specific database protocol. The type 4 driver is written completely in Java and is hence platform independent.
http://www.roseindia.net/jdbc/jdbc-driver-and-its-types.shtml
a. When the driver is not registered by Class.forname() method. b. When the user name, password and the database does not match. c. When the JDBC database URL passed is not constructed properly. d. When the type 4 driver is used. 37.
http://javabysri.blogspot.in/2012/06/jdbc-objective-questions.html
[a] JDBC is an API to connect to relational-, object-and XML data sources. [b] JDBC stands for Java DataBase Connectivity. [c] JDBC is an API to access relational databases, spreadsheets and flat files. [d] JDBC is an API to bridge the object-relational mismatch between OO programs and relational. databases. 2.
http://javabysri.blogspot.in/2012/06/jdbc-objective-questions.html
The JDBC DriverManager class then sends all JDBC API calls to the loaded driver. JDBC Driver This topic defines the Java(TM) Database Connectivity (JDBC) driver types. Driver types are used to categorize the technology used to connect to the database. A JDBC driver vendor uses these types to describe how their product operates.
http://www.roseindia.net/jdbc/jdbc-driver-and-its-types.shtml
which type of driver converts jdbc calls into the network protocol used by the database management system directly?
The Java Database Connectivity driver type 4 converts JDBC calls into the network protocol used by the database management system directly.  The network protocol used by the database management system directly is JDBC driver type 4.