Object-Oriented Programming

The statement 'Picklist values change at runtime' is NOT true for static picklists - static picklists have fixed values that are defined at design time and do not change during application execution. This is what distinguishes them from dynamic picklists. Options B, C, and D are true characteristics of static picklists (they can be bounded/unbounded, derive from List of Values, and are based on Picklist Generic Business Component).

Java automatically imports java.lang, which contains fundamental classes like String, Object, System, Math, and wrapper classes. All other packages (java.io, java.util, etc.) must be explicitly imported.

In OOP terminology, 'object' is a broader concept - anything with identity, state, and behavior (including anonymous or prototype-based objects). 'Instance' specifically means an object created from a class definition using instantiation. An object may not have a formal class (as in prototype-based languages), but an instance must originate from a class.

Protected members are accessible within the same package (to both classes and interfaces) and to subclasses in other packages via inheritance. Option C is wrong because it suggests same-class access isn't required.

QuickTest Professional organizes test objects into classes based on their type and behavior (e.g., Window, WebEdit, Button). This object-oriented classification allows QTP to identify and interact with similar objects consistently across different applications. The class hierarchy is fundamental to QTP's object recognition model.

In QuickTest Professional, the identifying characteristics of an object are called properties. These include attributes like name, class, value, and various other properties that help QTP uniquely identify and interact with the object during test execution. Properties distinguish one object from another in the application.

Virtual constructors are impossible in C++ because constructing an object requires knowing its exact type at compile-time for memory allocation. Virtual dispatch works through vtables on already-constructed objects, but construction must happen before the object (and vtable) exists. Therefore, constructors cannot be virtual.

The delete[] operator is required for arrays because it invokes the destructor for every element in the array. Using plain delete only invokes the destructor for the first element (myObj) and not the remaining 99 objects, causing resource leaks. The pairing must be new[] with delete[] and new with delete.

In UML class diagrams, classes can be grouped into packages to organize the model. Object diagram names are underlined (not italicized), package dependencies do not always force changes, and class/object diagrams are not fully interchangeable.

Polymorphism's key advantage is replacing conditional logic (case/switch statements and if-else chains) with dynamic dispatch through virtual functions. Instead of checking type and executing corresponding code, polymorphism lets each subclass implement its own behavior, invoked through a common interface. This reduces conditional complexity.

Java does not support multiple inheritance of classes (to avoid the diamond problem) nor does it support user-defined operator overloading. Therefore, this pair is not supported in Java.

In Java, Map is a separate interface from Collection. Map does NOT extend Collection - they are distinct hierarchies. Collection is for groups of objects, Map is for key-value pairs.