Which statement about upcasting is true?

Which statement about upcasting is true?

• A. It is explicit and hazardous.
• B. It is implicit and always safe.
• C. It requires a cast in all cases.
• D. It changes the runtime type of the object.

Answer: (D)

Upcasting is about treating a derived object as an instance of its base class. This view is usually implicit, so you don’t need an explicit cast. The object itself doesn’t change; it’s still the same instance with the same runtime type (the actual derived class). What changes is what members you’re allowed to access through the reference—the code now sees the base class interface, though overridden methods will still execute based on the actual object. So the key idea is that upcasting enables polymorphism by shifting the reference type to a base class, without altering the object’s true type. It’s generally safe and does not require a cast, unlike downcasting, which can require an explicit cast to recover the derived type.

Upcasting is about treating a derived object as an instance of its base class. This view is usually implicit, so you don’t need an explicit cast. The object itself doesn’t change; it’s still the same instance with the same runtime type (the actual derived class). What changes is what members you’re allowed to access through the reference—the code now sees the base class interface, though overridden methods will still execute based on the actual object.

So the key idea is that upcasting enables polymorphism by shifting the reference type to a base class, without altering the object’s true type. It’s generally safe and does not require a cast, unlike downcasting, which can require an explicit cast to recover the derived type.