Java Core Classes and Threads

onCreate() is the first method called when an activity is created. It's where you initialize your activity, set up the UI with setContentView(), bind data, and create any objects or resources the activity will need. This method is called once per activity instance, unlike onStart() or onResume() which can be called multiple times.

In Android activity lifecycle, onStart() indicates when the activity becomes visible to the user, and onStop() is called when it's no longer visible. Resources needed to display the activity to the user (such as views and UI elements) should be initialized in onStart() and released in onStop(). onResume() and onPause() are for foreground/interactive state, not visibility.

The onCreate() method receives a savedInstanceState Bundle parameter that contains the activity's previously saved state. This state is captured in onSaveInstanceState() when the activity may be killed by the system. onResume() and onStart() do not receive this Bundle parameter.

QTP handles exceptions using Recovery Scenarios, which allow you to define trigger events, recovery operations, and post-recovery test run options. This is QTP's built-in mechanism for handling unexpected events, errors, or application crashes during test execution. Option C (Exception handler) is a general programming term but not QTP-specific.

The waitproperty method is used for synchronization in QTP. It pauses test execution until a specified object property achieves a certain value or times out. This is the preferred synchronization method over static waits like wait() or sleep() because it waits dynamically based on application state rather than fixed time intervals.

All the above is correct because different methods are used in different contexts to retrieve text values. GetROProperty retrieves runtime object properties including text, GetVisibleText captures visible text on screen, and GetText is used for retrieving text from specific objects. The appropriate method depends on the testing scenario.

The onunload event is triggered when the document is being unloaded from the browser. This includes closing the browser window, reloading the current page, or navigating to a new webpage. Since all these actions trigger the unload sequence, 'All Of the Above' is the correct choice.

onreadystatechange is an event handler property of the XMLHttpRequest object, not a method. It's a property that you assign a function to (xhr.onreadystatechange = function(){}), not a method that you call. Methods are invoked with parentheses, properties are assigned values.

Android's Activity lifecycle includes standard callback methods such as onCreate, onStart, onResume, and onDestroy. There is no void onExit method in Java's Android Activity lifecycle class, making it an invalid method name, whereas the others are all standard, valid callbacks.

getContentResolver() is the correct method to obtain a ContentResolver instance within an Activity or other application component. It takes no parameters and returns a ContentResolver object that can interact with content providers. The other options incorrectly pass parameters (cr, content, void, context) to this method.

In Android, the MediaPlayer class uses the start() method to begin or resume playback of audio/video streams. The other listed options like initialize, do, run, or process are not standard methods of the Android MediaPlayer API for initiating media playback.

In Objective-C, strings are declared using NSString class with the @ symbol before the string literal to indicate it's an Objective-C string object (not a C string). The correct syntax is NSString *str = @"cocoa"; where the asterisk denotes a pointer to the object, and the @ symbol creates an NSString object from the literal.

The standard mouse event methods in Cocoa are mouseUp, mouseDown, and mouseDragged. There is no 'mouseClick' method in the standard mouse event protocol - click events are typically derived from up/down combinations.