Java Core Classes and Threads

QTP/UFT provides four main trigger event types for Recovery Scenarios: Pop-up window (unexpected dialog), Object State (property changes), Test run error (script failures), and Application crash (application terminates). These events trigger recovery operations to handle exceptions automatically during test execution. VBScript events are not trigger types in this context.

Integer, Boolean, and Long wrapper classes all have valueOf(String) methods for string-to-primitive conversion. Character is the exception - it uses charValue() and has no valueOf(String) method.

System.gc() is the correct method to suggest garbage collection to the JVM. Options A, B, and C list non-existent methods - System has no free(), setGarbageCollection(), or setGarbageCollector() methods.

VB.NET supports both structured exception handling (Try...Catch...Finally blocks) and unstructured exception handling (On Error GoTo statements) for backward compatibility with VB6. This dual approach allows developers to choose modern error handling or legacy-style error management.

The setContentType() method must be called before using PrintWriter because it sets the content type (MIME type) of the response being sent to the client. Once the PrintWriter is obtained and used to write content, the response headers are committed and cannot be modified.

The _jspService() method is generated automatically by the JSP container and contains the servlet's code. It cannot be overridden in a JSP page, whereas jspInit() and jspDestroy() can be defined by the developer.

The jspDestroy() method can be overridden in a JSP page to perform cleanup operations when the page is being unloaded or the JSP container is shutting down. This is part of the JSP lifecycle, parallel to the destroy() method in Servlets.

Setting <%@ page isThreadSafe="false" %> indicates the JSP is not thread-safe, implementing the SingleThreadModel interface. This ensures only one thread executes the JSP at a time by serializing requests through the same servlet instance, making it thread-safe by preventing concurrent access.

Statement A is false - only implementations of RandomAccess (ArrayList, Vector) provide fast random access. Statement B is false - LinkedList has slower random access than ArrayList. Statement C is false - LinkedList does NOT implement RandomAccess. Statement D is false - RandomAccess is a marker interface with no methods. Thus 'None of the above' (E) is correct.

Object Spy is QTP's built-in tool specifically designed to view and retrieve object properties, methods, and identification properties. Recording captures actions, Net Spy doesn't exist in QTP, and Step Generator creates test steps.

In QTP/UFT automation, GetRoProperty ('Run-time Object Property') retrieves the actual property value from the application during test execution, while GetProperty retrieves values from the object repository. Options A, B, and D are not valid QTP methods for retrieving runtime properties.

GetCellData(Row, Column) is the correct QTP method to extract a specific cell value from a WebTable when you know the row and column numbers. The other options (CellData, TableCellData, CellDataValue) are not valid QTP methods.

RowCount is the correct property/method to get the number of rows in a QTP WebTable object. 'Rows' is not a valid property, GetRows is an ADO method, and 'None of the above' is incorrect since RowCount exists.

ActionListener is the standard interface used for event handling in Echo2 (a web framework). ActionEvent is typically an event class, not the listener interface. ApplicationInstance is a different component entirely.

Monitor.Pulse notifies a single waiting thread in the waiting queue that the locked object's state has changed. The waiting thread can then re-acquire the lock and proceed. Thread.GetData retrieves thread-local data, Thread.SpinWait is a busy-wait mechanism, and Monitor.Wait releases the lock and puts the thread in the waiting queue.