Test Status
      JDBCRANDOMTEST
      (A) UNIQUE
      (B) AUTO_INCREMENT
      (C) SEQUENCE
      (D) None of the above -- Surrogate keys are not implemented in MySQL.
      (A) When a connection is created, it is in auto-commit mode.
      (B) If the value is true each individual SQL statement is treated as a transaction and will be automatically committed right after it is executed.
      (C) once auto-commit mode is disabled, no SQL statements will be committed until you call the method commit explicitly
      (D) By default the JDBC call is in auto-commit mode.
      (A) Type 1
      (B) Type 2
      (C) Type 3
      (D) Type 4
      (A) In the MySQL database mysql
      (B) In the MySQL database metadata
      (C) In the MySQL database metasql
      (D) In the MySQL database mysql
      (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) Regular Statement
      (B) Interim Statement
      (C) Callable Statement
      (D) Prepared Statement
      (A) TRANSACTION_READ_COMMITTED
      (B) TRANSACTION_READ_UNCOMMITTED
      (C) TRANSACTION_REPEATABLE_READ
      (D) TRANSACTION_SERIALIZABLE
      (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) a
      (B) b
      (C) c
      (D) d
      (A) Type 4
      (B) Type 3
      (C) Type 2
      (D) Type 1
      (A) Type 4 driver is "native protocol, pure java" driver
      (B) Type 4 drivers can not be used with Netscape
      (C) Type 4 drivers are 100% Java compatible
      (D) Type 4 drivers uses Socket class to connect to the database
      (A) Type 1 only
      (B) Type 2 only
      (C) Both Type 3 and Type 4
      (D) All of Type 1, Type 2, Type 3 and 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.