Best Recommendation for Inconsistent Relational Database

C.

When an IS auditor finds inconsistencies in a relational database, the best recommendation depends on the specific nature of the inconsistencies. However, given the options provided, the BEST recommendation is to normalize the database (Option C).

Normalization is the process of organizing data in a database to reduce redundancy and improve data integrity. It involves breaking down larger tables into smaller ones and establishing relationships between them. Normalization helps to eliminate inconsistencies, ensure data accuracy and integrity, and improve database performance.

Performing data modeling (Option A) is a valuable exercise for designing a new database or enhancing an existing one. However, it may not address the specific inconsistencies that the auditor has found.

Re-indexing the database (Option B) is a process of restructuring the indexes on database tables. This can help to optimize database performance but may not necessarily address inconsistencies in the data.

Implementing edit checks (Option D) is another way to prevent inconsistencies in the data. Edit checks are programmed validations that ensure data entered into the database conforms to specific criteria, and they can help prevent data inconsistencies. However, this recommendation may not be the best first step when inconsistencies have already been found.

Therefore, the BEST recommendation for an IS auditor who discovers inconsistencies in a relational database is to normalize the database (Option C) to improve data integrity, accuracy, and performance.