Question

Design an exception handling strategy

You are re-creating an application that was originally built with ASP 2.0. You need to break the monolithic application into a traditional three-tier application. One of the requirements is that database errors must be displayed in the UI. Which solution will present enough information to the user so they can notify the appropriate person of a problem, but not allow the user to gain information about the design of the database?

	Let the errors pass through the business layer to the UI layer where they can be handled as specific errors and presented as appropriate in the UI.
	Add a generic database-layer exception handler to the business layer, and pass appropriate error information to the UI layer for display in a custom error page.
	Add specific database exception handlers in the business layer and log the information into the database for further review.
	Add a first chance exception handler and log the information in the error.