You administer a Microsoft SQL Server 2012 database that has multiple tables in the Sales schema. Some users must be prevented from deleting records in any of the tables in the Sales schema. You…

Creating a custom database role allows grouping users who require the same permissions, and then denying the DELETE permission on the entire 'Sales' schema to this role. This efficiently applies the restriction to all current and future tables within that schema for all role members, minimizing administrative overhead.

Including a schema as an owned schema for the `db_denydatawriter` role is not the correct mechanism to selectively deny only DELETE permissions, as `db_denydatawriter` broadly denies INSERT, UPDATE, and DELETE permissions on all user tables in the database.

Denying Delete permissions on each individual table for each individual user is highly inefficient and administratively intensive, failing to meet the requirement for minimum administrative effort.

This choice is a duplicate of Choice A, which describes the correct approach to managing permissions efficiently using a custom database role.