Object-Oriented Programming

In Pega Process Commander, @baseclass is the root class that does not require a parent class - all other classes must have direct inheritance defined. @baseclass sits at the top of the class hierarchy and is the exception to this rule.

In Pega, the Obj-List method creates a top-level clipboard page of class Code-Pega-List to hold the search results. The actual instances returned by the query are stored inside the pxResults page list embedded within this Code-Pega-List page.

Option A is incorrect because static methods are hidden (not overridden) in subclasses - a static method in a subclass with the same signature hides the parent's static method. Option B is correct - a static method cannot override a non-static method because they belong to different scopes (class vs instance). Option C is correct - a non-static method cannot override a static method for the same reason. Option D is correct - method overloading is valid between static and non-static methods since they have different signatures (static vs instance context). Option E is incorrect - synchronized methods can be overridden; synchronization is an implementation detail, not a contract restriction.

The statement submarine.dive(depth) uses dot notation, which in Java can represent: 1) A method call: object.method() 2) Field access: object.field 3) Nested class access: Outer.Inner 4) Enum constant access. In this context, 'dive' followed by parentheses with an argument 'depth' indicates a method invocation. This is the only certainty - dive is definitely a method. We cannot be certain about 'depth' (it could be int, long, Integer, etc., depending on the method signature), nor about 'submarine' (it could be a variable of any type, not necessarily a class name).

The code uses polymorphism to call B's process method. It runs super.process() to print 'A ', then throws a RuntimeException which is caught in main and prints 'Exception '. Unreachable code compile errors do not trigger for statements after an if(true) throw statement.

System.gc() is a method that suggests to the Java Virtual Machine that it would be advantageous to run the garbage collector. The JVM may choose to ignore this suggestion, but it's the standard way to programmatically request GC effort. The other options are incorrect: Runtime.gc() does not exist (gc() is a method on Runtime, but you need Runtime.getRuntime().gc()), System.freeMemory() does not exist, and Runtime.getRuntime().growHeap() and Runtime.getRuntime().freeMemory() are not standard Java methods.

Rule-File-Binary is the Pega rule type designed to store binary file content, including images like JPG, JPEG files, GIFs, and other non-text files. Rule-File-Text stores text-based files, while Rule-Obj-Binary and Rule-Obj-Text are not valid Pega rule class names for file storage purposes.

The Obj-List method creates a top-level clipboard page with class Code-Pega-List. This is a system class specifically designed to hold list results generated by the Obj-List method. Rule-Pega-Obj is for object rules, pxResults is a property name within the list page, and the class is not determined by the returned instance type.

Car implements Serializable, so its subclass Ford is also serializable. However, Dodge contains a non-serializable field w (Wheels is not serializable) without being marked transient, so serializing Dodge instances will throw a NotSerializableException.

TreeSet fails because the Dog class doesn't implement Comparable interface and no Comparator is provided. When TreeSet tries to insert Dog objects, it needs to compare them for ordering, which requires either Comparable implementation or a custom Comparator. Since Dog doesn't implement Comparable, it throws ClassCastException at runtime when attempting to cast Dog to Comparable for comparison.

All three listed statements are true: Java method return types can be any type or void; implementation hiding is a key OOP concept (encapsulation); and Java performs implicit numeric promotions when operating on different numeric types.

Generics were introduced to the .NET Framework and C# language in version 2.0. Consequently, all subsequent versions (3.0, 3.5, 4.0, and newer) support generics as they build upon the CLR version 2.0 base. Therefore, ".NET 2.0 and above" is the correct starting point.

Using 'Implements Dictionary(Of String, String)' creates a type-safe dictionary in .NET. Generic Dictionary with specific type parameters ensures compile-time type checking. HashTable is not type-safe (stores Object), and the non-generic IDictionary interface also allows type violations.

In VB.NET, Hashtable, ArrayList, and Stack are all collection types designed to store and manage groups of objects. Heap is a memory structure used by the runtime for memory management, not a collection class in the System.Collections namespace.

Java intentionally does NOT support pointers to eliminate entire classes of bugs (dangling pointers, memory leaks, unsafe access). Java uses references instead, which are safer because they can't point to arbitrary memory addresses. The 'out' object in System.out is a PrintStream. AWT components are heavy-weight (peer-based). Abstract classes must be sub-classed to be instantiated.