Final answer:
According to the Liskov Substitution Principle, child implementations should not throw broader or new checked exceptions compared to the parent implementation. Child classes may throw the same or narrower exceptions, ensuring substitutability.
Step-by-step explanation:
According to the Liskov Substitution Principle (LSP), subtypes must be substitutable for their base types without affecting the correctness of the program. In the context of exceptions, this means that methods of the child class should not throw new or broader checked exceptions than the base class. Child classes may throw the same exceptions or they can throw narrower (subclass) exceptions, but they must not throw broader or new checked exceptions because this would violate the LSP. The principle aims to ensure that a user of the base class can also use its subtypes interchangeably without knowing the differences in the implementations.
Therefore, the answer to the student's question is (a) Yes, but with an emphasis that the child implementation must not throw broader or new checked exceptions compared to those declared by the parent implementation.