What happens if you declare an abstract class as final?

• A. It is valid and compiles
• B. It leads to a runtime error
• C. It results in a compile-time error
• D. It inherits from Object class automatically

Answer: (C)

Declaring an abstract class as final results in a compile-time error because the two keywords represent conflicting concepts in Java. An abstract class is designed to be a base class that cannot be instantiated on its own but is meant to be subclassed. It can include abstract methods that must be implemented by any non-abstract subclass. On the other hand, a final class cannot be subclassed; it is essentially the end of the inheritance chain for that class.

When you combine these two concepts, Java's compiler recognizes that an abstract class inherently needs to allow for extension (subclassing) to fulfill its purpose. Declaring it as final contradicts the intent of the abstract class. Attempting to compile this code will produce a compile-time error to prevent this contradiction from occurring.

The other choices do not represent valid outcomes in this scenario. There's no runtime error involved since the code never successfully compiles. Additionally, while all classes in Java inherit from the Object class by default, this inheritance is not an effect of being declared as final or abstract but rather a fundamental aspect of every class in Java. Therefore, the assertion regarding inheritance does not apply here in the context of the primary question about the final and abstract modifiers.