Quiz for Custom exception classes

Q1: What is the recommended base class for creating custom exceptions in C++?

A. std::exception B. std::runtime_error C. std::logic_error D. std::bad_alloc

Q2: Which method should be overridden in a custom exception class to provide error messages?

A. what() B. handle() C. message() D. getError()

Q3: What should the what() method in a custom exception return?

A. A C-style string describing the error B. An integer error code C. A boolean D. A stack trace

Q4: Which C++ keyword is used to throw a custom exception?

A. throw B. raise C. catch D. try

Q5: How do you catch a custom exception in a try-catch block?

A. By specifying the custom exception class type B. By specifying std::exception only C. Using catch(...) only D. Using throw

Q6: Can custom exception classes have additional members?

A. Yes, for detailed error info B. No, must only inherit std::exception C. Only static members allowed D. Only private members allowed

Q7: What is the benefit of using custom exceptions?

A. More specific error handling B. Faster execution C. Less code D. Automatic logging

Q8: Which header file is required to create custom exceptions?

A. <exception> B. <iostream> C. <stdexcept> D. <string>

Q9: Is it necessary to catch custom exceptions explicitly?

A. No, but recommended B. Yes, mandatory C. No, never D. Yes, only for std::exception

Q10: What type should the destructor of a custom exception class have?

A. virtual and noexcept B. virtual and throw() C. non-virtual and noexcept D. non-virtual and throw()

Q11: How to pass error details to a custom exception?

A. Via constructor parameters B. By global variables C. Using macros D. By modifying std::exception

Q12: What is the typical return type of a custom exception constructor?

A. void B. int C. class type D. bool

Q13: Can a custom exception class be caught by catch(...)?

A. Yes B. No C. Only if it inherits std::exception D. Only if it is a standard exception

Q14: What should you avoid in custom exception classes?

A. Throwing exceptions from destructor B. Inheriting std::exception C. Overriding what() D. Using constructors

Q15: Can custom exceptions have member functions besides what()?

A. Yes, for extra functionality B. No, only what() allowed C. Only static functions allowed D. Only inline functions allowed

Q16: Is multiple inheritance allowed for custom exceptions?

A. Yes B. No C. Only single inheritance allowed D. Only virtual inheritance allowed

Q17: Why override the what() method in custom exceptions?

A. To provide a specific error message B. To prevent catching exceptions C. To improve performance D. To hide the error

Q18: What type does the what() method return?

A. const char* B. std::string C. int D. void

Q19: Can custom exceptions be used with the noexcept specifier?

A. Yes, but rarely B. No, never C. Only for standard exceptions D. Only for runtime_error

Q20: What is a common practice for storing error messages in custom exceptions?

A. Using a std::string member B. Using a static char array C. Using int error codes D. Using macros