Java Web Technologies and JDBC Practice Test

Java applets are small applications designed to be delivered to a user's browser via HTTP and executed within the JVM on the client's machine. Servlets (Option C) run on the server side.

The JDBC-ODBC bridge is classified as a Type 1 JDBC driver because it uses a native library (the ODBC driver) to bridge Java applications to databases. Type 1 drivers are JDBC-ODBC bridge drivers that translate JDBC calls into ODBC calls.

Tomcat maintains only a single instance of each JSP page in memory at any given time. This single instance is then used to serve multiple requests concurrently through different threads, ensuring memory efficiency while handling simultaneous users.

Type 3 and Type 4 JDBC drivers are specifically designed for network communication. Type 3 drivers use a three-tier architecture where calls are translated to an intermediate middleware protocol, while Type 4 drivers are pure Java implementations that communicate directly with the database over the network using the database's native protocol.

Sun Microsystems, the original creator of Java, defined four JDBC driver types: Type 1 (JDBC-ODBC bridge), Type 2 (Native API partly Java), Type 3 (Net protocol fully Java), and Type 4 (Native protocol fully Java). This classification system categorizes drivers based on their implementation approach and platform dependence.

Tomcat executes JSP pages using threads from its thread pool rather than spawning separate processes or using CGI. When a JSP is requested, Tomcat uses one of its worker threads to execute the compiled servlet (which is what a JSP becomes after compilation), making it much more efficient than CGI scripts or separate processes.

JDBC stands for Java Database Connectivity, which is the standard Java API for database-independent connectivity between the Java programming language and a wide range of databases. This API allows Java applications to execute SQL statements and retrieve results from any database that provides a JDBC driver.

MySQL stores its metadata (system information about databases, tables, users, and privileges) in a system database called 'mysql'. This database contains tables like 'user', 'db', 'tables_priv', and others that store all the administrative and structural information about the MySQL server.

Java was invented by Sun Microsystems in 1995 under the leadership of James Gosling. The language was originally called 'Oak' and was developed for consumer electronics, later repurposed for web applications. Sun was acquired by Oracle in 2010, which now maintains Java.

MySQL is an open-source relational database management system that runs on multiple platforms including UNIX, Linux, and Windows. It is widely used in web applications and is known for its reliability, speed, and ease of use. The other options (JSP/SQL, JDBC/SQL, Sun ACCESS) are not actual database products.

JSP pages are translated into Java servlets by the JSP container. The servlet is then compiled into bytecode and executed by the server. This transformation happens automatically the first time the JSP is accessed or when it's modified. Options A is incorrect because applets run on the client side, not the server.

JSP uses Java as its primary server-side scripting language. While JavaScript may appear in client-side code within JSP pages, the server-side scriptlets and expressions must be written in Java. Options A and B are Microsoft technologies not used in JSP, and D is incorrect because JSP does not support VBScript or JScript.

Java bytecode is machine-independent code that runs on any platform with a JVM. It's an intermediate representation between Java source code and machine code, allowing Java's 'write once, run anywhere' capability. Option A is incorrect because bytecode is not machine-specific, and B is wrong because Java source code must be compiled to bytecode first.

When the web server and DBMS are on the same machine, all JDBC driver types can technically be used. Type 1 (JDBC-ODBC bridge) works locally, Type 2 (native API) can connect directly, and Types 3 and 4 (network protocols) can connect via localhost. The question's architecture constraint doesn't eliminate any driver type in this scenario.

Apache Tomcat is the servlet container developed jointly by Apache Foundation and Sun Microsystems (now Oracle). It implements Java servlet and JSP specifications. The Apache Web server (option B) serves static content and is not a servlet processor, and there is no official 'Sun servlet processor' product.

The JSP specification maintains a single instance of each JSP page in memory, with multiple threads handling concurrent requests. This design is memory-efficient and thread-safe. Options B and C are incorrect because the specification doesn't mandate multiple copies, and D is wrong because the instance is shared, not unlimited.

Java servlets run on the web server and respond to HTTP requests. They are the server-side counterpart to applets. Option A is incorrect because standalone Java applications aren't invoked via HTTP, and B is wrong because applets run client-side in browsers, not on servers.

The JDBC-ODBC bridge is a Type 1 JDBC driver that provides JDBC access via ODBC drivers. Type 1 drivers are bridge drivers that translate JDBC calls into another database API (in this case, ODBC). Types 2, 3, and 4 use different architectures.

Type 3 and Type 4 JDBC drivers are designed for network communication. Type 3 uses a middleware translation layer, and Type 4 is a pure Java driver that converts JDBC calls directly into the database's network protocol. Type 1 uses a bridge, and Type 2 uses native client libraries.

Tomcat executes JSP pages using threads from its thread pool, not as separate processes or CGI scripts. When a JSP is accessed, Tomcat's threads handle the request within the servlet container's process. This threading model is more efficient than spawning new processes for each request (CGI model).

JDBC stands for Java Database Connectivity, the Java API for connecting and executing queries on databases. It provides a standard interface for accessing various relational databases. Options B and C are incorrect - the official name uses 'Connectivity' not 'Components' or 'Control'.

A Java applet is a small application designed to run in a web browser. It is sent to the user via HTTP, invoked on the user's computer using the HTTP protocol, and executes as an application within the browser's JVM. A Java application runs standalone, not via HTTP. A Java servlet runs on the server side, not the client side.

AUTO_INCREMENT is the MySQL property used to create surrogate keys. It automatically generates a unique numeric value for each new row, typically used for primary key columns. UNIQUE is a constraint that ensures column values are distinct but doesn't auto-generate values. MySQL doesn't use SEQUENCE objects like some other databases (Oracle, PostgreSQL).

To run a compiled Java program, the machine must have the Java Virtual Machine (JVM) loaded and running. The JVM interprets Java bytecode and executes it on the host machine. The Java compiler is only needed during development to compile source code. Java bytecode is what the JVM executes, not what runs the program. A web browser is not required unless it's an applet.

JDBC driver Type 3 and Type 4 are pure Java drivers that can be used in either applet or servlet code. Type 3 is a net-protocol driver that converts JDBC calls to a database-independent protocol, while Type 4 is a native-protocol pure Java driver. Type 1 (JDBC-ODBC bridge) and Type 2 (native API partly Java) require native libraries and are platform-dependent, making them unsuitable for applets.