What approach should the DBA take to verify database code integrity?

• A. Review database logs
• B. Compare existing code with a copy
• C. Run a consistency check
• D. Check user permissions

Answer: (B)

To verify database code integrity, comparing existing code with a copy is an effective approach. This process involves taking the current version of the database code and meticulously checking it against a known, trusted version or a backup. Through this comparison, the database administrator (DBA) can identify any unauthorized changes, discrepancies, or corruption that may have occurred over time. This method is particularly useful for ensuring that the code matches expected standards and has not been altered in any unintended ways.

The other options serve different purposes that may contribute to maintaining overall database health but don't directly verify the integrity of the code itself. Reviewing database logs provides valuable information about operations performed on the database but does not specifically check for code differences. Running a consistency check can help ensure that data is structured correctly and free from corruption, yet it does not analyze the actual code for integrity. Checking user permissions is crucial for security and access control, but it does not evaluate the integrity of the database code. Hence, comparing existing code with a copy stands out as the most direct and effective method for verifying code integrity in the database context.