Test Status
      JDBCRANDOMTEST
      (A) Both Type 1 and Type 2
      (B) Both Type 3 and Type 4
      (C) Both Type 1 and Type 3
      (D) Type 4 only
      (A) Native-protocol, pure Java driver
      (B) JDBC-Net, pure Java driver
      (C) Native-API, partly Java driver
      (D) JDBC-ODBC Bridge plus ODBC driver
      (A) One
      (B) Two
      (C) Three
      (D) Four
      (A) a
      (B) b
      (C) c
      (D) d
      (A) A workaround is to explicitly call the method DriverManager.registerDriver(new YourDriverClass).
      (B) The problem is due to race condition in the class loader.
      (C) The race condition prevents the static section of code in the driver class from executing and registering the driver with the DriverManager.
      (D) All the above.
      (A) CallableStatement clbstmnt = con.prepareCall("{call totalStock}");cs.executeQuery();
      (B) Statement stmt = connection.createStatement();stmt.execute("totalStock()");
      (C) StoreProcedureStatement spstmt = connection.createStoreProcedure("totalStock()");spstmt.executeQuery();
      (D) PrepareStatement pstmt = connection.prepareStatement("totalStock()");pstmt.execute();
      (A) Type 1
      (B) Type 2
      (C) Type 3
      (D) Type 4
      (A) Both types of result sets will make changes visible if they are closed and then reopened.
      (B) A result set that is TYPE_SCROLL_INSENSITIVE does not reflect changes made while it is still open and one that is TYPE_SCROLL_SENSITIVE does.
      (C) You will get a scrollable ResultSet object if you specify one of these ResultSet constants.
      (D) A result set that is TYPE_SCROLL_INSENSITIVE makes the result set read only while one that is TYPE_SCROLL_SENSITIVE does not.
      (A) getNumberOfColumn
      (B) getMaxColumn
      (C) getColumnCount
      (D) getColumns
      (A) registerDriver() method
      (B) Class.forName()
      (C) Both A and B
      (D) getConnection()
      (A) Both Type 1 and Type 3
      (B) Both Type 1 and Type 2
      (C) Both Type 3 and Type 4
      (D) Type 4 only
      (A) Type 4
      (B) Type 3
      (C) Type 2
      (D) Type 1
      (A) A Type 3 driver is a JDBC-Net pure Java driver
      (B) This translates JDBC calls into a database -dependent net protocol.
      (C) Vendors of database middleware products can implement this type of driver into their products to provide interoperability with the greatest number of database servers.
      (D) a,b