Java Core Classes and Threads

JSP provides 9 implicit objects: request, response, out, session, application, config, pageContext, page, and exception. These are automatically available in JSP pages without explicit declaration.

In PHP, object methods are called using the arrow operator (->), which is the standard syntax for accessing properties and methods of an object. This is distinct from languages like JavaScript or Java that use dot notation.

A method's signature consists of the method name and the data types of its parameters (in order). This uniquely identifies overloaded methods. The return type is NOT part of the signature in most languages (Java, C++). Parameter names don't matter for overloading resolution, only their types.

The Iterator pattern provides a way to access the elements of an aggregate object sequentially without exposing its underlying representation. This is the exact mechanism used by Java Collections. Patterns like Visitor, Observer, Builder, and Proxy serve entirely different architectural purposes.

In ABAP executable programs, if no event keyword is explicitly specified, any processing blocks written before the first event keyword are automatically assigned to the START-OF-SELECTION event. Thus, it acts as the default event block.

Hashtable is the only inherently synchronized option among these classes, making it thread-safe for concurrent access. HashMap and its variant LinkedHashMap are not synchronized by design, while HashSet cannot store key-value pairs. Hashtable's built-in synchronization makes it suitable for multi-threaded environments without requiring additional synchronization code.

To answer this question one needs to know about threads in programming. Threads are the smallest unit of execution that can be scheduled by an operating system. Each thread represents a separate flow of control. Threads are lightweight compared to processes, and they share memory with other threads in the same process.

Now let's go through each option and explain why it is true or false:

A. If the start() method is invoked twice on the same Thread object, an exception is thrown at runtime.

This statement is true. If the start() method is invoked twice on the same Thread object, an exception (IllegalThreadStateException) is thrown at runtime.

B. The order in which threads were started might differ from the order in which they actually run.

This statement is true. The operating system schedules threads based on its own algorithm, which might differ from the order in which the threads were started.

C. If the run() method is directly invoked on a Thread object, an exception is thrown at runtime.

This statement is false. If the run() method is directly invoked on a Thread object, the run() method will execute just like any other method. However, it will not start a new thread of execution, and any other code that is waiting for the thread to complete will not be notified.

D. If the sleep() method is invoked on a thread while executing synchronized code, the lock is not released.

This statement is true. When a thread invokes the sleep() method while executing synchronized code, the lock associated with the synchronized code is not released. This means that other threads that require the same lock will have to wait until the sleeping thread releases the lock.

Therefore, the correct answer is: C. If the run() method is directly invoked on a Thread object, an exception is thrown at runtime.

The assert keyword was introduced in Java 1.4 as a mechanism for implementing assertions - boolean expressions that test assumptions during development. The other keywords (abstract, synchronized, strictfp) were present in earlier Java versions. Assertions are typically disabled in production but can be enabled at runtime with the -ea or -enableassertions flag.

getInitParameter(String name) returns null if the requested parameter does not exist. The other methods (getInitParameterNames returns an Enumeration, getServletName returns a String, getServletContext returns a ServletContext) never return null.

The setCenter method is required immediately after creating a map using the Google Maps constructor to specify the map's center point and zoom level. Without this, the map would not know where to focus. Options A, B, and C either use incorrect method names or improper syntax.

The DataTable.Value property (or shortcut DataTable("ParameterName", dtLocalSheet)) is the standard method to retrieve or set data in a QTP/UFT DataTable during a run. Import imports external sheets, while GetCell or GetValue are not standard DataTable retrieval methods.

QTP/UFT recovery scenarios support four trigger events: Pop-up window, Object state, Test run error, and Application crash (often referred to as QTP crash). Options A and B are incomplete and include VBScript events, which are not native recovery trigger types.

HashMap is not thread-safe, but can be wrapped using Collections.synchronizedMap() to obtain a synchronized wrapper. Option B correctly shows the syntax: Map m = Collections.synchronizeMap(hashMap); - note the class is Collections (plural), not Collection. Option A is incorrect because Collection.synchronizeMap doesn't exist.

In PeopleCode, GetLevel, GetRow, GetRecord, and GetField are standard classes and methods used to traverse the buffer hierarchy. There is no Getcomponent function or method used for buffer traversal; components are accessed via different APIs.