Object-Oriented Programming

In Java, the base class must be declared before the derived class, or at least be available to the compiler. The compiler needs to know the base class's structure to process inheritance syntax and verify that methods and fields used in the derived class are valid.

In Java, Map is an interface that defines the contract for key-value mappings, while HashMap is a specific class that implements the Map interface using a hash table.

The code compiles successfully. SubclassY extends SuperclassX (protected method, package-private field) from packageX.packageY - subclasses can access protected members. Line 5 is valid (polymorphism: SubclassY IS-A SuperclassX). Lines 9-11 access protected method and package-private field through a SubclassY reference, which is valid within the same package hierarchy. The code compiles and runs without errors, so 'None of these' (D) is correct.

Interface methods in Java are implicitly public and abstract. They cannot be private (no implementation to hide) or protected (interfaces define public contracts). Abstract is explicit but allowed since it's implicit anyway.

Java always passes references by value - the reference itself is copied, but both copies point to the same object. This means modifications to the object are visible to the caller, but reassigning the reference is not. The 'pass by value' terminology refers to the reference copy, not the object.

The question text is missing ('1.)'), but based on the options about ApplicationContext implementations, FileSystemXmlApplicationContext (option C) is indeed a valid Spring ApplicationContext implementation that loads configuration from the file system.

TransactionalTestExecutionListener is the TestContext framework class responsible for managing transactions in tests - it handles transaction creation, rollback for test isolation, and cleanup.

CObject provides serialization support through the Serialize method, runtime class information via DECLARE_DYNAMIC/IMPLEMENT_DYNAMIC macros, and diagnostic dumping through Dump. Platform independence is not a feature - CObject is part of Windows-specific MFC.

An MFC application must have exactly one unique object of a class derived from CWinApp. Having multiple CWinApp objects in a single application is not allowed.

The method Print() is an instance method, not a static method. Therefore, it must be called on an instance of the class (f.Print()), not on the class name itself (Foo.Print()).

Constructors are special member functions with the same name as their class. The default constructor initializes primitive fields to zero/null. If no constructor is written, the compiler provides a default constructor.