Note: This question is part of a series of questions that present the same scenario. Each question
in the series contains a unique solution that might meet the stated goals. Some question sets
might have more than one correct solution, while others might not have a correct solution.
After you answer a question in this section, you will NOT be able to return to it. As a result, these
questions will not appear in the review screen.
Your company has several Microsoft SQL Server instances. Each instance hosts many databases.
You observe I/O corruption on some of the instances.
You need to perform the following actions:
Identify databases where the PAGE VERIFY option is not set.

Configure full page protection for the identified databases.

Solution: You run the following Transact-SQL statement:

For each database that you identify, you run the following Transact-SQL statement:

Does the solution meet the goal?
Correct Answer: A
Explanation/Reference:
Explanation:
We should set the PAGE_VERIFY Database Option to CHECKSUM.
Note:
CHECKSUM is the Way to Go For Page Verify
This isn't about security- this is about you knowing if changes to SQL Server's files are happening outside
of its control, whether by corruption or any other means.
It's very easy to check if you're using CHECKSUM. Take a look at your settings today, and make a plan to
move to checksum for any databases which need it!
SELECT NAME
FROM sys.databases
WHERE page_verify_option_desc <> 'CHECKSUM'
References:
https://docs.microsoft.com/en-us/sql/relational-databases/policy-based-management/set-the-page-verify-
database-option-to-checksum?view=sql-server-2017