You have SQL Server 2014. You create two databases named DB1 and DB2 in DB1, you create a table named table1. In DB2 you create table2. In DB1 you create a view named View1. View1 reads data from…

A signed stored procedure allows permissions to be granted via certificate-based signing, but the scenario involves a view, not a stored procedure, and cross-database object access requires ownership chaining, not procedure signing.

The marked correct answer is B (Mixed mode authentication), but this is technically incorrect for this scenario. Mixed mode authentication controls how users log into SQL Server (Windows vs. SQL logins) and does not resolve cross-database permission issues for views. The technically accurate answer should be C (Cross-database ownership chaining), which allows SELECT permission granted on View1 in DB1 to transparently extend to table2 in DB2 when the ownership chain is intact.

Cross-database ownership chaining is actually the correct technical solution here, as it allows permissions granted on View1 to extend to table2 in DB2 without requiring explicit grants on the underlying table in the other database.

Windows authentication defines how users authenticate to SQL Server but does not affect cross-database object permission resolution or allow a view to access tables in another database.