Java Servlets and Web Technologies Quiz

The Servlet interface has 5 methods: lifecycle methods (init, service, destroy) and ancillary methods (getServletConfig, getServletInfo). The question asks for ancillary methods - those NOT part of the core lifecycle. getServletConfig() returns the servlet's configuration object, and getServletInfo() returns descriptive information about the servlet. These are considered ancillary/support methods. Options A and B are lifecycle methods. Option C (getServletContext) returns the context but is NOT a method of Servlet interface - it's a method of ServletConfig interface (accessed via getServletConfig().getServletContext()).

The service() method is indeed the core of a servlet - every client request triggers a single call to service(), which reads the HttpServletRequest and produces the HttpServletResponse. The InputStream from the client can be obtained via request.getInputStream(). Option D describes the destroy() method, not service().

Servlets process client requests (A), handle multiple concurrent requests for high performance (C), and can forward requests to enable load balancing (D). Option B is incorrect because it describes EJBs, not servlets. Option E is incorrect - clustering is achieved at the application server level, not by servlets themselves.

Servlets are server-side components that run in a web container, NOT in a browser (A is false). They are platform-independent Java programs (C), support multithreaded request processing (D), and can maintain session information via HttpSession (E). The term 'Serverside Applet' is accurate (B).

In Java, every Thread must implement the run() method, which contains the code that executes in the thread. The start() method is called to begin execution but is not implemented by subclasses - run() is the method you override with your thread's logic.

Interface methods in Java are implicitly public and abstract. They cannot be private (no implementation to hide) or protected (interfaces define public contracts). Abstract is explicit but allowed since it's implicit anyway.

Java always passes references by value - the reference itself is copied, but both copies point to the same object. This means modifications to the object are visible to the caller, but reassigning the reference is not. The 'pass by value' terminology refers to the reference copy, not the object.

The transient keyword in Java marks fields that should be skipped during serialization. When an object is serialized, transient fields are not written to the output stream and will have default values when deserialized.

The wait(), notify(), and notifyAll() methods are defined in the Object class, making them available to all Java objects. They're used for thread coordination and can only be called within synchronized contexts.

The standard lifecycle methods of a Java Applet include init(), start(), stop(), and destroy(). The method named starts(); with an 's' is incorrect, as the actual method is start();.

A Prepared Statement in JDBC is a precompiled SQL statement. Precompilation improves execution performance for repeated queries and provides strong protection against SQL injection.

TreeSet implements the SortedSet interface and maintains elements in ascending order using a red-black tree. HashSet does not guarantee any order and uses hash codes for storage, providing O(1) average case performance.

Java allows any order for method modifiers. 'static public void' and 'public static void' are identical to the compiler. The main method requires public, static, void return type, String[] args, but modifier order is flexible.

When no command-line arguments are provided, Java passes an empty String array (length 0) to main(), not null. The array object exists but contains no elements, so args.length would be 0.

The Java Applet lifecycle has standard methods: init(), start(), stop(), paint(), and destroy(). The option 'destroys()' is incorrect because the actual method is 'destroy()' (not 'destroys()'), making it the option that is NOT a phase of the applet lifecycle.